When the Client Wants the Data

General orientation, not legal advice.

In contracted operations the vehicle, the driver, the employer and the customer are frequently four different parties, and the data flows between them by default.

The arrangements

A client mandating camera systems on vehicles serving their contract, which is increasingly common in urban logistics.

A client requesting footage after an incident at their site.

An agency worker driving a client's vehicle, where the monitoring belongs to the client and the employment belongs to the agency.

And a client wanting behaviour reports on named drivers, which is the request to think carefully about.

Whose data

The driver's, whoever owns the equipment.

Which means a transfer between organisations needs a basis, a stated purpose and a record — and the driver needs to know it happens.

Agree it in the commercial contract before an incident, because during one the temptation is to send everything.

And tell drivers at induction that their data may go to the client, if it may.

What to agree in the contract

What is shared routinely — ideally aggregate, not individual.

What is shared after an incident: the incident window, scoped, not a history.

Who at the client can see it, and whether they log access.

Retention at their end, and deletion on contract termination.

And whether the client may act on it, which they generally should not: a client cannot discipline someone else's employee, and attempting it creates a status question.

The request to decline

Named driver behaviour reports on a routine basis.

Because the client's legitimate interest is the safety of the operation, which aggregate reporting serves, and individual scores serve only supervision that is not theirs to conduct.

Offer instead: contract-level safety metrics, incident reports, and evidence that a programme exists.

Client-mandated cab cameras

A common condition in some urban contracts.

The obligation to justify it still sits with the employer, not the client — "our customer requires it" is a reason but not an assessment.

Do the proportionality analysis anyway, and negotiate configuration: triggered rather than continuous, no live view, retention in days.

The measure

Data transfers to clients, logged, with the basis recorded.

Requests declined and why.

And whether drivers were told, which is the part that is routinely missed and the one that surfaces in a complaint.

Agree it in the contract

Before an incident rather than during one.

What is shared routinely, what after an incident, who may see it, and for how long they hold it.

Because the temptation during an incident is to send everything, and a transfer made in that moment has no basis recorded.

And tell drivers at induction that their data may reach the client, if it may.

A practical configuration prompt

During configuration, use professional time records for client fleets to prompt questions about purpose, ownership and output. Treat the page as a starting point and document each assumption.

Independent reference

For a thematic point of reference, see the Federal Motor Carrier Safety Administration. Use the current material as an outside check before turning the principle into a system rule.