What TrueSyt stores, how personal data is protected, and how intelligence sharing works.
TrueSyt stores the compliance records you enter, but personal data (names, phone numbers, emails, vehicle registrations) is redacted before any AI processing. Aggregated, anonymised intelligence sharing is off by default and must be explicitly enabled per organisation. Vehicle registrations and personal data are never forwarded to the AI training pipeline without your organisation's opt-in.
TrueSyt stores the compliance data your organisation enters: compliance checks and their completion logs, corrective actions, employee records and certifications, asset registers, inspection templates, and — where your plan includes it — fleet estimation and training records. Each record is scoped to the site and organisation it belongs to.
Some fields contain personal data (PII): employee names, contact details, inspector names, and — in the fleet estimation and training modules — vehicle registration plates, VINs, customer names, and insurance or claim numbers. These fields are flagged as PII in our data model and are handled as described below.
Before any data is sent to an AI model or external processing pipeline, TrueSyt applies a redaction layer that scrubs personally identifiable information — including names, phone numbers, emails, addresses, vehicle registrations, VINs, policy numbers, and claim numbers. Annotations and identifying marks on uploaded images are also detected and removed.
Each processed record carries a redaction audit trail recording what was detected, what was withheld, and the confidence of the redaction. Records below the redaction confidence threshold are quarantined for manual review rather than forwarded.
TrueSyt's intelligence layer aggregates anonymised, PII-scrubbed compliance data (for example, inspection pass/fail rates and defect trends) to produce market intelligence. Participation in this aggregation is strictly opt-in and is off by default for every organisation.
An organisation admin can enable intelligence sharing from the organisation settings. When enabled, only the agreed scope (e.g. aggregated inspection statistics) is shared, and only after PII has been removed. The opt-in record — who enabled it and when — is stamped on the organisation record.
Vehicle registrations and personal data are never forwarded to the AI training pipeline without the organisation's explicit opt-in. Even with opt-in enabled, only PII-scrubbed, aggregated data reaches the intelligence layer — never raw personal data or registration plates.
Your compliance records are retained for as long as your organisation is active on the platform. You may export or request deletion of your data at any time by contacting the platform admin. An immutable audit trail of record changes is retained for accountability purposes even after individual records are amended.
TrueSyt uses site-scoped tenancy. Each user is tied to one site, and records are scoped so that users can only access data belonging to their own organisation's sites. Platform administrators can access all organisations for support and provisioning purposes.
We may update this notice as our data practices evolve. Material changes will be reflected by a new version label. Continued use after changes take effect constitutes acceptance of the revised notice.