Security brief, October 2026
How your data moves
How your data moves
through The Blue Feet.
Where case data travels, where it is stored, who else receives any of it, and what we never do with it. Written for workshop, dealer and OEM security reviewers.
Isolation
One branch, one wall
No customer can read another customer's cases, files or vehicles.
Encryption
In transit and at rest
HTTPS for every connection; database and files encrypted.
AI
No training on your data
Each diagnosis sees only its own case.
Sharing
Off unless you opt in
Only anonymised patterns, never cases, customers or VINs.
The flow
Every arrow carries only what that step needs.
The AI step sees the vehicle, complaint, findings and files of the case being analysed, and nothing from any other case or customer.
- Workshop staffbrowser, phone
sign-in, two-step optionHTTPS - Secure edgefirewall, DDoS shield
certified hostHTTPS - The Blue Feet approle-based permissions
every query scoped to your branch
signed audit log - Stored, encrypteddatabase + file storage
separated per branch
region: Western Europe - AI processingthis case only, no training
- VIN decodingthe VIN only
- Paymentscard data never reaches us
- Email and WhatsAppmessages you choose to send
- Shared learning pooloff unless a manager opts in
anonymised patterns only
Controls at every stage
Moving, stored, analysed.
Moving
In transit
- HTTPS only; plain HTTP is redirected.
- Every transfer to a provider is encrypted.
- Customer pages (sign-off, questions) use signed links that expire.
Stored
At rest
- Database and files encrypted by our certified host.
- Each branch's data kept separate; no cross-customer reads.
- Passwords stored only as salted hashes.
- Keys and secrets never in code or the browser.
Analysed
In processing
- Each diagnosis sees only its own case.
- AI providers work under terms that forbid training on your data.
- Uploaded files checked by content; they can never run as code.
- Audio transcribed inside our hosting platform.
Who sees it
Access and audit
- Role-based permissions on every action, set by your managers.
- Two-step sign-in for every user; branch managers can make it mandatory for all staff (from our next release).
- Sensitive actions in a tamper-evident, signed audit trail.
- Support access recorded, start and stop.
Kept and erased
Lifecycle
- We collect what the diagnosis needs.
- Deleted cases go to a bin, then are permanently erased.
- A legal hold can pause erasure when required.
- Release backups encrypted and kept for 7 days only.
Built in
Development
- Every change tested automatically before release.
- Automated dependency vulnerability checks.
- Releases staged first, promoted by approval.
- An automated attack walk runs on staging before release.
Who receives what
Each provider, the least it needs.
The full list of providers, with their published terms, is available to your security team on request.
| Recipient | Receives | Never receives | Basis |
|---|---|---|---|
| Hosting | All platform data, encrypted at rest | Anything outside our account | Provider certified to SOC 2 and ISO 27001 |
| AI processing providers | Vehicle, complaint, findings and files of the case being analysed | Other cases, other customers, card data | Commercial terms with no training on your data; some keep requests up to about 30 days for abuse checks |
| VIN decoding | The VIN | Complaint, customer, files | Published privacy terms, GDPR-covered |
| Payments | Billing details entered on the payment page | Card numbers never touch our servers | PCI-DSS Level 1 |
| Email and WhatsApp | A recipient and the message you send | Case data beyond that message | Delivery only |
| Shared learning pool | Anonymised diagnostic patterns, only if your manager opts in | Raw cases, customer details, VINs | Opt-in, reversible, every change logged |
Our commitmentsWhat we never do.
What we never do.
What we build on.
What we never do
- Use your data to train AI models.
- Sell your data or share it with other customers.
- Put one customer's case into another customer's analysis.
- Move data into the shared pool without your opt-in.
GDPR principles we build on
- Data minimisation: only what the diagnosis needs.
- Purpose limitation: your data serves your cases.
- Security by design: isolation, encryption, audit.
- Erasure, and transparency about who processes what.
- Documented: records of processing, retention schedule, breach response and data-request procedures.
Transparency, prioritised by partner needs
On our roadmap.
- Single sign-on (SSO) for enterprise customers
- Independent penetration test, report shared under NDA
- Formal Data Processing Agreement for every customer
- SOC 2 or ISO 27001; TISAX for OEM programmes
- In-region data storage option for the GCC
- Written zero-retention terms with AI providers
Questions from your security team
Write to our security team
Walk through any part of this brief.
We are glad to walk through any part of this brief, answer a questionnaire, or review a specific requirement for your programme.