01Parties and scope
This agreement is between the customer (the controller) and Truvio (the processor). It applies to the personal data the customer puts into Truvio, or has Truvio collect, and forms part of the Terms of Service. It applies automatically while the customer uses Truvio; no separate signature is needed.
02What we process, and why
- Purpose. Providing Truvio to the customer: planning and running transport, fleet positions, documents, the driver app, invoicing and support.
- Duration. For as long as the customer uses Truvio, and until the data is deleted or returned after that.
- People concerned. The customer's users and drivers, the customer's own customers, subcontractors and their contacts, and people named or signing on transport documents.
- Kinds of data. Names and contact details; driver licences, qualifications, card numbers and their expiry dates; vehicle positions and driving times; scans and photos of documents, including signatures; messages between dispatch and drivers; invoicing details.
03Our obligations
- Instructions. We process the data only on the customer's documented instructions, which are this agreement and the customer's use of Truvio, unless the law requires otherwise, in which case we tell the customer first where the law allows.
- Confidentiality. Everyone who can access the data is bound to keep it confidential.
- Security. We keep the measures in the section on security below, and keep them up to date.
- Requests from people. We help the customer answer people who exercise their data protection rights, mainly through the features of Truvio itself.
- Breaches. We tell the customer without undue delay, and within 48 hours of becoming aware, of a personal data breach affecting its data, with what we know and what we are doing about it.
- Assessments. We help the customer with data protection impact assessments and consultations with authorities where they concern Truvio.
- Evidence. We make available the information needed to show we meet this agreement, and allow audits by the customer or its auditor on reasonable notice, at most once a year unless a breach gives reason for more.
04Sub-processors
The customer authorises us to use the sub-processors listed in our Privacy Policy. Each is bound by a written contract with data protection obligations no weaker than these, and we remain responsible for them.
We tell the customer at least 30 days before adding or replacing a sub-processor. The customer may object on reasonable data protection grounds; if we cannot meet the objection, the customer may end the affected part of the service.
05Transfers outside Europe
Where a sub-processor processes data outside the European Economic Area, the transfer is covered by the EU-US Data Privacy Framework where the sub-processor is certified under it, and otherwise by the European Commission’s Standard Contractual Clauses.
06Security measures
- Encryption of all data in transit.
- Encryption of stored credentials for connected services.
- Passwords stored only as one-way hashes; the sign-in renewal key replaced on every use and revoked at sign-out.
- Role-based access inside each customer account, and a record of changes made in it.
- Each customer's data kept separate from every other customer's.
- Access to production systems limited to the staff who need it.
07When the service ends
Before the account closes the customer can export its data. After it closes, we delete the customer’s personal data within 90 days, unless the law requires us to keep part of it, which we then keep only for that purpose.
08Liability and precedence
Liability under this agreement follows the Terms of Service. Where this agreement and the Terms differ on the protection of personal data, this agreement prevails.
09A signed copy
If your company needs this agreement signed for its records, write to us and we send you a copy to sign.