Anonymize AML Investigation Files for Oversight and Training – CCPA/HIPAA-compliant de-identification per 31 USC §5318

AML investigation files compiled under an institution's BSA AML program at 31 USC §5318 document the alert trigger, transaction analysis, subject research, and disposition decision for individual investigations. anonym.legal pseudonymizes subject and account identifiers in these files so compliance oversight teams and trainers can evaluate investigation quality and typology coverage without exposing the subject's personal data.

When this applies

Use this workflow when AML investigation files are reviewed by second-line compliance oversight, BSA auditors, or training facilitators who need to assess the analytical methodology, red-flag coverage, and disposition rationale without accessing the identities of the subjects under review.

  1. Upload the AML investigation file — including alert summary, transaction analysis, subject research notes, and disposition record — to anonym.legal.
  2. The engine identifies the subject's name, account numbers, date of birth, address, SSN, and any named transaction counterparties or associated persons.
  3. Each individual in the file receives a distinct, consistent pseudonym applied across the alert summary, investigation narrative, and disposition record.
  4. Alert trigger parameters, transaction amounts and categories, red-flag indicators, and the disposition decision are preserved in plain text.
  5. A reversible mapping table is encrypted and stored with US data residency.
  6. Export the pseudonymized investigation file for oversight review, audit, or training use.
  7. Retain the original investigation file in your BSA recordkeeping system for the applicable five-year retention period.

What you provide

  • AML alert summary and trigger documentation
  • Transaction analysis and subject research notes
  • Disposition decision record and any SAR referral documentation

Limitations & cautions

  • Pseudonymized investigation files must not be used as a substitute for the original file in any regulatory or law enforcement production.
  • Where an investigation results in a SAR filing, the SAR must be processed separately under the SAR workflow; the SAR itself may not be pseudonymized for regulatory submission.
  • The tool does not assess whether the investigation methodology meets the analytical standards expected by FinCEN or your primary federal regulator.
  • Investigation files that include embedded screenshots from transaction monitoring systems may require manual review of image-embedded text.

FAQ

Can I pseudonymize AML files that resulted in SAR filings to use as training case studies?

Yes. Files from completed investigations — including those that resulted in SAR filings — can be pseudonymized for training purposes. The SAR itself must remain on file unchanged, but the investigation file can be pseudonymized separately for training use.

Are transaction counterparty names pseudonymized alongside the primary subject?

Yes. Named transaction counterparties who are natural persons receive distinct pseudonyms. Corporate counterparty names are preserved unless you flag them for pseudonymization.

How are multi-subject investigations handled?

Each named subject receives a distinct pseudonym applied consistently throughout the investigation file. The relationship between subjects — such as co-account holders or transaction counterparties — is preserved in the pseudonymized structure.

Financial Services Compliance

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.