Pre-Action Protocol correspondence: pseudonymise before letter before action review – UK GDPR-compliant anonymisation

Pre-action protocol correspondence — including the letter before action required by most CPR pre-action protocols — sets out the factual basis of the claim and often names third parties such as witnesses or medical practitioners; anonym.legal pseudonymises those identifiers in draft letters so solicitors can conduct internal review without unnecessary third-party data exposure.

When this applies

Applies when a solicitor is drafting pre-action protocol letters, schedule of losses, or supporting documents for internal review before sending to the opposing party.

  1. Upload draft pre-action protocol letters and any enclosures (e.g. medical reports, schedule of loss) in DOCX or PDF.
  2. Configure the party-names allow-list to retain your client's name and the opponent's name in clear.
  3. anonym.legal pseudonymises third-party names, witnesses, and medical practitioners referenced in the correspondence.
  4. Factual allegations, financial figures, and legal basis are preserved in full.
  5. A reversible mapping is stored with EU data residency.
  6. Re-identify before sending the letter to the opponent.

What you provide

  • Draft letter before action or pre-action protocol letter (DOCX or PDF)
  • Enclosures: medical reports, schedule of loss, expert opinions (optional)
  • Party-names allow-list

Limitations & cautions

  • Compliance with the specific pre-action protocol applicable to the dispute (e.g. Personal Injury Protocol, Professional Negligence Protocol) must be confirmed by the solicitor.
  • anonym.legal does not advise on the content, tone, or legal adequacy of the correspondence.

FAQ

Does the letter before action need to comply with a specific protocol?

Yes — the applicable pre-action protocol depends on the type of claim. The solicitor must ensure the letter meets the protocol requirements. anonym.legal handles only the personal-data pseudonymisation step.

Can I process the protocol response letter from the opponent?

Yes — you can process any incoming correspondence through the same workflow to pseudonymise third-party data before circulating it internally.

What if the pre-action letter includes medical or health data?

Health data is special-category data under UK GDPR Article 9. anonym.legal identifies and pseudonymises medical identifiers; you should record the processing basis in your data-processing register.

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.