Privilege Log Redaction with anonym.plus

Clear PII from a privilege log while each withholding reason stays clear.

Privilege-log redaction is the removal of personal data from the index that describes withheld items under FRCP 26(b)(5). anonym.plus runs on your device. The entry still shows why each item is privileged.

When this applies

A privilege log must describe withheld documents without waiving the claim. Its author, recipient, and subject fields often carry names you must mask.

How anonym.plus handles it

  1. Load the file into anonym.plus on your device.
  2. The tool scans author, recipient, and description fields.
  3. It flags names, dates, and contacts in each row.
  4. Confirm the flags; keep the stated basis text intact.
  5. Replace or mask the confirmed PII.
  6. Save the clean index with no network call.

What you need to provide

PII entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONFrom: J. Marek → [AUTHOR]
NamesPERSONTo: Dr. Lindqvist → [RECIPIENT]
DatesDATE_TIMESent 04/02 → [DATE]
ContactEMAIL_ADDRESSj.marek@firm.com → [EMAIL]
IdentifiersUS_SSNSSN in subject → [SSN]
Document IDsPERSONBates PRIV-0042 → [DOC_ID]

Compliance achieved

Anonymize privilege logs offline — see plans & start free →

Limitations & cautions

Each row must still describe its item enough to test the claim. Mask names, but do not strip so much that the basis becomes vague. Over-redaction can itself draw a motion to compel, so review every entry.

Frequently asked questions

Will masking names waive the claim?

No. FRCP 26(b)(5) asks you to describe withheld items, not name every person. Masking PII while keeping the stated basis keeps the record defensible.

Can one person map to a steady alias across rows?

Yes. A name map gives each person one alias, so the index reads consistently without real names.

Does it read spreadsheet versions?

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