Pseudonymising Beneficial-Owner Disclosures for AML Compliance Review – UK GDPR-compliant anonymisation per Bribery Act 2010

A beneficial-owner disclosure document is a record identifying natural persons who own or control a corporate structure — prepared for AML compliance under the Bribery Act 2010. Under Companies Act 2006 Part 21A, any person holding 25 percent or more must be registered; UK GDPR fines reach £17.5 million or 4% of turnover. anonym.legal pseudonymises those individuals so compliance advisers assess the framework without exposing personal data.

When this applies

This task applies when beneficial-owner disclosure documents are reviewed by AML compliance consultants, legal advisers, or internal audit teams assessing the robustness of the entity's adequate-procedures framework, and those reviewers require sight of the disclosure structure and methodology rather than the individuals' identities. According to ECCTA 2023 — in force from November 2023 — Companies House received enhanced powers to verify PSC and beneficial-owner data, making accurate record-keeping with real identities essential for regulatory submissions while pseudonymised copies serve internal review.

  1. Upload the beneficial-owner disclosure document or UBO register extract.
  2. The engine identifies named beneficial owners, their nationalities, dates of birth, and addresses.
  3. Each individual is pseudonymised consistently; ownership percentages, control thresholds, and the tracing methodology are preserved.
  4. A mapping table is produced with UK/EU data residency.
  5. Release the pseudonymised version for compliance review; restore originals before submission to any regulatory body or counterparty.

What you provide

  • Beneficial-owner disclosure document or UBO register extract
  • Corporate structure chart showing ownership chain (if separate)
  • Any certification or declaration signed by named beneficial owners

Limitations & cautions

  • Beneficial-owner information submitted to regulatory bodies, counterparties, or financial institutions must contain the real identities of the beneficial owners — the pseudonymised version is for internal compliance review only. Breaches of UK GDPR in processing UBO data can attract fines of up to £17.5m or 4% of global annual turnover under Art. 83.
  • The Bribery Act 2010 s.7 adequate-procedures assessment requires specialist legal and compliance advice; pseudonymisation of the disclosure document does not itself constitute compliance.
  • The tool pseudonymises personal data in the disclosure but does not verify the accuracy or completeness of the underlying beneficial-ownership information. ECCTA 2023 (in force from 4 March 2024) introduced enhanced verification requirements for PSC and UBO data filed at Companies House — cross-check filings after any disclosure review.

FAQ

Can I share a pseudonymised UBO disclosure with an overseas correspondent bank?

No. Correspondent banks require the actual identities of beneficial owners for their own AML obligations. Share the re-identified version for formal AML submissions.

How does the tool handle complex multi-tier ownership structures?

The engine processes all individuals named in the ownership chain, regardless of the number of tiers. Each natural person receives a unique pseudonym; the ownership percentages and structural relationships between entities are preserved.

Is this tool suitable for use in the context of sanctions screening?

Sanctions screening must be conducted against the real identities of beneficial owners, not pseudonymised versions. Use this tool only for the internal review of disclosure methodology, not for sanctions checks.

Does the Bribery Act 2010 require beneficial-owner disclosures to be retained?

The Bribery Act 2010 requires adequate procedures but does not itself mandate a specific retention period for UBO disclosures. Retention requirements may arise under anti-money-laundering regulations — obtain specialist compliance advice. According to the Limitation Act 1980, civil claims may arise within 6 years of breach, so retain mapping keys for at least that period.

How does ECCTA 2023 affect beneficial-owner disclosure obligations?

According to ECCTA 2023, from November 2023 onwards Companies House can query and reject inaccurate information about PSCs and beneficial owners. The identification doctrine reform also means that offences committed by a senior manager acting within the scope of their authority can now be attributed to the corporate entity. Beneficial-owner disclosure documents used in regulatory submissions must contain real identities; pseudonymised versions are for internal compliance review only.

Commercial Contracts

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 company HQ is in Saarbrücken, Germany. Our servers run in Hetzner's Falkenstein datacenter.

Hetzner holds 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.