Customer records are often the first thing a buyer's eye goes to and the last thing you should agree to. They're not always off limits, but three tests have to pass.
01The three tests
1. The law
UK and EU: identifiable customer data is personal data, so UK GDPR applies. You need a lawful basis, and a new purpose must be compatible with why you collected the data or have its own basis.
US: there's no single federal law. State laws such as California's CCPA give people rights over the sale and sharing of personal information, and sector laws such as HIPAA add more. Take advice for each state your customers are in.
2. What you told customers
Read your privacy notice as a customer would. If it says you don't sell data, or lists purposes that don't include this, you have a problem. Changing a notice now doesn't automatically cover data you collected under the old one.
3. What you signed
If your customers are businesses, their contracts may decide this on their own. Confidentiality clauses and data processing agreements often limit you to using their data to provide your service. If you hold the data as a processor for them, it isn't yours to license at all.
02Consumer and business customers differ
| Consumers | Business customers | |
|---|---|---|
| Main constraint | Privacy law and your privacy notice | Contract and confidentiality |
| Does anonymising help? | Yes, if it's genuine | Only partly. The confidentiality duty can remain |
| Who to ask | Your lawyer or DPO | The client, in writing |
03Why removing names isn't enough
Pseudonymised data is still personal data under UK GDPR. Free text is the usual trap: support tickets and call notes can identify someone without a name in them. See anonymised vs pseudonymised and how de-identification works.
Programmes say they de-identify what they receive, which helps. It doesn't change whether you were allowed to pass the data on in the first place, so ask your lawyer about that step as well.
04A sensible order
- Start with records that have no customer data: SOPs, playbooks, templates and internal wikis.
- Then look at operational records where customer details can be properly removed.
- Leave identifiable customer data out unless your lawyer has signed it off.
This is usually where the programmes' interest lies too: they describe wanting records of how work gets done. See what AI labs buy and what to exclude. This isn't legal advice.
05Questions people ask
Can I sell my customer list to an AI company?
Treat that as a no without legal advice. A list of identifiable people is personal data, and programmes want operational records anyway, not contact lists.
Do I need customers' consent?
Not always, but you need a lawful basis, and you must tell people what you do with their data. Your privacy notice is the first thing to check. Take advice for your jurisdiction.
Does anonymising fix it?
Truly anonymised data falls outside UK GDPR, but the bar is high. It also doesn't remove a confidentiality duty you owe a business customer.
Sources
- ICO: UK GDPR guidance and resources, checked 4 November 2026
- California AG: CCPA, checked 4 November 2026
