Data license vs NDA: what each one protects in a data deal

Is an NDA enough to share data with an AI buyer?

No. An NDA protects confidential information exchanged while the parties evaluate each other; it does not grant anyone the right to use a dataset. A data license agreement is the document that defines what a buyer may do with the records after signing: purpose, term, exclusivity and limits. The two do different jobs and a data deal typically needs both.

For a partner, the useful point is reassurance. Early conversations about a company's data should rely on descriptions and metadata, such as which systems exist and how many years they cover, and not on the records themselves. Nothing is delivered before an executed agreement and the company's authorization.

What does each document protect?

This is a general comparison. Actual clauses vary, and the company's counsel should read both. This is general information, not legal, tax or financial advice.

What happens at each stage of a SourceX process?

1. Introduction. A partner passes on the company's contact details and basic fit information. No records are shared with the partner.
2. Qualification. SourceX checks size, history, data breadth and rights with the company's sponsor.
3. Data inventory. The company lists each system, its years of history and what can be exported. This describes the data; it does not transfer it.
4. Price and terms. One all-in price and the licensing terms are agreed with the company before buyers review.
5. Buyer review. AI labs and data buyers review the opportunity; once the company is deal-ready, buyers typically respond within about two weeks.
6. Signature, delivery, payment. Data is delivered only after an executed agreement and the company's authorization, under redaction rules agreed before work begins.

Nothing is binding until the company agrees price and terms and signs. A conversation, an inventory or a confidentiality agreement does not commit the company to license.

Where do people go wrong?

What should a partner say to an owner who is nervous?

Keep it short and factual.

Owners often ask whether to bring in a lawyer. The comparison of a data licensing lawyer and a platform explains how the roles divide. For the next stage, see term sheet versus license agreement, and for the contents of the license itself, what is in a data license agreement. Owners comparing this to a sale of the company can read acquiring a company for its data versus licensing it. Another common confusion is whether structured or unstructured records are more valuable; see structured versus unstructured data.

Which companies are not ready for either document?

Pause if peak headcount was under 50 full-time employees (contractors excluded), if the records belong to the company's clients and no consent exists, or if no one can export the archives. The company fit checker and the who qualifies page cover the baseline.

How are partner rewards affected?

They are not tied to either document. Partners earn 25% of the eligible platform fees SourceX actually collects, capped at $100,000 per referred company. A reward becomes payable only after the buyer pays and SourceX receives its fee; a meeting, NDA or signed agreement alone does not trigger payment. No reward is guaranteed.

A worked example

Illustrative, fictional. A 140-person logistics software company, "Harbor Route Systems", hears about data licensing from its fractional CFO. The owner is interested but wary: the support archive holds customer names and shipment details.

First, the CFO introduces the company; the owner applies and answers qualification questions about size, history and rights. Second, the owner asks for an NDA before discussing system details, and counsel reviews it. Third, the company builds an inventory: ticketing system, shared drive, finance system, eight years of history, exports available. No records leave the building. Fourth, price and terms are agreed, and the license agreement is where customer-data limits, redaction rules and the permitted AI-training purpose are written down. Only after signature and the owner's authorization is anything prepared for delivery.

Notice what the NDA never did in this story: it never allowed anyone to use the support archive. The license did that, with limits the owner approved.

Questions to ask your counsel

• Does our NDA cover only the evaluation, and for how long do the duties last?
• Which customer contracts restrict licensing of records that mention customers?
• Which employee notices and policies bear on call recordings, email and chat?
• Which clauses in the license set term, exclusivity and permitted purpose?
• What happens to the data when the license term ends?
• Who is allowed to see the inventory, and under what confidentiality terms?

Next step

If you know a US company that fits the baseline but worries about sharing information, register as a partner and use the reassurance above when you make the introduction.