Rights to License Company Data: What Owners Must Check
Check your rights to license company data: distinguish possession from permission, review client and contractor terms, and document restrictions before a deal.
Your rights to license company data depend on the records, how they were created or received, existing agreements, and the proposed use. Having an administrator account or paying for the software does not settle every permission question. Build a record of the relevant rights and restrictions, then have qualified counsel assess the intended license.
Replace “we own the data” with specific questions
A company's archive can contain several kinds of material: internally written procedures, incoming customer requests, third-party attachments, contractor deliverables, and personal information. Those materials may raise different questions even when they share a folder.
Recommend asking what right the buyer needs in each category. Does it want to reproduce documents, transform records, train models, run evaluations, or supply another organisation? A broad assertion of ownership does not answer whether your company can grant that specific permission.
Keep commercial control, copyright, confidentiality, privacy, and previous licenses distinct in your review. They interact, but satisfying one does not prove the others are settled.
Use a source inventory to identify the categories. Review privacy before selling business data alongside this guide. Neither document replaces a legal opinion on your actual records.
Understand what copyright does and does not answer
The US Copyright Office's copyright basics explains protection for original expression and distinguishes it from facts, ideas, systems, and methods. That distinction matters when an archive includes factual fields alongside authored text or images.
Do not turn it into a claim that factual business data is freely licensable. A contractual restriction or a privacy obligation can still matter even where copyright does not protect a particular fact.
Recommend asking counsel to classify the relevant material and identify the necessary grant. An internal troubleshooting manual, a customer's attached photograph, and a ticket status field may need different analysis.
For UK and Canadian records, ask local advisers about applicable intellectual-property rules rather than transplanting a US conclusion. This article offers questions to organize a review across markets; it does not establish a universal ownership rule.
Check who created the material
Review employees, contractors, founders, acquired businesses, and outside suppliers separately. Locate the relevant employment, commissioning, assignment, and acquisition documents.
The US Copyright Office's work-made-for-hire circular distinguishes employee work within employment from certain commissioned works meeting specific conditions. Simply commissioning something does not automatically answer all ownership questions.
Recommend preparing a creator register for important authored material. Record the source, creator category, relevant agreement, and outstanding question. A contractor's invoice is useful commercial evidence, but it should not be your sole basis for asserting a broad AI licensing right.
If a business acquisition added the archive, review the transfer documents. Confirm whether rights, restrictions, and records moved together. Do not assume that an old company's brand appearing in your systems settles the chain of authority.
Keep missing documents visible. “Agreement not located” is a meaningful issue for counsel. Silently marking the source cleared would make subsequent buyer warranties harder to support.
Separate your operating history from client-held work
Your company may document its own scheduling, purchasing, quality checks, and internal process improvements while also holding client materials. Recommend drawing the distinction at the record category level.
Polyshares' public licensing description says its scope does not cover material held on behalf of clients. That is a particular buyer's boundary, not a legal ruling on every client engagement. It is nevertheless a useful reason to prepare a precise account of whose work your archive represents.
In a hypothetical consulting engagement, the firm's internal resourcing notes and the client's confidential strategic report should not automatically be bundled together. A useful inventory would flag the report and its governing agreement separately.
For mixed documents, ask whether the restricted portion can be reliably excluded without misrepresenting the remainder. If not, recommend leaving the affected material outside the proposed package until the question is resolved.
Read the relevant contract clauses together
Ask counsel to review confidentiality, permitted use, intellectual property, data processing, subcontracting, return or deletion, and onward-disclosure provisions. A general data ownership clause may not be the only relevant text.
Recommend preparing a concise review note for each material agreement: which records it governs, what the proposed buyer would do, and which provisions might affect that use. Include the agreement version and any amendments.
Do not assume a client would agree simply because its name will be removed. De-identification may address some privacy concerns while leaving a separate confidentiality commitment unresolved.
If permission from another party is required, ask counsel what request and evidence would be appropriate. An informal expression of enthusiasm should not be treated as a documented grant covering all future AI uses.
This review is a recommended preparation step. It does not imply that every contract prohibits licensing or that every restriction can be cured with an email.
Keep privacy obligations in the rights review
Personal information is not settled solely by an assertion that the company owns its database. Ask your advisers to review collection purposes, notices, proposed recipients, and any required permissions.
The Canadian privacy commissioner's guidance explains that consent involves understanding the nature, purpose, and consequences of a use or disclosure. A historic notice should therefore be examined against the actual proposed activity.
In the US, the FTC warns against quietly expanding terms retroactively for AI uses. Do not treat a new website sentence as proof that all older information is cleared.
Recommend having the same source register carry both ownership and privacy flags. That helps prevent a source being marked approved by one reviewer while an unresolved obligation remains with another.
Review past licenses before granting new rights
Find previous data agreements, content licenses, exclusivity commitments, and relevant merger or financing documents. Ask whether they restrict the rights now requested by the buyer.
A non-exclusive agreement can still contain conditions. An exclusive grant may be limited by record set, purpose, territory, or term. Read the actual text rather than relying on the label used during the sales conversation.
Our exclusive versus non-exclusive licensing guide provides a commercial comparison. Counsel should decide whether grants conflict and what disclosures or changes are required.
Recommend keeping a grants register even when the company has never called its previous arrangements “data deals.” An agreement allowing a partner to use project material may be relevant to a proposed warranty that no overlapping rights have been granted.
Prepare evidence for the signer
The executive signing the license should understand what is included, what remains excluded, and what the company is being asked to warrant. Do not bury unresolved authority questions in an administrator's export notes.
Recommend assembling a review pack containing the source register, relevant agreements, outstanding questions, counsel's conclusions, and the final data schedule. Keep the pack updated if the buyer expands its requested use.
Ask who is authorized to sign for the company. Technical access, sales responsibility, and legal authority are separate roles. A purchaser requesting a fast signature does not remove the need to resolve them.
Review remedies and responsibility where an ownership statement proves wrong. The appropriate legal adviser should explain the exposure in the agreement rather than leaving the owner to infer it from a generic indemnity clause.
Qualify authority before buyer discussions
Recommend qualifying the ability to grant rights before investing heavily in buyer discussions. Keep an interested response separate from a cleared archive or a completed deal, and document unresolved client obligations before presenting records as available for licensing.
Garrow is an independent referrer and does not provide legal advice or inspect your files. If your authority is uncertain, describe the uncertainty rather than sending documents for us to decide it.
Start with Garrow's intake to describe the company-owned record and the questions that remain.
Frequently asked questions
Do records in our company account automatically belong to us?
Possession and account administration do not settle licensing authority. Check authorship, client obligations, privacy commitments, and previous grants.
Can we license documents made by contractors?
Review the relevant agreement and applicable law. Do not assume that paying an invoice establishes all the rights needed for a proposed data license.
Does keeping our original data mean no rights are lost?
No. The agreement may restrict further licensing or grant broad use rights to the buyer even when the company retains its working archive.