Anonymize adversary-proceeding complaints for legal research and training – CCPA/HIPAA-compliant de-identification per FRBP Rule 7001

An adversary proceeding commenced under FRBP Rule 7001 initiates contested litigation within a bankruptcy case on matters such as dischargeability, preference avoidance, and fraudulent transfers. The complaint names the plaintiff, defendant, and factual allegations that can identify the parties. anonym.legal pseudonymizes these identifiers so adversary complaints can support bankruptcy litigation training and academic research.

When this applies

Apply this workflow when adversary complaints and exhibits must be shared with litigation trainees, law-review editors, or co-counsel in different districts where the specific parties need not be identified.

  1. Upload the adversary complaint and any attached exhibits to anonym.legal.
  2. The engine identifies plaintiff and defendant names, attorneys of record, case numbers, and any third-party witnesses named in the factual allegations.
  3. Each named individual and entity receives a consistent pseudonym applied throughout the complaint and exhibits.
  4. Legal arguments, statutory citations, and procedural designations are preserved as non-personal structural content.
  5. The encrypted mapping is stored with US data residency for authorized re-identification.
  6. The pseudonymized complaint is exported in the same format for use in training materials or law-review appendices.
  7. Batch processing supports an adversary-proceeding library spanning multiple chapters and claim types.

What you provide

  • Adversary complaint in PDF or DOCX, including all exhibits
  • Any amended complaints filed after the initial pleading
  • Specification of whether third-party witnesses named in the factual allegations should also be pseudonymized

Limitations & cautions

  • anonym.legal does not assess the legal sufficiency of the complaint or the likelihood of success on the merits; those are legal judgments for counsel.
  • Exhibits containing financial statements with publicly reported figures may allow indirect identification of the debtor entity.
  • The tool does not pseudonymize case numbers or court-generated docket identifiers, which are public record.
  • References to parallel non-bankruptcy proceedings with publicly known case citations may allow indirect identification.

FAQ

Are the statutory claims asserted in the complaint pseudonymized?

No. Statutory claims — such as '11 USC §523 nondischargeability' or '11 USC §548 fraudulent transfer' — are legal structural content preserved verbatim. Only party and witness identifiers are pseudonymized.

Can amended complaints be processed consistently with the original?

Yes. Uploading the original and amended complaints together allows the engine to apply a unified pseudonym set, so any newly added parties receive new aliases while existing parties retain their original aliases.

How are attorney signature blocks handled?

Attorney names and bar numbers in signature blocks are pseudonymized. Firm names can be pseudonymized or generalized depending on the configuration selected.

Does this workflow cover cross-claims and counterclaims in adversary proceedings?

Yes. Cross-claims, counterclaims, and third-party complaints filed in the same adversary proceeding can be processed as a package with unified pseudonym assignment.

Bankruptcy & Insolvency

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.