What is a record of processing activities, and why should a fleet keep one?
A record of processing activities lists, in one place, what personal data you handle, why, where it goes, how long you keep it and who can see it. Many privacy rules ask organizations to keep something like it, or to produce it when a regulator or a customer asks. Whether yours does depends on your country, your size and what you do. Ask your adviser. The record is also useful on its own: it shows which camera clips nobody needs any more and which providers have no contract.
A fleet is a good case for a record because the data is easy to overlook. A tracker gives a position every few seconds. A driver-monitoring camera makes event clips of a face. Both are tied to a named driver, so both are personal data about people who work for you.
What personal data does a fleet system create?
- Location and trips. Position, speed, heading, trip start and end, ignition.
- Driver identity. Name, employee number, license number, card or RFID ID, sometimes a photo.
- Driver behavior events. Fatigue and distraction alerts from DSM, forward-collision and lane alerts from ADAS, with time and place.
- Video and audio. MDVR recordings, event clips and snapshots, audio if you switch it on.
- Device and SIM identifiers. IMEI, ICCID, phone number and the plate they are tied to.
- Portal accounts. The names, roles and login history of your own staff and your customers' staff.
The Register starts with one row for each of these. Rename, split or delete them to match what you really collect.
How to fill the register
- Start with the starter rows. Change the activity names to match your own systems. Add a row when the same data is used for a second purpose.
- Write the purpose in one plain sentence. If you cannot, the activity may be several activities. Split it.
- Pick the legal basis only with your adviser. The cell starts as "To be confirmed with counsel" in the Example sheet. The Check column keeps reminding you until you choose one.
- Follow the data. Where does it come from, which system holds it, in which country, who receives it, and does it leave the country?
- Set a retention period you can really keep. A number of days and the way it is deleted. An automatic rule is easier to keep than a monthly clean-up.
- Name a responsible role, not a person. People change jobs. Roles stay. Then enter the review date.
Which data does the device or platform record, in which country is it stored, and for how long? Put the answers in the Register and the Recipients sheet. If a provider cannot answer, write that down too.
Four columns people leave out
- Retention. Without a number of days nobody deletes anything. The Summary counts rows with no retention period.
- Transfers. Cloud platforms often store data in another country. The column asks "yes, no or unsure". Unsure is a fine answer, and it is counted so you follow it up.
- Notice. People should be told what you collect. The column asks whether they have been told fully, partly or not.
- Processor contract. A provider that handles data for you is usually a processor. The Recipients sheet flags a processor without a contract.
Limits
This is a spreadsheet, not legal advice. It keeps what you type, counts what is empty and reminds you of review dates. It does not read your platform or your contracts, and it does not decide the legal basis, the retention period or whether a transfer is allowed. Starter text and example rows are prompts, not recommendations.
Sources and when they were checked
The field names follow common record-of-processing practice. Three official sources were read on 2026-11-03. Each is also on the Sources sheet.
- EU GDPR, Article 30, records of processing activities (EUR-Lex): eur-lex.europa.eu. Used as a field list only.
- SDAIA, Rules for Appointing a Personal Data Protection Officer (Saudi Arabia, official text, Art. 5): dgp.sdaia.gov.sa. It names location tracking and surveillance cameras as examples of regular and systematic monitoring.
- Implementing Regulation of the Personal Data Protection Law, Article 33, records of processing activities (Umm Al-Qura Gazette, official text): uqn.gov.sa. Records are kept for the duration of processing and five years after it ends.
Source and date checked: 2026-11-03. Rules change, and your country may have others, so open the current text before you rely on it.