Skip to main content

Privacy

The owner publishes privacy notices to the organisation's drivers: Privacy → Notices.

  • Publish a notice: what is processed and why, and its legal basis. A notice that rests on consent asks; one that rests on a legal obligation (for example driving hours) informs.
  • Sensitive data, such as biometric data, needs consent: another basis is refused.
  • New version: a material change, such as adding audio to a cabin camera, makes earlier consent stop counting. The driver sees the change and decides again.
  • Retire: a retired notice allows processing for no one.

The driver decides in the driver app: Account → Privacy choices → a notice → I agree, No, thanks, or Withdraw my consent, as easily as agreeing. A notice on a legal obligation is acknowledged; it cannot be refused.

Register: each driver's standing. A driver's record → verified: each decision is sealed with the one before and with the exact text the driver was shown. A decision cannot be rewritten.

This follows GDPR Art. 7 and Saudi Arabia's PDPL.

What each feature shares​

FeatureWhat is kept back
Phone trackingthe phone reports only while the driver is on a job, and only with consent
Live video and footageviewers and mechanics see no cameras; every view is logged with who watched and for how long
Insurer programmesthe score only, and only for drivers who agreed; no trips, places or events
Leavethe kind of leave (sick is health information) only to people with payroll access
Customer tracking linksa consignee sees only their own stop's address
Shared secure tripsthe truck's position rounded to about 100 m; no alarms, people or vehicles
Audit logthe names of the fields changed, never their values
Proof-of-delivery signaturesstored encrypted

Between organisations​

No organisation sees another's records: not its vehicles, positions, drivers, alerts, documents or reports. Partners see only the customers under them. Freight marketplace partners see each other's invoicing details only on the invoices between them.