DOJ Second Request Redaction with anonym.plus

Clear personal data from a large production while the substance stays.

DOJ Second Request redaction is the removal of personal data from documents produced in a merger review. The HSR Act (15 U.S.C. §18a) authorises that second request for more data. anonym.plus strips names and contacts across the set on your device.

When this applies

A Second Request demands a huge volume of documents on a deadline. Employee and customer names recur across thousands of files and can be cleared where allowed.

How anonym.plus handles it

  1. Point anonym.plus at the production folder on your device.
  2. It scans each file for names, emails, and IDs.
  3. A shared label map keeps repeat people steady.
  4. Review the summary and fix low-confidence flags.
  5. Save the clean production set on your device.

What you need to provide

PII entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONemployee across files → [EMPLOYEE_1]
NamesPERSONcustomer contact → [CUSTOMER_1]
ContactEMAIL_ADDRESSwork email → [EMAIL]
DatesDATE_TIMEsent 09 Feb → [DATE]
IdentifiersNATIONAL_IDemployee no. → [ID]
FinancialUS_BANK_NUMBERaccount no. → [ACCOUNT]

Compliance achieved

Anonymize second request productions offline — see plans & start free →

Limitations & cautions

The DOJ may require some names in the clear. Redact only what the protocol allows. Mixed folders lean on OCR for scans, so review low-confidence flags before you produce.

Frequently asked questions

Can the batch handle a large volume?

Yes. Point the tool at a folder, up to 20 files per batch, and run sequential batches for a large production locally.

How does the shared map help at volume?

It logs each person once, so the same employee or customer maps to one alias in every file across the set.

Are scanned documents supported?

Yes. Local OCR reads scanned pages, so IDs in image files are caught before the check.