Seller intent
Data licensing agreement checklist
Last updated /Seller intent
A data licensing agreement checklist is a list of topics a draft should make readable before anyone signs. It is not a form you can copy into a contract, and it is not legal advice. Scope, term, exclusivity, deletion, and audit are the five that owners most often discover too late, written in a sentence they did not notice. If those five are vague, the rest of the document is not ready to sign, no matter how polished the payment language looks.
The sequence that leads to a draft, when a draft exists at all, is the owner-controlled steps for licensing company data. A profile comes before files. A match, if any, comes before negotiation. You can refuse the draft. What a license is, as distinct from a sale of the company or of the archive, is what AI data licensing means for a company. Whether you are allowed to grant even a clear permission is why legality is not a yes for every company. Counsel answers that. This checklist assumes you are looking at a piece of paper, not that you should have one.
How structure relates to a later figure, without a rate card, is how price drivers and deal structures are discussed. How the records get ready only after a yes is how a company gets records ready for a buyer. Read the five topics below as questions to ask of a draft. Do not read them as clauses we have written for you.
Why a buyer should want the same clarity
A team that trains or evaluates on company records needs to know what it received and what it is allowed to do. A muddy grant is a problem for them as well as for you. Scope that names the records, the years, and the use is easier to honor than a grant of all data for all purposes. Audit, in the plain sense of being able to check that the use stayed inside the scope, is how both sides notice a drift. Neither side should have to guess.
Clarity is not the same as a right to sign. A beautifully specific contract can still describe a use your customer agreement forbids. Specific and forbidden is still forbidden. The checklist does not override the documents you already have.
What each topic should force into the open
Scope
Which records, which years, which systems, and which use. Train, evaluate, or both. A field can be named, such as a product area or a research purpose. If the draft says all data or all purposes, ask what that excludes. If the answer is nothing, you are looking at a grant that is larger than a slice. You can insist on the slice. A buyer who needs a wider grant should say so in words you can refuse.
Term
How long the permission lasts, and what happens on the last day. A delivery of one approved slice is different from ongoing access to live systems. The draft should say which one it is. It should also say whether the permission renews by silence. Silence is a poor way to extend a use of company records. End dates belong in the open.
Exclusivity
Whether you may grant a similar use to someone else, and for which field. Exclusive is a promise not to do that. It is not a synonym for a sale, and it is not a detail. If the draft is exclusive, find the sentence that says exclusive of what. A narrow exclusive field is a different promise from a ban on every future conversation about the same archive.
Deletion
What happens to delivered copies, and to logs of the delivery, when the term ends or you terminate. Who confirms that copies under the buyer's control were deleted or returned. The draft should not pretend that every downstream effect of a training run can be waved away in a sentence if nobody can explain that sentence. Ask counsel what the deletion language actually covers. Do not sign a promise of erasure that the other side cannot perform, and do not accept a promise that leaves copies in unnamed places.
Audit
How either side can check that the use stayed inside the scope. That might be a right to ask for a description of where the slice went, a limit on subcontractors, or a narrower check. The point is not a surprise inspection of a stranger's lab. The point is that scope is enforceable only if someone can tell when it was exceeded. If the draft has no way to notice a breach, the scope is decorative.
What a weak draft hides
- A grant of all rights, all media, and all future uses, sitting under a title that says license. Read the grant, not the title.
- Exclusivity buried in a definition. If you would not say the promise out loud, it should not be in a subordinate clause.
- Deletion that binds only you, or only an unnamed affiliate, or nobody.
- No named purpose. A use described as any artificial intelligence purpose is close to no limit at all.
- A requirement that you connect systems or deliver files before the draft exists. Preparation follows approval. It does not precede the document that defines approval.
A weak draft is a reason to stop or to rewrite. It is not a reason to hope the relationship will be narrower than the words. How records are limited before a buyer can study them is about the handling of an approved slice. Handling cannot repair a grant that was too wide.
How a draft shows up, if one shows up at all
Unlockt, LLC is the operator. Big Data/Little Guy is the name on the marketplace. We do not hand you this checklist as your agreement. Many companies never reach a draft, because the profile does not match a need, or because the rights are unclear, or because the owner stops.
When a draft is in front of you, the five topics above are the ones to find with a pen. Bring counsel. We will not tell you that a clause is valid where you operate, and we will not tell you to sign because a buyer is impatient. Impatience is not a term.
You can also ask for a smaller scope instead of a cleverer price. Structure is the part you live with after the signature. The free check does not create a draft. It does not ask you to upload the records the draft would later describe. Leave the files where they are until the words match a use you are willing to permit. The difference between that permission and a sale of the archive is how a license differs from selling the data.
Questions people ask
Is this checklist my contract?
No. It is a list of topics a real draft should make easy to find. Your counsel reviews the draft. This page does not supply clauses.
What if the draft is exclusive and I did not expect that?
Then do not sign it until the exclusive field is one you accept, or until exclusivity is removed. Surprise exclusivity is a reason to pause.
Can deletion language undo a model that was already trained?
Do not assume that. Ask what the sentence actually requires, and ask counsel whether it can be performed. A vague promise of erasure is not a plan.
Who audits whom?
The draft should say how a use can be checked against the scope. It does not have to mean an open-ended tour of a buyer's systems. It does have to mean the scope is not a slogan.
Should I sign before the records are prepared?
You should understand the scope before preparation. Preparation of files is not how you discover what you agreed. The order is the draft you accept, then the approved slice.
Where do I start if I do not have a draft yet?
Use the free check if you want a commercial reading. A checklist is for the day a document exists. Many checks never reach that day.
See what your data could be worth
Your company's data could be worth up to $5M+.
Potential licensing value varies by dataset, rights, quality, volume, buyer demand, and transaction terms. Estimates and examples are not guaranteed offers.
Check my data value