Representations and warranties are the seller's formal statements about a dataset: that it owns the data, has authority to license it, infringes no one's rights, complied with privacy law, granted no conflicting exclusive license and described the data accurately. If a statement proves untrue, the buyer has a contractual remedy, usually through an indemnity.
This page is general information, not legal advice. Whether your company can license a given dataset depends on your contracts, your privacy notices and the law where you and your customers are. Review it with your own counsel before signing anything.
What representations and warranties do
A buyer of data cannot inspect rights the way it can inspect files. It can count records and scan for identifiers, but it cannot see every contract the seller ever signed. Representations and warranties fill that gap. The seller states certain facts in the agreement, and if a fact turns out to be false, the seller bears the consequence.
Strictly, a representation is a statement of present or past fact and a warranty is a promise that a fact is or will be true. In practice, US commercial agreements pair the two words and treat them together. This guide calls them reps.
Reps do three jobs. They force disclosure, because a seller that cannot make a statement must say why. They allocate risk for what neither side can verify. And they give the buyer a path to recovery after closing. This page is general information, not legal advice. The wording and effect of any rep depend on the governing law and should be reviewed by counsel.
The reps a seller is asked to give
The list varies by buyer, but six reps appear in most data licenses. Each one answers a question the buyer cannot settle by inspecting the dataset.
Sellers should read each rep as a factual claim and ask who inside the company can confirm it. A rep that no one can stand behind should be narrowed or disclosed against before signing, not accepted and hoped over.
| Rep | What the seller states | Usual negotiation point |
|---|---|---|
| Ownership | The seller owns the data or holds sufficient rights to grant the license | Whether it covers every record or only the data as described |
| Authority | The seller is duly organized and the signer may bind it | Rarely disputed |
| No infringement | The data and its licensed use do not infringe third-party rights | Knowledge qualifier; carve-out for the buyer's own use |
| Privacy compliance | Collection and processing complied with applicable privacy law and the seller's notices | Which laws; whether it covers the de-identification result |
| No prior exclusive license | No earlier grant conflicts with this license | Disclosure of earlier non-exclusive deals |
| Accuracy of the data card | The description of source, volume, span and processing is accurate | Materiality; estimates versus exact figures |
Knowledge qualifiers
A flat rep is a statement of fact. If it is wrong, the seller is in breach even if it could not have known. A knowledge-qualified rep says only that the seller is not aware of a problem. The difference decides who carries the risk of the unknown.
Sellers ask for knowledge qualifiers on reps about third parties, especially non-infringement, because no company can be sure that nothing in years of records touches someone else's rights. Buyers resist on ownership and authority, which the seller is expected to know.
Where a qualifier is agreed, the definition matters. Actual knowledge of named officers is narrow. Knowledge after reasonable inquiry is wider, because it assumes the seller looked. Constructive knowledge, meaning what the seller should have known, is wider still. A seller that has been through a title search has made the inquiry already and can more comfortably give the wider version.
Caps and other limits
A cap limits the total the seller can owe for breach of the reps. It is commonly set by reference to the fees paid under the license. Buyers often ask that certain reps sit outside the general cap or under a higher one, on the reasoning that a failure of ownership or a privacy violation can cost far more than the fee.
Other limits work alongside the cap. A basket or deductible means small claims are not brought until they pass a threshold. A time limit bars claims made after the survival period. An exclusion of indirect or consequential loss narrows what can be recovered. Fraud and willful misconduct are usually excluded from all of these limits.
The levels are a commercial negotiation tied to price. A seller that wants a low cap should expect a buyer to pay less or to ask for more diligence. This guide gives no typical figures, because they vary by deal and no reliable public data exists for company data licenses.
Survival
Survival is how long after closing the buyer can bring a claim for breach of a rep. Without a survival clause, the period is set by the limitation rules of the governing law, which may be longer or shorter than the parties expect.
Agreements often set a general survival period for ordinary reps and a longer one for those treated as fundamental, such as ownership, authority and sometimes privacy. For AI training licenses, the buyer's argument for longer survival is that a model trained on the data stays in use well after delivery, and a rights claim could surface late.
Sellers should match survival to what they can track. A company should be able to say, for the whole period, who holds the records that support each rep.
Indemnity mechanics
The indemnity is how a breach of a rep turns into payment. The seller agrees to cover the buyer's losses from specified events, most often a third-party claim that the data infringes rights or was unlawfully shared. The clause is usually longer than the reps themselves, because procedure decides whether it works.
Buyers of training data often give an indemnity in return, covering claims that arise from how the buyer used the data or from the outputs of its models.
- Scope: which losses are covered, and whether it reaches direct claims or only third-party claims
- Notice: how quickly the buyer must tell the seller about a claim, and what happens if it is late
- Control of defense: whether the seller may take over the defense and choose counsel
- Settlement: whether either side can settle without the other's consent
- Cooperation: the documents and access each side must give the other
- Mitigation: the buyer's duty to limit its loss, such as by ceasing use of affected records
- Remedies for the data: replacement, removal of affected records or a refund
- Interaction with the cap: whether indemnity claims sit inside or outside it
How a title report narrows the reps
A data title report examines ownership, contracts, privacy notices and earlier licenses before signing. It does not replace the reps, but it changes what they have to cover.
First, it converts unknowns into disclosed exceptions. If the search finds that certain customer contracts restrict use, those records are removed and the exclusion is recorded. The seller then gives its reps about the dataset as delivered, with the exceptions listed in a disclosure schedule. A buyer generally cannot claim for a matter that was fairly disclosed.
Second, it supports narrower wording. A seller can give a rep that refers to the documents reviewed, and the buyer has seen the same report. Third, it reduces the pressure on caps and survival, because both sides are pricing a smaller unknown. Outrich Data runs a title search before each purchase for this reason. The report is an examination, not insurance, so the reps and the indemnity remain in the license.
Before you sign
A seller preparing to give reps should treat the list as an internal audit. For each statement, identify the person who can confirm it and the documents behind it. Where the answer is uncertain, disclose the uncertainty or narrow the dataset.
A buyer should match each rep to a diligence finding. A rep with no diligence behind it is a promise from a counterparty whose ability to pay a claim may be limited. Both sides should have counsel review the final wording against the governing law.