Pseudonymising EDD Files for Politically Exposed Persons – UK GDPR-compliant anonymisation per Money Laundering Regulations 2017

Enhanced due diligence (EDD) files for politically exposed persons (PEPs) contain detailed personal profiles, source-of-wealth evidence, and senior management approval records that are especially sensitive under the Money Laundering Regulations 2017. anonym.legal pseudonymises those personal identifiers so compliance reviewers can assess EDD quality and approval adequacy without processing the PEP's personal data during oversight.

When this applies

This task applies when EDD files relating to PEPs are reviewed by second-line compliance oversight, internal audit, or external consultants assessing the adequacy of the firm's enhanced-due-diligence procedures, and those reviewers require the procedural record rather than the customer's identity.

  1. Upload the EDD file, including any source-of-wealth questionnaire, adverse-media summary, and senior management approval record.
  2. The engine identifies the PEP's name, political office or role, nationality, date of birth, family-member and close-associate references, and any other personal identifiers.
  3. Each individual — the PEP, associated family members, and close associates — is pseudonymised consistently across all documents in the pack.
  4. Source-of-wealth categories, political office type, risk level, approval authority tier, and procedural timestamps remain in clear text.
  5. A reversible mapping table is produced with UK/EU data residency.
  6. Release the pseudonymised EDD pack for oversight review; restore originals before any regulatory submission.

What you provide

  • EDD decision record and approval sign-off
  • Source-of-wealth questionnaire and supporting evidence summary
  • Adverse-media screening summary naming the PEP
  • Senior management approval memorandum

Limitations & cautions

  • The tool pseudonymises personal data in EDD files but does not assess whether the EDD procedure meets the standard required for the specific PEP risk level.
  • Adverse-media screening must be conducted against the real identity of the PEP; the pseudonymised file is for procedural review only.
  • Family-member and close-associate references are pseudonymised; the procedural rationale for including them as connected persons is preserved.

FAQ

Are close associates and family members pseudonymised separately from the PEP?

Yes. Each individual connected to the PEP is assigned a distinct pseudonym. The relationship label (e.g. 'close associate', 'family member') is preserved to maintain the procedural context.

Can the pseudonymised EDD file be used for regulatory reporting?

No. Regulatory submissions and SAR disclosures require the real identities of individuals. The pseudonymised file is strictly for internal procedural review and training.

How does the engine handle political office titles that may identify the individual?

Political office type is preserved (e.g. 'senior government minister', 'domestic PEP') but the specific role title that would identify the individual may be generalised to prevent re-identification. You can configure the generalisation level before processing.

Does the tool cover former PEPs as well as current ones?

Yes. Former PEP status and the period since leaving office are preserved as procedural context; the individual's identity is pseudonymised in the same way.

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.