Research Dataset Anonymisation with anonym.plus

Apply study safeguards to the file on your own machine, fully offline.

Research dataset anonymisation is the removal of participant identifiers under UK GDPR Art. 89 safeguards. anonym.plus runs on your own device. The measured variables stay usable while the people behind them stop being named.

When this applies

A study group shares a file with collaborators across institutions. Direct names, emails, and rare birth dates must be hidden first.

How anonym.plus handles it

  1. Load the file (CSV, XLSX, or DOCX) into anonym.plus on your device.
  2. The tool scans columns and notes for direct identifiers.
  3. Local OCR reads any scanned questionnaire you include.
  4. Confirm the flagged names, emails, and dates.
  5. Replace each with a steady pseudonym across the file.
  6. Save the safeguarded copy locally with no network call.

What you need to provide

Patient data entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONBridget Larson → [PARTICIPANT_2]
EmailEMAIL_ADDRESSb.larson@example.co.uk → [EMAIL]
Birth dateDATE_TIMEborn 04/04/1939 → [BIRTH_YEAR]
LocationLOCATIONNewcastle upon Tyne → [REGION]
PhonePHONE_NUMBER+44 191 496 0190 → [PHONE]
Free-text IDIDenrol EN-3382 → [ENROL_ID]

Compliance achieved

Anonymise research datasets offline — see plans & start free →

Limitations & cautions

UK GDPR Art. 89 allows pseudonymised data under safeguards, which is not the same as full anonymisation. If you keep a re-linking map, the file is still personal data. Store that map apart and apply the ICO motivated-intruder test before you share.

Frequently asked questions

What does UK GDPR Art. 89 cover?

It sets safeguards for processing personal data for scientific research, such as pseudonymisation and data minimisation. Removing direct identifiers is a core safeguard before sharing a file with collaborators.

Is pseudonymised data anonymous?

No. If a re-linking key exists, the file is still personal data. Full anonymisation under UK GDPR Recital 26 means no one can be identified by any means reasonably likely to be used.

Where should the key map live?

Apart from the shared file, on a protected store only the lead can reach. anonym.plus can produce a pseudonym map you hold separately.