Anonymising Foreign Conviction Certificates – UK GDPR-compliant anonymisation per UK GDPR Art. 10

Foreign criminal conviction certificates — required from overseas jurisdictions for employment vetting in regulated UK sectors — carry criminal-conviction data from non-UK legal systems that falls under UK GDPR Art. 10 when processed in the UK. anonym.legal pseudonymises the subject's personal identifiers across translated and original foreign conviction certificates, enabling UK vetting officers to assess the disclosure scope without unnecessary personal-data retention.

When this applies

This task applies when foreign criminal conviction certificates are reviewed by UK vetting officers, HR professionals, or legal advisers assessing the relevance of overseas criminal records for regulated employment in the UK, and those reviewers require the conviction details but not the subject's personal identifiers.

  1. Upload the foreign conviction certificate and any certified translation together as a batch.
  2. The engine identifies the subject's name (in original and transliterated forms), date of birth, nationality, and certificate reference number.
  3. Personal identifiers are pseudonymised consistently across both the original and the translation.
  4. Offence descriptions, court names, conviction dates, and sentencing information are preserved in clear text.
  5. A reversible mapping table is produced with UK data residency.
  6. The pseudonymised certificate and translation are released for vetting review; originals are restored for any formal employment decision.

What you provide

  • Foreign criminal conviction certificate (original language)
  • Certified translation (if available)
  • Issuing-country context notes (to assist offence-category assessment)

Limitations & cautions

  • The legal equivalence of foreign offences to UK offences is a specialist legal question requiring expert advice — the tool pseudonymises personal data but does not assess offence equivalence or rehabilitation status under the ROA 1974.
  • Some countries' criminal record certificates use national identification numbers as primary identifiers — these are detected and pseudonymised alongside the subject's name and date of birth.

FAQ

Does UK GDPR Art. 10 apply to foreign conviction data processed in the UK?

Yes. UK GDPR Art. 10 applies to criminal-conviction data regardless of the jurisdiction in which the offence was committed, provided the processing occurs in the UK or relates to persons in the UK.

How does the tool handle certificates in non-Latin scripts?

The engine supports a wide range of scripts and character sets. Transliterated versions and certified translations are processed alongside originals; personal identifiers are detected and pseudonymised in all versions consistently.

Can a pseudonymised foreign conviction certificate be used for a DBS application?

DBS applications require the subject's real identity. The pseudonymised certificate is for the vetting officer's preliminary legal review only; re-identify using the mapping key before submitting any formal application.

Criminal Records

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.