Anonymising Spent-Conviction Disclosures (ROA 1974) – UK GDPR-compliant anonymisation per Rehabilitation of Offenders Act 1974 s.4

The Rehabilitation of Offenders Act 1974 s.4 bars employers and others from requiring disclosure of spent convictions in most contexts, though legal exceptions apply for DBS-regulated roles. anonym.legal pseudonymises the individual's personal identifiers in spent-conviction disclosure documents, allowing legal teams to verify ROA 1974 compliance and the applicability of exceptions without unnecessary personal-data retention.

When this applies

This task applies when spent-conviction disclosure documentation — including self-disclosure forms, subject access data, or ROA 1974 exception correspondence — is reviewed by employment lawyers, HR compliance officers, or licensing authorities assessing whether a disclosure obligation lawfully applies.

  1. Upload the spent-conviction disclosure document or ROA 1974 exception correspondence.
  2. The engine identifies the individual's name, date of birth, and any reference numbers across the document.
  3. Personal identifiers are pseudonymised; offence descriptions, conviction dates, rehabilitation periods, and exception-order references are preserved.
  4. The spent or unspent status and the applicable rehabilitation period are preserved as stated in the document.
  5. A reversible mapping table is produced with UK data residency.
  6. The pseudonymised document is released for legal review; the original is restored before any formal employment or licensing decision.

What you provide

  • Spent-conviction disclosure form or subject access response
  • Rehabilitation of Offenders Act 1974 exception-order documentation (if applicable)
  • Role description and sector context (to assess which exceptions may apply)

Limitations & cautions

  • Whether a conviction is spent depends on the rehabilitation period applicable to the sentence imposed — the tool preserves the stated rehabilitation status but does not independently calculate rehabilitation periods under the ROA 1974 as amended.
  • The ROA 1974 exceptions applicable to DBS-regulated roles are complex; obtain specialist legal advice on the interaction between s.4 and the relevant Exceptions Order.

FAQ

Does the Rehabilitation of Offenders Act 1974 s.4 apply to DBS-regulated roles?

Section 4 of the ROA 1974 is modified for DBS-regulated roles by the Rehabilitation of Offenders Act 1974 (Exceptions) Order 1975, which requires disclosure of spent convictions in many regulated sectors. The applicable exception must be confirmed by legal advice.

Can a pseudonymised spent-conviction disclosure be used for an ROA 1974 s.4 compliance assessment?

Yes. The pseudonymised document preserves the conviction details, rehabilitation period, and any exception references needed for a legal compliance assessment — without exposing the individual's identity during the review process.

How does the tool handle convictions that become spent mid-review?

The tool preserves the rehabilitation status as stated in the uploaded document. If the spent date falls during the review period, note the date and re-assess the disclosure obligation with updated status.

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.