Anonymize preference action evidence for litigation research – CCPA/HIPAA-compliant de-identification per 11 USC §547

A trustee or debtor in possession pursuing a preference action under 11 USC §547 must assemble payment records, bank statements, and transfer histories that identify the transferee and the amounts paid within the 90-day lookback window. anonym.legal pseudonymizes transferee names, account numbers, and debtor identifiers so preference evidence can be reviewed by litigation consultants or used in insolvency-law teaching.

When this applies

Apply this workflow when preference-action evidence packets must be shared with expert witnesses, academic researchers studying preferential transfer patterns, or litigation-support analysts where the actual parties need not be identified.

  1. Upload the preference evidence packet — payment records, bank statements, ledger extracts — to anonym.legal.
  2. The engine identifies the debtor name, transferee names, account numbers, and any insider relationships disclosed in the records.
  3. Each transferee and the debtor receive consistent pseudonyms applied across all payment and transfer records.
  4. Payment dates, amounts, and the 90-day lookback window calculations are preserved as structural analytical content.
  5. The encrypted mapping is stored with US data residency for authorized re-identification.
  6. The pseudonymized evidence packet is exported for expert review or academic publication.
  7. Batch processing supports preference analyses across multiple preference defendants in the same case.

What you provide

  • Payment records, bank statements, and ledger extracts covering the 90-day preference period
  • Any insider-payment records covering the one-year lookback for insiders under 11 USC §547(b)(4)(B)
  • Specification of whether ordinary-course defense documentation should also be anonymized

Limitations & cautions

  • anonym.legal does not assess whether a payment constitutes an avoidable preference under 11 USC §547; that is a legal determination requiring trustee or counsel review.
  • The tool does not calculate the new-value defense or contemporaneous exchange defense amounts.
  • Bank statements with embedded images of checks may require supplemental processing to pseudonymize payee names on check images.
  • Insider relationship determinations under 11 USC §101(31) are not made by the tool.

FAQ

Are the 90-day payment dates retained in the pseudonymized evidence packet?

Yes. Dates are non-personal structural data and are preserved verbatim, maintaining the chronological integrity needed for preference-window analysis.

How does the tool handle payments to insider creditors in the one-year window?

Insider names and their relationship to the debtor are pseudonymized, while the extended lookback period and payment amounts are preserved. Insider status must still be legally determined by counsel.

Can this workflow support a new-value defense analysis without revealing the debtor?

Yes. New-value credits and the corresponding subsequent advances are preserved as financial structural content, allowing a consultant to assess the defense without knowing the debtor's identity.

Is ordinary-course-of-business defense documentation included?

Ordinary-course defense documentation can be included in the same upload. Counterparty names are pseudonymized while the payment timing and industry payment patterns are preserved for defense analysis.

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.