Know a company with years of records? Refer it and earn up to $100K
For general counsel and in-house lawyers

General Counsel Checklist for Licensing Data to AI Buyers

The legal review before a company licenses records for AI training: ownership, customer contracts, privacy, regulated records, terms and board approval.

A marked-up contract draft beside ribbon-tied precedents and law books
Short answer

Review rights before price. Confirm who owns each record set, read the customer, vendor and employee terms that touch it, check the privacy rule for each record type, and pull out export-controlled and regulated records. Only then negotiate: a non-exclusive licence limited to training and evaluation, with no re-identification, no resale, deletion at the end and a capped indemnity. The 12-item checklist below puts the steps in order.

  • Four checks come before any term sheet: ownership, contracts, privacy and regulated records.
  • Employee-made work is the company's by statute. Contractor-made work is not, without a written assignment.
  • A licence of identifiable records for money can be a "sale" under California law.
  • Most licences are management decisions, but check the charter, investor rights and lender covenants.

Who owns each record set?

Start with a list of record sets and one question for each: did the company create it, receive it or buy it? What employees made in their jobs is the company's. What contractors made, customers supplied or vendors licensed needs a document.

For copyright the statute is short: "In the case of a work made for hire, the employer or other person for whom the work was prepared is considered the author" and, unless the parties agreed otherwise in a signed writing, "owns all of the rights comprised in the copyright" (17 U.S.C. 201). A freelancer's or agency's work is not automatically within that rule, so look for the assignment.

Much of what a buyer wants is not copyright at all but confidential know-how. Federal law protects information as a trade secret only if "the owner thereof has taken reasonable measures to keep such information secret" (18 U.S.C. 1839). A licence should therefore keep the records confidential in the buyer's hands, or the company weakens the protection it relies on.

Record setUsual ownerDocument to find
Documents, code and designs made by employeesThe companyEmployment and invention assignment agreements
Work made by contractors, agencies and freelancersThe maker, unless assignedA signed assignment or work-for-hire clause
Content customers put into your product or sent youThe customerThe customer agreement and data processing terms
Deliverables made for a clientOften the clientThe statement of work and its IP clause
Data bought or licensed from a vendorThe vendorThe vendor licence. Resale is usually barred
Records of a company you acquiredDepends on the dealThe purchase agreement. See the guide to acquired and dormant entities

Which customer contracts block a licence?

Those with a confidentiality clause that covers the records, a use limitation, data processing terms, or an express restriction on AI training. One clause is enough. The practical output is an exceptions list: customers whose records stay out.

Data processing terms are the firmest block. Under European law a processor's contract must provide that it "processes the personal data only on documented instructions from the controller" (GDPR, Article 28). California's "service provider" is defined by a contract that prohibits "selling or sharing the personal information" (Cal. Civ. Code 1798.140). Licensing a customer's data to a third party is outside both.

The guide to NDAs and customer contracts goes through the four clauses and gives wording for consent requests and new contracts. Check vendor terms as well: software and data vendors often restrict what you may do with exports from their systems.

What is the privacy check for each record type?

Ask whose personal information is in the record set and which law treats a licence as a regulated disclosure. For most business records the answer is de-identification before delivery. For health records and consumer data there are extra conditions.

Record typeRule to checkWhat it says
Records with California residents' information, including business contacts and employeesCal. Civ. Code 1798.140"Sell" covers making personal information available "to a third party for monetary or other valuable consideration"
Records with personal data of people in EuropeGDPR, Article 5Data must not be "further processed in a manner that is incompatible with" the purposes it was collected for
Pseudonymised or hashed recordsGDPR, Recital 26Data "which could be attributed to a natural person by the use of additional information" is still personal data
Patient records held by a covered entity or business associate45 CFR 164.502It "may not sell protected health information" without authorisation. Sale includes receiving remuneration "directly or indirectly" for a disclosure
Email, chat and call archivesThe laws above, plus your own employee policies and noticesEmployees are data subjects too. Check what the handbook and monitoring notice told them

More detail: GDPR and CCPA in data licensing, de-identifying company data, patient records and Slack and email archives.

Which records are export-controlled or regulated?

Technical data for controlled items, patient records, tax return information and anything a regulator told the company to keep confidential. Identify them by record set before any sample is shared, because sharing with a foreign person can itself be an export.

Under the Export Administration Regulations, export includes "releasing or otherwise transferring 'technology' or source code (but not object code) to a foreign person in the United States (a 'deemed export')" (15 CFR 734.13). A buyer's engineering team is rarely all US persons. The ITAR and EAR checklist for CAD data shows how to screen engineering files.

Other regulated sets have their own gate. Tax preparers are bound by section 7216. Regulated financial firms, government contractors and companies under a consent order should read the confidentiality terms of the rule or order that applies to them.

Which licence terms should you hold firm on?

The ones that limit what the buyer may do with the records and what happens when the term ends. Price can move. These should not move much.

There is no published benchmark for indemnity in AI training data licences, so "normal" is what the two sides agree. Sellers commonly ask that the warranty on rights be limited to what the company knows after a reasonable review, that indemnities run both ways, and that liability be capped by reference to the fees. The data licensing agreement guide covers each clause.

TermPosition to start from
GrantNon-exclusive, to a named party, for training and evaluation of its models. No other use
Sublicensing and resaleNone. Affiliates and contractors only as needed and bound by the same terms
Re-identificationProhibited, with no attempt to contact anyone in the data
ConfidentialityThe records stay confidential. This also protects trade secret status
SecurityNamed storage location, access limits and breach notice
DeletionDelete or return at the end of the term, with a certificate. Say plainly what happens to trained models
Warranty on rightsLimited to the company's knowledge after reasonable review
Indemnity and capMutual, capped, with the buyer covering its own use of the data
AuditA right to confirm use and deletion
PublicityNo use of the company's name without consent

Exclusivity changes the price and the risk. See exclusive and non-exclusive data licences.

Does the board need to approve a data licence?

Often not as a matter of statute, but check four documents before deciding. A non-exclusive licence is normally a management decision within the board's general oversight. The documents that can change that are the charter, investor agreements, loan covenants and the company's own delegation of authority.

In Delaware, "the business and affairs of every corporation organized under this chapter shall be managed by or under the direction of a board of directors" (section 141). Stockholder approval enters when a corporation sells, leases or exchanges "all or substantially all of its property and assets" (section 271). A non-exclusive licence leaves the records with the company, so it is rarely that. An exclusive licence of the company's main asset deserves a closer look by counsel.

Venture-backed companies have a contractual layer on top. See the investor consent section of the guide for startups. Whatever the legal answer, a short memo to the board is good practice. The CFO guide has an outline.

The 12-item checklist

In order. Items 1 to 6 need no buyer and can be finished before any outside conversation.

  • 1. List the record sets, with the system each sits in and the years covered.
  • 2. Mark each set created, received or bought, and find the ownership document.
  • 3. Find contractor and agency assignments for anything they made.
  • 4. Read the standard customer terms and build the exceptions list of negotiated contracts.
  • 5. Read vendor terms for the systems the records come from and for any bought-in data.
  • 6. Identify personal data by set and choose the de-identification method.
  • 7. Pull export-controlled, health, tax and regulator-restricted records.
  • 8. Check employee policies and notices for email, chat and call archives.
  • 9. Check the charter, investor rights, loan covenants and delegation of authority for consent rights.
  • 10. Vet the buyer: who it is, where data is stored, who else gets access.
  • 11. Negotiate the terms in the table above and the deletion mechanics.
  • 12. Record the decision: a board memo or minute, the exceptions list and the delivery log.

For item 10, see how to vet an AI data buyer. For the buyer's questions to you, see due diligence in data licensing.

Common mistakes in the legal review

Most come from starting with the buyer's paper instead of the company's own records.

  • Reviewing the licence draft before anyone has checked ownership.
  • Reading the standard customer terms and missing the negotiated ones.
  • Assuming contractor work belongs to the company.
  • Treating hashed identifiers as anonymous.
  • Sending a sample before the export-control screen.
  • Giving an unqualified warranty that the company has every right needed.
  • Leaving out what happens to the data and the trained model at the end of the term.
  • Forgetting lender and investor consent rights until signing week.

Company records as a data asset

The review on this page is what turns an archive into something that can be licensed. A record set with a clear owner, a clean contract position and a documented de-identification method is rare, and that is why it has value to AI developers. The work is the same whether or not a deal follows, and it leaves the company with a better map of what it holds.

Origin works with buyers and helps a company describe what passes the checks, find out what it could be worth and decide whether to go further. Nothing is exported at the start, and your own counsel reviews any agreement. Origin Data Partners is an independent data partner that helps companies get their data bought. A buyer may pay Origin when a deal closes.

Does your company hold records like these? See what your data is worth.

Common questions

What should general counsel check before licensing data to an AI company?

Four things, in order: who owns each record set, which customer, vendor and employee terms restrict it, which privacy rule applies to each record type, and which records are export-controlled or regulated. Then the licence terms and any board, investor or lender consent.

Is employee consent needed to license chat and email archives?

There is no single rule. The archive usually belongs to the company, but employees are data subjects under GDPR and California law, so personal information has to be removed or de-identified and the use has to fit what employees were told. Check the handbook and monitoring notice.

What indemnity is normal in an AI training data licence?

There is no published benchmark. Sellers commonly ask for a warranty limited to their knowledge after reasonable review, indemnities that run both ways, a cap tied to the fees, and the buyer taking responsibility for how it uses the data and what its models produce.

Does licensing company data to an AI buyer need board approval?

Not usually by statute for a non-exclusive licence. Delaware requires stockholder approval only for a sale of all or substantially all assets. Check the charter, investor agreements, loan covenants and the delegation of authority, and brief the board in any case.

Which records should legal exclude from an AI data licence?

Customer content held under a service contract, anything under a confidentiality clause that covers it, bought-in vendor data, export-controlled technical data, patient records without a lawful route, tax return information and contractor work with no assignment.

Who owns work a contractor made for the company?

The contractor, unless a signed agreement says otherwise. The work-made-for-hire rule in 17 U.S.C. 201 makes an employer the author of employees' work. For freelancers and agencies, find the written assignment before licensing what they made.

Sources and further reading

What is your company’s data worth?

AI companies pay $20K to $5M for company records. Six questions, no files.