Standard Disclosure under CPR Part 31: redact non-party identifiers – UK GDPR-compliant anonymisation per CPR Part 31

Standard disclosure under CPR Part 31 requires each party to disclose documents on which it relies, adverse documents, and documents that support another party's case; anonym.legal pseudonymises non-party names, addresses, and contact details across the entire disclosure list and accompanying documents, preserving the substantive evidential narrative while satisfying UK GDPR obligations.

When this applies

Applies when the court has ordered standard disclosure under CPR Part 31 and the solicitor must inspect, list, and share documents that contain third-party personal data before exchange of lists.

  1. Upload the full disclosure bundle — typically a List of Documents (N265) and the underlying documents — in PDF or DOCX format.
  2. anonym.legal identifies non-party names, addresses, telephone numbers, email addresses, and other personal identifiers across all uploaded files using over 285 entity types.
  3. Each non-party is assigned a consistent pseudonym (e.g. 'Witness A', 'Third Party B') throughout the entire bundle so cross-references remain coherent.
  4. Substantive evidential content — dates, financial figures, contract terms, and the factual narrative — is preserved in full.
  5. A reversible pseudonym-to-real-name mapping is stored in an encrypted table with EU data residency.
  6. Review the pseudonymised bundle before exchange; re-identify with the stored key when producing the final disclosed set for the other side.

What you provide

  • List of Documents (Form N265) or equivalent schedule
  • Underlying documents to be disclosed (PDF or DOCX)
  • List of party names to retain in clear (claimant, defendant, legal representatives)

Limitations & cautions

  • anonym.legal does not assess whether a document is privileged or falls within a CPR Part 31 exception — legal privilege review remains the solicitor's responsibility.
  • The proportionality assessment under CPR Part 31.5 and decisions on withholding must be made by a qualified lawyer.
  • Re-identification requires secure retention of the mapping key; loss of the key renders re-identification impossible.

FAQ

Does anonym.legal automatically distinguish party names from non-party names?

You provide a list of party names and legal-representative names to retain in clear; the engine treats all other personal identifiers as non-party data subject to pseudonymisation.

Can I use the pseudonymised bundle for the court bundle as well?

No — the court bundle should contain full names unless the court has made an anonymity order. Use the re-identification step to restore clear names before filing with the court.

Will the N265 list remain structurally intact?

Yes, anonym.legal processes DOCX and PDF without altering document structure, pagination, or formatting — only personal-identifier text is replaced.

Does processing comply with UK GDPR Article 5?

Pseudonymisation under UK GDPR Article 5(1)(e) is a recognised data-minimisation technique. anonym.legal applies reversible pseudonymisation with EU data residency, consistent with data-minimisation and storage-limitation principles.

What if a document contains special-category data such as medical records?

Special-category data (UK GDPR Article 9) is identified and pseudonymised with the same approach. You should note the special-category nature in your data-processing record and apply appropriate access controls to the mapping key.

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