Licensing
What “rights-reviewed” should mean for code training data
A rights review is only useful if you know what it covered. Here is the structure we use and the questions it answers.
Buyers increasingly ask suppliers to show that training data was obtained and licensed properly. “Reviewed” on its own says little. What matters is what was reviewed, against which intended use, and what was left out of scope.
Separate the questions
We treat a rights review as a set of distinct questions, each with its own answer and evidence, rather than a single approval flag:
- Ownership: who holds the copyright and other rights in the material, and how they came to hold them.
- Authority: whether the person submitting the data can license it on the owner’s behalf.
- Inbound licenses: which open-source or commercial licenses apply to included code and what conditions they impose.
- Third-party content: vendored libraries, copied snippets, or data from other systems.
- Obligations: employment, contractor, client, and confidentiality terms that may restrict onward use.
- Permitted uses: which specific uses — pre-training, fine-tuning, evaluation — the owner can and will license.
Record the scope
Every review should state what it did not cover. A review of a company’s IP assignment clauses, for example, says nothing about whether individual files were copied from elsewhere. Recording scope lets a buyer’s counsel decide what additional assurance, if any, they need.
Tie rights to versions
Rights attach to specific content. If a dataset is extended with new sources, the new version needs its own review. Keeping published versions immutable makes it possible to say exactly what a license covers.
What a review is not
A documented review reduces uncertainty; it does not eliminate it, and it is not a substitute for the warranties and remedies in a license agreement. Be wary of anyone who claims otherwise.