Anonymise Redundancy Settlement Agreements for Template Use – UK GDPR-compliant anonymisation per ERA 1996 s.203

Settlement agreements under ERA 1996 s.203 waive statutory claims and name the departing employee, settlement sum, and often confidentiality obligations. anonym.legal pseudonymises these personal data elements so that agreements can be used as precedent templates, reviewed by senior management, or benchmarked against market rates without disclosing individual settlement terms.

When this applies

Use this workflow when settlement agreements need to be shared with senior leadership, external legal advisers, or used as drafting precedents where the specific employee's identity and exact settlement sum should not be disclosed unnecessarily.

  1. Upload the settlement agreement or a set of agreements for batch processing.
  2. The engine identifies the employee's name, address, employee number, and any monetary figures linked to the named individual.
  3. The employee and any other named individuals — solicitors, witnesses — are pseudonymised consistently.
  4. Clause structures, confidentiality obligations, tax indemnities, and reference obligations are retained as non-personal content.
  5. The reversible mapping is encrypted and stored with EU data residency.
  6. The pseudonymised agreement is shared as a precedent or benchmarking document.
  7. Re-identification is available via the stored key when needed for formal execution or archive purposes.

What you provide

  • Signed or draft settlement agreement
  • Any attached schedules, reference letters, or COT3 correspondence
  • Indication of whether the settlement sum should be pseudonymised or retained

Limitations & cautions

  • anonym.legal does not verify the enforceability of the waiver of statutory claims under ERA 1996 s.203 or assess whether the independent legal advice requirement has been met.
  • Where the agreement is executed under a COT3 through ACAS conciliation, the ACAS reference number and officer details should be reviewed for pseudonymisation separately.
  • Re-identification for formal execution or registration requires secure retention of the mapping key.

FAQ

Can the settlement sum be pseudonymised when sharing with senior management?

Yes. The settlement sum, bonus elements, and any financial schedules linked to a named individual can be pseudonymised or masked. You can configure the tool to retain aggregate figures for benchmarking while hiding the individual amount.

Will confidentiality and non-disparagement clauses be preserved?

Yes. Clause text, including confidentiality, non-disparagement, and reference obligations, is retained in full. Only personal identifiers in the recitals and signature blocks are pseudonymised.

Does this workflow cover COT3 agreements reached through ACAS?

Yes. COT3 agreements can be processed, and ACAS officer names and reference numbers are detected as identifiers. If you need to retain the ACAS reference for tracking purposes, you can configure those fields to remain in plain text.

Is a settlement agreement that has been pseudonymised still a valid record?

The pseudonymised version is a data-minimised copy for sharing purposes; it is not the executed legal instrument. The original signed agreement must be retained in your records management system. The pseudonymised version supplements but does not replace 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.