Anonymise Redundancy Consultation Notes for Internal Review – UK GDPR-compliant anonymisation per ERA 1996

Redundancy consultation notes are written records of individual meetings with at-risk employees under the Employment Rights Act 1996 — collective redundancies affecting 20 or more employees within 90 days trigger obligations under TULRCA 1992 s.188. Statutory redundancy pay is capped at £700 per week of service from 6 April 2024. anonym.legal pseudonymises names and counter-proposals so that records can be reviewed without disclosing affected employees' identities.

When this applies

Apply this workflow when consultation notes from individual redundancy meetings need to be reviewed by senior HR, legal advisers, or internal audit outside the immediate HR team handling the ERA 1996 s.139 redundancy process.

  1. Upload the consultation meeting notes or minutes.
  2. The engine identifies employee names, personal circumstances mentioned (such as caring responsibilities or health conditions), and the names of HR personnel or managers present.
  3. All individuals mentioned are pseudonymised consistently across multiple consultation rounds.
  4. Substantive content — the role at risk, redeployment options discussed, and counter-proposals — is retained in plain text.
  5. The reversible mapping is encrypted and stored with EU data residency.
  6. The pseudonymised notes are shared with reviewers; re-identification is available via the stored key when legally required.

What you provide

  • Individual consultation meeting notes or minutes
  • Names of HR personnel and managers present at meetings
  • Any written counter-proposals from at-risk employees

Limitations & cautions

  • anonym.legal does not assess the adequacy of the consultation process under ERA 1996 s.139 or whether non-compliance with TULRCA 1992 would attract a protective award; legal advice on procedural compliance remains necessary.
  • Sensitive personal circumstances — health conditions, caring responsibilities — disclosed during consultation are special-category data under UK GDPR Art. 9 and DPA 2018 s.10; enhanced pseudonymisation is applied and manual review is recommended.
  • The tool processes documents provided to it and does not record or transcribe meetings.

FAQ

Can consultation notes from multiple rounds be processed together?

Yes. Documents from successive consultation meetings can be batched so that the same employee receives the same pseudonym throughout all rounds, preserving the continuity of the consultation record.

Will the employee's redeployment preferences be retained in the pseudonymised notes?

Yes. Substantive content — redeployment preferences, alternative roles discussed, and counter-proposals — is retained in plain text. Only the personal identifiers linking that content to a named individual are pseudonymised.

How should I handle consultation notes containing health disclosures?

Where an employee has disclosed a health condition during consultation, that information is special category data under UK GDPR Art. 9 and DPA 2018 Schedule 1. The engine flags such content for enhanced pseudonymisation. You should review the output and consider whether the health information needs to be separately controlled even in pseudonymised form.

Is the employer's duty to consult affected by pseudonymising the notes?

No. Pseudonymisation is a data-sharing measure applied after the consultation meeting. It does not affect the employer's statutory duty to consult meaningfully with at-risk employees under ERA 1996.

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 company HQ is in Saarbrücken, Germany. Our servers run in Hetzner's Falkenstein datacenter.

Hetzner holds 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.