Request ID: FOI-3428-2324 Date published: 23 February 2024
You asked
Some follow up queries for you regarding TfL's handling of ULEZ expansion camera data and TfL road user charging projects:
1. Regarding pseudonymised data used by TfL, you say "Vehicle registration numbers used for our traffic monitoring are encrypted at source with a multi-character unique encryption code". This code is apparently unique to each vehicle and never changes. Given this:
(a) Who generates and who maintains the multi-character unique encryption code for each vehicle?
(b) What vehicle characteristics are used to form the multi-character unique encryption code for each vehicle? Is it possible to understand these characteristics from the multi-character unique encryption code?
(c) Are there any random components to the multi-character unique encryption code, or is computable from the registration mark?
(d) How long does TfL (note TfL,not Yunex) store pseudonymised data collected by ULEZ expansion cameras?
2. What TfL projects have made use of pseudonymised data collected by ULEZ expansion cameras since 1 August 2023? Please supply project name, approximate FTEs employed on project and approxmate annual project budget.
3. What is the current status of Project Detroit/Project 2030 (https://project2030tfl.co.uk/)? If it is active, how many FTEs are employed on it. If it is not active, has it been replaced by another road charging project?
We answered
Our Ref: FOI-3428-2324 Thank you for your request received on 30 December 2023 asking for information about the Ultra Low Emission Zone (ULEZ) camera data. Your request has been considered in accordance with the requirements of the Environmental Information Regulations (EIR) and our information access policy. I can confirm that we do hold the information you require. You asked for:
Regarding pseudonymised data used by TfL, you say "Vehicle registration numbers used for our traffic monitoring are encrypted at source with a multi-character unique encryption code". This code is apparently unique to each vehicle and never changes. Given this:
Who generates and who maintains the multi-character unique encryption code for each vehicle?
This is done by our contractor, Yunex.
What vehicle characteristics are used to form the multi-character unique encryption code for each vehicle? Is it possible to understand these characteristics from the multi-character unique encryption code?
Are there any random components to the multi-character unique encryption code, or is computable from the registration mark?
The vehicle registration mark (VRM).
How long does TfL (note TfL,not Yunex) store pseudonymised data collected by ULEZ expansion cameras?
We currently hold pseudonymised automatic number plate recognition (ANPR) data within a database for past five years. The current data time series commenced in 2019, however ULEZ expansion cameras have only been returning data since June 2023. The data is used to report on compliance with the LEZ and ULEZ schemes. It is also used as an input to air quality modelling. There is no personal data (eg names and addresses) involved.
What TfL projects have made use of pseudonymised data collected by ULEZ expansion cameras since 1 August 2023? Please supply project name, approximate FTEs employed on project and approximate annual project budget.
None.
What is the current status of Project Detroit/Project 2030 (https://project2030tfl.co.uk/)? If it is active, how many FTEs are employed on it. If it is not active, has it been replaced by another road charging project?
