GDPR applies to any organisation processing personal data of EU and UK residents, regardless of sector. Transportation organisations face a specific configuration of obligations shaped by the personal data they collect, the regulatory environment they operate in, and the systems they use to do it.
This page covers the GDPR obligations specific to Transportation, the lawful bases that apply, and the implementation approach that survives supervisory authority scrutiny.
Regulatory context
Supervisory authority: National data protection authorities + transport regulators
Key personal data categories: driver location data, vehicle telematics, employee records, customer shipment data
Special category data present: Typically no — standard Article 6 lawful bases apply
Primary lawful bases: Contract (employment), Legitimate Interests (fleet management, fraud prevention), Legal Obligation (tachograph records)
In many EU jurisdictions, works council or employee representative consultation is required before deploying telematics systems. This is a labour law obligation separate from GDPR but directly relevant to the lawful basis analysis — processing that employees have not been consulted on is harder to defend under legitimate interests.
The hard part
Telematics and fleet tracking systems generate continuous location data for identifiable drivers. Consent is rarely the right basis for employee monitoring — legitimate interests requires a documented balancing test, and data minimisation limits how long raw GPS data can be retained.
This is the implementation decision that most Transportation GDPR programmes get wrong. It is also the issue most likely to appear in a supervisory authority audit or a data subject complaint.
Required controls
- Documented legitimate interests assessment for driver telematics
- Data minimisation policy: aggregate GPS data after defined retention period
- DSAR workflow spanning fleet management, HR, and dispatch systems
- Privacy notice for drivers covering monitoring scope and purpose
- Tachograph records retained per regulatory requirement with restricted access
GDPR gap assessment framework for Transportation
A gap assessment for a Transportation organisation covers five areas:
1. Data inventory and ROPA
Map every system that holds personal data specific to Transportation operations: driver location data, vehicle telematics, employee records, customer shipment data. Document the purpose, lawful basis, retention period, and third-party recipients for each. The ROPA must be current — a snapshot taken at implementation and not updated is not compliant.
2. Lawful basis audit
For each processing activity, confirm the lawful basis is documented and appropriate. Transportation organisations frequently find that processing that was assumed to be covered by legitimate interests has not had a Legitimate Interests Assessment completed. Where special category data is present, Article 9 requires a separate documented basis.
3. Consent management
Where consent is the lawful basis, verify that consent records meet GDPR Article 7 requirements: freely given, specific, informed, unambiguous, and withdrawable. Legacy consent from before the current privacy notice version should be assessed for adequacy.
4. DSAR readiness
Test the DSAR workflow with a synthetic request. The test should cover: intake, identity verification, data discovery across all systems identified in the data inventory, response assembly, and delivery within the 30-day deadline. Most Transportation DSAR gaps are discovered at the data discovery stage — systems that hold personal data but are not connected to the DSAR workflow.
5. Breach preparedness
Verify the incident log, the severity classification matrix, and the 72-hour notification workflow. The Transportation-specific question is: which data categories, if breached, trigger notification to individuals (not just to the supervisory authority)? Notification to individuals is required where the breach is likely to result in high risk to their rights and freedoms.
Implementation priority order
For Transportation organisations starting a GDPR programme:
- Data inventory — identify all systems holding personal data before configuring any controls
- Lawful basis documentation — stop processing for which there is no documented basis
- DSAR workflow — rights requests can arrive at any time; the workflow must be operational before launch
- Consent remediation — address legacy consent before running any marketing to the affected population
- ROPA — live, connected to source systems, reviewed quarterly
- Breach procedure — tested annually; DPO and legal team both trained on the 72-hour obligation