Anonymize Chapter 11 disclosure statements for research and training – CCPA/HIPAA-compliant de-identification per 11 USC §1125

A Chapter 11 disclosure statement under 11 USC §1125 must provide creditors adequate information to vote on a plan of reorganization. It discloses the debtor's full financial history, management identities, and valuation analyses. anonym.legal pseudonymizes personal and entity identifiers so disclosure statements can support restructuring-practice training and academic research without exposing the reorganizing debtor.

When this applies

Use this workflow when a Chapter 11 disclosure statement must be shared with restructuring-practice trainees, academic researchers, or creditors' committee advisers in a different matter where the specific debtor's identity is not required.

  1. Upload the disclosure statement in PDF or DOCX format to anonym.legal.
  2. The engine identifies the debtor entity name, officer and director names, key creditor names, and financial adviser identities throughout the document.
  3. Each named individual and entity is assigned a consistent pseudonym applied across all sections and exhibits.
  4. Valuation figures, capital structure summaries, and projected financial statements are preserved as non-personal structural content.
  5. The encrypted mapping is stored with US data residency for authorized re-identification.
  6. The pseudonymized disclosure statement is exported for use in training libraries or academic paper appendices.
  7. Batch processing supports multiple disclosure statements from the same industry sector for comparative restructuring research.

What you provide

  • Chapter 11 disclosure statement in PDF or DOCX format
  • Any amended or supplemental disclosure statements filed after the initial version
  • Instruction on whether trade creditor names should be pseudonymized or only financial-institution names

Limitations & cautions

  • anonym.legal does not assess whether the disclosure statement satisfies the adequate-information standard under 11 USC §1125; that is a legal determination subject to court approval.
  • Publicly traded debtors with extensive SEC cross-references may require additional review to identify indirect disclosure of the debtor's identity.
  • The tool does not pseudonymize embedded financial tables formatted as images; text-based financial data is processed but image-embedded data is flagged.
  • References to the debtor's industry or geographic market may allow indirect identification even after name pseudonymization.

FAQ

Are officer and director names pseudonymized throughout the entire document?

Yes. Officer and director names appearing in biographical sections, signature blocks, and the body of the disclosure statement are all pseudonymized consistently using the same alias for each individual.

Will projected financial statements be altered?

No. Projected revenue, EBITDA, and debt-service figures are preserved verbatim. Only personal and entity identifiers are pseudonymized; the financial projections remain intact for restructuring-education purposes.

Can the disclosure statement be processed alongside the companion plan of reorganization?

Yes. Uploading both documents together ensures that the same pseudonyms are applied across the disclosure statement and the plan, maintaining consistency for training or research use.

How does the tool handle voting solicitation materials attached to the disclosure statement?

Solicitation materials and ballots attached as exhibits are processed as part of the same package, with creditor names and addresses pseudonymized consistently with the main document.

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.