The license names one licensee, but affiliates, contractors, customers, resellers and a future acquirer can all sit behind it, and who gets the data next is one of the choices in AI training data licensing. Keeping the grant non-sublicensable, or not licensing at all, is a valid outcome.
Sublicense, Assignment, Resale and Onward Transfer Defined
Four mechanisms move licensed data beyond the first buyer, and each is controlled by a different clause.
- Sublicense: the licensee grants a third party rights out of its own license and stays bound to the licensor.
- Assignment: the whole contract moves to a new party, usually on a merger or asset sale.
- Resale or redistribution: the licensee hands the data itself on as a product.
- Onward transfer: the privacy and export-law term for any further disclosure of the data.
Which uses each recipient may make of the data is the purpose clause's job, set out under field of use and scope limits.
Onward Transfer Terms in Published AI Data Contracts
Published AI data terms fall between two poles: non-sublicensable and non-transferable, or sublicensable through multiple tiers to customers and their service providers.
The table compares 13 published terms as of 2026-11-09 (micro1 re-read 2026-11-17).
| Party (role) | Document | Sublicensing and transfer | Resale and downstream limits | Source and check date |
|---|---|---|---|---|
| Asimov (contributor-side terms) | Contributor agreement (version 2026-06-20.us-launch) | "worldwide, transferable, sublicensable, royalty-free, paid-up license" | deletion does not recall data already licensed, sold or shared | tryasimov.ai/contributor-agreement, 2026-11-09 |
| Corpus Bridge (intermediary) | illustrative draft on home page | not stated | model training only, "no resale" | corpusbridge.com, 2026-11-09 |
| Defined.ai (licensor of its datasets) | Data License Agreement, effective 2022-11-30 | non-exclusive, non-sublicensable, non-transferable (1(a)) | chain ends at the customer | defined.ai/data-license-agreement, 2026-11-09 |
| ELRA / ELDA (distributor) | distribution licensing | users get a non-exclusive, non-transferable right | no redistribution | elra.info, 2026-11-09 |
| Endless (licensee and sublicensor) | home and FAQ | non-exclusive; Endless licenses to labs | not stated | endless-data.com, 2026-11-09 |
| Kled (contributor-side terms) | Terms of Service | transferable, fully sub-licensable, perpetual, irrevocable | Kled may but need not delete on account deletion | kled.ai/terms-of-service, 2026-11-09 |
| Labelbox Prism (buyer) | Prism FAQ | not stated before revocation | after revocation no further training, transfer or sublicensing; change-of-control trigger | prism.labelbox.com/faq, 2026-11-09 |
| micro1 (buyer) | Data License Master Terms, last updated 2026-11-12 | licensee and affiliates; customers and their affiliates and service providers; multi-tier (s.1.2); assignment in a merger, not to a competitor (s.9.1) | PII measures before customer training (s.1.4(a)); no standalone resale (s.1.4(e)); flow-down (s.2.6) | micro1.ai/legal/data-license-master-terms, re-read 2026-11-17 |
| Origin Lab (buyer) | IP holders page | not stated | "not for reselling or republishing" | originlab.ai/ip-holders, 2026-11-09 |
| Patronus AI (buyer) | data page | not stated | "does not resell code or records" | data.patronus.ai, 2026-11-09 |
| Protege (marketplace) | Provider Terms | non-exclusive license to Protege (s.1.1) | licensees keep access 12 months, academic 3 years after termination (s.7.2) | withprotege.ai/provider-terms, 2026-11-09 |
| Proximal (service provider) | MSA, last updated 2026-07-06 | customer license non-transferable, non-sublicensable, internal business use (s.8.2) | not applicable | proximal.ai/msa, 2026-11-09 |
| Turing Project Lazarus (intermediary) | program page | license to Turing exclusive for the first 6 months | Turing "may license the same record to more than one lab" | lazarus.turing.com, 2026-11-17 |
Each entry is the stating party's own published wording; the order form can change it. Asimov and Kled terms bind individual contributors, not companies.
Many company-data programs publish no sublicensing term at all, so the order form decides. The license clause matrix compares published buyer contracts clause by clause.
Who Else Can Receive the Data Under a Sublicensable Grant
A sublicensable grant reaches four groups beyond the signing buyer: its affiliates, its contractors, its customers and, for vendors, their own licensees.
The Buyer's Affiliates
Affiliate rights let every company in the buyer's group use the data under one signature. micro1's grant runs to "Licensee and its affiliates" (s.1.2, Data License Master Terms, last updated November 12, 2026, read November 17, 2026), and which entities count as affiliates follows the contract's own definition, which this page does not cover.
Contractors and Service Providers
Contractors and service providers receive the data to work for the buyer, and published terms name them expressly. micro1 extends customer rights to customers' "affiliates and service providers" (s.1.2), and the Tempus side letter keeps "subcontractors" inside its restriction next to BMS and Pathos.
Proximal's services contract, by contrast, gives its customer a non-transferable, non-sublicensable license for internal business use (s.8.2, checked November 9, 2026).
The Buyer's Customers and the Models They Build
A customer sublicense lets the buyer's own clients train on the seller's data, which multiplies the number of models built from it.
micro1 may grant its customers "the same rights in the Data" (s.1.2), but may not sublicense to a customer for AI training without first implementing reasonable measures to "redact, anonymize, or pseudonymize" (s.1.4(a)).
What the customer may keep of the models and outputs is a question of ownership, not of the data: what customers keep is a question of ownership of derivatives and models trained on licensed data.
Downstream Licensees of Vendors and Intermediaries
Some counterparties take a license precisely to license the data on, so onward transfer is the business model rather than an exception. Each of these states its terms, checked November 9, 2026:
- Endless states a non-exclusive license and licenses to labs.
- Turing states that the license to Turing is exclusive for the first 6 months and that "we may license the same record to more than one lab" (checked 2026-11-17).
- Protege states a non-exclusive license (s.1.1), and its licensees keep access after termination.
- Defined.ai states that it licenses its datasets to customers on non-sublicensable, non-transferable terms (1(a)), so the chain stops at its customer.
Placing the same data with several buyers this way is a parallel-selling choice, covered under running several AI data buyers in parallel.
Flow-Down: Duties That Must Travel With Every Copy
A flow-down clause makes each downstream recipient carry the same duties the first buyer accepted, so the seller's protections do not stop at the first signature.
micro1 s.2.6 requires that before providing Data to an affiliate or customer, the licensee "shall ensure that such party is bound to confidentiality, security, and permitted-use obligations" that are "substantially equivalent" to its own (read November 17, 2026). What flow-down does not do:
- The seller has no direct contract with the sublicensee.
- Enforcement runs through the buyer, whose indemnity covers use or sublicensing outside the license scope (micro1 s.8.2).
- Flow-down does not reveal who the recipients are.
The encryption, access and breach-notice terms themselves are covered under security during an AI data sale.
Assignment and a Change of Control at the Buyer
An assignment clause decides whether the whole license, with every right in it, can move to a new owner of the buyer.
micro1 s.9.1 bars assignment "without the prior written consent of the other party", except that either party may assign in connection with a merger, acquisition, or sale of all or substantially all of its assets, and no such assignment may be made to a competitor of the other party without consent (read November 17, 2026).
Labelbox states that every Prism license has a kill clause with a seller-defined change-of-control trigger, deletion within 30 days, and no further training, transfer or sublicensing after revocation (checked November 9, 2026).
When the seller itself is acquired, the question flips to who may license the target's records, which is answered under data from acquired companies.
Sublicenses Disclosed in SEC Filings
Tempus AI's filings show sublicensing on both sides of one relationship, with named sublicensees and a fee attached to one of them.
Under the 2025 Pathos license of de-identified oncology data for the sole purpose of training a foundation model, Tempus receives a license to the model that is sublicensable to AstraZeneca, which pays Tempus a USD 35 million fee under a separate statement of work (10-K for the year ended 2025-12-31).
The neurology order form of 2026-10-22 licenses 500,000 de-identified records to Pathos with a sublicense to BMS, and a side letter bars Tempus from licensing the records to third parties other than BMS, Pathos and subcontractors for 18 months after the later of delivery and 2027-10-22 (10-Q for the quarter ended 2026-09-30).
These are health data from a licensor that is itself a data company, not a norm for company data.
What Happens to Sublicensees When the Main License Ends
Ending the main license does not automatically end the rights of everyone who received the data under it.
Protege's Provider Terms let licensees keep access 12 months, and academic licensees 3 years, after termination (s.7.2, checked November 9, 2026), while Labelbox states no further training, transfer or sublicensing after revocation.
Contributor-side terms show the far end. Asimov's contributor agreement takes a "worldwide, transferable, sublicensable" license, and deletion does not recall data already licensed, sold or shared, and micro1's grant is irrevocable and perpetual (s.1.2).
Models a sublicensee already trained are a separate question, covered under retraining and model retention rights.
Onward Transfer Duties Set by Privacy and National Security Law
Some laws require onward-transfer terms in the contract, whatever the parties would otherwise agree.
California's definition of deidentified information requires contractual obligations on recipients (Cal. Civ. Code 1798.140(m), statute version effective 2026-01-01), and Utah's definition of deidentified data requires a public commitment and contractual flow-down (Utah Code 13-61-101, version in force 2023-12-31).
Personal data leaving the EU under the 2021 standard contractual clauses (Commission Implementing Decision (EU) 2021/914, in force 2021-06-27) is subject to a clause on onward transfers, Clause 8.7.
28 CFR Part 202 (in force 2025-04-08) requires data brokerage with any foreign person to carry a contractual bar on onward transfer to countries of concern and a report of known or suspected violations within 14 days (202.302). Thresholds and countries are on the DOJ bulk sensitive data rule page.
Clause Options That Limit Onward Transfer
Seven clause options narrow onward transfer, and each already appears in a published contract or filing.
- No sublicensing or transfer: Defined.ai 1(a) and Proximal s.8.2.
- Named sublicensees only: BMS and AstraZeneca in the Tempus filings.
- A condition before customer training: micro1 s.1.4(a), PII measures.
- Flow-down of equivalent duties: micro1 s.2.6.
- No resale of the data as such: micro1 s.1.4(e) "as a standalone data product", Origin Lab "not for reselling or republishing", Patronus "does not resell", The Corner "no resale until anonymized", and Corpus Bridge's illustrative draft "no resale".
- Assignment only in a merger and never to a competitor: micro1 s.9.1.
- A change-of-control exit: Labelbox's seller-defined trigger.
Any added restriction is negotiated against price, with no public figure. These options are traded against price when negotiating an AI data licensing deal.
Allowing Onward Transfer or Not: Benefits, Risks, Downsides and Alternatives
Allowing sublicensing widens the buyer's market for the data and narrows the seller's view of where it goes.
Benefits:
- Buyers with customers or affiliates may need it to sign.
- Intermediaries that license on can place data the seller could not reach.
- Flow-down and PII conditions can keep core protections.
Risks:
- Recipients stay unknown to the seller.
- Data can reach competitors through a customer unless the contract bars it.
- Downstream access can survive termination.
Downsides:
- Enforcement runs only through the buyer.
- Flow-down does not identify recipients.
- No public price difference exists between grants.
Alternatives:
- A non-sublicensable license.
- Named sublicensees only.
- Collective or purpose-limited licenses.
- Not licensing at all.
The full range sits under alternatives to selling data to AI labs, including not selling.
How Sublicensing Works With the Other Clauses of the License
Sublicensing sets who may receive the data, and the exclusivity, scope, term, audit and deletion clauses set what each recipient may do and for how long. The parent page explains every clause of AI data licensing agreements.
Related clause pages:
- Exclusive vs non-exclusive data licenses
- License term and perpetual licenses
- Audit rights in AI data licenses
- Deletion and return clauses
- Indemnities and warranties
- Governing law and disputes
Process steps:
Information, Not Legal Advice
This page explains sublicensing and onward transfer clauses for information and is not legal advice; a lawyer in the seller's jurisdiction should review any grant before signing. Whether a licensee may sublicense or assign when the contract is silent depends on national law and is not covered here.
Terms, Filings and Laws Cited on This Page
The terms above come from these documents, each checked on November 9, 2026, dated by its filing, or re-read on November 17, 2026.
- California CCPA and AI training data: statute version effective 2026-01-01
- Endless profile: home and FAQ
- Labelbox Prism profile: FAQ
- micro1 data buyer profile: Data License Master Terms, re-read 2026-11-17
- Protege profile: Provider Terms
- Tempus AI clinical data licensing deals: 10-K and 10-Q
- Transferring training data to US buyers: standard contractual clauses
- Turing Project Lazarus profile: program page
- Asimov, Corpus Bridge, Defined.ai, ELRA, Kled, Origin Lab, Patronus AI, Proximal, The Corner: published terms and pages
Frequently Asked Questions
What is the difference between a license and a sublicense?
A license is granted by the data owner; a sublicense is granted by the licensee to a third party out of the rights it received, so the licensee stays answerable to the owner.
What does a sublicensing clause in an AI data license look like?
micro1's master terms grant a license to the licensee and its affiliates "with the right to sublicense through multiple tiers" (s.1.2, re-read November 17, 2026).
Can an AI company resell the data I license to it?
Only if the contract allows it; micro1's terms bar reselling the data as a standalone data product (s.1.4(e)), and Origin Lab states its license is not for reselling (checked November 9, 2026).
What happens to my data license if the AI buyer is acquired?
It usually moves with the buyer: micro1's terms allow assignment without consent in a merger, acquisition or sale of substantially all assets, but not to a competitor of the other party (s.9.1, re-read November 17, 2026).