Genomic pseudonymisation is the swap of donor labels for stable codes in the accompanying file. It supports UK GDPR Art. 9 on genetic data. anonym.plus runs offline and keeps the sample manifest usable while the donor names go.
When this applies
A lab shares a sequencing manifest with a bioinformatics group. The sheet still ties each donor name to a sample and a sequencing run.
How anonym.plus handles it
- Open the manifest (CSV, XLSX, or DOCX) in anonym.plus.
- The tool flags donor names, dates, and contact fields.
- Local OCR reads a scanned consent or intake page.
- Confirm the flags and keep the sample and run codes.
- Replace each donor label with a stable pseudonym.
- Save the manifest locally with no upload.
What you need to provide
- The manifest (CSV, XLSX, DOCX, or scan).
- An operator: Replace for pseudonyms across the sheet.
- Optional: a pseudonym map held apart for re-linking.
Patient data entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Donor | PERSON | donor Lucy Romano → [DONOR_A] |
| Sample code | ID | sample SQ-7782 (kept) → [SAMPLE] |
| Dates | DATE_TIME | sequenced 11/06/2026 → [DATE] |
| Lab | ORGANIZATION | Genome Lab London → [LAB] |
| Contact | EMAIL_ADDRESS | l.romano@example.co.uk → [EMAIL] |
| NHS number | MEDICAL_RECORD_NUMBER | NHS 943 476 5919 → [NHS_NO] |
Compliance achieved
- Protects genetic special-category data under UK GDPR Art. 9.
- Runs offline, so no cloud data-processor contract is triggered.
- On-device AES-256-GCM guards the working manifest.
- Pseudonymisation is a named UK GDPR Art. 32 safeguard, not full anonymisation.
Anonymise genomic datasets offline — see plans & start free →
Limitations & cautions
Pseudonymising the manifest does not anonymise the sequence itself. A genome is inherently identifying and cannot be fully de-identified by swapping a label. Treat the codes as personal data and hold the re-linking map under strict, separate access.
Frequently asked questions
Is pseudonymised genomic data anonymous?
No. Pseudonymisation swaps a label for a code, but a key still links back. A genome is also unique to one person by nature, so it stays personal data under UK GDPR Art. 9 even after the manifest is cleaned.
What does this tool actually do?
It cleans the manifest and supporting files: donor names, dates, and contacts become stable codes. It does not alter the sequence data itself.
Where should the key map live?
Apart from the shared manifest, under strict access only the lab lead can reach. anonym.plus produces a pseudonym map you hold separately.