Compliance first: We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Home / Insights / Checklist
Checklist

Data Rights Checklist: What to Confirm Before You Sell Business Data

Data Rights Checklist: What to Confirm Before You Sell Business Data

Before you license your company's data to AI builders, confirm you actually have the right to. This checklist covers ownership, customer contracts, software vendor terms, employee notice and privacy laws such as California's definition of a data "sale." Informational, not legal advice.

Selling or licensing operational data is a legitimate business decision, but it is only as solid as your rights to the data. Buyers will ask. Their lawyers will ask harder. Working through the questions below before you request a bid makes the deal faster and protects you afterward. This article is informational and is not legal advice; laws vary by state and country, so talk to your own attorney about your specific situation.

By OpenDataPolicies Editorial · October 29, 2026 · 6 min read

1. Do you own or control the data?

Start with the basic question: is this your company's data to license?

  • Records your business created in the course of operating (internal email, project tasks, ticket histories, bookkeeping entries) are usually the strongest candidates.
  • Records that belong to clients under a contract, such as client files held by an accounting firm or matter documents held by a law firm, may be governed by engagement letters, confidentiality duties and professional rules. They often need to be excluded or handled with extra care.
  • Data from a past acquisition may come with restrictions from the original purchase agreement.
  • Shared or co-owned data from joint ventures or partnerships may need the other party's consent.

Write down, system by system, what is clearly yours, what is uncertain and what is out. That inventory doubles as the starting point for your data readiness checklist.

2. What do your customer and partner contracts say?

Pull your standard terms of service, master service agreements and NDAs and look for:

  • Confidentiality clauses that restrict use of information received from customers.
  • Data use limits that say information may be used only to provide the service.
  • Privacy commitments in your own published privacy policy. If your policy promises you will never share data with third parties, that promise matters even for de-identified data, and you may need to update the policy going forward.
  • Notice or consent requirements for new uses of data.

De-identification changes the analysis a great deal, because many restrictions apply to identifiable or confidential information. But do not assume; read the actual language.

3. What do your software vendors' terms allow?

Your data lives inside tools: email platforms, CRMs, ticketing systems, accounting software. Generally, the customer owns the content it puts into business software, but check each vendor's terms for:

  • Export rights and the approved methods for bulk export (admin consoles, APIs, reports).
  • API usage limits and restrictions on automated extraction.
  • Restrictions on vendor-generated data such as aggregated benchmarks or metadata the vendor considers its own.

Our tool pages, such as Salesforce, Zendesk and QuickBooks, describe where to find counts in each system. Use the vendor's documented export paths rather than scraping.

4. Have you considered employee notice?

Operational data is full of employees' work: their emails, chats and notes. Even when names are removed, it is good practice, and in some places a legal requirement, to tell staff how company systems and records may be used.

Points to check:

  • Your employee handbook or acceptable use policy: does it say company systems and communications belong to the company and may be used for business purposes?
  • Local employee privacy rules, which vary widely, especially outside the U.S.
  • Union or works council agreements, where they apply.

A short, plain-English notice that the company may license de-identified operational records goes a long way toward avoiding surprises.

5. Which privacy laws could apply?

Privacy laws mostly regulate personal information, which is why de-identification is the center of any operational data deal. Two frameworks are worth understanding even if you are a small business.

California (CCPA/CPRA). California's law defines "sell" broadly: "selling, renting, releasing, disclosing, disseminating, making available, transferring, or otherwise communicating orally, in writing, or by electronic or other means, a consumer's personal information by the business to a third party for monetary or other valuable consideration" (CCPA statute text, CPPA). Consumers have the right to opt out of the sale or sharing of their personal information (California Attorney General).

The same statute defines deidentified information as information that cannot reasonably be used to infer information about, or be linked to, a particular consumer, provided the business takes reasonable measures to prevent association, publicly commits to keep it deidentified and not attempt re-identification, and contractually obligates recipients to comply (CCPA statute text).

Whether the CCPA applies to your business at all depends on thresholds. The California Privacy Protection Agency lists them, including gross annual revenue of $26.625 million or more (effective January 1, 2025), buying, selling or sharing the personal information of 100,000 or more California residents or households, or deriving 50% or more of annual revenue from selling or sharing it (CPPA FAQ).

Europe (GDPR). GDPR does not apply to anonymous information, but pseudonymized data that could be re-attributed with additional information is still personal data (GDPR Recital 26). If you have EU customers or staff, the bar for "anonymous" is high.

Other U.S. states have passed comprehensive privacy laws with their own definitions. Ask your attorney which apply to you.

This is the reason for our firm rule: we never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control. Our explainer on de-identification techniques covers how that works.

6. Are there sector-specific rules?

Some industries carry extra obligations:

  • Healthcare and dental: HIPAA and state health privacy laws. ODP works with admin-side workflows only and never patient records. See healthcare practices and dental and veterinary.
  • Financial services and lending: financial privacy rules govern customer financial information. See financial advisors and lending.
  • Legal: client confidentiality and professional conduct rules. See law firms.
  • Education: student records laws. Only administrative operations are in scope; see education providers.
  • Payment card data: card numbers should never be part of any data set.

7. What will the license actually grant?

Once you are confident in your rights, think about what you are granting. Key terms to understand before you see a data licensing agreement:

  • License vs. sale: most deals license a copy; you keep the originals.
  • Exclusivity: an exclusive license usually commands a higher price but limits who else you can license to. See /glossary#exclusivity.
  • Term: a perpetual license versus a term license.
  • Permitted uses: for example training, evaluation, or fine-tuning only.
  • Re-identification ban: recipients should be contractually barred from attempting to re-identify anyone.
  • Payment: amount, timing and any escrow, all set in the purchase agreement.

The checklist, in one place

  • I have listed every system and confirmed which data my company owns or controls.
  • I have excluded client-owned, PHI, payment card and personal customer data.
  • I have read the confidentiality and data-use clauses in my customer contracts.
  • My privacy policy does not promise something a data license would break.
  • I have checked each software vendor's export terms.
  • Employees have been, or will be, given notice that de-identified operational records may be licensed.
  • I know which privacy laws (CCPA, GDPR, other states) might apply, and I have talked to counsel.
  • I understand exclusivity, term and permitted-use options.

When you are through it, the next step is a header sample and a free bid request. According to founder Jeff Cline, bids typically arrive within 72 hours if the data is correct and a header sample is provided. Results vary; not a guarantee. For a broader view of legality, see is it legal to sell business data?.

Our compliance promise: We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.

Frequently asked questions

Is selling de-identified business data legal?

In many cases, yes, but it depends on your contracts, your privacy policy, applicable privacy laws and your industry. Properly de-identified data generally falls outside laws that regulate personal information. This is informational, not legal advice; check with your attorney.

Does the CCPA's definition of "sale" apply to my data deal?

The CCPA's definition of sale covers personal information transferred for monetary or other valuable consideration. Properly deidentified information, as the statute defines it, is treated differently. Whether the CCPA applies at all depends on revenue and volume thresholds published by the CPPA.

Do I need employee consent to license company email?

Rules vary by location. Many employers' handbooks already state company systems belong to the company, but giving staff clear notice is good practice and may be required in some places. Ask your counsel.

What data does ODP never take?

We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.

Sources

  1. California Privacy Protection Agency — CCPA statute text (Civ. Code 1798.140)
  2. California Privacy Protection Agency — FAQ (applicability thresholds)
  3. California Attorney General — CCPA overview
  4. GDPR Recital 26 — Not applicable to anonymous data

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.