Defence and Counterclaim: pseudonymise third-party data in draft pleadings – UK GDPR-compliant anonymisation

A Defence (and any Counterclaim) responds to each allegation in the Particulars of Claim and may introduce new third-party witnesses or documents; anonym.legal pseudonymises non-party personal data in draft Defence pleadings so solicitors can share internal working versions without unnecessary data exposure while preparing the final response.

When this applies

Applies when a defendant's solicitor is preparing a Defence or Defence and Counterclaim that references individuals beyond the immediate parties and wishes to circulate drafts internally.

  1. Upload the draft Defence (and Counterclaim if applicable) in DOCX or PDF.
  2. Set the party-names allow-list to retain claimant, defendant, and solicitor names in clear.
  3. anonym.legal pseudonymises third-party names, witnesses, and other personal identifiers throughout.
  4. Pleaded facts, admissions, denials, and counterclaim particulars are preserved in full.
  5. A reversible mapping is stored with EU data residency.
  6. Re-identify before service to produce the final pleading with all names in clear.

What you provide

  • Draft Defence or Defence and Counterclaim (DOCX or PDF)
  • Party-names allow-list

Limitations & cautions

  • Compliance with the time limits for filing a Defence is not monitored by anonym.legal — that remains the solicitor's responsibility.
  • The legal adequacy of the Defence is not assessed by the tool.

FAQ

Can I process the Reply to Defence in the same session?

Yes, upload both the Defence and the Reply together for consistent pseudonymisation across the full pleadings set.

What happens if the Defence cross-references paragraph numbers in the Particulars?

Cross-references are preserved as structural text; pseudonymisation targets personal-identifier strings, not paragraph references.

Does a Counterclaim require separate processing?

No — if the Counterclaim is in the same document as the Defence, it is processed in one pass with consistent pseudonyms throughout.

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.