Investigation Subject Access Redaction with anonym.plus

Reveal the requester's own details while you shield other named people.

Subject access redaction is the removal of other people's data from an investigation file before disclosure. GDPR Art. 15 gives a person access to their own records, not to third-party details. anonym.plus clears those other names on your device.

When this applies

An employee files a subject access request (DSAR) for an investigation about them. The file also names witnesses and colleagues whom you must shield.

How anonym.plus handles it

  1. Open the file in anonym.plus on your device.
  2. The tool flags every named person in the text.
  3. Keep the requester's own details; flag the rest.
  4. Swap or black out third-party names and contacts.
  5. Save the disclosable copy on your device.

What you need to provide

PII entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONrequester → kept (their right)
NamesPERSONwitness → [REDACTED]
NamesPERSONnamed colleague → [REDACTED]
ContactEMAIL_ADDRESSwitness email → [REDACTED]
ContactPHONE_NUMBERwitness phone → [REDACTED]
IdentifiersNATIONAL_IDthird-party ID → [REDACTED]

Compliance achieved

Anonymize subject access files offline — see plans & start free →

Limitations & cautions

Art. 15 needs a balance between the requester's right and others' privacy. The tool flags names; you decide what to keep. A witness may still be obvious from context even with the name gone.

Frequently asked questions

Why keep the requester's own details?

GDPR Art. 15 gives a person the right to access their own file. You keep their identifiers and shield only the records of other people.

How do I protect a witness in the file?

Flag and redact the witness's name and contacts. The tool also flags indirect mentions so you can review them.

Can I set the requester's own IDs as allowed?

Yes. An allow-list keeps the requester's identifiers in place while the tool removes everyone else's.