AI evaluation vs training data licensing rights: two clause-by-clause permitted-use checklists

Short answer

Training and evaluation licenses ask different scope questions because the records do different jobs. Training records change a model, so the questions are about which models, which methods and what survives the term. Evaluation records measure a model, so the questions are about staying out of training, who sees results and how long reruns are allowed. Each question below is tied to the clause of a signed license where counsel finds the answer, so a missing answer shows up as a missing clause.

Visual briefFull-size diagram
A signed license document with five clause tabs sits between a training checklist and an evaluation checklist; ticks appear on each list and connect to the clause where the answer is found.
Illustrative. The signed agreement, not a checklist, sets permitted use.

These checklists sit under the broader comparison of an evaluation-only data license. That page explains why the two uses differ; this one is the working tool a company's counsel holds against an agreement.

How to read a license with these checklists

Work from the signed or draft agreement, not from a summary of it. For each check, go to the clause named, and mark one of three results.

ResultMeaningWhat happens next
AnsweredThe clause states the answer in terms someone outside the deal could applyNothing; note the clause number
SilentThe clause exists but does not address the questionCounsel raises it with SourceX before signature
ConflictingTwo clauses point different waysCounsel resolves which governs, usually through the definitions or an order-of-precedence clause

Clause names vary between agreements. The five used here, definitions, grant, restrictions, term and termination, and ownership of outputs, are generic labels for where each topic usually lives.

Checklist A: training permitted use

Training scope is about what the records may shape and what remains afterward.

CheckClause to readAnswered looks likeFlag if
Methods coveredGrantLists the permitted methods, such as pretraining or fine-tuning"Any AI purpose" with no method or model named
Models and teams coveredGrant and definitionsDefines the licensee, its affiliates and contractors who may trainAffiliates undefined
Records in scopeDefinitionsNames systems, date ranges and record typesScope described only as "the dataset"
ExclusivityGrantStates whether the training right is exclusive and for how longExclusivity implied but no term stated
Trained models after the termTerm and terminationSays what happens to models trained during the termReturn or deletion of records only, nothing on models
RedistributionRestrictionsBars resale or sublicensing of the recordsSilent on onward transfer

On exclusivity, SourceX licenses are exclusive for AI training; the term and scope are agreed in each deal. The trade-offs are set out in exclusive vs non-exclusive data licenses, and onward transfer in whether licensed data can be resold.

Checklist B: evaluation permitted use

Evaluation scope is about separation. Google's machine learning course states the core rule: never train on test data, because duplicates across training and test sets mean the measurement stops reflecting how the model generalizes. The EU AI Act's Article 10 likewise treats testing data as its own category, used for an independent evaluation. A license that permits evaluation has to protect that separation in writing.

CheckClause to readAnswered looks likeFlag if
Held out from trainingRestrictionsBars any training use of the evaluation records, including by affiliates and contractorsTraining barred for the licensee only
Leak handlingRestrictions or terminationSays what happens if evaluation items reach a training runNo consequence stated
Scores and quotationRestrictions or confidentialityStates whether results may be published and whether records may be quotedSilent on publication
Reruns on later modelsGrant and termAllows a defined number of reruns or a defined retention periodRetention "as needed"
Rubrics and labelsOwnership of outputsSays who owns scores, rubrics or annotations built on the recordsSilent on derived materials
Return or destructionTerm and terminationCertified destruction at term end, with a dateDestruction "on request" only

The rubric-based evaluation guide shows what the derived materials in the fifth row usually look like.

Where the checklists collide: one archive, split scope (Illustrative)

Illustrative and fictional. A 410-person third-party logistics provider has eight years of carrier dispute tickets. Leadership will consider training use for routine tickets and wants the 2,000 hardest disputes, those with a documented final ruling, kept for evaluation only.

Collision pointTraining answerEvaluation answerClause that must reconcile them
Which ticketsRoutine tickets, 2017 onwardThe 2,000 ruled disputes, named by ticket ID rangeDefinitions: two separate defined sets
OverlapMust exclude the evaluation setMust never appear in trainingRestrictions: express carve-out from the training grant
After the termTrained models stay with the licenseeCopies destroyed after the last permitted rerunTerm and termination: separate survival rules
SharedCustomer contract limits and redactionCustomer contract limits and redactionWarranties and the agreed redaction schedule

If the definitions clause does not separate the two sets, every later clause inherits the ambiguity, which is why it is the first place counsel looks. None of this sets a price; terms are agreed in writing between the company and SourceX.

What the partner records, and what only counsel reads

A partner's part is metadata: that the records exist, roughly how many and over which years, which system holds them, and who can authorize a licensing discussion. A partner never asks for samples and never reads the agreement. Gaps in permission are easier to catch before the first call; see identifying missing permissions before a discovery call.

Introduced companies need 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Who qualifies has the full list. What stays unknown until SourceX reviews the company: whether buyers want an evaluation set at all, whether the company's own customer contracts allow either use, and any offer.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If an owner wants their counsel to test either scope against these checklists, register as a partner before making the introduction, and point them to the program terms and who qualifies; the reward is paid separately by SourceX and never comes out of the company's compensation.

Common questions

Can a partner fill in these checklists for the company?

No. The checklists are for the company's counsel reading a draft or signed agreement. A partner can share the page, but does not read contracts, judge scope or negotiate terms.

Why tie each check to a clause?

Because the same question can be answered in different places. Held-out status may sit in the grant, the restrictions or the confidentiality clause; pointing to the clause makes it clear whether the answer is in writing at all.

Does the reward depend on which checklist applies?

No. The reward is the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout SourceX pays the company, with no cap, whichever use the agreement permits.

Sources

  1. developers.google.com/machine-learning/crash-course/overfitting/di…
  2. eur-lex.europa.eu/legal-content/EN/TXT/PDF
  3. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment