Where the Vehicle Ends and the Person Begins

General orientation, not legal advice.

A box wired into a van reads engine temperature and also reads where a named person was at nine on Sunday evening. Both come from the same device.

What is asset data

Engine parameters, fault codes, fuel level, battery health, tyre pressure.

Odometer and engine hours.

These describe a machine. Where the vehicle is not attributable to an individual, they carry little personal data weight.

What is personal data

Position, whenever the vehicle is attributable to a person — which it is if it is assigned, or if a rota says who was driving.

Anything outside working hours, which for a take-home vehicle includes a home address.

Driving behaviour metrics, which describe conduct.

The same device, a different legal analysis, and the difference is what the deployment is configured to keep.

Why the distinction is worth defending

An asset-focused deployment needs no consultation, no impact assessment in most cases, and no policy about monitoring.

Adding position history of identified drivers changes all three.

Which means the cheapest deployment legally is also the one that delivers the maintenance and cost value, and that coincidence is worth exploiting deliberately.

Keeping them separate in practice

Configure the retention separately: engine data for years, position for days.

Restrict access separately: the workshop needs fault codes and never needs position history.

And decide explicitly whether position is stored at all beyond what dispatch needs today.

A fleet that keeps six months of position because it was the default has acquired an obligation it did not need.

When you do need position

Dispatch, proof of attendance, safety of people working alone, stolen vehicle recovery.

Each is legitimate and each has its own analysis, which is a different subject from this collection.

The point is that they are separate decisions, taken deliberately, rather than a consequence of buying a telematics system.

What to say to drivers

What the device reads about the vehicle.

Whether it reads position, and when.

What happens to it and for how long.

And if the answer is genuinely that position is not retained, say it — it is checkable, it is unusual, and it changes how the whole deployment is received.

The check

List every field the platform stores and mark each as asset or personal.

Then ask, for each personal one, which decision it informs.

The list of those with no answer is what to turn off.

Classify every stored field

An afternoon that decides the legal position.

List every field the platform stores.

Mark each as asset or personal.

For each personal one, name the decision it informs.

The list with no answer is what to switch off — and doing that is what keeps the deployment in the lighter category.

Connect policy and data

The choices in this note can be compared with stealth monitoring software boundaries. Keep the written purpose in control and enable only the information needed at this boundary.

Independent reference

For a thematic point of reference, see the Information Commissioner's Office. Consult the source directly because technical, operational and legal details change.