Redaction Log De-Identification with anonym.plus

Clear PII from the log itself while each stated reason stays clear.

Redaction-log de-identification is the removal of personal data from the record that lists each cut and its basis, often a privileged work-product file. anonym.plus runs locally and keeps the reason given for every entry.

When this applies

This record lists each cut and why you made it. The description fields can themselves name people, so the file needs cleaning before it is shared.

How anonym.plus handles it

  1. Load the log into anonym.plus on your device.
  2. It scans the description and basis columns.
  3. The tool flags names and contacts in each entry.
  4. Confirm the flags; keep the stated basis for each cut.
  5. Replace or mask the confirmed PII.
  6. Save the clean record on your device.

What you need to provide

PII entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONredacted-party name → [NAME]
Document IDsPERSONpage ref ABC-0099 → [DOC_ID]
DatesDATE_TIMEentry date → [DATE]
ContactEMAIL_ADDRESSentry email → [EMAIL]
IdentifiersUK_NINONINO in basis → [NINO]
NamesPERSONreviewer name → [REVIEWER]

Compliance achieved

Anonymise redaction logs offline — see plans & start free →

Limitations & cautions

Each entry must still justify its cut. Mask names in the rows, but keep the stated basis, or the file loses its purpose. Confirm that masking does not make two different cuts look identical.

Frequently asked questions

Why de-identify the log itself?

Its description fields can name the very people you redacted. Cleaning the record keeps that PII from leaking when it is shared, while litigation privilege over your work stays.

Will it still justify each cut?

Yes. The stated basis for each entry stays. Only PII inside the rows is masked or replaced.

Does it read spreadsheet versions?

Yes. XLSX and CSV files are supported, plus DOCX and PDF versions.