Getting started
How data licensing compares with patent and software licensing
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Data licensing differs from patent and software licensing mainly in what the buyer receives: a delivered copy of records with limited permitted uses, protected chiefly by contract and trade secret law rather than a patent or code copyright. The working rule for a CFO: treat a data license as a contract-defined right, then ask auditors how IP licensing guidance applies.
Key takeaways
- A patent license is a promise not to sue, a software license grants use of code, and a data license grants defined uses of a delivered copy of records.
- Data is not a single category of intellectual property, so the contract carries more of the protection than it does in a patent or software deal.
- The ASC 606 examples of IP licenses name software, patents, trademarks and copyrights but not datasets, so revenue treatment is a judgment for your auditors.
- Exclusivity, term and end-of-term deletion are the terms that most change a data license's economics.
- The company licensing its records keeps ownership; the buyer receives permission, not title.
What is actually licensed in each model?#
In all three models the licensor grants permission and keeps ownership, but the thing being permitted differs. A patent license is essentially a promise not to sue the licensee for practicing a claimed invention. A software license grants the right to install, run or access copyrighted code. A data license grants the right to use a delivered copy of specific records for stated purposes, such as training or evaluating AI models.
That difference drives everything else. A patent licensee receives nothing physical, and a software customer usually receives code it cannot inspect. A data licensee receives the records themselves, so the licensor's protection after delivery depends on what the contract says the buyer may and may not do with them.
| Term | Patent license | Software license | Data license |
|---|---|---|---|
| What is licensed | Right to practice claimed inventions | Right to install, run or access code | Right to use a delivered copy of records for stated purposes |
| Main legal protection | Issued patent claims | Copyright in the code, plus contract | Contract and trade secret law, sometimes copyright in original text |
| Ownership after the deal | Patent owner keeps the patent | Vendor keeps the code | Supplier keeps the records; the buyer gets permission, not title |
| Exclusivity norms | Exclusive grants by field or territory are common | Almost always non-exclusive | Usually non-exclusive; exclusivity is negotiated and priced |
| Payment structures | Upfront fee, running royalty, minimums | Subscription, seat or usage fees | Delivery fee, refresh fees, sometimes usage-linked terms |
| Audit | Royalty reports and audits of the licensee's books | Seat and deployment audits | Permitted-use limits, deletion certificates, use attestations |
| Term and end | Often runs until the patent expires | Ends with the subscription; access stops | Fixed term; deletion or retention rules set at signing |
Is data intellectual property?#
Data is not one category of intellectual property; whether a given set of records is protected depends on which rules apply to it. Copyright generally protects original expression, such as an engineer's written explanation in a code review, but not the underlying facts in an order history. Trade secret law can protect records that are kept confidential and have value because they are not generally known.
The federal Defend Trade Secrets Act treats information as a trade secret only if its owner has taken reasonable measures to keep it secret and it derives independent economic value from not being generally known. Licensing records widely without confidentiality terms can weaken that status, which is one reason data licenses lean on access limits and use restrictions.
Bankruptcy law shows the gap clearly. The Bankruptcy Code's definition of intellectual property covers trade secrets, patented inventions and designs, works of authorship and mask works, and it does not name data or databases. Records count only to the extent they fit one of those categories, so the license contract does work that a patent would do on its own.
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
How do fees and royalties compare?#
Fees and royalties follow the shape of the asset in each model. Patent licenses often combine an upfront payment with a running royalty tied to sales of products that use the invention. Software is usually billed by subscription, seat or usage. Data licenses more often price a defined delivery, with separate terms for later refreshes of newer records.
The structure matters to a CFO for cash timing and reporting. A running royalty depends on the licensee's sales, which the licensor cannot see without audit rights. A delivery fee is simpler to forecast but ends unless a refresh is agreed. SourceX does not publish a price list; value is known only once a buyer engages with a specific, scoped package.
- Delivery fee: paid on delivery or acceptance of a defined record set; the simplest to forecast.
- Refresh fee: paid for later deliveries of newer records; depends on the supplier's systems and approvals staying in place.
- Running royalty: tied to the licensee's sales or usage; common for patents, less common for datasets, and only as good as the reporting rights behind it.
- Minimum payment: sets a floor regardless of usage; useful whenever a royalty is involved.
- Exclusivity premium: paid for a field, time-limited or full exclusive grant that restricts other licenses.
How might accounting and tax treatment differ?#
Accounting treatment for a data license is less settled than for patents or software, because the standard examples were written with those assets in mind. ASC 606 lists software and technology, media and entertainment, franchises, and patents, trademarks and copyrights as examples of licenses of intellectual property. Datasets are not named, so whether a given data license is treated as an IP license or as a service is a judgment for your auditors.
If a data license is treated as an IP license, the functional and symbolic distinction may matter. Under ASC 606, a license to functional IP is generally a right to use the IP as it exists when granted, recognized at a point in time, while a license to symbolic IP such as a brand is recognized over time. Sales-based or usage-based royalties follow their own rule: revenue is recognized no earlier than when the underlying sale or usage occurs.
Tax follows the facts of the payment. The Internal Revenue Code lists royalties as an item of gross income, but whether a particular data fee is a royalty or a payment for services depends on the contract and the work involved. This is general information, not tax or accounting advice; review your situation with your auditors and tax advisers before signing.
Where exclusivity, audit and term work differently#
Exclusivity, audit and term are where data licenses diverge most from the patent and software models a CFO already knows. An exclusive patent license by field or territory is routine. In data licensing, exclusivity limits whether the same records can be licensed again, so it should be narrow, time-limited and priced on purpose.
Audit also changes character. A patent licensor audits royalty statements and a software vendor audits seat counts, but a data licensor mostly cannot see inside a buyer's systems. The protections are therefore written up front, clause by clause.
| Data license clause | What it controls | Closest patent or software equivalent |
|---|---|---|
| Permitted use | Which models and purposes the records may serve | Field-of-use limit in a patent license |
| No resale or sublicensing | Stops the buyer passing records to third parties | Non-transferable software license |
| No re-identification | Bars attempts to recover removed personal details | No direct equivalent |
| Exclusivity scope | Field, duration and record set covered | Exclusive field or territory grant |
| End-of-term handling | Deletion, certification and whether trained models may stay in use | Return or destruction of software copies |
| Rights warranty and indemnity | What the supplier promises about ownership and privacy | Non-infringement warranty |
Illustrative: a software CFO maps the familiar to the new#
Illustrative: a fictional vertical software company sells dispatch software to field service businesses. Its CFO has negotiated a patent cross-license and handles annual software renewals, so the board asks whether a data license is just another license. The records in question are Zendesk tickets linked to Jira issues, GitHub pull requests and release notes covering many years.
The CFO builds a one-page comparison along the lines of the tables above. The proposed terms: license non-exclusively, define permitted use as training and evaluating models, bar resale, set a fixed term with deletion certification, and remove customer-identifying details during preparation. The CFO also asks the auditors early how they would view the fee under ASC 606.
The outcome is a board memo that explains the data license in terms directors already understand, with a short list of differences: no patent behind it, a delivered copy rather than access, and contract terms doing the protective work. The board approves moving to a rights review, not a signed deal.
How SourceX structures a data license#
SourceX structures each data license through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The supplier approves every step, data is licensed rather than sold outright, and nothing is shared during the initial fit check, which collects metadata only.
Each delivery is documented in a SourceX Evidence Packet covering provenance, licensing rights, permitted use, the privacy record and release authorization. To discuss value without a price list, SourceX uses the SourceX Enterprise Data Value Framework, in which exclusivity increases price while preparation cost and privacy burden reduce net value.
Frequently asked questions
Can a company license the same records to more than one buyer?
Yes, if the licenses are non-exclusive, which is the usual arrangement for business records. It resembles a software vendor selling the same product to many customers. Any exclusive grant, even a narrow field or time-limited one, should be checked against existing licenses before signing, because it can block later deals.
Are company records recorded on the balance sheet before a license?
Usually not. US GAAP, in ASC 350-30-25-3, generally expenses what a company spends building intangibles internally when they are not specifically identifiable or are part of running the business as a whole, so years of tickets and job records rarely show up as assets. Revenue from a later license is assessed under ASC 606; ask your auditors how it applies to your contract.
Does the buyer keep the records forever?
Not unless the contract says so. Data licenses usually set a term and spell out what happens at the end: deletion of the delivered copy, certification of that deletion, and whether models already trained on the records may stay in use. Those end-of-term terms deserve as much attention as the fee.
Who inside the company should review a data license?
The CFO for deal structure, revenue recognition and tax; the general counsel or outside counsel for rights, warranties and indemnities; and the CTO or COO for scope, export effort and security. The CEO or authorized signer approves the final scope, as with any significant patent or software agreement.
Are data licenses priced like patent royalties?
Sometimes in part, but most data licenses are priced around a defined delivery rather than a share of the buyer's product sales. A usage-linked component is possible, but it needs reporting and audit terms the licensor can actually enforce. There is no standard rate card; value depends on the specific records and the buyer's need.
Sources
- ASC 606-10-55-54 gives as examples of licenses of intellectual property licenses of software and technology; motion pictures, music and other forms of media and entertainment; franchises; and patents, trademarks and copyrights. Source
- Under ASC 606, a license to functional IP is generally a right to use recognized at a point in time, and a license to symbolic IP is a right to access recognized over time. Source
- ASC 606-10-55-65 recognizes sales-based or usage-based royalties for IP licenses only when the later of the subsequent sale or usage or satisfaction of the related performance obligation occurs. Source
- Under 18 U.S.C. 1839(3), information is a trade secret only if its owner has taken reasonable measures to keep it secret and it derives independent economic value from not being generally known. Source
- 11 U.S.C. 101(35A) defines intellectual property as trade secrets, inventions, processes, designs or plants protected under title 35, patent applications, plant varieties, works of authorship protected under title 17, and mask works. Source
- Section 61(a)(6) of the Internal Revenue Code lists royalties as an item of gross income. Source
- ASC 350-30-25-3 requires costs of internally developing intangible assets that are not specifically identifiable or are inherent in a continuing business to be expensed when incurred. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.