Pseudonymising SARs for AML Training Without Tipping-Off – UK GDPR-compliant anonymisation per POCA 2002 Part 7

Suspicious activity reports (SARs) filed under the Proceeds of Crime Act 2002 identify the subject of suspicion and the nature of the suspected activity. Using real SARs in training risks breaching tipping-off restrictions under POCA 2002 Part 7 and exposing personal data. anonym.legal pseudonymises SAR content to produce realistic training scenarios that preserve the typology without disclosing the subject's identity.

When this applies

This task applies when AML training facilitators need illustrative SAR examples to demonstrate reporting quality and typology coverage to staff, and the real subject's identity and any associated tipping-off risk must be removed before the material is used in training.

  1. Upload the internal SAR or draft SAR to anonym.legal; the document is processed in a secure, access-controlled environment.
  2. The engine identifies the subject's name, account references, transaction counterparties, and any other personal identifiers in the narrative.
  3. Each individual and account reference is pseudonymised consistently; the suspicion narrative, typology description, and transaction pattern are preserved.
  4. Grounds-of-suspicion text, transaction amounts, and reporting-officer role reference remain in clear text to preserve the training value.
  5. A reversible mapping table is produced with UK/EU data residency and access restricted to the compliance team that uploaded the document.
  6. Release the pseudonymised version for training; the original remains filed with the UK Financial Intelligence Unit (UKFIU) record.

What you provide

  • Internal SAR or draft SAR narrative
  • Supporting transaction summary (if attached to the SAR narrative)

Limitations & cautions

  • The pseudonymised SAR is for internal training only; it must not be submitted to UKFIU or any other body in place of the original.
  • Tipping-off risk is eliminated in the pseudonymised version, but the original SAR remains subject to POCA 2002 Part 7 tipping-off restrictions — do not disclose the original or its existence to the subject.
  • The tool does not assess whether the original SAR meets the quality standards expected by UKFIU.

FAQ

Does pseudonymising a SAR breach the tipping-off provisions of POCA 2002 Part 7?

No. Pseudonymisation removes the identifying information that would enable the subject to be identified, so the pseudonymised version does not constitute a disclosure within the meaning of POCA 2002 s.333A. However, the original SAR and its existence remain protected — consult your MLRO before sharing the pseudonymised version outside the compliance team.

Can the pseudonymised SAR be included in a published typologies report?

A pseudonymised SAR may be suitable for internal typologies documentation. For any external publication, obtain legal advice on whether the pseudonymisation is robust enough to prevent re-identification in context.

Will the engine preserve the suspicion grounds and red flags in the narrative?

Yes. The suspicion narrative, red-flag indicators, and transaction pattern description are preserved in clear text, which is essential for the training value of the scenario.

Does the tool handle SARs that reference multiple suspects?

Yes. Each suspect named in the SAR narrative receives a distinct, consistent pseudonym, preserving the multi-party structure of the suspicion narrative.

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.