Pleading Batch Redaction with anonym.plus

Clean a whole folder of pleadings in one local run with steady labels.

Pleading batch redaction is the removal of FRCP 5.2 personal identifiers from a whole folder in one run. The rule applies the same identifier limits to each file. anonym.plus processes up to 20 at a time on your device, with a shared map so one party maps to one alias everywhere.

When this applies

A case file holds many pleadings that name the same parties. One-by-one work risks drift, so a batch run applies Rule 5.2 evenly across the set.

How anonym.plus handles it

  1. Point anonym.plus at the case folder on your machine.
  2. It scans each file for the Rule 5.2 identifier set.
  3. Local OCR reads any scanned pages in the set.
  4. A shared map keeps repeat parties steady across files.
  5. Review the summary and fix low-confidence flags.
  6. Save the clean set locally.

What you need to provide

PII entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONparty across files → [PARTY_1]
IdentifiersUS_SSNSSNs → [SSN]
FinancialUS_BANK_NUMBERaccounts → [ACCOUNT]
DatesDATE_TIMEbirth dates → [DOB]
MinorPERSONminors → initials
ContactEMAIL_ADDRESSemails → [EMAIL]

Compliance achieved

Anonymize pleading sets offline — see plans & start free →

Limitations & cautions

A mixed folder of scans and native files leans on OCR for the images, so review low-confidence flags. The shared map can re-link the set if kept; turn it off when you need true anonymity.

Frequently asked questions

How does batch mode keep one party steady?

A shared map logs each person once, so the same party maps to the same alias in every file across the folder.

How many pleadings can one run handle?

Up to 20 files per batch, all processed locally with OCR for any scanned pages.

Does batch work upload anything?

No. The whole run is offline, so privilege and work-product stay on your machine.