GDPR Data processing modelTicketing system of transport organizing authorities
Purposes (5)
A purpose is the objective pursued by the setting up of your file. It indicates what the processing of personal data will be used for, its purpose. This purpose must be clear and understandable
Data categories (5)
Personal data is any information relating to an identified or identifiable natural person. A natural person can be identified either directly (eg surname and first name) or indirectly (eg phone number, social security number, email or postal address, but also voice or image)
Data for managing overdue payments
Data details
Definition
person's date of birth
Data conservation rules
Active base:
Information on unpaid amounts is removed from the card deny list (hotlist) as soon as the sums due have been paid. No statutory period applies to the deny list; the controller should set a maximum, e.g. 2 years from listing, based on the time reasonably needed to recover the debt. Records of the debt itself may be kept until the limitation period expires, i.e. 6 years from when the sum fell due (Limitation Act 1980, s.5).
Limitation Act 1980, s.5
Destruction
Validation data
Data details
Data conservation rules
Active base:
Customer data are kept for the duration of the contractual relationship. No statutory period applies after it ends; the controller should set a period, e.g. 2 years, for customer relations and statistics, using aggregated or anonymised data for statistics where possible. Data needed to deal with claims or disputes may be kept until the limitation period expires (6 years, Limitation Act 1980, s.5). Deleting the card number, or deleting the date, time and place of use, can contribute to anonymisation; hashing the card number is only pseudonymisation and the data remain personal data under UK GDPR. Journey (validation) data linked to a card or account number: no statutory period applies; the controller should keep them only as long as needed, e.g. 48 hours where used solely to detect technical fraud. Where the customer uses post-payment (pay as you go) travel, the data needed for billing (excluding location where not needed) may be kept, e.g. for 4 months from the journey, to handle charging disputes and refund claims. When validation data are collected centrally, they should be sorted so that only the data of post-payment customers are kept for that period.
Limitation Act 1980, s.5; UK GDPR
Destruction
Payment data
Data details
Data conservation rules
Active base:
Customer data are kept for the duration of the contractual relationship. No statutory period applies after it ends; the controller should set a period, e.g. 2 years, for customer relations and statistics, using aggregated or anonymised data for statistics where possible. Data needed to deal with claims or disputes may be kept until the limitation period expires (6 years, Limitation Act 1980, s.5).
Limitation Act 1980, s.5
Destruction
Management data for free or reduced fare transport tickets
Data details
Data conservation rules
Active base:
Customer data are kept for the duration of the contractual relationship. No statutory period applies after it ends; the controller should set a period, e.g. 2 years, for customer relations and statistics, using aggregated or anonymised data for statistics where possible. Data needed to deal with claims or disputes may be kept until the limitation period expires (6 years, Limitation Act 1980, s.5).
Limitation Act 1980, s.5
Destruction
Traveler identification data
Data details
Definition
Photograph including the person's face
Data conservation rules
Active base:
Customer data are kept for the duration of the contractual relationship. No statutory period applies after it ends; the controller should set a period, e.g. 2 years, for customer relations and statistics, using aggregated or anonymised data for statistics where possible. Data needed to deal with claims or disputes may be kept until the limitation period expires (6 years, Limitation Act 1980, s.5).
Limitation Act 1980, s.5
Destruction
Data subject (1)
A data subject is any person whose data is collected, retained or processed by the data processing. e.g. In a recruitement process, any candidate for a position proposed in recruitement management process
- Customers
Attribution / Pas d'utilisation commerciale
CC-BY-NC
