Anonymise Grievance Documents for HR Review and Legal Disclosure – UK GDPR-compliant anonymisation per ACAS Code of Practice on Disciplinary and Grievance Procedures

Grievance documents — including the initial complaint, investigation notes, and outcome letters — contain the grievant's name, details of the alleged conduct, and the names of colleagues or managers implicated. anonym.legal pseudonymises this personal data so that grievance materials can be reviewed by HR leadership, external advisers, or used in policy development without identifying the individuals involved.

When this applies

Use this workflow when grievance documentation needs to be shared with senior HR, external employment solicitors, or used as training case studies, and the identities of the grievant and those named in the complaint should not be disclosed beyond those with a need to know.

  1. Upload the grievance letter, investigation report, and outcome or appeal letters.
  2. The engine identifies the grievant's name, the names of individuals mentioned in the complaint, HR personnel names, and any sensitive incident details.
  3. All individuals are pseudonymised consistently across the grievance bundle, preserving the narrative thread of the complaint and investigation.
  4. Substantive content — the nature of the complaint, procedural steps taken under the ACAS Code of Practice, and outcome — is retained in plain text.
  5. The reversible mapping is encrypted and stored with EU data residency.
  6. The pseudonymised bundle is shared with reviewers or used for training purposes.
  7. Re-identification is available via the stored key if the matter proceeds to tribunal or formal mediation.

What you provide

  • Grievance letter submitted by the employee
  • Investigation notes and witness statements
  • Outcome letter and any appeal correspondence

Limitations & cautions

  • anonym.legal does not assess whether the grievance procedure complied with the ACAS Code of Practice; legal advice on procedural compliance remains necessary.
  • Witness statements may contain contextual details — descriptions of specific incidents — that could indirectly identify individuals even after automated pseudonymisation; manual review is recommended.
  • Where a grievance contains allegations of harassment or discrimination referencing protected characteristics, special category data under UK GDPR Art. 9 and the Equality Act 2010 may be present and should be reviewed carefully.

FAQ

Will the nature of the grievance complaint be retained in the pseudonymised document?

Yes. The substantive nature of the complaint — the conduct alleged, procedural steps taken, and outcome — is retained in plain text. Only personal identifiers linking that content to named individuals are pseudonymised.

How does the tool handle grievances that name multiple colleagues?

Each individual mentioned in the grievance bundle receives a distinct, consistent pseudonym. This means the relationship between the grievant and those named is preserved structurally, but no real names appear in the pseudonymised output.

Can pseudonymised grievance documents be used as training case studies?

Yes. Once personal identifiers have been removed, grievance case studies can be used in HR or management training. You should satisfy yourself that the pseudonymised version does not allow identification by context — for example, if the described incident is well known within the organisation.

What happens if the grievance involves allegations under the Equality Act 2010?

Where the grievance involves allegations of discrimination, harassment, or victimisation referencing a protected characteristic, the engine treats references to that characteristic as special category data under UK GDPR Art. 9. Enhanced pseudonymisation is applied, and the output should be reviewed before sharing.

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.