How to verify rights for data from a closed company
A step-by-step guide to confirm ownership, contract permission, and privacy compliance before licensing records from a shut-down business.
Written by Jimmy Lin
, 4 min read
You verify rights by confirming who now owns the data, checking the contracts that created it, and running a privacy test before any lab sees a sample. That three-step routine protects you from legal surprises and keeps the deal moving.
Identify the current data owner
When a company winds down, its digital assets are handed to whoever runs the wind-down, a trustee, a court-appointed administrator, a successor entity, or the original owners if they kept title. Your first move is to get a written statement that names that holder and confirms their authority to grant a licence. Ask for a board resolution, a trustee declaration, or a court order that documents the transfer of data rights. If the business was sold before closing, the buyer may have inherited the licence. In every case you need a clear chain of title before you proceed. Our blog on who can sign a data licence for a closing company gives more detail on the types of authorities you may encounter.
Review the contracts that generated the records
Each ticket, chat thread, sales entry, or invoice lives under a contract, typically a service agreement, an employment contract, or customer terms of service. Those documents often contain data-use clauses that can make or break a licence.
- Customer agreements. Look for language that permits sharing anonymised data for research or development. Some contracts require explicit consent; others grant a blanket permission for "aggregate analysis."
- Employee agreements. Check handbooks or NDAs to ensure they do not forbid re-using internal communications once they are de-identified.
- Vendor contracts. If a third-party tool stored the data, confirm that the tool's licence allows you to export the data and licence it to a new party.
If any clause limits purpose or demands extra consent, you either obtain that consent or carve those records out of the licence.
Need licensed data for a model? Tell us what you need
Run a privacy compliance test
Title and contract clearance are only half the battle; the data may still contain personal information. The test you run depends on where the people in the records live, because privacy definitions vary by jurisdiction. A practical approach is to run a personal-data scanner that flags names, email addresses, phone numbers, and any other identifiers. After the scanner finishes, a human reviewer inspects the flags and replaces identifiers with stable pseudonyms such as "employee 632."
When the data includes health records, credit-card numbers, or other regulated categories, you must apply the safeguards required by the relevant law, for example, HIPAA for U.S. health data or GDPR for EU residents. We also offer a separate de-identification service that follows this exact workflow; the cost is negotiated case-by-case and is usually covered by the buying lab.
Draft a licence that matches the verified rights
With ownership, contract, and privacy checks in hand, you can draft a licence that reflects exactly what you are allowed to provide.
- Scope of data. List the record types (support tickets, CRM activity, project histories, etc.) and the time period covered.
- Term. Most buyers ask for a 24-month exclusive right; a shorter term can lower the price.
- Renewal. If you anticipate future data flows, include an option to refresh the licence after the initial period. Our article on one-time vs. renewable licence for company data explains the trade-offs.
Remember, the seller keeps ownership of the data; the licence is a permission to use, not a transfer of title.
Why rights verification matters
Even when a company is no longer operating, its data can still be valuable for training large language models, building reinforcement-learning (RL) environments, or creating synthetic datasets. AI labs pay between $200,000 and $300,000 USD for well-documented, clean data, but they will walk away if the provenance is unclear. A solid rights audit protects you from breach claims, prevents costly renegotiations, and often results in a higher offer because the buyer trusts the provenance memo.
What you need to provide to start the process
To kick off a deal, gather the following items and have them ready for our review:
- A legal document that identifies the current data owner and their authority.
- Copies of any customer, employee, or vendor agreements that reference the data.
- An inventory of the data sources you intend to license, including system names and date ranges.
Once you have these, use the button below to submit a request. We will match you with sellers who have already completed the rights verification for closed-company records and guide you through the next steps. Learn more about how a buyer request runs on our buyer workflow page.
Questions people ask
How can I be sure the seller really owns the data after the company closed?
Ask for a legal document, a trustee declaration, a court order, or a board resolution, that names the current data owner and confirms their authority to licence the data. We attach that document to the provenance memo for every deal.
What if a customer contract forbids sharing the data?
When a contract contains a prohibition, you either obtain a waiver from the customer or exclude those records from the licence. The final licence can be limited to the data that has clear permission.
Does the privacy test happen before the lab sees any data?
Yes. All personal identifiers are removed or replaced on the seller's side before any sample reaches a buyer. Only the cleaned copy ever leaves the seller's environment.
Who pays for the de-identification work?
In most brokered deals the buying lab covers the cost of de-identification, but the exact arrangement is negotiated as part of the licence terms. If you prefer the data cleaned before it is offered, let us know and we'll discuss the option.
Didn't find your question? Ask us directly.
Read next
More articles- For buyers3 min read
How linked records across tools enrich training data
Linking tickets, CRM entries, and project logs creates a traceable workflow that improves AI model quality and business insight.
- For buyers3 min read
Understanding RL environments for business owners
A clear guide to reinforcement-learning environments, how they turn operational records into AI training tasks, and what licensing means for your company.
- For buyers4 min read
How to get trajectory data for AI agents
Learn how to source licensed operational data that captures end-to-end workflows, decisions and outcomes for training AI agents.