Yes, a data license will come up in due diligence if you sell the company later, and the buyer’s lawyers will read it as closely as any customer contract. A well-documented, narrow license is one more contract on the schedule. An exclusive, perpetual license with an uncapped indemnity is a liability the acquirer inherits, and it can change what they will pay or what they ask you to promise. If you want a sense of what your records are worth before you weigh this, get a confidential estimate.
Owners usually say “sell” their data. In practice you license it: you keep ownership and grant a written right to use a copy. An acquirer then buys what you still own and steps into the rights you have already granted. Our overview, can you sell your company’s data to AI companies?, covers the basics.
Will a data license come up in due diligence?
Yes. Daniel Goldberg of Frankfurt Kurnit Klein & Selz (FKKS) put it plainly on Oct 1, 2026: “If the company is later acquired, a prior data sale will come up in diligence, and buyers will expect to see this record.” The same note says “gaps in data rights and notices can surface in M&A diligence and affect how the company and its data are valued.”
Buyers’ counsel review outbound IP licenses as a standard item. Gibson Dunn’s June 2023 technology diligence checklist lists the terms they look at: whether the license is “exclusive or nonexclusive,” whether it is “transferable or sublicensable,” royalties, scope, and any “change in control” or anti-assignment provisions. A data license to an AI lab or a data partner is an outbound license of your information, so expect the same questions.
Which clauses will the acquirer’s lawyers read first?
Seven clauses in a data license carry over to a new owner and get the closest reading: exclusivity, term, assignment, indemnity, deletion, revenue share and non-circumvention. Each example below is from a buyer’s published terms, read on Oct 27, 2026.
| Clause | Why an acquirer cares | Published example |
|---|---|---|
| Exclusivity | The acquirer cannot license the same records elsewhere, and may be bound itself if “affiliate” is drawn broadly | Labelbox Prism: “exclusive by default” (Prism) |
| Term and survival | Rights already granted may outlast the agreement and any sale of your company | pre.dev: buyer licenses are “perpetual, and irrevocable” once closed (section 6.1) |
| Assignment | Decides whether the license moves with the company or needs consent | pre.dev: owner may assign to a “successor in a merger, acquisition, or sale of substantially all assets” without consent (section 12.2) |
| Indemnity | Open-ended promises stay with the company after closing | pre.dev: owner’s indemnity is “not subject to any cap or exclusion” (section 9.4) |
| Deletion and retention | Shows where copies of the records still sit | micro1: deleted “upon request or at the end of an engagement”; Ooak Data: raw archive deleted within 30 days of delivery |
| Revenue share | An ongoing payment stream the acquirer will value and want to audit | Labelbox Prism: “an upfront licensing fee at signing plus a revenue share on downstream use” |
| Non-circumvention | Limits who the company can deal with directly | pre.dev: the owner may not close directly with a buyer pre.dev introduced, including buyers introduced up to 12 months after termination (section 11) |
pre.dev terms are from its Codebase Agreement, read Oct 27, 2026. Our guide to what’s in an AI data licensing agreement walks through each clause in more depth.
Does a change-of-control clause in a data license matter?
A change-of-control or anti-assignment clause decides whether a data license follows the business to its new owner, and on what terms. Gibson Dunn advises acquirers to confirm “early in the diligence process” whether a target’s IP agreements contain change-in-control or anti-assignment provisions. It notes that “some courts have held” a transfer of contractual IP rights in a forward merger breaches an anti-assignment clause, so the deal structure matters (June 2023).
pre.dev’s agreement lets the owner assign to a successor in a merger or acquisition without consent, and lets pre.dev assign without the owner’s consent (section 12.2). Ask for the first half of that in any data license you sign. Also look for a “springing” license, where a named event such as a change of control grants the counterparty new rights. Gibson Dunn flags these because a deal can trigger them.
Can an exclusive data license bind the company that buys you?
Yes. An exclusive data license binds the business you sell: if you gave an AI lab exclusive rights to five years of support tickets, the acquirer cannot license those tickets to anyone else until the exclusivity ends. The harder question is whether it reaches the acquirer’s own records. Gibson Dunn describes the “affiliate” problem for patent licenses: parties often “define this term in a manner that is perhaps unintentionally overly-broad,” so that after closing the license “could be deemed to apply to the acquiror’s patent portfolio” (June 2023). Ask your counsel whether the affiliate definition in a data license could do the same.
To keep exclusivity manageable in a sale, limit it to named systems and dates and give it a fixed end. Our guide to exclusive and non-exclusive licenses covers how to price and narrow it.
Does licensing records weaken our trade secrets?
Licensing internal records can weaken trade secret protection, and an acquirer will ask about it. Under the Defend Trade Secrets Act, information is a trade secret only if “the owner thereof has taken reasonable measures to keep such information secret” (18 U.S.C. 1839(3), read Oct 27, 2026). FKKS warns that a data sale may “jeopardize trade secret protection for pricing logic, strategy documents, and source code” (Oct 1, 2026).
Keep pricing models, strategy files and core source code out of scope unless the price justifies it, and make sure the license has confidentiality terms you can point to. FKKS also notes that email and chat hold other companies’ confidential information under NDAs, which you should exclude.
Do privacy promises carry over to the buyer?
Privacy promises made when the data was collected stay with it after an acquisition. In April 2014 the FTC told Facebook and WhatsApp that “regardless of the acquisition, WhatsApp must continue to honor these promises to consumers” (FTC, Apr 10, 2014). California’s CCPA says a transfer of personal information “as an asset that is part of a merger, acquisition, bankruptcy, or other transaction” is not a sale, provided it is used consistently with the law; a new owner that materially changes use must give prior notice (Cal. Civ. Code 1798.140(ad)(2)(C), CPPA text effective July 15, 2024).
That carve-out covers the acquisition. A data license to an AI lab is a separate transfer, and if it includes personal information it can count as a “sale” under the same section. Gibson Dunn also notes that a target’s own privacy policy “may require prior consent from the user to transfer its data in a merger or sale.” The acquirer’s privacy counsel will check both. Our guide on whether it is legal to sell company data to AI covers the privacy rules in more detail.
Should we sign a data license while we are negotiating a sale?
Only after talking to the buyer and your own counsel. Once a purchase agreement is signed, most deals require the seller to run the business “in the ordinary course” until closing and to get the buyer’s consent for anything outside it. Mayer Brown explains the purpose: “to give a buyer some certainty that, at closing, it will acquire the business in substantially the same condition as it was when the buyer performed its due diligence and valued the target” (The M&A Journal, April 2020). A first data license is hard to describe as ordinary course.
Before a purchase agreement is signed, the question is disclosure: if a buyer is already in diligence, tell them before you sign a license, because it changes what they are buying. Insurance is another reason to have the paperwork ready. Fasken notes that representation and warranty insurers may exclude AI risk, and that an exclusion “could be limited to a known issue, such as a particular data set” when the record is good. It lists “training data origin and usage rights” among the records sellers should assemble (Fasken, 2026, via ALFA International, read Oct 27, 2026).
What should be in the file before diligence starts?
FKKS recommends documenting “the review, exclusions, de-identification protocol, and business justification, along with any required risk assessment” (Oct 1, 2026). In practice that means:
- The signed license, every amendment, and any order or confirmation that set exclusivity or price.
- A list of systems, date ranges and fields licensed, and what was excluded.
- The de-identification standard used, who applied it, and a sample of the output.
- The privacy notices, employee handbooks and customer contracts in force when the records were created, and your counsel’s note on why the license fit them.
- Written confirmations of deletion, and the dates raw data left your control.
- Payment records, revenue-share statements and any audit rights.
- A short note on exclusivity: what it covers, for how long, and whether “affiliate” could reach a parent company.
If you are still choosing a buyer, this list is also a good test of a program. A buyer that will not give you clear scope, deletion and assignment terms is giving your future acquirer a harder contract to read. Figures on what buyers pay are in our market index and our guide on how much company data is worth.
How Marin Data handles this
If a sale of the company is possible in the next few years, tell any advisor or buyer at the start, so assignment, exclusivity and deletion terms are negotiated with that in mind. Marin Data costs the company nothing up front, and nothing at all if no deal closes; the AI lab pays us. We do not give legal advice. For any decision on a pending sale, talk to your own M&A counsel.
Get a confidential estimate. It takes two minutes and asks for no documents.
Sources
- Frankfurt Kurnit Klein & Selz, selling company data for AI training, Oct 1, 2026, read Oct 27, 2026
- Gibson Dunn, top technology sector-specific legal diligence concerns in acquisitions, June 8, 2023, read Oct 27, 2026
- pre.dev Codebase Agreement (PDF), sections 6.1, 9.4, 11 and 12.2, read Oct 27, 2026
- Labelbox Prism, micro1, data partnerships, Ooak Data, partner page, all read Oct 27, 2026
- 18 U.S.C. 1839, definitions (Defend Trade Secrets Act), read Oct 27, 2026
- FTC, FTC notifies Facebook, WhatsApp of privacy obligations, Apr 10, 2014, read Oct 27, 2026
- California Consumer Privacy Act, CPPA text effective July 15, 2024 (PDF), section 1798.140(ad), read Oct 27, 2026
- Mayer Brown, The M&A Journal, vol. 20 no. 4, pre-closing covenants, April 2020, read Oct 27, 2026
- Fasken, when AI meets RWI in M&A (via ALFA International), 2026, read Oct 27, 2026