Pseudonymising DBS Enhanced Certificates – UK GDPR-compliant anonymisation per Police Act 1997 s.113B

A DBS Enhanced certificate issued under Police Act 1997 s.113B includes all Standard certificate content plus additional police-held suitability information considered relevant by the chief constable. anonym.legal pseudonymises the subject's personal identifiers across both the standard conviction data and the locally-held intelligence section, enabling reviewers to assess suitability without unnecessary personal-data exposure.

When this applies

This task applies when a DBS Enhanced certificate is reviewed by safeguarding leads, HR professionals, or legal advisers in regulated sectors — such as education, healthcare, or childcare — who require sight of both conviction data and police suitability information but not the subject's personal identifiers.

  1. Upload the DBS Enhanced certificate to anonym.legal.
  2. The engine identifies and pseudonymises the subject's name, date of birth, address, and DBS reference number in the certificate header.
  3. Conviction and caution entries are preserved with their offence descriptions, dates, and sentencing outcomes in clear text.
  4. Any locally-held police suitability information in the enhanced section is preserved; the subject's personal identifiers within that section are also pseudonymised.
  5. A reversible mapping table is generated with UK data residency.
  6. The pseudonymised certificate is released for safeguarding or HR review; the original is restored via the mapping key before any formal suitability decision.

What you provide

  • DBS Enhanced certificate (PDF or high-quality scan)
  • Role description and regulated-activity category (to contextualise the review)

Limitations & cautions

  • The pseudonymised certificate must not be used as the basis for a formal regulated-activity suitability decision — the original must be referenced.
  • Police suitability information in the enhanced section may itself identify third parties; the tool pseudonymises the subject's data but reviewers should apply professional judgement to third-party references.
  • The tool does not advise on the legal threshold for relevance of locally-held police information — obtain specialist safeguarding or legal advice.

FAQ

Does the enhanced certificate's police suitability section require special handling under UK GDPR?

Yes. Information in the enhanced section constitutes criminal-conviction data under UK GDPR Art. 10 and is processed under DPA 2018 Part 3 (law-enforcement regime) where competent authorities are involved. anonym.legal applies pseudonymisation to the subject's identifiers in both sections under a consistent framework.

Can I use the pseudonymised enhanced certificate for a barred-list check cross-reference?

No. Barred-list checks require the real identity of the subject. The pseudonymised certificate is for reviewing the scope of disclosed conviction and suitability information only.

How does the engine handle third-party names mentioned in the police suitability section?

Third-party names in the suitability section that can be identified as natural persons are flagged for review. You can elect to pseudonymise them in addition to the subject's data.

Is Police Act 1997 s.113B the only provision for enhanced certificates?

Section 113B is the principal provision for enhanced criminal record certificates. Section 113BA provides for additional suitability information relating to children and vulnerable adults — that variant is also supported by this workflow.

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.