Anonymize fraudulent-transfer evidence for insolvency litigation research – CCPA/HIPAA-compliant de-identification per 11 USC §548

A trustee pursuing a fraudulent transfer action under 11 USC §548 must establish the debtor's insolvency, the consideration received, and the identity of the transferee. The assembled evidence — appraisals, wire records, corporate resolutions — names individuals and entities connected to the transaction. anonym.legal pseudonymizes these identifiers for use by litigation consultants or insolvency-law researchers.

When this applies

Use this workflow when fraudulent-transfer evidence must be shared with valuation experts, academic researchers studying constructive and actual fraud patterns, or litigation support teams where the specific parties need not be identified.

  1. Upload the fraudulent-transfer evidence package — wire transfers, appraisals, corporate resolutions, and board minutes — to anonym.legal.
  2. The engine identifies debtor entity names, transferee names, signatories on resolutions, and individual names in board minutes.
  3. Each named individual and entity receives a consistent pseudonym across all evidence documents.
  4. Transaction dates, dollar amounts, and asset descriptions are preserved as structural analytical content.
  5. The encrypted mapping is stored with US data residency for authorized re-identification.
  6. The pseudonymized evidence package is exported as a compiled set for expert review or academic case study.
  7. Multiple fraudulent-transfer transactions from the same case can be processed together to maintain consistent pseudonyms.

What you provide

  • Wire transfer records, corporate resolutions, and board minutes covering the two-year lookback under 11 USC §548
  • Appraisal reports or valuation analyses establishing fair consideration
  • Specification of whether individual signatories or only entity names should be pseudonymized

Limitations & cautions

  • anonym.legal does not assess whether a transfer satisfies the elements of actual or constructive fraud under 11 USC §548; legal analysis is required.
  • The two-year lookback period in the Bankruptcy Code does not limit state fraudulent-transfer claims, which may extend further; this workflow covers only federal Bankruptcy Code requirements.
  • Corporate resolutions with embedded signature images are processed for text but the image signatures are flagged for manual review.
  • Valuation opinions by named appraisers are pseudonymized; the appraiser's credentials within the opinion are also replaced with a pseudonym.

FAQ

Are board-minute signatories pseudonymized alongside the corporate resolution signatories?

Yes. All named individuals who sign, approve, or are referenced in board minutes and corporate resolutions receive consistent pseudonyms across all documents in the package.

Will appraisal values and fair-market-value conclusions be preserved?

Yes. Appraisal values and fair-market-value conclusions are non-personal financial data preserved verbatim. Only the appraiser's name and firm are pseudonymized.

Can this workflow also address state-law fraudulent transfer claims under UVTA?

This workflow is scoped to the federal Bankruptcy Code §548 framework. State-law UVTA claims involve separate limitations periods and elements not addressed here.

How are shell-entity intermediaries in multi-step transfers handled?

Each entity in a multi-step transfer chain receives its own pseudonym, applied consistently across all documents in the package so the transaction structure remains traceable without revealing real entity names.

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.