Pseudonymising Firm-Wide Financial-Crime Risk Assessments – UK GDPR-compliant anonymisation per FCA SYSC 6

Firm-wide financial-crime risk assessments (FCRAs) document the firm's exposure to money laundering, fraud, and sanctions risks, and may reference named high-risk customer segments or named senior managers responsible for risk ownership. anonym.legal pseudonymises those personal references so the FCRA can be shared with external advisers or auditors assessing the adequacy of the firm's systems and controls under FCA SYSC 6 without disclosing individual identities.

When this applies

This task applies when an FCRA is shared with external assurance providers, skilled-person reviewers, or board advisers who require sight of the risk methodology, exposure ratings, and control gaps but do not need to know the identities of named individuals referenced in the assessment.

  1. Upload the FCRA document (PDF or DOCX).
  2. The engine identifies named senior managers, named risk owners, and any named customer-segment examples referenced in the narrative.
  3. Each named individual is pseudonymised consistently; risk exposure ratings, control descriptions, gap analysis, and remediation timelines are preserved.
  4. Board-approval records and regulatory-submission history references remain in clear text.
  5. A reversible mapping table is produced with UK/EU data residency.
  6. Release the pseudonymised FCRA for external adviser or auditor review; restore originals before any regulatory submission.

What you provide

  • Firm-wide financial-crime risk assessment document
  • Risk-register appendix (if it names individuals as risk owners)
  • Board-approval sign-off documentation

Limitations & cautions

  • The tool pseudonymises personal references in the FCRA but does not assess whether the risk methodology or control framework is adequate under FCA SYSC 6.
  • FCRAs that reference named customer segments or customer types (rather than named individuals) do not require pseudonymisation of those segment descriptions.
  • The pseudonymised FCRA must not be submitted to the FCA or UKFIU in place of the original.

FAQ

Should I pseudonymise the names of senior managers listed as risk owners?

Yes. Senior manager names are personal data under UK GDPR and should be pseudonymised when the FCRA is shared outside the compliance team. Role titles and responsibility areas are preserved.

Does the tool handle FCRAs that reference third-party correspondent bank relationships?

Named natural persons at correspondent banks are pseudonymised. Correspondent bank institution names are preserved unless you flag them for pseudonymisation.

Can a pseudonymised FCRA be shared with an external skilled-person reviewer?

Yes, for preliminary review purposes. However, the skilled-person reviewer may ultimately require the re-identified version to fulfil their obligations under an FCA s.166 review — confirm this requirement before sharing the pseudonymised version.

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.