Anonymising Police National Computer Record Extracts – UK GDPR-compliant anonymisation per DPA 2018

Police National Computer (PNC) record extracts compile an individual's full criminal history as recorded by UK police forces, including arrests, charges, convictions, cautions, and intelligence markers. anonym.legal pseudonymises the subject's personal identifiers across PNC printouts, enabling legal teams and custody staff to review the criminal history without direct personal-data exposure.

When this applies

This task applies when a PNC record extract is shared with defence solicitors, pre-sentence report authors, or legal-aid auditors who require sight of the full criminal history for case preparation but have no legitimate need to retain the subject's personal identifiers in their working documents.

  1. Upload the PNC extract (PDF, printout scan, or structured text export) to anonym.legal.
  2. The engine identifies all personal identifiers: full name, aliases, date of birth, PNC identifier, and any addresses held on record.
  3. Each identifier is pseudonymised consistently across all pages of the extract.
  4. Offence codes, court outcomes, disposal dates, and intelligence markers are preserved in clear text.
  5. A reversible mapping table is produced with UK data residency.
  6. The pseudonymised extract is released for legal or case-management review; originals are restored via the mapping key before submission to court or regulatory bodies.

What you provide

  • PNC record extract (PDF, printout scan, or text export)
  • Case reference number (to link the pseudonymised output to the correct matter)

Limitations & cautions

  • PNC extracts are law-enforcement data processed under DPA 2018 Part 3; their disclosure is strictly controlled. Ensure the recipient holds the appropriate authorisation before sharing even the pseudonymised version.
  • Intelligence markers on the PNC may themselves contain sensitive operational information; review sharing decisions with the disclosing force's data-protection officer.
  • The tool does not advise on the admissibility or weight of PNC data in court proceedings — obtain specialist criminal-law advice.

FAQ

Is a PNC extract personal data under UK GDPR or DPA 2018?

PNC data is processed by competent authorities for law-enforcement purposes and falls primarily under DPA 2018 Part 3 rather than UK GDPR. anonym.legal applies pseudonymisation consistent with both regimes.

Can the pseudonymised PNC extract be used in a pre-sentence report?

The pseudonymised version is suitable for drafting and peer-review purposes. The finalised pre-sentence report submitted to court must contain the subject's real identity and must use the re-identified version.

How does the engine handle multiple aliases recorded on the PNC?

Each alias is detected and linked to the same subject record, receiving the same pseudonym. The alias field is preserved to indicate multiple identities were recorded, without disclosing the real names.

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.