Pseudonymising Asset Purchase Agreements and Transfer Schedules – UK GDPR-compliant anonymisation per UK GDPR Art. 6(1)(b)
An asset purchase agreement (APA) transfers specific business assets rather than shares, but it still identifies individual transferring employees in the TUPE schedule, names key supplier and customer contacts in assigned contract schedules, and lists IP registrants in intellectual-property transfer schedules. anonym.legal pseudonymises these individuals while preserving the asset descriptions, transfer values, and TUPE obligations so advisers can assess the deal without unnecessary personal-data exposure.
When this applies
This task applies when an APA and its schedules are shared with operational due-diligence teams, employment lawyers advising on TUPE obligations, or IP specialists reviewing the intellectual-property transfer schedule, and those reviewers do not require access to the named employees' or contacts' personal data.
How anonym.legal handles it
- Upload the APA and all schedules — TUPE employee list, assigned-contracts schedule, and IP transfer schedule — in a single batch.
- The engine identifies natural persons: transferring employees in TUPE schedules, named contract counterparty contacts, and IP registrants.
- Each individual is pseudonymised consistently across all schedules; the pseudonymisation of the TUPE employee list preserves role and employment-term data while protecting names.
- Asset descriptions, consideration, TUPE obligations, IP descriptions, and assigned-contract summaries remain in clear text.
- A mapping table is produced with UK/EU data residency.
- Release the pseudonymised batch for adviser review; restore originals before exchange.
What you provide
- Asset Purchase Agreement
- TUPE employee information schedule
- Assigned-contracts schedule (with named counterparty contacts)
- IP transfer schedule (with named registrants)
Limitations & cautions
- TUPE compliance assessment — including measure consultation and ETO reasons — requires specialist employment-law advice not provided by this tool.
- Employee personal data in TUPE schedules is sensitive; ensure only those with a legitimate review purpose access the pseudonymised schedule.
- IP registrant pseudonymisation affects assignment deeds; the mapping table must be preserved for re-identification before filing with the IPO.
FAQ
Does pseudonymising the TUPE schedule affect the transferee's obligations?
The TUPE obligation structure — roles, terms, and continuity of employment — is preserved. The pseudonymised schedule is for due-diligence review; the operative transfer requires the employees' real identities and must use the re-identified version.
Can the tool handle an APA where some employees are objecting to transfer?
The tool pseudonymises the employee list as presented. Whether an employee has indicated an intention to object is a factual matter recorded in the TUPE schedule — that status is preserved, with the name pseudonymised.
Are IP registration numbers pseudonymised?
No. Registration numbers are not personal data under UK GDPR and are preserved. Only the named registrant's identity is pseudonymised.