Anonymising Sex Offender Register Notification Documents – UK GDPR-compliant anonymisation per Sexual Offences Act 2003

Sex Offender Register notification documents issued under Sexual Offences Act 2003 Part 2 record the notifying offender's registration obligations, address details, and notification compliance history — among the most sensitive categories of criminal-conviction data. anonym.legal pseudonymises personal identifiers in these documents, enabling multi-agency public protection training and legal review without directly exposing the offender's personal data.

When this applies

This task applies when Sex Offender Register notification documents or MAPPA case records are used in multi-agency training, legal-aid supervision, or academic research on public-protection frameworks, and the users require the procedural and compliance content but not the offender's personal identifiers.

  1. Upload the notification document, registration confirmation, or MAPPA case summary.
  2. The engine identifies the offender's name, date of birth, address, and registration reference.
  3. All personal identifiers are pseudonymised; notification obligations, reporting periods, compliance records, and risk-categorisation information are preserved.
  4. Multi-agency case references are preserved to maintain operational context without disclosing the offender's identity.
  5. A reversible mapping table is produced with UK data residency under strict access controls.
  6. The pseudonymised document is released for training or legal-review use under appropriate access restrictions.

What you provide

  • Sex Offender Register notification document or MAPPA case summary
  • Notification-compliance history or police check records (if reviewing compliance context)

Limitations & cautions

  • Sex Offender Register data is among the most sensitive categories of personal data — even pseudonymised versions should be subject to strict access controls and shared only within authorised training or legal-review cohorts.
  • MAPPA management involves multi-agency risk assessment decisions that require specialist safeguarding and probation expertise; the tool provides data-minimisation for training review but does not advise on risk-management decisions.
  • Re-identification capability must be strictly controlled given the nature of this data — mapping-table access should be limited to the minimum number of authorised personnel.

FAQ

Does Sexual Offences Act 2003 Part 2 restrict sharing of notification documents?

Sexual Offences Act 2003 Part 2 imposes obligations on offenders to notify police; it does not itself restrict training use of pseudonymised notification documents. However, operational MAPPA protocols and DPA 2018 obligations govern sharing decisions — obtain appropriate MAPPA lead advice.

Can a pseudonymised notification document be used in MAPPA level-3 training?

Yes, subject to your MAPPA lead authority's data-sharing protocols. Pseudonymised documents satisfy the data-minimisation principle for training purposes, but the MAPPA lead must authorise the training use of even pseudonymised materials.

Are the offender's notification conditions preserved in the pseudonymised document?

Yes. Notification obligations, reporting periods, travel restrictions, and compliance conditions are all preserved in clear text — only the offender's personal identifiers are pseudonymised.

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.