Anonymising Family Judgments for Publication (FPR r.27.11) – UK GDPR-compliant anonymisation per Family Procedure Rules 2010

Family Procedure Rules 2010 rule 27.11 permits accredited media and legal bloggers to attend family hearings and publish reports, while requiring that parties, children, and other individuals are not identified. anonym.legal applies systematic pseudonymisation across draft judgments so that judges, clerks, and journalists can prepare compliant published versions efficiently and reliably.

When this applies

This task applies when a family-court judge or their clerk is preparing a judgment for publication on the Judiciary website or BAILII, and wishes to apply consistent pseudonymisation across all named individuals before the judgment is released to accredited reporters or published publicly.

  1. Upload the draft or approved judgment to anonym.legal.
  2. The engine identifies parties, children, named witnesses, experts, solicitors, and any other natural persons mentioned in the judgment.
  3. Each individual receives a consistent pseudonym (e.g. 'Mother', 'Father', 'Child A') aligned with the standard publication conventions for family judgments.
  4. Legal analysis, statutory citations, case authorities, and the ratio decidendi are preserved in full.
  5. A reversible mapping table is produced so the judge or clerk can verify the pseudonymised text against the original before authorising publication.
  6. The pseudonymised judgment is ready for submission to the Judiciary's publication team or BAILII.

What you provide

  • Draft or approved family-court judgment (PDF or DOCX)
  • List of parties' pseudonym preferences if the judge has specified conventions
  • Any reporting restriction order that defines the anonymisation scope

Limitations & cautions

  • The judge retains responsibility for approving the pseudonymised version before publication; anonym.legal provides a systematic first pass, not a final editorial decision.
  • Reporting restriction orders may require specific pseudonymisation conventions that differ from the engine's defaults — review and adjust using the mapping key.
  • Case citation references and statutory citations are not pseudonymised and remain as published.

FAQ

Does the engine follow the 'Mother / Father / Child A' convention for family judgments?

By default the engine applies role-based pseudonyms where a clear familial role is identified. The judge can review and adjust the pseudonym mapping table to align with preferred publication conventions.

Can the pseudonymised judgment be submitted directly to BAILII?

The pseudonymised output provides a systematic starting point. The judge or court clerk should review and approve the pseudonymised text before submission, as the publishing decision remains the court's responsibility.

What if the judgment refers to a named expert whose anonymisation would be disproportionate?

Expert witnesses who are not parties or children may legitimately be named in published judgments. Flag any individuals who should retain their real name — the mapping table allows selective re-identification before publication.

Is a reporting restriction order itself pseudonymised by the engine?

No. The reporting restriction order defines the scope of anonymisation; it is used as an input, not pseudonymised. Orders restricting publication of parties' details are applied by the engine when processing the judgment.

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.