AI Training Data License Agreement
AI TRAINING DATA LICENSE — TRANSACTION AND DRAFTING PACKET
Use this packet to identify the actual data, rights, systems, people, restrictions, and commercial terms before counsel drafts an operative license. It is deliberately non-operative and has no signature block. Blank fields and unchecked boxes are unresolved.
1. Matter control
| Item | Information |
|---|---|
| Proposed data provider or licensor | [________________________________] |
| Proposed recipient or licensee | [________________________________] |
| Other contributors, platforms, or data hosts | [________________________________] |
| Internal matter or project name | [________________________________] |
| Proposed effective date | [__/__/____] |
| Target delivery or access date | [__/__/____] |
| Reviewing counsel and jurisdictions | [________________________________] |
| Privacy reviewer | [________________________________] |
| Security reviewer | [________________________________] |
| Model or product owner | [________________________________] |
2. Transaction-classification gate
Counsel should classify the transaction before anyone describes a party as an owner or grants a right.
☐ One-time dataset delivery
☐ Continuing feed, API, hosted access, or subscription
☐ Publicly available material curated by a provider
☐ Provider-created or commissioned content
☐ Third-party licensed content
☐ User, customer, employee, contractor, or community content
☐ Personal, biometric, health, financial, location, communications, or other sensitive data
☐ Synthetic, generated, augmented, labeled, or inferred data
☐ Open-source, open-data, research, cultural, archival, or government material
☐ Cross-border collection, access, training, deployment, or distribution
☐ Exclusive field, territory, customer, model, or use restriction proposed
☐ Data acquisition, services, model development, or revenue share beyond a license
Counsel's classification and required related agreements: [________________________________]
3. Asset and component register
Avoid a single catch-all definition of “Training Data.” Identify each component and its source.
| Component ID | Description and format | Source or contributor | Date range | Volume | Storage location |
|---|---|---|---|---|---|
| [____] | [________________] | [________________] | [________] | [________] | [________________] |
| [____] | [________________] | [________________] | [________] | [________] | [________________] |
| [____] | [________________] | [________________] | [________] | [________] | [________________] |
For each component, identify separately:
☐ Raw content
☐ Labels or annotations
☐ Metadata
☐ Taxonomy or ontology
☐ Documentation and data cards
☐ Code, scripts, tools, or queries
☐ Embeddings, indexes, vectors, or features
☐ Updates, corrections, or deletion lists
☐ Credentials, keys, or access configuration
Excluded assets: [________________________________]
4. Provenance and rights ledger
A possession record is not a rights conclusion. Record the evidence supporting each proposed permission.
| Component ID | Collection or acquisition method | Governing source agreement or terms | Contributor permissions | Restrictions or reservations | Evidence file |
|---|---|---|---|---|---|
| [____] | [________] | [________] | [________] | [________] | [________] |
| [____] | [________] | [________] | [________] | [________] | [________] |
| [____] | [________] | [________] | [________] | [________] | [________] |
4.1 Rights questions
| Question | Response and evidence |
|---|---|
| Who created, collected, selected, arranged, labeled, or modified each component? | [________________________________] |
| Which rights does each proposed licensor actually control? | [________________________________] |
| Are any permissions nontransferable, revocable, time-limited, territory-limited, or use-limited? | [________________________________] |
| Do platform, website, API, repository, publisher, union, employment, or contributor terms apply? | [________________________________] |
| Are attribution, notice, share-alike, source, audit, reporting, or downstream-pass-through terms present? | [________________________________] |
| Are any opt-outs, objections, takedowns, deletion requests, disputes, or reservations recorded? | [________________________________] |
| Are confidential information, trade secrets, export controls, or security restrictions implicated? | [________________________________] |
Uncleared components and hold instructions: [________________________________]
5. Person-level data and privacy gate
Do not use labels such as “anonymous,” “public,” “consented,” or “de-identified” without a recorded method and reviewer conclusion.
| Review item | Finding, jurisdiction, and evidence |
|---|---|
| Categories of people represented or affected | [________________________________] |
| Data elements linked or linkable to a person | [________________________________] |
| Collection notice, permission, expectation, or other asserted basis | [________________________________] |
| Children, workers, patients, students, consumers, creators, or vulnerable groups | [________________________________] |
| Biometric, likeness, voice, image, health, financial, precise-location, or communications data | [________________________________] |
| De-identification, aggregation, pseudonymization, or synthetic-data method | [________________________________] |
| Re-identification and linkage risk | [________________________________] |
| Access, correction, deletion, objection, opt-out, or withdrawal process | [________________________________] |
| Retention and deletion controls | [________________________________] |
| Cross-border transfer, localization, or remote-access issue | [________________________________] |
| Required assessment, notice, contract, or regulator interaction | [________________________________] |
Separate privacy or processing document required: ☐ yes ☐ no ☐ unresolved
6. Intended model and use map
| Item | Proposed scope |
|---|---|
| Model, system, or product | [________________________________] |
| Pretraining, fine-tuning, retrieval, evaluation, benchmarking, safety testing, or other use | [________________________________] |
| Internal research, internal operations, customer product, or public deployment | [________________________________] |
| Model owner and operator | [________________________________] |
| Hosting and compute providers | [________________________________] |
| Users, customers, affiliates, contractors, and sublicensees | [________________________________] |
| Fields of use | [________________________________] |
| Territories | [________________________________] |
| Languages and modalities | [________________________________] |
| High-impact, regulated, safety-sensitive, or prohibited contexts | [________________________________] |
| Training start, update cadence, and deployment date | [________________________________] |
Uses expressly outside the proposed deal: [________________________________]
7. License drafting inputs
Every selection below is a drafting instruction, not a grant.
| Issue | Negotiated instruction |
|---|---|
| Licensed components | [________________________________] |
| Rights or activities to be described | [________________________________] |
| Exclusive or nonexclusive | [________________________________] |
| Transfer and assignment | [________________________________] |
| Sublicensing and approved recipients | [________________________________] |
| Affiliate, contractor, cloud, and researcher access | [________________________________] |
| Field, territory, channel, product, customer, or model limits | [________________________________] |
| Term and renewal | [________________________________] |
| Reservation of rights | [________________________________] |
| Attribution, notices, credits, or provenance display | [________________________________] |
| Modification, normalization, annotation, augmentation, and combination | [________________________________] |
| Evaluation, publication, demonstration, and research-paper use | [________________________________] |
| Raw-data redistribution or exposure | [________________________________] |
8. Restrictions and technical controls
| Risk or restriction | Contract instruction | Technical or operational control | Owner |
|---|---|---|---|
| Unauthorized access or copying | [________] | [________] | [________] |
| Raw or near-raw redistribution | [________] | [________] | [________] |
| Re-identification or person targeting | [________] | [________] | [________] |
| Memorization, extraction, or reconstruction | [________] | [________] | [________] |
| Use outside field, territory, product, or model | [________] | [________] | [________] |
| Prohibited decisions or deployments | [________] | [________] | [________] |
| Combining with restricted datasets | [________] | [________] | [________] |
| Security incident or credential compromise | [________] | [________] | [________] |
| Opt-out, takedown, correction, or deletion propagation | [________] | [________] | [________] |
| Subprocessor or downstream recipient control | [________] | [________] | [________] |
9. Delivery, access, and security plan
| Item | Instruction |
|---|---|
| Delivery or hosted-access method | [________________________________] |
| Authentication and authorization | [________________________________] |
| Encryption and key management | [________________________________] |
| Approved environments and regions | [________________________________] |
| Copying, export, download, or local-storage controls | [________________________________] |
| Logging and monitoring | [________________________________] |
| Vulnerability and incident handling | [________________________________] |
| Backup and disaster recovery | [________________________________] |
| Return, deletion, verification, and media handling | [________________________________] |
| Audit evidence and frequency | [________________________________] |
10. Quality, documentation, and change control
| Item | Provider record or negotiated standard |
|---|---|
| Source and collection description | [________________________________] |
| Data schema, format, and delivery specification | [________________________________] |
| Annotation method and reviewer process | [________________________________] |
| Known gaps, bias, errors, duplication, contamination, or limitations | [________________________________] |
| Benchmark or acceptance method | [________________________________] |
| Malware, secrets, unsafe content, or prompt-injection screening | [________________________________] |
| Update, version, and change-notice process | [________________________________] |
| Correction and replacement process | [________________________________] |
| Rejected-data handling | [________________________________] |
| Support contacts and response expectations | [________________________________] |
11. Models, derived artifacts, and outputs
Do not assume that a contract label settles ownership, protectability, infringement, confidentiality, or person-level rights.
| Artifact | Proposed allocation or permission | Dependency, restriction, or unresolved issue |
|---|---|---|
| Cleaned or transformed data | [________] | [________________________________] |
| Labels and annotations | [________] | [________________________________] |
| Embeddings, vectors, and indexes | [________] | [________________________________] |
| Checkpoints, weights, and adapters | [________] | [________________________________] |
| Evaluation sets and results | [________] | [________________________________] |
| Prompts, configurations, and safety layers | [________] | [________________________________] |
| Model outputs | [________] | [________________________________] |
| Feedback, corrections, and usage data | [________] | [________________________________] |
| Improvements and derivative datasets | [________] | [________________________________] |
Extraction, reconstruction, memorization, and output-similarity test plan: [________________________________]
12. Commercial terms
| Item | Negotiated instruction |
|---|---|
| One-time, recurring, usage, volume, milestone, or revenue-based consideration | [________________________________] |
| Measurement and reporting | [________________________________] |
| Invoicing and payment timing | [________________________________] |
| Taxes and withholding | [________________________________] |
| Minimums, credits, refunds, or adjustments | [________________________________] |
| Audit of usage or revenue | [________________________________] |
| Currency and payment method | [________________________________] |
| Expenses and third-party costs | [________________________________] |
13. Statements, risk allocation, and claims process
Select only statements supported by evidence and reviewed for knowledge qualifiers, scope, exceptions, duration, and remedy consequences.
| Issue | Counsel-approved drafting instruction |
|---|---|
| Authority and controlled rights | [________________________________] |
| Conformity to documentation | [________________________________] |
| Source-permission or person-level-right statement | [________________________________] |
| Security and confidentiality | [________________________________] |
| Noninfringement or claim allocation | [________________________________] |
| Data quality, completeness, accuracy, bias, or fitness | [________________________________] |
| Regulatory or policy compliance | [________________________________] |
| Third-party claim notice and control | [________________________________] |
| Indemnity, defense, and settlement | [________________________________] |
| Damage exclusions and liability limits | [________________________________] |
| Insurance or financial assurance | [________________________________] |
14. Governance, incidents, and requests
| Event | Notice path | Decision owner | Required record or response |
|---|---|---|---|
| Rights or provenance dispute | [________] | [________] | [________] |
| Privacy or person-level request | [________] | [________] | [________] |
| Security incident | [________] | [________] | [________] |
| Takedown, opt-out, correction, or deletion | [________] | [________] | [________] |
| Quality failure or contamination | [________] | [________] | [________] |
| Prohibited-use allegation | [________] | [________] | [________] |
| Regulator, court, or third-party inquiry | [________] | [________] | [________] |
| Model extraction or memorization finding | [________] | [________] | [________] |
| Material law, platform-term, or product change | [________] | [________] | [________] |
15. Termination and transition design
| Issue | Negotiated instruction |
|---|---|
| Ordinary expiration or nonrenewal | [________________________________] |
| Breach, cure, suspension, and termination | [________________________________] |
| Rights dispute, person request, or legal-change response | [________________________________] |
| Insolvency or business discontinuity review | [________________________________] |
| Cessation of new training | [________________________________] |
| Continued use of existing models or artifacts | [________________________________] |
| Data return, deletion, quarantine, or archival copy | [________________________________] |
| Backup and downstream-recipient treatment | [________________________________] |
| Verification or certification | [________________________________] |
| Transition assistance | [________________________________] |
| Survival of selected terms | [________________________________] |
16. Current-law and terms register
For each applicable location, person category, data type, model use, and distribution channel, record the current official authority or governing source terms and the resulting instruction.
| Topic | Jurisdiction or source | Current official authority or terms | Version or effective date | Drafting consequence |
|---|---|---|---|---|
| Copyright, database, publicity, or other source right | [________] | [________] | [________] | [________] |
| Privacy, biometric, communications, or consumer data | [________] | [________] | [________] | [________] |
| AI training, transparency, documentation, or deployment | [________] | [________] | [________] | [________] |
| Children, workers, patients, students, or other protected context | [________] | [________] | [________] | [________] |
| Platform, website, repository, publisher, or API terms | [________] | [________] | [________] | [________] |
| Cross-border transfer, localization, export, or sanctions | [________] | [________] | [________] | [________] |
| Electronic contracting and signatures | [________] | [________] | [________] | [________] |
| Choice of law, forum, arbitration, and remedies | [________] | [________] | [________] | [________] |
Research completed by and date: [________________________________]
Open legal questions: [________________________________]
17. Approval and drafting handoff
| Review item | Initials and date |
|---|---|
| Asset and component register complete | [________] |
| Provenance and rights evidence reviewed | [________] |
| Person-level data and privacy review complete | [________] |
| Intended models, uses, users, and territories confirmed | [________] |
| License scope and restrictions approved | [________] |
| Security and incident controls approved | [________] |
| Derived artifacts and outputs addressed | [________] |
| Commercial terms reconcile | [________] |
| Risk allocation and termination approved | [________] |
| Current-law and source-terms register complete | [________] |
| Operative agreement approved for signature by counsel | [________] |
18. Signature hold
This packet is not an AI training data license agreement and should not be signed as one.
Operative agreement file or version: [________________________________]
Prepared by: [________________________________]
Approved by counsel: [________________________________]
Approved by privacy and security reviewers: [________________________________]
Exhibit A — Component and provenance schedule
[Attach the completed asset, source, rights, and evidence register.]
Exhibit B — Data documentation and quality package
[Attach the current schema, data card, limitations, validation, and change history.]
Exhibit C — Security and access-control schedule
[Attach the approved delivery, environment, access, logging, and incident controls.]
Exhibit D — Model, use, and artifact map
[Attach the approved model, use, downstream-recipient, derived-artifact, and output instructions.]
This template is provided for informational purposes only and does not constitute legal advice.
About this template
- Last updated
- August 21, 2026
- Citations checked
- August 21, 2026
- Jurisdiction
- All states
- Category
- Intellectual Property
Intellectual property law protects inventions, brand names, creative works, and trade secrets. Filings with federal IP offices have strict formal requirements, and demand letters or licensing agreements have to identify the exact rights being claimed. Weak IP paperwork makes it harder to enforce your rights against copycats, harder to sell or license your IP, and easier for someone else to claim it first.
Not legal advice
This template is provided for informational purposes. We recommend having an attorney review any legal document before signing, especially for high-value or complex matters.
Checked against the law it cites
A reviewer verified this template's legal citations against the official source on August 21, 2026.
Draft your AI Training Data License Agreement in the editor
Answer a few questions, let the AI editor draft each section from your answers, review it, and download Word and PDF. $99 one time, or $249 per month for every document and every Ezel app.