Non-party access under CPR 5.4C: prepare redacted court file copy – UK GDPR-compliant anonymisation per CPR Part 5

CPR 5.4C is the rule that governs non-party access to statements of case and other documents on the court file, introduced under the Civil Procedure Rules 1998; anonym.legal pseudonymises third-party identifiers in documents released to non-parties — according to HMCTS, over 1.4 million claims were issued in 2023 and CPR 5.4C requests arise regularly from journalists, researchers, and interested persons.

When this applies

Applies when a solicitor receives a CPR 5.4C request from a non-party journalist, researcher, or interested person and must produce a redacted version of a statement of case. Data shows that CPR 5.4C requests increased significantly after 2018; the Senior Courts Act 1981 s.11 empowers courts to restrict publication in specific cases.

  1. Identify the statement of case or court document requested under CPR 5.4C.
  2. Upload the document in DOCX or PDF format.
  3. Configure which party names are permissible in the released version (typically the named parties remain, but witness and third-party identifiers are redacted).
  4. anonym.legal pseudonymises third-party and witness names and contact details as appropriate.
  5. Review the output to ensure any court-ordered anonymisation directions are respected.
  6. Release the pseudonymised or redacted version to the requesting non-party.

What you provide

  • Statement of case or court document subject to CPR 5.4C request (DOCX or PDF)
  • Any court order limiting disclosure or imposing anonymity
  • Configuration specifying which names may remain in clear

Limitations & cautions

  • Whether to comply with a CPR 5.4C request, and on what terms, is a legal decision for the solicitor and the court — anonym.legal assists with the technical redaction only.
  • Court-ordered anonymity under the Senior Courts Act 1981 s.11 must be respected separately — the tool does not parse court orders automatically.
  • Release of personal data to non-parties without proper legal basis can attract UK GDPR fines of up to £17.5 million or 4% of global annual turnover under DPA 2018 s.157.

FAQ

Does CPR 5.4C apply to all categories of documents on the court file?

CPR 5.4C grants non-parties a right to obtain copies of statements of case from the court file. Other documents may require a court order. According to HMCTS guidance, legal advice should be taken on the scope of any particular request — this applies across all 1.4 million annual claims.

What if the court has made an anonymity order under Senior Courts Act 1981 s.11?

A court anonymity order under Senior Courts Act 1981 s.11 takes precedence. You must ensure the released document complies with the precise terms of the order — check the order carefully before releasing any version.

Can the pseudonymised version be published by a journalist or researcher?

Whether publication is appropriate is a matter for the journalist and the law — anonym.legal produces a technically redacted document but does not advise on the legality of publication. Research shows that UK media organisations have invoked CPR 5.4C in hundreds of cases since 2010.

Civil Litigation

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 company HQ is in Saarbrücken, Germany. Our servers run in Hetzner's Falkenstein datacenter.

Hetzner holds 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.