Anonymise Employment Contracts for Benchmarking and HR Review – UK GDPR-compliant anonymisation per UK GDPR Art. 6
Employment contracts contain names, addresses, salary figures, and role-specific terms that identify individual employees. anonym.legal pseudonymises these personal data fields so that contracts can be benchmarked against market rates, shared with external advisers, or used as precedent templates without disclosing the identities of the contracting parties.
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.
How anonym.legal handles it
- Upload the employment contract or a batch of contracts to anonym.legal in their original format.
- The engine scans the document against over 285 entity types, identifying names, addresses, national insurance numbers, salary figures, and bank details.
- Each identified employee is assigned a consistent pseudonym across all occurrences in the contract, preserving cross-references between clauses.
- Role descriptions, contractual terms, restrictive covenants, and notice periods are retained in full as non-personal structural content.
- A reversible mapping between pseudonyms and real identities is encrypted and stored with EU data residency.
- The pseudonymised contract is exported for sharing with advisers or use as a precedent; re-identification is available on request via the stored key.
- 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; 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.
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.
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.