Anonymising Criminal-Records DSAR Responses – UK GDPR-compliant anonymisation per DPA 2018

A data subject access request (DSAR) made to a law-enforcement authority under DPA 2018 Part 3 may yield police records, custody records, intelligence logs, and criminal history data that collectively constitute the subject's full criminal-records profile. anonym.legal pseudonymises third-party personal data within the DSAR response before sharing with the data subject's legal adviser, satisfying third-party redaction obligations without losing substantive content relevant to the data subject.

When this applies

This task applies when a DSAR response received from a law-enforcement authority under DPA 2018 Part 3 is reviewed by a solicitor acting for the data subject, and the response contains third-party personal data that must be redacted before the full response can be shared with the client.

  1. Upload the DSAR response package (all documents disclosed by the law-enforcement authority).
  2. The engine distinguishes the data subject's own identifiers from third-party personal data appearing in the disclosed records.
  3. Third-party personal identifiers — named officers, co-suspects, informants, or witnesses — are pseudonymised; the data subject's own data is preserved as the subject of the DSAR.
  4. The substantive content of each record — dates, events, and disposal outcomes — is preserved in clear text.
  5. A reversible mapping table covering third-party identifiers is produced with UK data residency.
  6. The pseudonymised response is provided to the data subject or their legal adviser; the mapping table is retained by the controller for regulatory purposes.

What you provide

  • DSAR response package (all disclosed documents)
  • Controller's covering letter or schedule of disclosed records
  • Any third-party redaction schedule already applied by the disclosing authority

Limitations & cautions

  • DPA 2018 Part 3 allows law-enforcement controllers to withhold third-party data on specified grounds; the tool pseudonymises third-party data rather than redacting it, which is a distinct approach — confirm the appropriate standard with specialist data-protection counsel.
  • Intelligence records may contain third-party data whose pseudonymisation itself could be operationally sensitive — consult the disclosing authority's data-protection officer before sharing even pseudonymised intelligence content.

FAQ

Does DPA 2018 Part 3 give individuals the right to access their criminal records held by police?

DPA 2018 Part 3 provides a right of access to personal data processed by competent authorities for law-enforcement purposes, subject to exemptions. The scope of any particular DSAR response depends on the exemptions applied by the disclosing authority.

Can a solicitor share the full DSAR response with their client before third-party data is redacted?

Sharing third-party personal data from a DSAR response with the data subject may breach UK GDPR obligations to third parties. Pseudonymising or redacting third-party identifiers before sharing is standard practice — this workflow automates the pseudonymisation step.

Is the pseudonymisation of third-party data in a DSAR response reversible?

Yes. The mapping table allows full re-identification of third-party pseudonyms if required for regulatory purposes or legal proceedings. Access to the mapping table should be strictly controlled.

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.