Anonymise Employment Contracts for Benchmarking and HR Review – UK GDPR-compliant anonymisation per UK GDPR Art. 6

An employment contract is a legally binding agreement between employer and employee under the Employment Rights Act 1996 and UK GDPR Art. 6 — ICO fines reach up to £17.5 million or 4% of global turnover under the Data Protection Act 2018. anonym.legal pseudonymises names, addresses, and salary figures so that contracts can be benchmarked or shared with advisers without disclosing individual identities.

When this applies

Apply this workflow when sharing employment contracts with remuneration consultants, external solicitors, or internal teams for benchmarking or template-drafting purposes where the specific employee's identity is not required and data minimisation under UK GDPR Art. 6 should be demonstrated.

  1. Upload the employment contract or a batch of contracts to anonym.legal in their original format.
  2. The engine scans the document against over 267 entity types, identifying names, addresses, national insurance numbers, salary figures, and bank details.
  3. Each identified employee is assigned a consistent pseudonym across all occurrences in the contract, preserving cross-references between clauses.
  4. Role descriptions, contractual terms, restrictive covenants, and notice periods are retained in full as non-personal structural content.
  5. A reversible mapping between pseudonyms and real identities is encrypted and stored with EU data residency.
  6. The pseudonymised contract is exported for sharing with advisers or use as a precedent; re-identification is available on request via the stored key.
  7. For bulk benchmarking, multiple contracts can be processed together so that salary and benefit data remain comparable without revealing individual names.

What you provide

  • Employment contracts in PDF, DOCX, or plain-text format
  • List of data fields to be pseudonymised (e.g. name, address, NI number, salary)
  • Indication of whether contracts should be processed individually or as a batch

Limitations & cautions

  • anonym.legal does not assess the legal validity or enforceability of any contractual term under UK GDPR Art. 6 or otherwise; that remains the responsibility of the instructed solicitor.
  • Highly contextual identifying detail — such as a uniquely described role at a named small employer — may not be flagged automatically and should be reviewed manually.
  • Re-identification requires the secure retention of the mapping key; loss of the key makes re-identification impossible and may impair obligations under DPA 2018 s.10.

FAQ

Will restrictive covenants and notice period clauses be preserved in the pseudonymised version?

Yes. Non-personal structural content — including restrictive covenants, notice periods, and clause numbering — remains in plain text. Only personal data fields such as names and identifiers are pseudonymised, so the contract remains legally intelligible as a precedent.

Can salary figures be pseudonymised when sharing with a remuneration consultant?

Yes. Salary, bonus, and benefit figures linked to a named individual are treated as personal data and can be pseudonymised or masked. You can configure which financial fields are replaced so that benchmarking data remains statistically meaningful without disclosing individual remuneration.

Is this workflow compliant with UK GDPR when sharing with external advisers?

Pseudonymisation reduces the identifiability of personal data in line with UK GDPR Art. 6 principles of data minimisation and purpose limitation. However, you remain the data controller and must ensure the adviser relationship is covered by an appropriate data-processing agreement before sharing even pseudonymised materials. The ICO's Employment Practices Code (2011) and Employment Information Guidance (2023) both confirm that data minimisation — including pseudonymisation — is expected practice when sharing employment records with third parties. The statutory minimum notice period under ERA 1996 s.86 ranges from 1 week (for 1 month to 2 years' service) to 12 weeks, and these terms are preserved in plain text through the pseudonymisation process.

Does the tool handle fixed-term as well as permanent contracts?

Yes. The workflow applies to any employment contract format, including fixed-term, zero-hours, and consultancy agreements, provided they are uploaded in a supported file format.

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.