How TraceID is hosted and protected
Your inspection records and product data sit in the TraceID Hub, hosted in AWS London. This page sets out where the data lives, who can reach it, what is recorded, and who else handles it.
Hosting and encryption
The Hub runs on Amazon Web Services in the London region (eu-west-2). Your records, files and the database that holds them are stored in the UK.
Hosted in AWS London
The application runs in Docker containers on Amazon EC2. Data is held in Amazon RDS for MySQL, files and photos in Amazon S3, and email from the Hub is sent through Amazon SES.
Encrypted in transit and at rest
Every connection to the Hub uses TLS. The database in RDS and the files in S3 are encrypted at rest.
Short-lived document links
Documents are shared through pre-signed links that expire after a short time, rather than sitting at a permanent public address.
Sign-in and access
Accounts are set up by us and by your own administrators. There is no public sign-up.
Three ways to sign in
Email and password, with the account locked after repeated failed attempts. A six-digit code sent by email, with no password at all. Or single sign-on with Google or Microsoft Entra ID.
Four role tiers
Super Admin, Client Admin, Client Manager and Client User. Your administrators invite people and choose each person's role.
Sessions that end
Session length is set per user. People are warned before an idle session times out, so an unattended iPad does not stay signed in.
An insert-only audit log
Every action in the Hub is written to an audit log. The application only ever adds entries; it has no way to edit or delete them.
Each entry records who acted, what they did and when, with the IP address, the browser's user agent and a request ID. When a question comes up months later, the answer is in the log rather than in someone's memory.
Protections and change control
Layered protection
Traffic to the Hub is routed through Cloudflare. The application sets security headers with Helmet, including a strict Content Security Policy and HSTS with preload. Sessions are held server-side in Redis.
Assessed in 2025
The Hub went through a security assessment in 2025, with all Critical and High findings fixed.
Controlled releases
Automated checks must pass before any change reaches production. Releases roll out with zero downtime, so inspectors are not interrupted by an update.
Sub-processors
These are the companies that process data on our behalf.
| Sub-processor | What it does for us |
|---|---|
| Amazon Web Services (AWS) | Hosts the Hub in London (eu-west-2): application servers, database, file storage and email sent from the Hub. |
| Cloudflare | Carries all traffic to the Hub before it reaches AWS. Hosts this website and runs the bot check on its contact form. |
| Resend | Delivers messages sent through this website's contact form to us. |
| Umami | Counts visits to this website. Its analytics are cookieless and report only aggregated figures. |
Data Processing Agreement
When you use the Hub, you are the controller of your data and we process it for you. A Data Processing Agreement covering that is available on request.
For defence suppliers
Supports the controls a defence supplier needs under DEFCON 658 and DEF STAN 05-138: role-based access, single sign-on, an insert-only audit log, encrypted storage in the UK, and controlled revisions with a recorded reason.
Questions from your IT or quality team?
Book a demo and bring them along. We will walk through hosting, sign-in and the audit log on the real system.