The core answer
Buying a business together with its customer database does not automatically give the buyer the right to use that data for its own marketing. Names, phone numbers, LINE IDs and purchase histories that identify a person are personal data under the Personal Data Protection Act B.E. 2562 (PDPA). What the buyer may do with them depends on what the seller notified and did when it collected them, not on the price paid.
Keep two stages apart. The first is receiving data to examine before the purchase. That is already a disclosure and must be handled carefully. The second is using the data after closing, which depends on the original purpose, the original notice, the legal basis, any consent, and the structure of the deal (share purchase or asset purchase). The real answer is often "usable in part", "usable after certain steps" or "not yet usable", depending on each dataset.
This page answers only the customer-data question in an acquisition. For the structure comparison as a whole, read share purchase or asset purchase. For a customer list taken by a departing employee, read a former employee took the customer list. For a general PDPA checklist, see the PDPA compliance checklist.
Who should read which part
| Where you are | Start with |
|---|---|
| Planning (no serious negotiation yet) | Sections 1 and 2: whether customer data drives the price, and ground rules for disclosure |
| Negotiating (due diligence and drafting) | Sections 3 to 6: questions for the seller, deal structure and contract protections |
| Already done (closed, data in the buyer's hands) | Sections 7 and 8: notifying data subjects, separating and deleting unusable data |
1. Why "we bought it" is not the same as "we can use it"
The PDPA regulates the personal data and the purpose of use, not who owns the file under a contract. The relevant rules in outline:
| Topic | What the PDPA addresses | Effect on the deal |
|---|---|---|
| Consent (Section 19) | Must be explicit, in writing or electronic, separate from other text, state the purpose, be easy to understand, and can be withdrawn | Consent the seller obtained covers what was stated when it was requested, not the buyer's use by implication |
| Purpose (Section 21) | Collect, use and disclose in line with the notified purpose; a new purpose needs notice and consent first unless the law permits otherwise | Using the seller's customer data for the buyer's own promotions may be a new purpose |
| Notice (Section 23) | Before or at collection, notify the purpose, categories of recipients, retention period and rights | The seller's original notice is the main evidence of what people expected |
| Bases without consent (Section 24) | For example necessity for a contract, legitimate interests or legal compliance; legitimate interests cannot be used where the data subject's fundamental rights outweigh them | The seller's basis does not travel with the file; the buyer must identify its own |
| Use and disclosure (Section 27) | A controller must not use or disclose without consent unless the data was collected without consent under Section 24 or 26; a person who receives data through a disclosure must not use or disclose it beyond the purpose notified when requesting it | A buyer who receives data is tied to the purpose it gave the seller when it asked |
This is a summary of broad rules. The full wording and exceptions are in the statute, so check the official text at the PDPC or the Office of the Council of State before relying on it.
Our practical view. The buyer should ask at the outset what it will do with the data after closing, then check whether the seller's original notice covers that. If the business plan depends on messaging the existing customers, the uncertainty about the right to use the data should show up in the price and in the contract terms.
2. Showing data to the buyer during due diligence
Sending the customer file to a prospective buyer is already a disclosure of the seller's personal data to an outsider, even if the deal never closes. Ways to reduce the risk:
- Start with summary data: number of customers, sales by segment, customer age, repeat-purchase rate, none of it identifying anyone.
- If individual records are needed, mask names, numbers and emails or use a small sample, and release full data only close to closing.
- Sign a confidentiality agreement first, limiting use to evaluating the deal (see NDA before business negotiations).
- Limit access to named people, use a data room with access logs, and do not send files by personal chat.
- Agree in advance that if the deal fails the buyer deletes or returns the data and confirms in writing.
- The buyer should not contact customers using data seen in the data room before closing.
For the wider legal due diligence picture, see scope and red flags of legal due diligence.
3. What to ask the seller before agreeing a price
These questions show how usable the database really is, as opposed to how large it looks in the accounts or the presentation.
| Topic | Question | Documents to request |
|---|---|---|
| Source | Where did the data come from: customers entering it themselves, bought from another business, scraped from social media, brought by staff? | Collection channel records, contracts with earlier data sellers |
| Notice | What did the notice say about purpose, recipients and retention? How many privacy notices existed and which applied when? | Every version of the privacy notice, sign-up page text, application and order forms |
| Consent | For which customers is there consent? Was marketing consent requested separately? How is it evidenced? | Individual consent records, timestamps, the wording used |
| Other bases | For which customers does the seller rely on contract or legitimate interests, and how was that assessed? | Any legal-basis assessment |
| Opt-outs | Is there a list of people who refused marketing or withdrew consent, and how is it held in the system? | The opt-out list with dates, data deleted on request |
| Processors | Who runs the CRM, cloud or email marketing for the seller, and is there a data processing agreement? | Contracts with CRM, cloud and messaging providers |
| Sensitive data | Any health, religion, biometric, criminal-record or children's data? | List of data types per table |
| Complaints and breaches | Any customer complaints, leaks or letters from authorities? | Incident log, correspondence, any statutory notifications |
| Foreign data | Any foreign customers, or data stored on servers abroad? | System list, server locations, provider contracts |
| Internal records | Does the seller keep a record of processing activities, a retention and deletion policy, and a process for data-subject requests? | Internal policies, request log and responses |
The answers usually split the database into groups: data with clear evidence and a notice wide enough, data with gaps, and data whose origin even the seller cannot explain. The buyer should price these groups differently.
4. How the deal structure changes the question
The structure decides whether the data moves and who is the controller after closing. The table is a broad picture; the exact result depends on the facts of each deal.
| Structure | What happens to the data | What to check |
|---|---|---|
| Share purchase | The company holding the data stays the same legal entity and no file goes to another entity, but shareholders and management change | Past collection defects stay with the company, so the buyer takes that risk indirectly; using the data for a new purpose or moving it to another group company still needs the Section 21 check |
| Asset purchase (including the database) | The seller passes data to a different legal entity | Whether the seller could lawfully make that disclosure given its notice and basis, and that the buyer may use the data only for the purpose notified when it asked for it (Section 27, second paragraph) |
| Purchase of the customer list only (not the business) | Data leaves a business that continues to operate | Highest risk: customers may not expect any continuity, and the original purpose and the buyer's purpose are usually far apart |
For liabilities, contracts and licences under each structure, see share purchase or asset purchase. This page covers only the customer-data angle.
5. Warranties, indemnities and conditions in the purchase agreement
If every row of the database cannot be checked before closing, the contract allocates the risk. Items commonly proposed:
- Seller warranties that data was collected lawfully, the required notice was given, consent records are as disclosed, there are no undisclosed complaints, data breaches or authority letters, and passing the data to the buyer does not conflict with the original notice.
- A disclosure schedule listing each database, its source, legal basis and the exceptions the seller already knows about.
- Conditions before closing, such as the seller notifying customers or updating its notice, delivering consent records and the marketing opt-out list, or separating data that has no basis.
- A specific indemnity for loss from data not lawfully collected, including complaints and the cost of remediation, with a stated cap, time limit and claims procedure.
- Retention, escrow or earn-out tied to the portion of the database that is uncertain; see earn-out clauses.
- Post-closing duties, such as the seller helping to notify data subjects, forwarding pending rights requests and not using the sold data to compete.
- Seller's own retention: whether the seller may keep a copy after handing over the data should be stated.
The right wording and limits depend on the value of the database relative to the price, the seller's ability to pay under an indemnity, and what the due diligence turned up.
6. Checklist before closing
- State what the buyer will do with the customer data after closing and compare it with the original notified purposes
- Sign an NDA and set data-room rules before opening customer data; start with summary or masked data
- Send the seller a questionnaire on source, notice, consent and marketing opt-outs
- Obtain every version of the seller's privacy notice with the dates it applied
- Obtain consent records and the list of people who withdrew consent or refused marketing
- Review the seller's processor contracts (CRM, cloud, messaging)
- Sort the database into groups: usable, needs fresh consent, should not be used
- Put warranties, a disclosure schedule, an indemnity and closing conditions in the agreement
- Plan the notice to data subjects (Section 7): who sends it, when and through which channel
- Prepare the buyer's own privacy notice to cover the data it receives
- Agree what is deleted or returned, by both sides, if the deal collapses
7. After closing: notifying data subjects and asking for fresh consent
If the buyer intends to use the data for a purpose different from the original one, the usual approach is to notify and obtain consent before use, following the logic of Sections 21 and 19.
- Announce the change of operator or controller. Say that the business changed hands, who the new controller is, how to contact them and what rights the data subject has.
- Keep the notice separate from advertising. The first message should be about the change, not a promotion with a consent link tucked inside.
- Ask for marketing consent separately. Use plain wording, state the purpose, do not tie it to a service that does not need the data, and make withdrawal as easy as giving consent.
- Respect earlier opt-outs. Anyone who refused marketing or withdrew consent with the seller must not receive marketing just because the business was transferred.
- Keep records of what was sent, when, to whom and how people responded, as the buyer's own evidence.
Data the buyer receives from the seller was not collected directly from the data subjects, so Section 25 also matters. It prohibits collecting personal data from other sources unless the controller informs the data subject of that collection without delay, and no later than 30 days after collecting it, and obtains consent, or the data falls within the consent exemptions in Section 24 or 26. Which route fits a given deal depends on the facts, so have a lawyer review it before planning the notices (law as of 21 November 2026).
8. Handling data that cannot be used
Some data may have no basis on which the buyer can use it, for example because its source is unknown, there is no consent record, or it was collected for a purpose far from the buyer's plans. Common steps:
- Separate this data from the marketing systems and stop messaging those contacts.
- Decide whether to ask for fresh consent, invite people to provide their details themselves, or delete.
- Delete or destroy what has no reason to be kept, including copies in email, shared drives and sales staff devices.
- Record what was deleted, when, why and who approved it.
- If the seller gave inaccurate information, check your rights under the warranties and indemnity quickly, because notice periods are usually short.
Keeping data "in case it becomes useful", without a lawful purpose, is the buyer's own risk.
9. Hypothetical example: an online shop buys a cosmetics business
This is a hypothetical scenario, not a real case. The numbers are illustrative only.
Company A buys the assets and customer database of online cosmetics shop B, which has 20,000 customers. A plans to send promotions for its group's products to everyone. Due diligence finds:
- 12,000 customers signed up through a website with a separate consent line for B's product news, but nothing about transfer to others.
- 6,000 customers bought through a marketplace; the data was received only to deliver orders, with no marketing consent.
- 2,000 customers have no evidence of where the data came from.
A lawyer might advise sorting the three groups. For the first, check whether the consent wording covers A and its group's products; if unclear, announcing the change and asking for fresh consent before sending promotions is probably safer. For the second, using delivery data for marketing may be a new purpose needing consent first. The third should not be used and should be deleted. In the contract, A would ask B to warrant the sources, attach a disclosure schedule and hold back part of the price until the notification process is complete. The real outcome depends on the exact consent wording, the privacy notice in force at the time and the other facts.
Common misunderstandings
| What people assume | What to know |
|---|---|
| Paying for the database means we can use it like the previous owner | The right to use personal data does not come from payment. It depends on the notified purpose, the legal basis and the data subject's consent |
| A share purchase avoids PDPA problems because the old company still exists | Past collection defects stay with the company, and a new purpose still needs the same check |
| The people are customers of the business, so we can contact them about anything | Contact must fit what was notified; a new purpose needs notice and consent first unless the law permits otherwise |
| Viewing the file before buying is fine because we are not using it yet | Giving the file to the buyer is already a disclosure. Disclose only what is needed, sign an NDA and delete if the deal fails |
| A warranty in the contract means we need not check ourselves | A warranty only allocates risk after a problem arises. It does not make use of data without a basis lawful |
| Deleting unusable data is enough, no need to keep a record | Record what was deleted, when and why, so you can answer if asked later |
Further reading
- Share purchase or asset purchase: choosing the acquisition structure
- A former employee took the customer list: trade secrets and paperwork
- PDPA compliance checklist for businesses
- NDA before business negotiations
- Scope and red flags of legal due diligence
The price paid for a customer database does not carry the right to use it. Check the source and the original notice before agreeing the price, and write the remaining risk into the contract.
We help buyers and sellers review the source and PDPA paperwork of a customer database, draft the warranties, indemnity and conditions in the acquisition agreement, and prepare the notice to data subjects and the privacy notice for after closing. We are not accountants or tax advisers, we do not value databases, and we cannot promise that a regulator or a data subject will not challenge the use of the data. Fees depend on the stage of the matter and the work required. Send us the documents first, and we will give you the scope of work and fees in writing before we start. Call +66 92 254 2045 or send us the details. See also PDPA compliance for business and business sale and acquisition.
This guide is published by Suwanvara Law Firm — a Khon Kaen law firm established in 1986. General information only, not legal advice on a specific matter.

