Anonymise Employment Tribunal ET1 and ET3 Claims for Legal Review – UK GDPR-compliant anonymisation per ERA 1996 s.94

Employment tribunal ET1 claim forms and ET3 response forms identify the claimant and respondent by name, address, and employer details, and set out the factual basis of the claim in detail. anonym.legal pseudonymises this personal data so that tribunal pleadings can be reviewed by senior management, used in training, or disclosed to insurers without revealing party identities unnecessarily.

When this applies

Apply this workflow when ET1 or ET3 forms, or accompanying tribunal correspondence, need to be shared with HR leadership, employment practices liability insurers, or used as training precedents for employment advisers.

  1. Upload the ET1 claim form, ET3 response form, or both together.
  2. The engine identifies the claimant's name, address, employee number, and employer details on both forms.
  3. All individuals named in the forms — claimant, respondent contacts, witnesses cited — are pseudonymised consistently.
  4. The legal basis of the claim, remedy sought, and factual narrative are retained as non-personal content.
  5. The reversible mapping is encrypted and stored with EU data residency.
  6. The pseudonymised pleadings are shared with the intended recipients; re-identification is available for formal tribunal proceedings via the stored key.

What you provide

  • ET1 claim form and/or ET3 response form
  • Any accompanying case management orders or correspondence from the tribunal
  • Attached supporting documents such as witness statements or bundle indices

Limitations & cautions

  • anonym.legal does not provide legal advice on the merits of the claim or the appropriate response strategy; that remains the instructed solicitor's responsibility.
  • Tribunal case reference numbers may remain identifiable through public tribunal records even after personal identifiers are pseudonymised; consider whether recipients should be made aware of this residual risk.
  • Re-identification is required before submitting documents in formal tribunal proceedings.

FAQ

Can ET1 and ET3 forms be processed together to align pseudonyms across both documents?

Yes. Processing ET1 and ET3 forms together ensures that the claimant and respondent contacts receive consistent pseudonyms across both documents, making it easier for reviewers to follow the correspondence.

Will the legal basis of the claim — for example, unfair dismissal — be retained?

Yes. The legal basis of the claim, the remedy sought, and the factual narrative in the box-by-box answers are retained as substantive content. Only the names and contact details of the parties are pseudonymised.

How should I handle tribunal case reference numbers in pseudonymised documents?

Tribunal case reference numbers are publicly searchable in employment tribunal judgment databases. If you wish to prevent recipients from searching the number, you should redact or pseudonymise the case reference. You can configure anonym.legal to treat case reference numbers as personal identifiers.

Can pseudonymised tribunal documents be shared with employment practices liability insurers?

Yes. Sharing pseudonymised pleadings with insurers for coverage assessment is a common use case. The insurer receives enough information to assess the nature and value of the claim without accessing the claimant's personal data unnecessarily. A full-identity version can be provided under a formal disclosure protocol if the insurer requires it.

Employment Law

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.