In brief
- Regulation: GDPR.
- Transport operators, ticketing managers and mobility service providers are data controllers.
- Ground every processing activity.
- Minimise the data.
- Governing geolocation.
- Fines of up to €20M or 4% of global turnover.
Regulatory deadlines
The key dates of this regulation.
May 2018
Entry into application
In forceWhat does GDPR cover?
GDPR applies to data linkable to a traveller: named tickets, location, journeys. Geolocation and travel histories are particularly sensitive as they allow inference of home address, workplace, and habits.
The data minimisation principle calls for limiting collection and retention.
Is the 'Transport & mobility' sector concerned?
Transport operators, ticketing managers and mobility service providers are data controllers. Third-party services (under the Data Act) are controllers for their own processing activities.
The purpose (transport pass, fraud prevention, service) determines the legal basis and minimisation requirements.
Detailed obligations
Ground every processing activity
Define a legal basis per purpose and inform travellers.
Minimise the data
Limit the collection and precision of movement data to what is necessary.
Govern geolocation
Handle location data with care: user information and user control.
Control retention periods
Applying appropriate retention periods to travel history records.
Secure
Encryption, access control and data flow security.
Sanctions & risks
Fines of up to €20M or 4% of global turnover. Geolocation and movement profiling are drawing the attention of supervisory authorities.
Common mistakes in the sector
- 1Excessive collection. Retaining detailed logs without necessity.
- 2Poorly governed geolocation. Tracking location without adequate information.
- 3Unregulated profiling. Profiling movements without a framework.
- 4Excessive retention. Retain data beyond what is necessary.
Practical case
A network was retaining nominative journey histories indefinitely. Following analysis, it defined retention periods, anonymised data beyond those periods, informed passengers and restricted use to fraud prevention purposes.
Compliance roadmap
- 1
Map. Map ticketing, geolocation and historical data.
- 2
Qualify. Verify legal bases and data minimisation.
- 3
Frame. Defining user information and control.
- 4
Secure. Strengthen security and retention periods.
- 5
Document. Maintain the register.
Frequently asked questions
Yes: named tickets, geolocation data, and usage history are personal data.
Take action on GDPR
Free assessment or a chat with an expert dedicated to transport & mobility.
They already trust us
See how organisations in the transport & mobility sector secured their compliance with DCO.