Specific Disclosure Application under CPR Part 31: prepare redacted exhibit – UK GDPR-compliant anonymisation per CPR Part 31

A specific disclosure application under CPR Part 31 asks the court to order production of particular documents not caught by standard disclosure; anonym.legal redacts third-party personal data from the draft application witness statement and exhibits, enabling solicitors to present the documentary evidence to the court without unnecessarily exposing non-party identifiers.

When this applies

Applies when a party applies to the court for an order compelling the other side to disclose specific documents or categories of documents, and the supporting evidence includes third-party personal data.

  1. Upload the draft application notice and any supporting witness statement or exhibit file.
  2. anonym.legal identifies third-party names, addresses, and identifiers in the supporting materials.
  3. Each third party is pseudonymised consistently across the application and all exhibits.
  4. Factual and legal argument is preserved without alteration so the application remains coherent.
  5. An encrypted mapping table is stored with EU data residency for re-identification when required.
  6. Produce the filing-ready version by re-identifying party names only; retain pseudonymised versions for internal review.

What you provide

  • Draft application notice (Form N244 or equivalent)
  • Supporting witness statement
  • Exhibit documents referenced in the witness statement

Limitations & cautions

  • The merits of the specific disclosure application and the legal test under CPR Part 31 must be assessed by a qualified solicitor or counsel.
  • anonym.legal does not redact information that is genuinely part of the legal argument — only standalone personal-identifier fields.

FAQ

Can I pseudonymise the exhibits separately from the witness statement?

Yes, upload each document individually or as a batch; the engine assigns consistent pseudonyms across all documents in a single processing session.

What CPR sub-rules govern specific disclosure?

CPR Part 31 governs disclosure generally; the court's power to order specific disclosure flows from Part 31 itself. Cite at Part level — do not rely on sub-rule numbers unless you have verified them in the current White Book.

Does pseudonymisation affect the exhibit reference numbers?

No — exhibit reference labels (e.g. 'AB1', 'CD2') are treated as structural markers, not personal identifiers, and are preserved in full.

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.