Anonymise Disciplinary Records for Audit, Training, and Review – UK GDPR-compliant anonymisation per ACAS Code of Practice on Disciplinary and Grievance Procedures

Disciplinary records — warnings, suspension letters, hearing notes, and outcome decisions — contain the employee's name, the specific allegations, witness accounts, and penalty imposed. anonym.legal pseudonymises this personal data so that disciplinary case files can be audited for consistency, shared with legal advisers, or used in management training without disclosing the identities of those involved.

When this applies

Apply this workflow when disciplinary records need to be shared for consistency auditing, legal review, or training purposes, and the identity of the employee subject to disciplinary action should not be disclosed to the recipient.

  1. Upload the disciplinary file including invitation to hearing letters, hearing notes, witness statements, and outcome letters.
  2. The engine identifies the employee's name, witness names, manager names, and incident-specific details across the entire file.
  3. All individuals are pseudonymised consistently across every document in the bundle.
  4. Procedural content — the alleged misconduct, sanctions imposed, appeal rights, and reference to the ACAS Code of Practice — is retained in plain text.
  5. The reversible mapping is encrypted and stored with EU data residency.
  6. The pseudonymised file is exported for audit, review, or training use.

What you provide

  • Invitation to disciplinary hearing letter
  • Hearing notes and any witness statements
  • Outcome letter (warning, final written warning, or dismissal)
  • Appeal outcome letter, if applicable

Limitations & cautions

  • anonym.legal does not assess whether the disciplinary process was procedurally fair or compliant with the ACAS Code of Practice; legal advice remains necessary.
  • Contextual details in witness accounts may allow indirect identification even after automated pseudonymisation; manual review of witness statements is recommended.
  • Where the misconduct alleged involves protected characteristics under the Equality Act 2010, enhanced review of special category data handling is required.

FAQ

Will the level of sanction imposed be retained in the pseudonymised record?

Yes. The type of disciplinary sanction — verbal warning, written warning, final written warning, or dismissal — is retained as procedural content. Only personal identifiers linking the sanction to a named employee are pseudonymised.

Can I use pseudonymised disciplinary records for consistency auditing?

Yes. A common use case is auditing whether similar misconduct across the workforce has been handled consistently. Pseudonymised records allow the HR function or an external auditor to review outcomes without accessing unnecessary personal data about each employee.

How are witness names handled in hearing notes?

Witness names are detected as personal data and pseudonymised alongside the subject employee's details. Each witness receives a consistent pseudonym throughout the document bundle, preserving the structure of witness evidence without identifying the witnesses.

Does pseudonymising the record affect the employee's ability to exercise data subject access rights?

No. Pseudonymisation does not affect the employee's rights as a data subject under UK GDPR. The original records remain in your systems; the pseudonymised version is a data-minimised copy for sharing purposes only. Any subject access request must be fulfilled from the original records.

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.