The takeaway
“You keep ownership” is a starting point. Review the actual permissions, restrictions, and obligations in the agreement.
Make the dataset specific
Before a commercial conversation gets far, describe the proposed dataset in terms someone can verify: systems, record types, fields, dates, and exclusions. Ask whether attachments, linked tables, future updates, or derived versions are included.
For an internal review, keep a short list of collections that require separate decisions. Customer-supplied documents, employee communications, licensed reference material, and vendor-enriched records may raise different questions. Having access to an export is not the same as having every permission needed for a new use.
Ask what the recipient may do
Bring these questions to the commercial and legal review: Is use limited to evaluation, or does it include training? Can the recipient share raw data, sublicense access, or create derivative datasets? Which restrictions apply to resulting models and outputs? Are permitted recipients named or defined as a category?
Published data licenses illustrate why the wording matters. The Linux Foundation's CDLA Permissive 2.0, for example, treats data sharing and computational results separately. It is an open-data license, not a suggested template for a confidential commercial deal, but it shows why “data use” needs a precise definition.
Discuss exclusivity and future options
Ask whether exclusivity applies at all, and if so, to which records, uses, buyers, territories, and time period. Clarify whether your team can continue using the data internally and whether future datasets are affected.
A narrowly defined restriction is easier to evaluate than an undefined promise. Have your team describe the business activities it expects to continue, including internal analytics and existing customer commitments, so the contract can be reviewed against real needs.
Connect payment to clear events
Review what triggers compensation: signature, delivery, acceptance, a downstream license, or another milestone. Ask who determines acceptance, how discrepancies are addressed, and whether preparation costs or other fees are deducted.
If compensation depends on later transactions, discuss the reporting available to you. An attractive headline amount is difficult to assess without understanding the payment conditions and the obligations required to reach them.
Plan for the end as well as the beginning
Ask what happens to copies, backups, access, and derived materials when the arrangement expires or is terminated. Discuss which uses can continue, what deletion can actually cover, and how compliance with agreed restrictions will be documented.
Use these questions to brief your counsel and the people who operate your systems. They are a discussion guide, not a legal interpretation of your contracts. The goal is an agreement whose practical meaning your business understands before it commits to sharing data.
Sources & further reading
Sources checked October 2, 2026.