Particulars of Claim: pseudonymise third-party identifiers before drafting review – UK GDPR-compliant anonymisation

Particulars of Claim set out a claimant's case in full and frequently reference non-party individuals — witnesses, bystanders, or contractual counterparties — whose personal data appears incidentally; anonym.legal pseudonymises those identifiers in draft Particulars so the document can circulate internally for review without exposing third-party data before the final pleading is settled.

When this applies

Applies when a solicitor or counsel is drafting or reviewing Particulars of Claim that name third parties whose personal data is not yet in the public domain and is not strictly necessary in clear form at the internal review stage.

  1. Upload the draft Particulars of Claim in DOCX or PDF format.
  2. Configure the party-names allow-list to retain claimant and defendant names in clear.
  3. anonym.legal identifies and pseudonymises all other personal identifiers — witness names, addresses, third-party contact details.
  4. Legal allegations, facts, and relief claimed remain untouched.
  5. A reversible mapping is stored with EU data residency.
  6. Re-identify from the mapping key when producing the settled pleading for service.

What you provide

  • Draft Particulars of Claim (DOCX or PDF)
  • Party-names allow-list
  • Supporting documents referenced in the Particulars (optional, for consistent pseudonymisation)

Limitations & cautions

  • The pleaded facts, legal basis, and relief are not reviewed or amended by anonym.legal — drafting responsibility remains with the solicitor or counsel.
  • The final served Particulars must contain all party names in clear; always re-identify before service.

FAQ

Can I process the Particulars and the Schedule of Loss in the same session?

Yes, upload both documents together so any individual named in the Schedule receives the same pseudonym as in the Particulars.

Does pseudonymisation affect paragraph numbering?

No — paragraph numbers, cross-references, and headings are structural elements preserved without alteration.

Is this useful for pre-action drafts shared with the client?

Yes — sharing a pseudonymised draft for client approval limits exposure of third-party data to the client before the pleading is finalised.

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.