Pseudonymising Source of Funds Declarations for AML Compliance Review – UK GDPR-compliant anonymisation per MLR 2017

Source-of-funds declarations — required under the Money Laundering Regulations 2017 for conveyancing transactions above risk thresholds — identify the purchaser or tenant, disclose the origin of transaction funds, and attach supporting evidence such as bank statements, gift letters, and beneficial owner declarations. anonym.legal pseudonymises the personal identifiers in these packs so AML compliance teams can review the adequacy of the declaration framework without retaining unnecessary personal data.

When this applies

This task applies when source-of-funds packs are reviewed internally by AML compliance officers, external compliance consultants, or quality-assurance teams assessing the firm's MLR 2017 compliance, and those reviewers require sight of the disclosure structure and evidence categories rather than the individual's personal details.

  1. Upload the source-of-funds declaration and all supporting evidence (bank statements, gift letters, beneficial owner declarations, sale proceeds certificates) to anonym.legal.
  2. The engine identifies the declarant's name, address, date of birth, bank account details, and any third-party donors or gift providers named in supporting documents.
  3. Each natural person is pseudonymised consistently across the declaration and all evidence; the fund origin description, fund amounts, and evidence categories are preserved.
  4. Bank statement entries naming third parties (e.g. salary payors, investment providers) are pseudonymised at the individual name level while transaction amounts and dates are retained.
  5. A mapping table is produced with UK/EU data residency.
  6. Release the pseudonymised pack for AML compliance review; restore originals before any regulatory submission or production to law enforcement.

What you provide

  • Source-of-funds declaration form
  • Supporting bank statements (certified copies)
  • Gift letters naming donor and recipient
  • Beneficial owner declaration if third-party funds are involved
  • Sale proceeds certificate or mortgage redemption statement (if applicable)

Limitations & cautions

  • Source-of-funds information submitted to law enforcement, the National Crime Agency, or as part of a Suspicious Activity Report must use the real identities of the declarant and any third parties — the pseudonymised version is for internal compliance review only.
  • The MLR 2017 require adequate customer due diligence; pseudonymisation of the source-of-funds pack for internal review does not itself satisfy CDD requirements under the MLR 2017.
  • Bank account numbers and sort codes in bank statements are pseudonymised alongside personal names; retain the mapping key to cross-reference with the firm's AML records.

FAQ

Are bank account numbers treated as personal data in source-of-funds packs?

Bank account numbers and sort codes that can identify an individual account holder are personal data under UK GDPR when combined with a name. The engine pseudonymises them alongside the account holder's personal identifiers.

Can this workflow be used for reviewing a firm's AML file quality across multiple matters?

Yes. Upload multiple source-of-funds packs in a batch for a consistent quality-assurance review. The compliance team can assess the adequacy of the declaration structure and evidence across multiple matters without retaining client personal data.

Does the MLR 2017 require source-of-funds checks on all conveyancing transactions?

The MLR 2017 require customer due diligence and, in higher-risk scenarios, enhanced due diligence including source-of-funds verification. The specific trigger thresholds depend on the transaction's risk profile — obtain specialist AML compliance advice.

Are gift donors named in gift letters pseudonymised separately from the main purchaser?

Yes. Each named individual in the gift letter — donor and recipient — is pseudonymised with a unique pseudonym. The gift amount, the relationship description, and any declaration of non-repayment are preserved.

Property & Conveyancing

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.