Reply to Defence: pseudonymise new third-party identifiers – UK GDPR-compliant anonymisation

A Reply to Defence is the claimant's optional pleading that addresses new matters raised by the defendant and may introduce further third-party names; anonym.legal pseudonymises those identifiers in draft Replies, maintaining a consistent pseudonym scheme with earlier pleadings — according to HMCTS, over 1.4 million County Court claims were issued in 2023, and Reply pleadings arise in a significant proportion of defended cases.

When this applies

Applies when a claimant's solicitor drafts a Reply to Defence that introduces new factual matters referencing third parties not named in the original Particulars of Claim. In multi-track cases above £25,000, Replies frequently reference additional witnesses whose personal data warrants protection under UK GDPR.

  1. Upload the draft Reply alongside the previously processed Particulars of Claim (or the mapping table from that session).
  2. anonym.legal applies the existing pseudonym assignments from the Particulars session and assigns new pseudonyms to any newly introduced individuals.
  3. The factual responses and any new averments are preserved without alteration.
  4. A combined mapping table covering both sessions is produced.
  5. Re-identify all pseudonyms before service.

What you provide

  • Draft Reply to Defence (DOCX or PDF)
  • Mapping table from the Particulars of Claim processing session (to ensure consistency)

Limitations & cautions

  • If the Particulars mapping table is unavailable, new pseudonyms will be assigned independently — cross-document consistency relies on providing the original mapping.
  • Whether a Reply is necessary or advisable in the particular proceedings is a matter for the solicitor.
  • Misuse of third-party personal data introduced in a Reply can attract UK GDPR fines of up to £17.5 million or 4% of global turnover under DPA 2018 s.157.

FAQ

Is a Reply to Defence always required in CPR proceedings?

No — under CPR, a claimant need not file a Reply unless they wish to allege facts in answer to a Defence. Whether to serve a Reply is a tactical and legal decision for the solicitor.

How do I ensure the same pseudonym is used for a person named in both the Particulars and the Reply?

Upload the original mapping table when processing the Reply. The engine will match names to the existing mappings and assign consistent pseudonyms. Research shows that consistent pseudonyms across 2 or more pleadings reduce re-identification errors by a significant margin.

Can the pseudonymised Reply be shared with counsel for settling the final wording?

Yes — a pseudonymised Reply is appropriate for sharing with counsel at the drafting stage. According to the ICO Code of Practice on Anonymisation (2021), pseudonymised documents shared for legal advice purposes represent a proportionate data-minimisation approach.

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.