Anonymize statements of financial affairs for audit and research use – CCPA/HIPAA-compliant de-identification per FRBP Rule 1007 / Official Form B107

The Statement of Financial Affairs (Official Form B107), required under FRBP Rule 1007, discloses a debtor's income sources, prior lawsuits, asset transfers, and business ownership going back several years. It is dense with personal identifiers. anonym.legal pseudonymizes names, business affiliations, and transaction counterparties so the SOFA can be used for audit training or academic analysis.

When this applies

Apply this workflow when a completed SOFA must be shared with audit consultants, academic researchers, or creditors' committee members who require the financial narrative but not the debtor's identity.

  1. Upload the completed Official Form B107 in PDF or DOCX to anonym.legal.
  2. The engine scans all SOFA sections — income, lawsuits, payments, asset transfers, business ownership — for personal and entity identifiers.
  3. Debtor name, co-debtor name, business names, attorney names, and counterparty identifiers are pseudonymized consistently.
  4. Dollar amounts, date ranges, and court names are preserved as non-personal structural content.
  5. The encrypted pseudonym mapping is stored for authorized re-identification.
  6. The pseudonymized SOFA is exported in its original form layout for distribution.
  7. Batch processing supports entire case dockets for systemic audit-training purposes.

What you provide

  • Completed Official Form B107 in PDF or DOCX format
  • Any supplements or amendments to the SOFA filed after the initial submission
  • Instructions on whether business entity names should also be pseudonymized or only natural-person names

Limitations & cautions

  • The tool does not assess legal sufficiency of SOFA disclosures; counsel must ensure all required transfers and lawsuits are listed.
  • Historical business names involving well-known public entities may require manual review to determine whether full pseudonymization is appropriate.
  • The workflow addresses federal disclosure requirements under FRBP Rule 1007 only; no state-law obligations are assessed.
  • Complex multi-entity ownership charts disclosed in the SOFA may require supplemental diagram-level review.

FAQ

Will payment entries in Part 2 of the SOFA be fully pseudonymized?

Yes. Creditor names and addresses in Part 2 payment history entries are pseudonymized. The payment amounts and date ranges are retained so that the financial pattern remains visible for audit training.

How are references to prior lawsuits handled?

Party names in prior-lawsuit entries are pseudonymized. Court names, case numbers, and nature-of-suit descriptions are preserved as structural content.

Can the SOFA be processed alongside the related petition and schedules?

Yes. When uploaded together, the engine applies a unified pseudonym set so the debtor and each named party carry the same alias across the petition, all schedules, and the SOFA.

Does this workflow cover the corporate-version SOFA fields for business debtors?

Yes. Business-debtor SOFA fields — including insider payments, business closings, and property held for others — are processed using entity-level pseudonymization in addition to natural-person pseudonymization.

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.