Witness Statement under CPR Part 32: pseudonymise third-party identifiers – UK GDPR-compliant anonymisation per CPR Part 32

A witness statement is the formal written evidence served under CPR Part 32 in which a witness sets out their account of relevant facts; anonym.legal replaces non-party identifiers with consistent pseudonyms across the statement and exhibits — research shows that over 1.4 million civil claims proceeded in 2023, generating substantial volumes of third-party personal data (HMCTS Civil Justice Statistics).

When this applies

Applies when a solicitor is preparing or reviewing a witness statement that names or describes third parties not party to the proceedings. According to CPR Part 32, witness statements must be verified by a statement of truth; the small claims track threshold is £10,000, and statements appear across all tracks.

  1. Upload the draft witness statement and any exhibits in DOCX or PDF format.
  2. anonym.legal identifies third-party names, addresses, telephone numbers, and other personal identifiers throughout the statement.
  3. Each non-party is pseudonymised consistently so all references to the same individual are replaced with the same pseudonym.
  4. The deponent's own name and the names of parties are retained in clear (configured via the party-names allow-list).
  5. The factual narrative, dates, and evidential content remain unaltered.
  6. An encrypted reversible mapping is stored; the solicitor can restore clear names when finalising the statement for service.
  7. The final served version is produced by re-identifying from the mapping key before signing and filing.

What you provide

  • Draft witness statement (DOCX or PDF)
  • Exhibits annexed to the statement
  • Party-names allow-list (claimant, defendant, deponent)

Limitations & cautions

  • The statement of truth and the deponent's identity must appear in clear in the filed version — confirm re-identification before service.
  • anonym.legal does not verify that the statement complies with the CPR Part 32 formal requirements (e.g. heading, statement of truth wording).
  • Unauthorised disclosure of third-party personal data extracted from witness statements can attract UK GDPR enforcement; fines can reach £17.5 million or 4% of global annual turnover under DPA 2018 s.157.

FAQ

Can the same pseudonym session cover multiple witness statements for one matter?

Yes, upload all statements together in one session so the engine assigns consistent pseudonyms across the full set — 'Witness A' in statement one will be the same individual as 'Witness A' in statement two. Data shows that multi-witness matters frequently involve 5 or more statements.

Does pseudonymisation extend to photographs or plans annexed as exhibits?

Image-based exhibits are not currently processed for embedded text. Redact any personal data in image exhibits manually before upload.

Is the pseudonymised draft suitable for sharing with counsel for legal opinion?

Yes — sharing pseudonymised drafts with counsel limits data exposure at the advice stage. According to the ICO Code of Practice on Anonymisation (2021), pseudonymisation is a recognised risk-reduction measure for internal sharing of personal data.

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.