Anonymize section 341 meeting notices for training and research – CCPA/HIPAA-compliant de-identification per 11 USC §341

The notice of the meeting of creditors under 11 USC §341 identifies the debtor, their attorney, the case number, and the hearing date and location. Distributed to all listed creditors, it creates broad exposure of the debtor's filing status and contact information. anonym.legal pseudonymizes debtor and attorney identifiers so 341 notices can be used in creditor-communication training without revealing real debtors.

When this applies

Apply this workflow when 341 meeting notices must be shared with creditor-counsel trainees, claims agents, or academic researchers studying notice distribution without the need to identify the actual debtor.

  1. Upload the 341 meeting notice in PDF or DOCX format to anonym.legal.
  2. The engine identifies the debtor name, address, attorney name and bar number, case number, and trustee contact details.
  3. Each named individual and entity is assigned a consistent pseudonym.
  4. The hearing date, time, location, and chapter designation are preserved as structural scheduling information.
  5. The encrypted mapping is stored for authorized re-identification.
  6. The pseudonymized notice is exported in the same layout as the original court-generated document.
  7. Batch processing supports entire case dockets for systemic notice-practice analysis.

What you provide

  • 341 meeting notice in PDF format as issued by the court or trustee
  • Any amended notices resetting the meeting date
  • Indication of whether trustee contact information should also be pseudonymized

Limitations & cautions

  • The tool does not assess whether notice was properly served on all creditors under FRBP Rule 2002; that is a procedural compliance matter for counsel.
  • Court-generated documents may include embedded metadata identifying the case; metadata stripping should be performed separately if required.
  • Trustee names are public record; users should decide whether to pseudonymize them based on their specific research or training context.
  • The workflow does not simulate or replace the actual 341 meeting transcript.

FAQ

Are the hearing date and location pseudonymized in the output?

No. The hearing date, time, and location are structural scheduling fields preserved verbatim. Only party identifiers such as debtor name, attorney name, and addresses are pseudonymized.

Can a batch of 341 notices from the same case be processed together?

Yes. Original and amended notices from the same case can be uploaded together so that the debtor and attorney appear under the same pseudonyms across all versions.

Does the tool handle 341 notices for Chapter 11 cases differently?

The pseudonymization logic is the same across chapters. Chapter 11 notices may include additional parties such as a creditors' committee; all named parties receive individual pseudonyms.

What if the notice contains a QR code or barcode linking to the case on PACER?

QR codes and barcodes embedded in court documents are flagged for manual review. They may encode case-identifying information that pseudonymization of text fields alone would not address.

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.