Social Security Number Redaction in Federal Filings under FRCP Rule 5.2 – CCPA/HIPAA-compliant de-identification per FRCP Rule 5.2

FRCP Rule 5.2(a)(1) mandates that only the last four digits of a Social Security number appear in any federal court filing; anonym.legal scans pleadings, exhibits, and supporting declarations for full nine-digit SSNs and automatically reduces each to the required last-four-digit format, eliminating the risk of inadvertent full-SSN disclosure in the public court record.

When this applies

Applies in any federal civil matter where SSNs appear in documents — Social Security disability appeals, employment discrimination cases with payroll records, bankruptcy proceedings, and any civil matter where tax records or government identification documents are exhibits.

  1. Upload the document containing SSNs in PDF or DOCX format.
  2. anonym.legal scans for SSNs in all standard formats: XXX-XX-XXXX, XXXXXXXXX, and common variants.
  3. Each full SSN is replaced with the Rule 5.2-compliant 'XXX-XX-[last four]' format.
  4. Associated identifying context — name, address, employer — is preserved so the filing remains coherent.
  5. A count of identified and replaced SSNs is provided in the processing summary for quality review.
  6. Review the output, then file the redacted document via CM/ECF.

What you provide

  • Document containing one or more Social Security numbers (PDF or DOCX)
  • Case caption information (to retain party names in full)

Limitations & cautions

  • anonym.legal targets standard nine-digit SSN formats; non-standard or handwritten SSNs in image-based exhibits may require manual review.
  • The last four digits of an SSN remain in the public record after Rule 5.2 redaction — for heightened protection, consider a motion to seal under local rules.
  • Rule 5.2 does not require redaction of Employer Identification Numbers (EINs) — only individual SSNs are covered. EINs are preserved in full by default.

FAQ

Does Rule 5.2 apply to SSNs in exhibits attached to declarations?

Yes — any document filed with the court, including exhibits to declarations, must comply with Rule 5.2. Process exhibits and the declaration together in one session.

What if the court orders that full SSNs be included in a sealed filing?

An order to seal under Rule 5.2(d) can permit full SSNs in the sealed version. The publicly accessible version must still use only the last four digits.

Does the tool process foreign national identification numbers the same way?

anonym.legal recognizes US SSN formats under Rule 5.2. Foreign national identification numbers (e.g. passport numbers, alien registration numbers) are detected as general personal identifiers and flagged for manual review.

Civil Litigation

About this page

We update this page when our platform or the law changes.

Read our founder note for how we work.

Each change shows up in the timestamp at the top.

We follow these rules

  • GDPR (EU 2016/679).
  • ISO/IEC 27001:2022.
  • NIS2 (EU 2022/2555).
  • HIPAA safe harbor under 45 CFR § 164.514(b)(2).

Our promise

We do not sell your data.

We do not train models on your text.

We store your files in Germany.

You can delete your account at any time.

You own your work.

Where we run

Our servers live in Falkenstein, Germany.

We use Hetzner. They hold ISO 27001 certification.

All data stays in the EU.

Backups run every day.

Need help?

Email support@anonym.legal.

We reply within one business day.

How we test

We run a full check suite on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We track recall and precision on a labelled set.

Bad runs block the deploy.

What we never do

  • We never sell your information to third parties.
  • We never train models on what you upload.
  • We never keep your work after you delete it.
  • We never share keys with any outside firm.
  • We never run ads inside the product.

Plans in plain words

We sell credits, not seats.

One credit covers one short job.

Long jobs use a few credits each.

You can top up at any time.

Unused credits roll over each month.

Read the plans page for current rates.

Who built this

A small team of engineers and lawyers built this.

We ship from Europe and work in the open.

Our founder note spells out why we started.

Where to start

How the parts fit

A browser add-on cleans text inside Chrome.

A Word plug-in handles drafts in Office.

A small desktop tool works on whole folders.

An agent protocol link feeds large models safely.

All four share one core engine and one rule set.

Words from our team

We started this work after a lunch about cookies.

One friend kept getting odd ads on her phone.

We asked why a court file leaked through a draft.

We sketched the first build on a napkin that week.

By month three we had a tiny demo for a friend.

She used it on her first case the next day.

Common questions we hear

Can the tool read scanned PDFs? Yes, with OCR.

Does it work on long files? Yes, in small chunks.

Can I roll my own rule set? Yes, save it as a preset.

Does it run offline? The desktop build runs offline.

Do you keep my files? No, the cloud build wipes after each run.

Will it learn from my work? No, we never train on inputs.

A short tour of the workflow

Upload a file or paste a snippet of prose.

Pick the entities you want gone from the draft.

Choose a method: replace, mask, hash, encrypt, or redact.

Press run and watch the side panel show each hit.

Skim the result and tweak any rule that misfired.

Save the cleaned file or send it to a teammate.