Vehicle tracking can improve fleet security, mileage records and operational control, but GPS data linked to an employee is personal data. This guide explains how UK employers can design a proportionate tracking arrangement, document decisions, protect private journeys and review access, retention and supplier controls over time.
Overview
A company vehicle tracker does not remove an employer’s data-protection responsibilities. A location record may identify a driver directly through a user account, or indirectly through a vehicle allocation, shift pattern or journey history. The same applies to telematics information such as speed events, harsh braking, mileage, route history, working patterns and dash-cam footage.
Before introducing a fleet tracking system, the organisation should be able to answer five basic questions:
- What business purpose requires tracking?
- Which data is necessary to achieve that purpose?
- When will tracking be active, particularly where a vehicle can be used privately?
- Who can view, export or change the information?
- When will records be deleted or anonymised?
The relevant compliance framework will depend on the organisation and the proposed use, but UK employers should consider the UK GDPR, the Data Protection Act 2018, employment obligations and applicable guidance from the Information Commissioner’s Office. This article is practical guidance rather than legal advice. A documented assessment should reflect the employer’s circumstances, workforce arrangements and tracking features.
Tracking should be proportionate. A system used to recover stolen vehicles may not need continuous driver-behaviour scoring, individual journey replay or long-term route history. Conversely, a business managing safety-critical operations may have a clearer reason to retain selected event data. The purpose should determine the settings, not the other way round.
What to track
Define the purpose and lawful basis
Record each intended use separately. Common purposes include vehicle security, maintenance planning, mileage administration, route coordination, customer service, health and safety, and investigation of incidents. Avoid combining every possible purpose into a broad statement such as “monitoring productivity”. That wording makes it harder to explain necessity and may encourage uses that were not part of the original decision.
Employers should identify an appropriate lawful basis for each processing purpose and document the reasoning. Consent may not always be suitable in an employment relationship because of the imbalance between employer and employee. Depending on the circumstances, another basis may be more appropriate, but this should be assessed rather than assumed. If tracking is used to make employment decisions or impose disciplinary action, the organisation should also document how the data will be interpreted and checked for context.
Set boundaries for private use
A vehicle allocated to an employee may be used outside working hours. Continuous tracking during private journeys can reveal home addresses, medical appointments, religious attendance, family routines and other sensitive details. A privacy mode, driver-controlled switch, scheduled shutdown or separate private-use vehicle setting may reduce unnecessary collection. The chosen control should be tested in the actual vehicle and explained clearly to drivers.
Private-use boundaries should cover:
- when work-related tracking starts and ends;
- whether emergency, theft or accident functions remain active;
- who can override privacy mode and under what circumstances;
- whether mileage totals are still recorded when location history is hidden; and
- how a driver can report a malfunction or challenge an unexpected tracking event.
Use a simple data-flow map
Document where information is collected, processed, viewed, exported and deleted. A data-flow table makes gaps easier to identify than a general policy statement.
| Stage | Example data | Control to check |
|---|---|---|
| Collection | GPS position, timestamp, vehicle identifier and event data | Is collection limited to the stated purpose and operating hours? |
| Transmission | Device data sent through a mobile network to the platform | Is the connection protected, and what happens during signal loss? |
| Platform storage | Live map, journey history, alerts and reports | Are retention settings, backups and deletion processes understood? |
| Access | Information viewed by fleet, HR, security or managers | Are permissions role-based, individual and regularly reviewed? |
| Export and sharing | CSV reports, incident files or insurer information | Are exports logged, protected and deleted when no longer needed? |
Complete a DPIA-style assessment
Where tracking is likely to create a high risk to individuals, consider a formal data protection impact assessment. Even where a formal DPIA is not required, the same questions provide a useful governance record:
- What problem is the tracking intended to solve?
- Could the objective be met with less detailed or less frequent location data?
- Does the system monitor private use, lone workers, passengers or members of the public?
- What could happen if the data is inaccurate, misused, exposed or retained too long?
- What technical and organisational safeguards reduce those risks?
- Who approved the assessment, and when will it be reviewed?
For related operational controls, see the UK fleet compliance checklist and the guide to driver behaviour monitoring software.
Cadence and checkpoints
Give drivers a clear policy notice
A tracking policy should be available before monitoring begins and written in language drivers can understand. It should identify the vehicles or devices covered, the purposes, the data collected, the active hours, privacy controls, recipients, retention approach, individual rights and a contact route for questions or complaints.
A concise policy template might read as follows:
Purpose: We use vehicle tracking for [listed business purposes].
Scope: Tracking applies to [vehicles, devices and user groups] during [defined work periods].
Private use: During approved private use, [privacy control and exceptions] apply.
Access: Information is available to [named roles] for [listed purposes]. Access is reviewed regularly.
Retention: Routine location history is retained for [documented period], while incident records may be kept separately where justified.
Rights and concerns: Drivers can contact [internal contact] to ask questions, exercise applicable rights or raise a concern.
Do not treat a policy acknowledgement as a substitute for transparency. A signature confirms that the notice was received; it does not make unnecessary monitoring proportionate.
Review access and retention on a schedule
Use a quarterly review for most small and medium-sized fleets, with more frequent checks where the system contains sensitive information or many managers have access. Compare the active user list with current roles, remove leavers promptly, and check whether administrators still need elevated permissions. Use individual accounts rather than shared logins so access and changes can be attributed.
Retention should be tied to a purpose and a documented business need. Separate routine journey history from records needed for a live investigation, accident, insurance matter or legal requirement. Do not retain everything indefinitely because the platform permits it. Test deletion or anonymisation, including backups and exported reports where those are under the organisation’s control.
Check the supplier contract
Confirm how the tracking provider processes data, where it stores information, which sub-processors it uses, how security incidents are reported, how data is returned or deleted at the end of the contract, and what support is available for rights requests. Check whether the platform offers role-based access, audit logs, privacy mode, configurable retention and export controls. A feature listed on a sales page is not the same as a control that has been configured and tested.
How to interpret changes
More data does not automatically mean better fleet management. A sudden rise in tracked journeys may reflect a new vehicle allocation, a change in privacy settings, duplicate devices or a platform update rather than a change in driver behaviour. Before acting on a report, check the time period, vehicle assignment, device health, GPS accuracy and whether the driver had a legitimate explanation.
Driver-behaviour metrics should be used as prompts for conversation and safety improvement, not as automatic conclusions. Harsh-braking events can be affected by road layout, weather, traffic and calibration. A location anomaly may result from weak signal or map matching. Keep a record of how significant events are reviewed, corrected and, where appropriate, removed from a person’s profile.
Complaints and access requests should follow a repeatable workflow:
- Log the request, complaint or suspected misuse with its date and owner.
- Confirm what information and systems are in scope, including exports and dash-cam files.
- Restrict unnecessary access while the matter is investigated.
- Check the relevant policy, purpose, lawful basis, retention rule and audit trail.
- Provide a clear response, correcting inaccurate data where appropriate.
- Record the outcome and any change to settings, training or policy.
For mileage-specific questions, the guide to company vehicle mileage tracking and private use provides a useful companion reference. Hardware choices also affect privacy controls, so compare OBD, hardwired and battery-powered trackers before installation.
When to revisit
Make privacy governance part of the fleet routine rather than a one-off installation task. A quarterly checkpoint should cover user access, leavers, privacy-mode tests, retention and deletion results, complaints, policy acknowledgements, supplier changes and any new tracking features. Record the review even when no change is required.
Refresh the assessment sooner when the organisation adds driver-behaviour scoring, dash cams, temperature sensors, lone-worker functions, private-use vehicles, new integrations or a different supplier. Also revisit it after a security incident, a significant complaint, a change in working practices or relevant changes to data-protection and employment requirements.
At the annual governance review, ask whether the original purpose still applies, whether less intrusive settings would now work, and whether every retained field is still needed. Update the privacy notice, staff training and supplier records together so that the documents describe the system people actually use.
Practical next step: create a one-page tracking register listing each vehicle or device, assigned driver group, purpose, active hours, data fields, access roles, retention period, supplier and next review date. Use it as the starting point for the next quarterly audit and keep evidence of the checks completed.