Pseudonymising Asset Purchase Agreements and Transfer Schedules – UK GDPR-compliant anonymisation per UK GDPR Art. 6(1)(b)

An asset purchase agreement is a contract under which a buyer acquires specific business assets rather than shares — identifying transferring employees in the TUPE schedule, supplier and customer contacts in assigned-contract schedules, and IP registrants in transfer schedules. UK GDPR fines for unlawful processing reach £17.5 million or 4% of global turnover. anonym.legal pseudonymises these individuals 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 named employees' or contacts' personal data. According to TUPE 2006, employee-liability information must be provided before transfer — that disclosure uses the re-identified version; the pseudonymised schedule is for preliminary diligence review only.

  1. Upload the APA and all schedules — TUPE employee list, assigned-contracts schedule, and IP transfer schedule — in a single batch.
  2. The engine identifies natural persons: transferring employees in TUPE schedules, named contract counterparty contacts, and IP registrants.
  3. Each individual is pseudonymised consistently across all schedules; the pseudonymisation of the TUPE employee list preserves role and employment-term data while protecting names.
  4. Asset descriptions, consideration, TUPE obligations, IP descriptions, and assigned-contract summaries remain in clear text.
  5. A mapping table is produced with UK/EU data residency.
  6. 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.
  • The Limitation Act 1980 provides 6 years for simple contract claims and 12 years for deeds — APA completion mechanics executed as a deed carry the 12-year period, so retain the mapping table accordingly.

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.

What Companies Act 2006 obligations are relevant to an APA?

According to the Companies Act 2006, Part 25, certain charges created in connection with an asset purchase — such as fixed charges over acquired intellectual property — must be registered at Companies House within 21 days of creation. The registration filings must identify the charging party by their legal name; pseudonymised documents are not suitable for those filings. As at 2024, over 5.3 million companies are registered at Companies House, many of which hold registered charges.

Does the Bribery Act 2010 affect asset purchases involving overseas sellers?

According to the Bribery Act 2010, commercial organisations must have adequate procedures to prevent bribery by associated persons. Asset purchases from overseas sellers require adequate-procedures due diligence on the seller's business — that assessment uses the re-identified versions of relevant documents. The pseudonymised APA is suitable for preliminary commercial review only. The ICO fined British Airways £20 million in 2020 for unrelated data failures, illustrating the scale of regulatory penalties for compliance shortfalls.

Commercial Contracts

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.