Security
Trust is the whole product, so the security model is public. Here is how the history stays honest.
Last updated 1 July 2026
Tamper evidence by design
Every stamp is hashed with SHA-256 together with the hash of the previous stamp, forming a per-vehicle chain anchored to the VIN. Stamps live in insert-only tables — the application role has no UPDATE or DELETE on them. Changing any historical record breaks every fingerprint after it, and the public verifier recomputes the whole chain from scratch on every check. Daily jobs sign and archive all chain heads as a transparency digest.
Authentication
No passwords to steal: sign-in uses single-use email codes. Sessions use short-lived (15-minute) access tokens with rotating refresh tokens that are revoked on sign-out. Admin access is separated behind its own audience claim.
Encryption & residency
TLS 1.2+ for everything in transit; AES-256 at rest for databases, backups and document storage. All production infrastructure runs in AWS eu-west-2 (London) for UK data residency. Uploaded documents are virus-scanned and EXIF-stripped before they are served.
Abuse controls
Public endpoints are aggressively rate-limited (plate lookups: 10/min per IP). Lookup and share-view patterns are monitored with hashed IPs, and share links can be scoped, expired, view-capped and revoked instantly by the owner.
Responsible disclosure
Found something? Please email security@service-book.co.uk with steps to reproduce. We acknowledge within two working days, we won’t take legal action against good-faith research, and we credit reporters who want it.