The Rights Checklist Before Licensing Data for AI

Buyers of AI training data do not pay for bytes. They pay for the right to use them. Every disclosed licensing deal, and every private one, is at bottom a rights transaction: the data merely carries the rights along. Which means the preparation that matters most before a deal is not technical. It is knowing what you own, what covers the people in your material, and what, if anything, stands in the way.

The good news is that the list is shorter than sellers fear, and most of it can be fixed. This is the checklist a specialist walks with every consignor, in the order that decides a deal.

Ownership comes first

Start with who made the material. Work created by employees in the course of their jobs generally belongs to the company outright: the codebase your team wrote, the manuals your staff produced, the recordings your systems made. Contractors are the first wrinkle. Their output belongs to whoever the contract says it belongs to, and older agreements are sometimes silent. Acquired assets are the second. If the archive arrived through a merger or a purchase, the rights must have arrived with it, which is usually a matter of reading the agreement rather than renegotiating it.

None of this needs to be perfect before you consign. It needs to be knowable. A seller who can say who created what, under which terms, is ready. A seller who cannot yet say is one inventory away from ready.

That inventory is smaller than it sounds. For most companies it is an afternoon with a spreadsheet: the categories of material you hold, who produced each, and which contracts touch them. Sellers routinely overestimate this step because they imagine it done to litigation standard. It is not. It is done to description standard, enough to tell a specialist the truth, and the specialist tells you which parts actually matter.

The consent posture

Where people appear in the data, consent decides scope. Recorded calls made on lines with recording notices carry a usable posture. Releases on file widen what a buyer may do with images and footage. Terms of service govern user-generated material. The key point is that consent is a spectrum, not a gate: a weaker posture narrows the license a buyer can take rather than blocking the deal outright. And an honest description of the posture is worth more than an optimistic one, because only the honest one survives diligence.

Two practical notes. Consent documentation you already have is worth gathering before it scatters: release forms, notice scripts, the terms your users accepted and when they accepted them. And the absence of documentation is information, not disqualification. Plenty of archives license on a narrowed scope precisely because the posture was described honestly at the start.

Third-party material inside the archive

Almost every real archive contains material that belongs to someone else. Licensed stock inside designs. Embedded libraries inside code. Client deliverables inside project folders. Outside correspondents inside email threads. The wrong response is to pretend it is not there. The right response is an inventory and a decision per category: exclude it, generalize it, or confirm that the license you hold covers the use. Exclusions are entirely normal; no buyer expects an archive with no edges.

Employee and customer identities

The asset a buyer wants is the work, not the people who did it or received it. Names, contact details, account identifiers, and the personal texture of records are removed or generalized to a documented standard during preparation, before any buyer reviews the material. Your obligation as a seller is disclosure, not scrubbing: say where identities live in the data, and preparation handles them. Attempting to scrub your own archive in advance usually removes value along with the names.

What preparation fixes

A useful division: preparation can fix the state of the data, and only you can establish the truth about it. On the fixable side sit secrets and credentials buried in code history, identities in records, duplicates, inconsistent formats, and the excision of third-party material, all handled at the house's cost and to standards a buyer will audit. Fixable problems should not delay a consignment by a single day.

What must already be true

Three things cannot be manufactured after the fact. You own the material or hold the rights to license it. You can describe its provenance honestly, because diligence will test the description. And no binding agreement forbids the use: a client NDA that covers the deliverables, or a data processing agreement that restricts what customer records may be used for, must be read and resolved, not papered over. Where such an agreement exists, the answer is usually scope, licensing the part of the archive the agreement does not reach, rather than abandoning the deal.

Sellers sometimes ask whether to fix a rights question quietly and say nothing. The answer is no, for a commercial reason rather than a moral one: every serious buyer runs diligence, and a surprise found there costs more than the same fact disclosed on day one. Disclosure prices the issue into the range. Discovery collapses the deal.

The checklist

Seven yeses make a fast deal. A few maybes make a normal one. The specialist's first job is turning maybes into answers, and that work, like the rest of preparation, costs you nothing.