Pilot baseline
Privacy notice
tracedx handles workshop, vehicle, evidence, diagnostic, and account data. This notice explains the pilot data posture in plain language.
Data handled by tracedx
tracedx can store account email, workspace name, country, vehicle identifiers, vehicle details, case notes, photos, PDFs, manual evidence, extracted observations, assessments, test results, report snapshots, outcomes, feedback, and support audit events.
Vehicle registrations, VINs, customer-linked vehicle histories, photos, reports, and workshop notes are treated as sensitive operational data.
Why data is used
Data is used to provide the diagnostic case workspace, preserve evidence provenance, generate assessment/report records, operate support, improve pilot reliability, and investigate safety or security issues.
Feedback is used to understand pilot friction and usefulness. Anonymised learning contribution remains opt-in.
Storage and access
Workspace data is scoped by workspace membership. Raw evidence files are stored in private Supabase Storage paths, not public buckets.
Support access is restricted by a server-side allowlist and uses aggregate metadata for pilot support unless a specific support request requires deeper investigation.
AI and providers
Current Assessment generation may send structured evidence snapshots and case context to approved server-side AI providers. Provider keys are not exposed in frontend code.
AI outputs are stored with schema, version, provider/model, and provenance metadata where the implemented workflow supports it.
Retention and rights
Pilot retention periods are still being finalised. You can request export, correction, restriction, or deletion through the pilot support route.
For privacy or data-rights requests, contact the support contact supplied with your pilot invitation.