Redacting DBS Standard Certificates Before Legal Review – UK GDPR-compliant anonymisation per Police Act 1997 s.113A

A DBS Standard certificate issued under Police Act 1997 s.113A lists spent and unspent convictions, cautions, reprimands, and warnings held on the Police National Computer. anonym.legal pseudonymises the subject's personal identifiers — name, date of birth, and reference number — so employment advisers can assess the disclosure's scope without processing unnecessary personal data.

When this applies

This task applies when a DBS Standard certificate is reviewed by HR professionals, legal advisers, or compliance officers assessing suitability for a role, and those reviewers require sight of the conviction and caution details but not the subject's personal identifiers.

  1. Upload the DBS Standard certificate (PDF or scan) to anonym.legal.
  2. The engine identifies the subject's name, date of birth, address, and DBS reference number across the certificate header and body.
  3. Each personal identifier is pseudonymised consistently; conviction details, caution types, dates of offence, and sentencing outcomes are preserved in clear text.
  4. The issuing authority details and certificate date remain intact to confirm authenticity context.
  5. A reversible mapping table is generated and stored with UK data residency, allowing full re-identification when the original is required.
  6. Download the pseudonymised certificate for HR or legal review; use the mapping key to restore the original before any formal employment decision or regulatory submission.

What you provide

  • DBS Standard certificate (PDF or high-quality scan)
  • Role description or vetting context (to guide review scope)

Limitations & cautions

  • The pseudonymised certificate is a working copy for review only; formal employment decisions must reference the original identified certificate.
  • Heavily degraded scans may require OCR pre-processing before entity detection achieves full coverage.
  • The tool pseudonymises personal data but does not advise on the legal significance of disclosed offences for the specific role — obtain specialist employment-law advice.

FAQ

Does pseudonymising the DBS certificate affect its evidential value?

The pseudonymised copy is for internal HR or legal review only. The original certificate retains its evidential value and should be used for any formal employment decision, regulatory submission, or appeal.

Can I share the pseudonymised certificate with an external employment adviser?

Yes. The pseudonymised version does not contain the subject's personal data within the meaning of UK GDPR Art. 4(1), so data-minimisation requirements are satisfied for preliminary advice on the scope of disclosed offences.

Are spent convictions treated differently from unspent convictions on a Standard certificate?

The engine preserves all conviction and caution entries regardless of spent or unspent status; only the subject's personal identifiers are pseudonymised. The reviewer can assess the disclosure scope without knowing the individual's identity.

Is this suitable for bulk-processing multiple DBS certificates?

Yes. Batch processing is supported. Each certificate is processed individually, and subjects receive distinct pseudonyms to prevent cross-subject confusion.

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.