Redaction-log de-identification is the removal of personal data from the record that lists each cut and its ground. FRCP 26(b)(5)(A) requires a description of what was withheld and why. anonym.plus keeps that ground on every row while the names go.
When this applies
The log is the audit trail for the pass, so it names Bates ranges, reviewers, and often the very people you removed. A reason field that restates a masked value undoes the cut. An entry too thin to test invites a Rule 37(a) challenge.
How anonym.plus handles it
- Load the file into anonym.plus on your device.
- It scans the description and basis columns.
- The tool flags names and contacts in each entry.
- Confirm the flags; keep the stated basis for each cut.
- Replace or mask the confirmed PII.
- Save the clean record on your device.
What you need to provide
- The file (XLSX, CSV, DOCX, or PDF).
- An operator; Mask for partial names in entries.
- Optional steady labels so one person maps to one alias.
PII entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | redacted-party name → [NAME] |
| Document IDs | PERSON | Bates ABC-0099 → [DOC_ID] |
| Dates | DATE_TIME | entry date → [DATE] |
| Contact | EMAIL_ADDRESS | entry email → [EMAIL] |
| Identifiers | US_SSN | SSN in basis → [SSN] |
| Names | PERSON | reviewer name → [REVIEWER] |
Compliance achieved
- The log answers FRCP 26(b)(5)(A): what came out, and on what ground.
- A reason field must not restate the value it removed — that is checked row by row.
- Bates ranges and page references stay, so every entry can be traced back.
- Offline work keeps the audit trail inside your firm.
Anonymize 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
Do the rules require a log for content cuts?
Rule 26(b)(5)(A) is written for privilege claims. Courts and ESI protocols routinely ask for the same detail on content cuts, since the other side cannot test what it cannot see. Check your protocol before you fix the format.
How can the log itself leak?
Its description field explains why a value came out, and the shortest explanation is often the value. Mask the names in each row and describe the category instead.
Does it read spreadsheet versions?
Yes. XLSX and CSV files are supported, plus DOCX and PDF versions.