Data retention is the first thing auditors ask about. The default answer — 'we keep everything forever' — is wrong. Ridezora ships a configurable retention policy: passenger trip records default to 36 months, with corporate contracts often requiring longer. Anything beyond the retention window is pseudonymised automatically.
Passenger name display in the driver app is the second question. Best practice is to show the first name and last-name initial to the driver — enough for a kerbside greeting, not enough to identify the passenger to a bystander looking over the driver's shoulder.
Dashcams are the third. They generate personal data — passenger faces, sometimes audio. If the fleet uses them, the operator is a data controller for that footage. Ridezora doesn't ship a dashcam; if you do, the retention and subject-access-request pathway needs to include it explicitly.
Subject access requests are the fourth. A passenger has the right to ask what you hold on them. Ridezora provides a one-click export per passenger identifier, in a structured JSON format that satisfies the ICO's expectations.
The DPA — the data processing agreement — is the fifth. Every corporate contract needs one. Ridezora ships a standard DPA covering the operator-as-controller, Ridezora-as-processor relationship, ready to counter-sign.
The sixth is honest breach reporting: 72 hours to the ICO, no exceptions. The audit trail across bookings, allocations and payments makes the timeline reconstructable — which is what a regulator wants to see.