Anonymising Customer Screening Hit Files for Oversight – UK GDPR-compliant anonymisation per Money Laundering Regulations 2017

Customer screening-hit files document the results of sanctions and adverse-media screening, recording the customer's name, the hit description, and the disposition decision. anonym.legal pseudonymises the customer identifiers in these files so compliance oversight teams and auditors can review hit-management quality and escalation adequacy without processing the screened customer's personal data.

When this applies

This task applies when screening-hit files are reviewed by second-line compliance, internal audit, or external assurance teams assessing the firm's hit-management procedures and escalation decisions, and those reviewers require the procedural record rather than the customer's identity.

  1. Upload the screening-hit record or alert-disposition file to anonym.legal.
  2. The engine identifies the customer's name, any associated individual references, and the specific hit descriptor that would identify the screened party.
  3. Each individual is pseudonymised consistently; the hit category (sanctions list type, adverse-media source category), disposition outcome, and escalation pathway remain in clear text.
  4. Disposition rationale, analyst notes, and approval-authority sign-off are preserved in their entirety.
  5. A reversible mapping table is produced with UK/EU data residency.
  6. Release the pseudonymised record for oversight review; restore originals before any regulatory or correspondent-bank production.

What you provide

  • Screening-hit alert or disposition record
  • Escalation memorandum naming the customer and hit details
  • Senior management approval sign-off (if applicable)

Limitations & cautions

  • Live sanctions screening must be conducted against the real identities of customers; the pseudonymised hit file is for retrospective procedural review only.
  • The tool does not determine whether a screening hit constitutes a true match or a false positive; that assessment requires specialist compliance judgement.
  • Adverse-media sources referenced in the hit descriptor are preserved at category level; the specific article or source that would identify the customer is pseudonymised.

FAQ

Can pseudonymised screening-hit files be used in a thematic review of our hit-management process?

Yes. Pseudonymised files that preserve the hit category, disposition rationale, and escalation pathway are suitable for thematic review of procedural quality without exposing individual customer data.

How are false-positive dispositions recorded in the pseudonymised file?

The disposition outcome (e.g. false positive, true match, escalated) and the rationale are preserved in clear text. Only the customer's identifying information is pseudonymised.

Does the tool handle screening hits that involve both an individual and a corporate entity?

Named natural persons are pseudonymised. The corporate entity name is preserved unless you flag it for pseudonymisation, as corporate names are generally not personal data under UK GDPR.

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.