Declaration Anonymization under 28 USC §1746: protect third-party identifiers in unsworn declarations – CCPA/HIPAA-compliant de-identification per 28 USC §1746

28 USC §1746 permits unsworn declarations under penalty of perjury as substitutes for notarized affidavits in federal proceedings; such declarations routinely name third-party witnesses, medical providers, and business contacts, and anonym.legal pseudonymizes those non-party identifiers in draft declarations so teams and clients can review and approve the content without exposing third-party personal data before the declaration is executed and filed.

When this applies

Applies when counsel is preparing an unsworn declaration under 28 USC §1746 for support of a motion, opposition, or other court filing and the declaration references individuals beyond the declarant and the named parties.

  1. Upload the draft declaration in DOCX or PDF format.
  2. Configure the allow-list to retain the declarant's name and party names in full — these must appear in clear in the executed document.
  3. anonym.legal identifies and pseudonymizes third-party names, contact details, and personal identifiers referenced in the declaration body.
  4. Factual assertions, exhibit references, and the penalty-of-perjury certification language are preserved without alteration.
  5. A reversible mapping is stored; full names are restored before the declarant signs and before filing with the court.
  6. Apply Rule 5.2 partial redactions to any filing-bound declaration that contains SSNs, birth dates, financial account numbers, or minor names.

What you provide

  • Draft declaration (DOCX or PDF)
  • Declarant's name and party names to retain in full
  • Exhibits referenced in the declaration (optional, for consistent pseudonymization)

Limitations & cautions

  • The declarant must execute the final, re-identified declaration — anonym.legal does not facilitate electronic signing.
  • The legal sufficiency of the declaration's factual assertions is for counsel to confirm — anonym.legal handles data-minimization only.
  • Declarations used as deposition exhibits or filed as court exhibits must comply with Rule 5.2 in addition to this pseudonymization workflow.

FAQ

What is the difference between an affidavit and a declaration under 28 USC §1746?

An affidavit requires notarization; a declaration under §1746 requires only the declarant's signature and the statutory penalty-of-perjury language, making it procedurally simpler for supporting motions in federal court.

Does anonym.legal preserve the §1746 penalty-of-perjury certification language?

Yes — the statutory certification language ('I declare under penalty of perjury that the foregoing is true and correct') is recognized as structural text and preserved without alteration.

Can a pseudonymized draft declaration be sent to the client for approval?

Yes — sharing a pseudonymized draft limits exposure of third-party personal data during the client-review stage. The client must review and approve the re-identified, full-name version before signing.

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.