
Is it legal to sell business data? Often yes, when the data is yours, your contracts allow it, and it is properly de-identified. This guide covers SaaS terms, employee and customer privacy, state laws like the CCPA, HIPAA and the FTC. General information, not legal advice.
This page is general information, not legal advice. Laws differ by state and country, they change, and the right answer depends on your contracts and your facts. Use this guide to organize the questions, then take them to your attorney before you license anything.
The short answer
In the United States there is no single law that says a business may or may not license its own operational records. Instead, the answer comes from layers:
- Ownership: is the data actually the company's?
- Contracts: what did you promise customers, clients, vendors and employees?
- Privacy and sector laws: do state privacy laws, HIPAA or other rules apply to any of it?
- Fairness rules: would the use surprise people in a way the FTC could treat as unfair or deceptive?
When every layer clears, licensing de-identified operational data is generally something businesses can do. When any layer is unclear, that is exactly where your attorney should focus. The rest of this guide takes each layer in turn.
Layer 1: Do you own the data?
Most of what a business generates in the ordinary course of operations is business records: internal email, help desk tickets, project tasks, invoices, call logs, job schedules. Those are typically the company's records.
Ownership gets less clear when:
- A client owns the work product. Agencies, law firms, accountants and consultants often hold material that belongs to a client under an engagement letter or master services agreement.
- The data came from a partner. Data shared with you under a data-sharing or reseller agreement may carry use limits.
- The records were inherited. After an acquisition, the purchase agreement may define what the buyer can do with the target's historical data.
A practical test
Ask: "If we stopped working with this client, vendor or partner tomorrow, would we be entitled to keep this record?" If the honest answer is no, treat it as out of scope until a lawyer says otherwise.
Layer 2: SaaS vendor terms of service
Your data lives in software you rent: a CRM, a help desk, an accounting package, a phone system. Those vendors' terms matter in two ways.
- Ownership of content. Most business SaaS agreements say the customer owns the content it puts in. Confirm that yours do.
- Export and use limits. Some agreements limit bulk export methods, automated scraping or API usage. Use the vendor's sanctioned export tools and stay inside rate limits and acceptable-use rules.
Note what you are not licensing: the vendor's software, schema documentation, or anything the vendor itself owns. You are licensing your own records, de-identified, that happen to be stored in their system. Each tool page on this site describes the native export path for that system.
Layer 3: Customer privacy and your own promises
Even if you own the records, you may have made promises about how you would use the personal information inside them. Your privacy notice, your terms of service and individual customer contracts all count.
The FTC has been direct about this. In a February 2024 Technology Blog post, the agency warned that a company that adopts more permissive data practices, such as using data to train AI, and tells people only through a quiet, retroactive change to its terms or privacy policy may be engaging in unfair or deceptive conduct. The lesson for sellers: do not rewrite old promises to fit a new deal. Remove personal data instead.
That is why our model is built around exclusion rather than consent tricks:
We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
What buyers receive is the operational pattern (timings, categories, sequences, outcomes), not the people. Your attorney should still compare your specific notices against the planned de-identification.
Layer 4: Employee communications
Email and chat archives contain the words of your own staff. In many workplaces, written policies already state that company systems and their contents belong to the business and are not private. Check whether yours says so, and whether it has been acknowledged by employees.
Practical safeguards that most counsel will want to see:
- remove or replace employee names, email addresses, phone numbers and signatures;
- strip personal topics, HR matters and anything about health, benefits or discipline;
- replace individual identities with role labels such as "support agent" or "project manager";
- exclude mailboxes or channels used for legal, HR or executive confidential matters.
Some states and countries have specific rules on employee monitoring and employee data. If you operate outside the United States, or have staff in multiple states, make sure your attorney knows.
Layer 5: State privacy laws and de-identified data
A growing number of U.S. states have comprehensive consumer privacy laws. California's is the best known, and it is a useful model for understanding how de-identification works legally.
Under the California Consumer Privacy Act as amended by the CPRA, "personal information" does not include consumer information that is deidentified or aggregate consumer information (Civil Code 1798.140, subdivision (v)(3)). But "deidentified" has a specific meaning in subdivision (m). The business holding the information must:
- take reasonable measures to ensure the information cannot be associated with a consumer or household;
- publicly commit to maintain and use it in deidentified form and not attempt to reidentify it; and
- contractually obligate any recipients to comply with the same requirements.
Notice that two of the three conditions are about promises and contracts, not just technique. A good data license carries those obligations forward to the buyer. California's Attorney General notes the CPRA amendments took effect January 1, 2023. Other states use similar but not identical definitions, so ask your attorney which ones apply to you.
Hashing is not de-identification
The FTC reiterated in July 2024 that hashing an identifier does not make data anonymous, because a hash is still a unique identifier that can track a person. Real de-identification removes or generalizes the identifying fields rather than disguising them. Our de-identified data guide explains the difference.
Layer 6: HIPAA and healthcare practices
Health information held by covered entities and their business associates is governed by HIPAA. HIPAA recognizes two ways to de-identify protected health information, set out at 45 CFR 164.514(b):
- Expert Determination: a qualified expert applies statistical and scientific methods and documents that the risk of re-identification is very small.
- Safe Harbor: 18 specified categories of identifiers are removed and the covered entity has no actual knowledge that the remainder could identify an individual.
We do not operate in that space. Patient records are never part of a deal, and PHI is never accepted, even in de-identified form. For clinics, dental and veterinary practices, only administrative operations such as scheduling patterns and billing workflow are considered, with identifiers removed. See the healthcare practices page and the practice system admin page.
Layer 7: The license agreement itself
Selling data almost never means handing over ownership. It means granting a license: a contract that says what the buyer may do, for how long, and under what limits. A sound data licensing agreement typically covers:
- Scope: which systems, date ranges and fields are included.
- Permitted use: for example, training and evaluating machine learning models.
- Re-identification ban: the buyer may not try to reverse the de-identification.
- Onward transfer: whether, and under what conditions, the buyer may share the data.
- Security: how the data is stored and who can access it.
- Representations and warranties: what each side promises about the data.
- Payment terms and term length.
For a fuller walk-through, see data licensing agreements.
When to call your attorney (and what to bring)
Bring in counsel before you sign anything, and ideally before you share more than a header sample. You will save time if you bring:
- a list of systems and date ranges (the data readiness checklist produces this);
- your current privacy notice, customer terms and any major client contracts;
- your employee handbook sections on systems and communications;
- a header sample for each system, which shows exactly which fields exist without exposing any records;
- the draft license and the de-identification plan.
A header sample is a useful legal tool in its own right: it lets your attorney see what personal fields exist and confirm they will be removed, without anyone touching real data.
How the process stays inside the lines
Our process is designed so that legal review happens before anything sensitive moves:
- You tell us your tools, years, seats and volume at /get-a-bid.
- You share a header sample: field names, never records.
- Buyers submit competing bids based on that description.
- Only after you accept, the data is de-identified inside your control, licensed under written terms, delivered, and you are paid.
According to founder Jeff Cline, deals typically close in about 90 days, which leaves room for proper legal review. Results vary; not a guarantee. Read how it works for detail on each step.
Frequently asked questions
Is it legal to sell my company's data?
Often yes, if the company owns the data, its contracts and privacy promises allow the use, and the data is properly de-identified. The answer depends on your specific contracts and the laws that apply to you, so have your attorney review the deal. This is general information, not legal advice.
Does the CCPA allow businesses to sell de-identified data?
The CCPA excludes deidentified consumer information from its definition of personal information, but only if the business meets three conditions: reasonable technical measures, a public commitment not to reidentify, and contracts binding recipients to the same rules. Your attorney should confirm how this applies to you.
Can I sell data from my medical or dental practice?
Patient records and PHI are never included. We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control. Only administrative operations, such as scheduling and billing workflows, are considered.
Do I need my employees' permission to license email or chat data?
It depends on your policies and where your employees are located. Many companies already state that work systems belong to the business, and de-identification removes names and personal content. Ask your attorney whether additional notice is wise in your situation.
Is hashing names and emails enough to de-identify data?
No. The FTC has said that hashing does not make data anonymous, because a hashed value is still a unique identifier. Proper de-identification removes or generalizes identifying fields instead of disguising them.
Does my SaaS provider own my data?
Usually not. Most business SaaS agreements state that the customer owns the content it stores, while the vendor owns the software. Check your specific terms and use the vendor's approved export tools.
Can I change my privacy policy so I can sell data?
Be careful. The FTC warned in 2024 that quietly applying a more permissive policy retroactively to data already collected may be unfair or deceptive. The safer path is to exclude personal data entirely and license only de-identified operational patterns.
Do I sell ownership of the data?
Typically no. Data deals are usually licenses that grant a buyer specific rights, such as training machine learning models, for a defined scope and term, while you keep your original records.
Sources
- California Civil Code 1798.140 (definitions, incl. (m) deidentified and (v)(3))
- California Attorney General: California Consumer Privacy Act (CCPA)
- California Privacy Protection Agency: Regulations
- U.S. HHS: Guidance on de-identification of protected health information
- 45 CFR 164.514 (Cornell LII): de-identification standard
- FTC Technology Blog: AI (and other) companies: quietly changing your terms of service could be unfair or deceptive (Feb 2024)
- FTC Technology Blog: No, hashing still doesn't make your data anonymous (July 2024)
Updated November 19, 2026.
OpenDataPolicies.org connects businesses with buyers of de-identified operational data. We are not a law firm, broker-dealer or investment adviser, and nothing on this site is legal, tax or financial advice. Statements about amounts, timing and outcomes are Jeff Cline's statements based on past transactions. Results vary; nothing here is a guarantee of any bid, price, buyer or closing. Every deal depends on the data, its quality, its rights and buyer demand at the time.