Anonymising Materials for Transparency Pilot Reporting – UK GDPR-compliant anonymisation per FPR PD 36J

The Family Court Transparency Pilot under FPR PD 36J allows accredited journalists and legal bloggers to observe family hearings and publish reports, subject to strict anonymisation obligations that protect parties, children, and other individuals. anonym.legal supports pilot participants and court staff in preparing compliant anonymised case summaries, position statements, and judgments while preserving the legal and welfare narrative.

When this applies

This task applies when a judge, legal journalist, or court-appointed transparency reporter is preparing a case report or summary for publication under the FPR PD 36J Transparency Pilot, and requires systematic pseudonymisation of all named individuals before the report is published.

  1. Upload the draft case report, position statement extract, or judgment summary intended for publication.
  2. The engine identifies all named parties, children, witnesses, and professionals in the document.
  3. Each individual receives a consistent pseudonym aligned with standard transparency-pilot reporting conventions (e.g. 'the Father', 'Child B', 'the Local Authority').
  4. Legal analysis, statutory references, procedural history, and welfare outcomes are preserved in full.
  5. A reversible mapping table is produced so the reporter or clerk can verify the pseudonymised text.
  6. The pseudonymised report is ready for editorial review and publication in compliance with FPR PD 36J.

What you provide

  • Draft case report or court summary
  • Approved or approved-in-principle judgment (if being published in full)
  • Any reporting restriction order specifying anonymisation requirements

Limitations & cautions

  • FPR PD 36J reporting requires compliance with any specific reporting restriction order made in the case — review the order before relying solely on the engine's default pseudonymisation.
  • The journalist or reporter retains editorial responsibility for ensuring the published account is fair, accurate, and compliant with the Transparency Pilot guidelines.
  • anonym.legal provides a systematic anonymisation pass; the reviewing journalist or clerk should verify all pseudonymised content before publication.

FAQ

Does FPR PD 36J permit naming the local authority in public-law proceedings?

Whether the local authority can be named depends on the specific reporting restrictions in the case. Local authority names are pseudonymised by default; the reporter can selectively re-identify them using the mapping table if permissible.

Are expert witnesses' names pseudonymised in transparency pilot reports?

Expert witnesses who are identified by name in the judgment may be named in the published report unless a specific reporting restriction applies. Flag experts for selective re-identification via the mapping table where appropriate.

Can accredited journalists use this tool to prepare their own case reports?

Yes. The tool is suitable for accredited journalists and legal bloggers attending under FPR PD 36J who wish to prepare a compliant anonymised case report. The journalist retains full editorial responsibility for compliance.

How does the tool handle case reference numbers in transparency pilot reports?

Case reference numbers are not personal data and are preserved. Only the personal data of named individuals is pseudonymised.

Family Law

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.