Start by identifying what is changing
A share sale and an asset transfer can have different implications for the identity of the controller. In a share sale, the company holding the information may remain the same legal entity, although new access, uses and integration can still raise questions. An asset transfer may involve another entity receiving the records. Do not decide the privacy work solely from the transaction’s commercial name.
Ask the transaction team to identify each dataset, its present controller, proposed recipient and intended use. Include employees, applicants, suppliers, former customers, complaints, litigation records and marketing preferences. A deal description saying “all business information” is too broad to serve as an operational instruction. The useful output is a schedule showing what moves, what remains, what is archived and what should not be transferred.
Treat pre-sale disclosure as its own activity
Potential buyers may need evidence about trading and liabilities, but that does not justify unrestricted access to identifiable records. The ICO’s employment guidance advises anonymising worker information wherever possible in prospective acquisition and reorganisation discussions. Other data-sharing duties also apply to disclosures before completion. A confidentiality agreement is useful protection, not a standalone lawful basis for everything placed in a data room.
Our recommended approach is staged access. Start with aggregated information and redacted examples that answer the commercial question. Release more detailed information only where justified, to named people with an appropriate purpose and access period. Record approvals and downloads where practical. Review hidden document properties and spreadsheet tabs before upload. Restricting the room is less effective if the supplied files already contain unnecessary personal detail.
Test the quality of the database, not merely its size
Due diligence should examine the original collection purposes and the basis on which information has been used. Ask for the relevant notices, consent evidence where relied on, objection records, retention rules and significant complaints or incidents. A count of contacts says little about whether those people can be contacted for the buyer’s intended purpose.
For a practical sample, trace several records from collection through the current system. Can the seller explain the source, permissions and subsequent changes? Are suppressed contacts mixed into an export marked active? Are old addresses or inaccurate records presented as current customers? These checks help valuation as well as privacy: a smaller, well-understood dataset may be more usable than a large collection with uncertain provenance.
Do not assume marketing permissions transfer unchanged
Purchasing a database does not create a general permission to email everyone in it. Electronic-marketing rules, subscriber type and the wording and scope of any consent remain relevant. A buyer should not assume that the seller’s existing-customer soft opt-in becomes its own merely because a contact list is included in the deal. The structure of the transaction and continuity of the controller need careful assessment.
Our suggested diligence question is specific: which messages does the buyer intend to send, from which entity, using what evidence? Separate service communications from promotional campaigns. Where the evidence does not support a proposed campaign, reflect that limitation in the commercial assessment. Do not plan to solve the problem later by sending a mass “permission update” without checking whether that message itself would be marketing.
Plan transparency and rights before completion
The ICO’s acquisition guidance emphasises considering when and how people will be informed about changes affecting their information. Where a new controller obtains data indirectly, Article 14 information duties and their timing are relevant, subject to applicable exceptions. The right answer is not always to send every person the same notice on completion day; it depends on the processing and legal requirements.
Prepare the communication plan alongside the integration plan. Identify the correct entity and contact route, explain significant changes clearly and make sure support staff can answer likely questions. Allocate responsibility for open access requests, complaints and objections. A person should not be bounced between buyer and seller because the deal team failed to agree who would handle an existing issue.
Handle employee and sensitive records separately
Employee transfers can involve specific legal obligations, including relevant TUPE requirements, alongside data protection duties. That does not mean every employment file must be disclosed to every bidder. Health, disciplinary and other sensitive information requires particular care. Distinguish information needed for assessing a transaction from records needed by an employer to meet its responsibilities after the transfer.
For implementation, create controlled workstreams for HR and legal material rather than adding them to a general commercial folder. Agree named recipients and secure delivery arrangements. Preserve privilege and confidentiality questions for the appropriate advisers. Record which historic files have an ongoing justification and which need restricted retention or disposal. A rushed transfer should not become an excuse for copying every old document indefinitely.
Make integration a privacy project
Two apparently compatible customer systems can use different permission fields, retention triggers and definitions of active records. Merging them without mapping those differences can reactivate suppressed marketing contacts or expose records to a wider workforce. The ICO highlights governance, accuracy, retention and security during post-transaction integration. Those concerns deserve a plan, not an assumption that the IT migration will handle them.
Our practical recommendation is a test migration using a controlled sample, with explicit checks for permissions, ownership, access and deletion rules. Keep an audit trail of the mapping decisions. Establish a rollback and incident route before the full transfer. Review inherited supplier contracts and international access arrangements rather than assuming the buyer’s usual terms automatically replace the seller’s agreements.
Put unresolved issues into the deal decision
Privacy findings should be translated into concrete commercial consequences: a restricted use, a remediation cost, an integration dependency or a matter requiring specialist legal advice. Warranties and indemnities may allocate contractual risk, but they do not make unlawful processing lawful or prevent complaints. The buyer still needs a workable operating plan.
Before signing off the data workstream, ask whether the organisation can explain what it is receiving, justify its intended use and deliver the promised protections. A clear answer can support a transaction. An unclear answer should be visible to the decision-makers before completion, not hidden in a folder of policies that nobody has compared with the actual database.
Sources and further reading
Primary guidance behind this briefing. Requirements depend on the facts; check the current guidance before making a decision.
This is general guidance, not a legal opinion on your circumstances or a guarantee of compliance. An individual assessment may be needed, particularly where sensitive information, disputed rights or regulatory action is involved.