Short answer
Never include protected health information, payment card numbers, government ID numbers, children's data, identifiable customer or employee personal data, or data licensed to you by a third party. Paid4Data does not accept these. Personal details inside ordinary business records, such as names and emails in a CRM, are removed or transformed before any buyer sees the data.
The never-include list
| Category | Examples | Why it stays out |
|---|---|---|
| Protected health information (PHI) | Patient records, diagnoses, treatment notes, health plan data | HIPAA and state health-privacy laws. Paid4Data does not accept PHI, even de-identified. |
| Payment card data | Card numbers, CVVs, full magnetic-stripe or chip data | PCI DSS rules and fraud risk |
| Government ID numbers | Social Security numbers, driver's licence and passport numbers, tax IDs of individuals | Identity-theft risk and state data-security laws |
| Children's data | Any records about children, including under-13 data covered by COPPA | Heightened legal protection |
| Consumer financial information | Bank account details, credit reports, loan files tied to individuals | GLBA and the FCRA |
| Sensitive personal data | Biometrics, precise location, health, religion, sexual orientation, immigration status | Sensitive-data rules in state privacy laws and GDPR |
| Employee records | HR files, payroll, performance reviews, background checks | Employment and privacy law; high re-identification risk |
| Third-party licensed data | Purchased contact lists, market-data feeds, research subscriptions, vendor databases | You do not own it, and resale is usually forbidden |
| Confidential client material | Records a contract or professional duty keeps confidential, privileged legal files, tax returns without consent | Breach of contract or professional rules |
| Credentials and secrets | Passwords, API keys, private keys, access tokens | Security risk with no training value |
Personal data inside ordinary business records
Most operational systems contain some personal data even when the business is B2B: contact names in a CRM, signatures in email threads, phone numbers in tickets, addresses on invoices. This does not disqualify the whole source. Direct identifiers are removed or replaced before any buyer has access, free-text fields are scanned, and records with sensitive details are dropped. Paid4Data does not buy or sell consumer data and does not license data that identifies individuals. See how de-identification works.
Health data and HIPAA
If your business is a covered entity or business associate, or simply holds health details about people, keep those records out. HIPAA allows de-identification under specific methods, but Paid4Data excludes protected health information and patient records entirely, so medical practices and health-adjacent businesses should limit any discussion to non-patient operational data and get counsel first.
Licensed and third-party data
A common mistake is including data the company paid for but does not own: a purchased lead list, an industry pricing feed, analyst reports, or content inside a software tool. These licenses almost always forbid resale or sublicensing. Only records your business created, or has clear rights to, belong in a data license.
Mixed sources: what to do
- Filter, don't dump. Export only the objects, fields, and date ranges approved in the license.
- Drop whole records that mention health, children, or other sensitive details rather than trying to redact them.
- Exclude accounts whose contracts forbid secondary use.
- Keep a written list of what was excluded and why.
If you are unsure about a source, leave it out until it has been reviewed under a mutual NDA. Use the data rights checklist to decide.
What usually is suitable
De-identified CRM activity, invoices and bills, support threads, work orders, quotes, SOPs, and project files often qualify once identifiers are removed and rights are clear. See data sources and the guide to selling business data.
Common questions
What data should never be included in a business data sale?
Protected health information, payment card numbers, government ID numbers, children's data, identifiable customer or employee personal data, consumer financial information, credentials, and data licensed to you by a third party. Paid4Data does not accept these.
Can I sell HIPAA data if it is de-identified?
Paid4Data does not accept protected health information or patient records, even de-identified. Health-adjacent businesses should limit any discussion to non-patient operational data and get counsel first.
My CRM has customer names and emails. Can I still license it?
Often yes, as long as rights are clear. Names, emails, phone numbers, and other direct identifiers are removed or transformed before any buyer sees the data, and records with sensitive details are dropped.
Can I sell a contact list I bought?
No. Purchased lists and data feeds are licensed to you, not owned, and their terms usually forbid resale. They also contain identifiable personal data.
Should employee records be included?
No. HR, payroll, performance, and background-check records should stay out. Workplace messages that name employees need careful filtering or exclusion.
What if I'm not sure whether a source is allowed?
Leave it out until it has been reviewed under a mutual NDA, ideally with your own counsel. A smaller dataset with clean rights is more useful than a larger one with open questions.
Paid4Data does not promise a sale, price, or payout. This page is general information, not legal advice. Questions? Contact us.