Telematics anonymisation is the removal of direct identifiers from driving data. A score that sets a price with no human input engages UK GDPR Art. 22, which limits solely automated decisions with legal or similarly significant effects. Continuous location tracking sits on the ICO's list of processing that calls for an impact assessment under Art. 35. Removing the alias map is what moves pseudonymised data, defined in Art. 4(5), toward the anonymity Recital 26 describes.
When this applies
A driving log ties each trip to a named motorist and a start address. The pricing model needs the behaviour, not the person. You strip the identifiers and coarsen the start point before the data feeds the model.
How anonym.plus handles it
- Open the log in anonym.plus on your device.
- The tool flags names, IDs, and addresses.
- Local OCR reads any scanned trip summary.
- Turn the alias map OFF for true anonymity.
- Swap or black out the confirmed identifiers.
- Save the clean log locally.
What you need to provide
- The driving log (CSV exported to PDF, DOCX, TXT).
- An operator (Redact suits a trip table).
- The alias map turned OFF so no link survives.
PII & financial identifiers detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | motorist name → [SUBJECT] |
| Identifiers | UK_DRIVER_LICENSE | ORTIZ901234AB9CD → [LICENCE] |
| Location | LOCATION | home start point → [REGION] |
| Dates | DATE_TIME | trip time 07:42 → [TIME] |
| Contact | EMAIL_ADDRESS | driver@example.co.uk → [EMAIL] |
| Identifiers | UK_VRN | AB12 CDE → [VEHICLE] |
Compliance achieved
- Flags where a price set purely by an algorithm engages UK GDPR Art. 22 — solely automated decisions with a significant effect need a lawful route and a human review path.
- Supports the impact assessment UK GDPR Art. 35 calls for; the ICO lists systematic location tracking among high-risk processing.
- Pseudonymisation is defined in Art. 4(5) and remains personal data; only removing the map moves you toward Recital 26 anonymity.
- Everything runs offline, so the driving log never reaches a server.
Anonymise telematics datasets offline — see plans & start free →
Limitations & cautions
Recital 26 treats data as anonymous only if no one can re-identify a person. A regular home-to-work trace is close to a fingerprint, and the first and last points of a trip usually name a household. Coarsen the start point and the times before you publish.
Frequently asked questions
Why are trip traces hard to anonymise?
A repeated home-to-work pattern can re-identify a person even with the name gone, because the endpoints name places. Coarsen the start point and the times to get near the Recital 26 standard.
Does telematics pricing engage Art. 22?
It can. UK GDPR Art. 22 limits decisions based solely on automated processing that have legal or similarly significant effects. Where a score sets a price with no human involvement, check the lawful route and build in a review.
Is pseudonymised telematics data anonymous?
No. Art. 4(5) defines pseudonymisation as data that can still be attributed with extra information, so it remains personal data. Turning the alias map off is the step toward Recital 26 anonymity.