Deal economics
Contract red flags in a data license offer
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
The biggest red flags in a data license offer are terms that let the buyer keep or reuse your records beyond the deal: unlimited derivative rights, perpetual retention, broad sublicensing and uncapped supplier indemnities. A practical rule: if a term has no limit in use, time or amount, treat it as a red flag until counsel has narrowed it.
Key takeaways
- Read an offer for what the buyer can keep, not only for what it pays.
- Unlimited derivative and aggregate data rights can outlast deletion and defeat permitted use limits.
- Perpetual retention often hides inside compliance, backup and legal hold exceptions.
- Payment conditioned on the buyer's sole discretion turns a license into a free option on your records.
- Most red flags can be negotiated; a refusal to define permitted use is a reason to walk away.
What counts as a red flag in a data license offer?#
A red flag in a data license offer is a term that moves control or risk to the buyer without a limit in use, time or amount. Offers arrive as term sheets, order forms or short license drafts, and the red flags usually sit in definitions and exceptions rather than next to the headline price.
Sort red flags into three groups as you read. Walk-away terms cannot be fixed without changing the deal. Renegotiate terms are common opening positions that buyers usually narrow when asked. Clarify terms are vague wording that may be harmless once defined, such as a reference to aggregated insights.
Rights red flags: derivatives, sublicensing and permitted use#
Rights red flags decide what the buyer can do with your records after delivery, so read them first. The table pairs each red flag with a counter-position that suppliers commonly propose.
| Red flag | Why it matters | Ask instead |
|---|---|---|
| Licensee owns all derivatives, extracts and outputs without limit | Derived datasets can reproduce your records outside the license | Trained models may be kept; datasets that can reproduce records follow the deletion terms |
| Permitted use is any purpose, or any AI purpose | Covers resale, benchmarking for others and products you never approved | A defined use, such as training and evaluation of named model types |
| Sublicensing to affiliates, partners and contractors | Records reach parties you never reviewed | No sublicensing of raw records; contractors bound by the same terms |
| Right to publish or release the dataset | Public release cannot be reversed | No publication of records or excerpts |
| Use to build products that compete with the supplier | Your own operations could fund a rival | Exclusion of named competitive uses |
Retention red flags that defeat deletion#
Retention red flags defeat deletion by creating exceptions broad enough to keep everything. A deletion clause can look strong and still let the buyer retain copies for legal compliance, backups, audit, research or records management, with no end date and no certification.
Ask that any retained copy stays under the license's use limits and security terms, is deleted when the reason for keeping it ends and is covered by an officer's written deletion certificate. If the buyer needs a litigation hold, it should tell you and keep the held copy out of any training run.
- Retention for compliance or legal hold with no link to what the law actually requires.
- Backup copies kept until overwritten, with no use or security limits while they exist.
- Copies held by contractors or cloud providers outside the deletion obligation.
- No written deletion certificate, or certification only on request.
- A perpetual right to keep raw records after the term ends.
Risk red flags: indemnity, warranties and liability#
Risk red flags put open-ended liability on the supplier for things the supplier cannot control. The most damaging is an uncapped indemnity covering any claim arising from the data, which in an AI deal can include claims about the buyer's models and outputs.
Watch for warranties that the records are accurate, complete, fit for training or free of personal information in absolute terms, with no knowledge qualifier and no link to the agreed preparation process. Combine those with a limitation of liability that caps the buyer's exposure but not yours, and the offer carries more risk than any fee is likely to justify.
Counter-positions are well established: a cap tied to fees received, indemnities limited to your own breach of the rights and privacy commitments you made, and no responsibility for model outputs or the buyer's downstream use.
Commercial and process red flags#
Commercial and process red flags show up in how the offer is paid and run rather than in the license grant. They often signal a buyer that wants to evaluate your records without committing to them.
Process red flags are the easiest to fix early. A buyer that accepts a metadata-first sequence and a written evaluation license before any sample moves gives you an early read on how the rest of the negotiation may go, and it keeps your leverage intact while the license terms are still open.
| Red flag | What it can mean | Response |
|---|---|---|
| Payment only on acceptance at the buyer's sole discretion | The buyer can take the records and decline to pay | Objective acceptance criteria and deemed acceptance after a short review |
| Full dataset requested before any agreement | Confidentiality and leverage depend on goodwill | Metadata first, then a small sample under a signed evaluation license |
| Fees contingent on model performance | Payment depends on factors you cannot see or influence | Fees tied to delivery of the agreed records |
| Terms that change by reference to buyer policies | The deal can shift after signing | Fixed terms, changed only by signed amendment |
| Unnamed affiliate or thinly capitalized licensee | Enforcement and payment risk | A named, creditworthy licensee or a parent guarantee |
| Pressure to sign before counsel review | Terms may not survive scrutiny | A review timeline set by the supplier |
Illustrative: a consulting firm sorts a first offer#
Illustrative: a fictional operations consulting firm receives a license offer for its proposals, project review notes and internal playbooks, stored in SharePoint and a Salesforce CRM. Counsel sorts the offer into the three groups before the managing partner discusses price.
Walk-away: permitted use is any purpose, and the first draft declines to define it. Renegotiate: an uncapped indemnity, a perpetual right to retain raw records and sublicensing to partners. Clarify: a reference to aggregated insights, which turns out to mean statistics with no record text.
The buyer agrees to define use as training and evaluation, cap indemnities at fees received and delete raw records at the end of the term with a certificate. Client deliverables were already excluded in the rights review, so the license covers only the firm's own internal records.
How SourceX reviews offers#
Offer terms come up at two points in the SourceX five-step transaction (Supply, Rights, Preparation, Approval and Delivery): the Rights step, where scope is set, and the Approval step, where the supplier signs off. Counsel for the supplier decides what to accept, and SourceX points out terms that conflict with the approved scope or with the privacy preparation actually performed.
Permitted use is one of five parts of the SourceX Evidence Packet, next to provenance, licensing rights, the privacy record and release authorization, so the limits a supplier negotiated are kept in the same file as the record of what was delivered.
Frequently asked questions
Are buyer-friendly first drafts normal?
Yes. Buyers usually open with their own paper, and broad rights are a common starting point rather than a sign of bad faith. What matters is how the buyer responds to reasonable limits. A buyer that narrows derivatives, retention and indemnities is negotiating; one that refuses to define permitted use is telling you something about the deal.
Which red flag should we raise first?
Raise permitted use first, because every other term depends on it. Indemnity scope, retention exceptions and derivative rights are all easier to settle once both sides agree what the records may be used for. Leaving use broad while negotiating price usually means trading control for a fee you cannot compare with anything.
Is a non-disclosure agreement enough before sharing a sample?
An NDA protects confidentiality but usually does not limit use for training. Before any sample leaves your systems, sign an evaluation license that says the sample may be used only to assess the records, may not be used to train or tune models, and must be deleted if no deal follows.
Who should read the offer first, the business team or counsel?
Both, in parallel. The business team checks whether scope, exclusivity and payment structure make commercial sense; counsel checks rights, retention, indemnity and liability. A joint list of red flags, sorted into walk-away, renegotiate and clarify, keeps the first response to the buyer short and focused.
Can a red flag be acceptable at the right price?
Some can. Broader use or a longer term may be worth accepting if the price reflects it and the risk stays capped. Terms that create uncapped liability, allow publication of records or conflict with privacy promises to customers are different: price does not change the exposure, so those stay off the table.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.