Pseudonymising Conditional Caution Paperwork – UK GDPR-compliant anonymisation per Criminal Justice Act 2003

A conditional caution imposes rehabilitative or reparative conditions on the cautioned individual and creates a criminal record entry that may lead to prosecution if conditions are breached. anonym.legal pseudonymises the individual's personal identifiers across the caution notice, conditions schedule, and compliance monitoring records, allowing legal advisers to review the conditions' scope and compliance history without unnecessary personal-data exposure.

When this applies

This task applies when conditional caution paperwork — including the conditions schedule and any compliance correspondence — is reviewed by defence solicitors, CPS decision-makers, or diversion-scheme coordinators who require sight of the conditions and compliance history but not the individual's personal identifiers.

  1. Upload the conditional caution notice, conditions schedule, and any compliance correspondence as a batch.
  2. The engine identifies the individual's name, date of birth, address, and reference numbers across all documents.
  3. Personal identifiers are pseudonymised consistently across the full batch; conditions text, compliance dates, and breach records are preserved.
  4. Any named third-party victims or programme coordinators in the conditions schedule are flagged; you may elect to pseudonymise those as well.
  5. A reversible mapping table is generated with UK data residency.
  6. The pseudonymised batch is released for legal or scheme review; originals are restored before any prosecution or enforcement decision.

What you provide

  • Conditional caution notice
  • Conditions schedule (including any rehabilitative or reparative conditions)
  • Compliance monitoring correspondence or sign-off records

Limitations & cautions

  • Breach of a conditional caution may result in prosecution — formal prosecution decisions must be taken by reference to the identified original documents, not the pseudonymised versions.
  • Third-party victim details in conditions schedules are sensitive and subject to victim-privacy obligations; treat pseudonymisation of victim data as a separate decision requiring appropriate authorisation.

FAQ

Does a conditional caution appear on a DBS Standard or Enhanced certificate?

Yes. A conditional caution creates a criminal record entry and may appear on DBS Standard and Enhanced certificates subject to filtering rules. The pseudonymised paperwork allows scope review without exposing the individual's identity.

Can I process the conditions schedule without the caution notice?

Yes. Individual documents can be processed in isolation, but processing the full batch ensures that the individual's identifiers are pseudonymised consistently across all related documents.

How does the engine handle named victim references in the conditions schedule?

Named victims are detected as natural persons and flagged for your review. You control whether victim identifiers are pseudonymised or preserved, depending on the purpose of the review.

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.