Anonymising M&A Due-Diligence Data Rooms – UK GDPR-compliant anonymisation per UK GDPR Art. 5(1)(c)

An M&A due-diligence data room aggregates hundreds of documents — contracts, board minutes, employment records, and regulatory filings — that collectively expose the personal data of directors, employees, and counterparties at scale. anonym.legal pseudonymises natural-person identifiers across the entire document corpus in a single batch, satisfying the data-minimisation principle of UK GDPR Art. 5(1)(c) so acquirers and their advisers review commercial substance without unnecessary personal exposure.

When this applies

This task applies when a target company or its advisers are populating a virtual data room for buyer due diligence, and the buyer's legal, financial, and operational advisers require access to commercial and financial information but not to the personal data of named employees, directors, or counterparties.

  1. Upload the full data-room document corpus to anonym.legal in a batch job — supported formats include PDF, DOCX, XLSX, and TXT.
  2. The engine maps all natural-person entities across the corpus, building a unified entity registry so that a director mentioned in board minutes, employment contracts, and share registers receives the same pseudonym throughout.
  3. Pseudonymisation is applied consistently across every document in the batch; commercially material information — prices, dates, obligations, financial figures — is preserved.
  4. A master mapping table covering the entire corpus is produced with UK/EU data residency and access-control logging.
  5. The pseudonymised corpus is released to the data room; the mapping table is retained by the target's legal advisers.
  6. On closing, the mapping table is used to re-identify any documents required in their original form for completion documents or filings.

What you provide

  • Full data-room document corpus (PDF, DOCX, XLSX, TXT)
  • Data-room index or folder structure (to preserve organisation post-processing)
  • List of known key individuals (directors, executives) to verify entity detection

Limitations & cautions

  • Large corpora (500+ documents) should be processed in scheduled batches — contact support for batch scheduling.
  • Financial statements naming individuals in notes or signatory lines will have those names pseudonymised, but numerical financial data is preserved.
  • The tool does not assess the legal adequacy of warranties or indemnities — obtain M&A legal advice.
  • Re-identification of the full corpus on completion requires the master mapping table to be securely maintained throughout the deal lifecycle.

FAQ

How does the engine handle the same director appearing in 50 different documents?

The unified entity registry assigns one pseudonym per individual at the start of batch processing. That pseudonym is applied consistently across every document in the corpus, so cross-document references remain coherent.

Can buyers request access to the mapping table?

The mapping table contains the original personal data and is itself personal data within the meaning of UK GDPR. It should not be shared with the buyer unless there is a specific lawful basis for doing so.

Does the tool handle password-protected PDFs?

Password-protected PDFs must be decrypted before upload. anonym.legal does not store or process document passwords.

Is this suitable for use with a third-party VDR such as Intralinks or Datasite?

Yes. Pseudonymise the documents using anonym.legal, then upload the pseudonymised versions to the VDR. This is complementary to VDR access controls, not a replacement.

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 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.