Skip to content
Guide · 7 chapters

The telematics and GDPR guide

Tracking a company’s vehicles is not a technical question. It is the subject that sinks projects in the boardroom — not because the answer is hard, but because nobody in the room has prepared it. This guide gives the answer, and says where to check it.

This guide is for you if you are preparing a telematics deployment, if your IT or legal team has asked "and what about GDPR", or if your drivers have reacted and you are looking for something to stand on.

Is tracking company vehicles legal?

Yes, where it serves a purpose the French data protection authority allows: the safety of employees and vehicles, billing a service, or checking compliance with the rules of use. It must neither monitor an employee permanently nor check their speed. The employee must be able to switch it off outside working time, and the works council must be informed or consulted beforehand. Source: CNIL.

Chapter 1What telematics actually measures

Three sources, three kinds of data: the device fitted in the vehicle; the connected vehicle at its manufacturer, with no hardware; the driver’s mobile app, which locates the phone and therefore the person, including outside the vehicle — the most intrusive of the three, and the one most often forgotten as such.

A position attached to a vehicle assigned to an identified person is personal data about that person. It is not the ownership of the vehicle that counts, it is whether the driver can be identified.

The question to ask before any other

Which data do you actually need for the use you have in mind? Many projects collect a continuous position when the objective is satisfied by far poorer data. This is not a legal precaution: it is the minimisation principle, and it is also what will get the project accepted internally.

Chapter 2Permitted purposes and forbidden uses

The six recognised purposes

  1. Tracking and invoicing a transport service for people or goods.
  2. Ensuring the safety of employees, goods or vehicles.
  3. Allocating resources better for work carried out in scattered locations.
  4. Tracking working time, as a secondary purpose only.
  5. Complying with a legal or regulatory obligation.
  6. Checking that the rules on vehicle use are followed.

The six forbidden uses

  • Checking compliance with speed limits.
  • Monitoring an employee permanently.
  • Tracking an employee who is free to organise their own journeys.
  • Tracking a staff representative in the exercise of their mandate.
  • Collecting location outside working time, commutes and breaks included.
  • Calculating working time when another system already does it.
The most important practical consequence

The employee must be able to switch off the collection or transmission of their location outside working time. The employer can monitor how often this happens and act on abuse, but cannot remove the possibility. A system that does not provide for it is non-compliant, however good the rest of the project.

Private mode: how Dadycar applies it

The French data protection authority requires that employees be able to switch off the collection of their location outside working time. With Dadycar private mode, your drivers switch off the collection of their location outside working time. It works in the mobile app and on the web platform. This is the answer to prepare before consulting the works council. Our written answers on hosting, sub-processors and retention periods are on the Trust and security page.

SourceCNIL — Tracking of employees’ vehicles (in French)

Chapter 3Choosing a legal basis and documenting it

The employer’s legitimate interest is the most common basis: it requires a real interest, processing that is necessary to achieve it, and no disproportionate impact on employees’ rights. That test is documented, not asserted. Consent is rarely relevant in an employment relationship: subordination makes it hard to consider freely given.

DocumentWhat it containsWho asks for it
Record of processingPurposes, data, recipients, periods, securityThe authority in an inspection
Legitimate interest assessmentInterest, necessity, balancingThe authority, a court in a dispute
Impact assessmentRisks to people and the measures that reduce themThe authority, when the risk is high
Information noticeWhat is told to employeesEmployees, works council, labour inspectorate

These documents are not produced after the fact. Written at deployment they cost a few hours; written after a complaint they cost far more and come out worse.

Chapter 4Informing employees and consulting the works council

The information notice carries the identity of the controller, the purposes stated precisely — not "improving management" —, the legal basis, the recipients including providers, the retention period of each category, the rights of access, rectification and objection, and the possibility of lodging a complaint with the authority.

Consulting staff representatives comes before deployment. It is not an end-of-project formality: a system deployed before consultation can be challenged, and the discussion that should have happened upstream then happens downstream, in worse conditions.

What is really at stake here

Everything you do not say will be assumed. And what is assumed is always worse than the reality.

SourceCNIL — Example information notice for vehicle tracking (in French)

Chapter 5Retention periods and minimisation

UsePeriod
General rule2 months
Route optimisation, proof of work done1 year
Working time tracking5 years

An automatic purge, not a manual one that gets forgotten: a period announced and not applied is worse than a long period owned up to. And different periods per category — raw positions are not kept as long as an aggregated report.

Three questions that shrink the footprint without shrinking the usefulness

  1. Do you need the position, or an event? "The vehicle arrived on site" is often enough, without keeping the journey.
  2. Do you need individual data, or an aggregate? A cost per kilometre per site does not need named journeys.
  3. Do you need continuous collection, or triggered collection? Event-based collection is less intrusive and often easier to explain.

SourceCNIL — Tracking of employees’ vehicles (check again at deployment, the doctrine evolves)

Chapter 6Security, processors and hosting

The company remains the controller; the vendor acts on its behalf, as a processor. The relationship is contractual: subject and duration of the processing, categories of data, security obligations, further processors, assistance with complaints or breaches, what happens to the data at the end of the contract.

The six questions to ask a vendor

  1. Where is the data hosted? The country, not the commercial region.
  2. Which further processors are involved? Host, router, the device’s mobile operator, support.
  3. Is there any transfer outside the European Union? And on what basis.
  4. How are accesses traced? Who sees what, and is it logged.
  5. What is the procedure in case of a breach? Deadline, contact, form.
  6. What happens at the end of the contract? Usable export, deletion deadline, proof of deletion.
Including for us

These questions apply to any solution, ours included. A vendor that cannot answer them in writing leaves you carrying alone a risk that is in fact shared.

Go furtherCybersecurity and fleet management·Trust and security

Chapter 7Deploying without turning the company against you

The real risk is not the fine: it is social. A badly prepared deployment produces conflict, systematic switching off, unplugged devices and unusable data. The company has paid for a system it cannot use.

The sequence that works

  1. Write the purposes first, on one page, before choosing a tool.
  2. Consult staff representatives with that document, not with a sales brochure.
  3. Inform each driver individually, explaining switching off outside working time and how it is done.
  4. Start with a narrow scope — one site, one category of vehicles — and learn from it.
  5. Show what it gives. A driver who sees that the data spared them a breakdown or defended a disputed invoice does not experience it the same way.
The three sentences that defuse it

"Here is exactly what we collect, and what we do not." · "Here is how long it is kept, and what deletes it." · "Here is how you switch collection off outside work." None of them is a sales promise: they are verifiable facts, and that is why they work.

Go furtherGeofencing·The software evaluation grid·The fleet management guide

Frequently asked questions

How long can vehicle location data be kept?

Two months as a general rule, according to the French data protection authority. One year where it serves to optimise rounds or evidence the work carried out. Five years where it serves working-time records. Beyond that it must be deleted.

Can an employee be tracked outside working hours?

No. Collecting location outside working time is prohibited, including home-to-work journeys and breaks. The employee must be able to switch off the collection or the transmission of their position. The employer may monitor how often or how long it is switched off, and sanction abuse.

Must employees be informed and the works council consulted first?

Yes. Each employee is told the controller, the purposes, the legal basis, the recipients, the retention period and their rights. Staff representatives are informed or consulted before any decision to install the system.

Can tracking be used to check drivers’ speed?

No. That use is excluded, as is the permanent monitoring of an employee. The system stays limited to the purposes announced to employees.

Can a salesperson’s vehicle be tracked?

Not if they are free to organise their own travel: that is prohibited, as it is for a staff representative acting in their mandate. The criterion is not the job, it is the freedom to organise journeys.

Ask us the six questions

A demo is also the occasion to check in writing what this guide teaches you to ask.

Request a demo