Telematics Data Anonymisation with anonym.plus

Strip driver identifiers and trip traces from telematics data before analysis.

Telematics anonymisation is the removal of direct identifiers from driving data. UK GDPR Recital 26 says truly anonymous data falls outside the rules, and the ICO Anonymisation Code applies a motivated-intruder test. anonym.plus marks each identifier on your device, so the patterns stay analysable while the person stays shielded.

When this applies

A driving log ties each trip to a named motorist and start address. You strip those identifiers before the data feeds a pricing model.

How anonym.plus handles it

  1. Open the log in anonym.plus on your device.
  2. The tool flags names, IDs, and addresses.
  3. Local OCR reads any scanned trip summary.
  4. Turn the alias map OFF for true anonymity.
  5. Swap or black out the confirmed identifiers.
  6. Save the clean log locally.

What you need to provide

PII & financial identifiers detected

Categoryanonym.plus entity typeExample
NamesPERSONmotorist name → [SUBJECT]
IdentifiersUK_DRIVER_LICENSEORTIZ901234AB9CD → [LICENCE]
LocationLOCATIONhome start point → [REGION]
DatesDATE_TIMEtrip time 07:42 → [TIME]
ContactEMAIL_ADDRESSdriver@example.co.uk → [EMAIL]
IdentifiersUK_VRNAB12 CDE → [VEHICLE]

Compliance achieved

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 can still single someone out. Coarsen the start point and 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. Coarsen the start point and times to meet the Recital 26 standard.

Why turn off the alias map?

An alias map can re-link a trace to a person. For true anonymity under Recital 26, leave it off so no reverse path remains.

Is the log uploaded?

No. The app runs locally, so the data never leaves your device.