Skip to content
Outrich Data

Licensing a closed company's data to AI labs

Updated 2026-11-16 · 6 min read · By the Outrich Data team

A closed or winding-down company can often license its archives, such as code and workspace data, to AI labs. The deal must be authorized by whoever controls the assets, which may be the board, an officer, an assignee or a trustee. Creditor interests, surviving contracts and privacy duties still apply. General information, not legal advice.

This page is general information, not legal advice. Whether your company can license a given dataset depends on your contracts, your privacy notices and the law where you and your customers are. Review it with your own counsel before signing anything.

Why closed companies' archives have buyers

When a company shuts down, its records usually remain: source code, tickets, documents, chat history, design files. These archives show how a real team built and ran a product, which is the kind of material AI labs want for training.

The practice is now reported in the press. MIT Technology Review reported on 2026-10-13 that closed startups were selling a code base for about $25,000 and workspace data for about $15,000. Those are reported figures for particular cases, not a price list, and they say nothing certain about any other archive.

For founders, investors and creditors, a license can recover some value from an asset that would otherwise be deleted. It also raises questions an operating company does not face. The rest of this guide sets them out. It is general information, not legal advice, and the answers vary by jurisdiction and by the company's own documents.

What the archive usually contains

A wind-down archive is rarely one clean dataset. It typically includes several kinds of material with different owners and different risks.

Each category needs its own review. Code raises licensing questions. Workspace data raises privacy questions. Customer content may not belong to the company at all.

  • Source code and version history, which may include open source components and code licensed from others.
  • Workspace data such as chat, email, documents, wikis and project trackers.
  • Customer records, support tickets and anything customers uploaded to the product.
  • Employee records, including HR files and personal messages sent on work accounts.
  • Credentials, keys and security configuration, which should never be licensed.

Who can authorize a license

The first question is who has authority over the company's assets at the moment of signing. That depends on the stage and form of the wind-down, and it can change quickly.

A founder who still holds the laptop or the admin password does not necessarily hold the right to license what is on it. A buyer or intermediary should ask for evidence of authority, such as a board resolution, the assignment agreement or a court order. A license signed without authority may be open to challenge, and the signer may face personal exposure.

  • The board. In a solvent, voluntary wind-down, the board typically still directs the sale or license of assets, sometimes with shareholder approval where substantially all assets are involved.
  • Officers. An officer may sign if the board has delegated that authority. A former officer of a dissolved company may have none.
  • An assignee. In an assignment for the benefit of creditors, control of the assets generally passes to the assignee, who decides what to sell or license.
  • A trustee, receiver or liquidator. In a bankruptcy or court-supervised process, an appointed person generally controls the estate. Transactions outside the ordinary course may need court approval and notice to creditors.

Creditor and bankruptcy-estate interests

Once a company is insolvent, its assets are generally to be managed with creditors in mind. Data and code are assets. Proceeds from licensing them usually belong to the company or its estate, not to founders or individual shareholders.

Secured lenders may hold a lien over intellectual property or over all assets. If so, a license may need the lender's consent, and the proceeds may be owed to the lender first. In a formal bankruptcy, the archive is typically part of the estate. In the United States, a transfer of personally identifiable information in bankruptcy can draw additional review where it conflicts with the company's privacy policy, including the possible appointment of a consumer privacy ombudsman.

Timing also matters. A transfer made shortly before a filing, for less than fair value or to an insider, may later be challenged. A documented, arm's-length process with a written offer helps show the estate received fair value.

Employee and customer data left in the archive

Closing the company does not close its privacy obligations. The people described in the archive keep their rights under privacy law, and those rights do not depend on whether the business still trades.

Employee data is the most pervasive. Chat logs and email contain names, opinions, health details, family matters and disputes. Former employees were generally told their data would be used to run the business, not licensed after it ended. Some jurisdictions restrict such reuse without a fresh legal basis.

Customer data needs closer attention. The company's privacy policy and customer contracts set what it promised, and those promises typically bind a successor or assignee. Content that customers uploaded is often owned by them, with the company holding only a limited right to process it. That material usually has to be excluded, not merely cleaned.

Contract obligations that survive closure

Many contracts contain clauses written to outlast the relationship. Dissolving the company, or assigning its assets, does not usually erase them.

If a deletion duty applies, the data should be deleted, not licensed. A review of the main contract templates, plus any heavily negotiated agreements, usually shows which parts of the archive are clear.

  • NDAs. Confidentiality duties commonly continue for a set period or indefinitely, and cover information received from customers, partners and investors.
  • Data processing agreements. A DPA typically limits processing to the customer's instructions and requires return or deletion of customer personal data when the service ends.
  • Customer agreements. These may bar use of customer data for any purpose beyond providing the service.
  • Inbound licenses. Third-party code, datasets and content in the archive come with their own terms, and open source licenses carry conditions too.
  • Employment and contractor agreements. These decide whether the company actually owns the work product in the archive.

Why de-identification still applies

It is tempting to think a defunct company has nothing left to protect. The people and clients in its records still do. An AI model can reproduce details from its training data, so personal and client-identifying information that goes in may come out.

De-identification means removing or replacing names, contact details, account identifiers, client names and similar markers before any buyer sees the data. Secrets such as credentials and keys are stripped as well. It reduces legal exposure, although it does not remove every obligation, and some laws set a specific standard for when data counts as de-identified.

Outrich Data licenses proprietary data from companies with 50+ employees and 2+ years of history, and its rule is the same for every supplier: personal and client-identifying details are removed before a dataset is shown to any buyer, and the method is documented. Whoever holds authority over the assets approves each package and license scope in writing. For an assignee or trustee, that record also helps show the process was careful.

A practical sequence before signing

The order of work matters more than the speed. A reasonable sequence looks like this.

  • Establish authority. Identify who controls the assets today and obtain the document that proves it.
  • Check liens and creditor rights. Ask whether a lender's consent or a court's approval is needed.
  • Inventory the archive. Separate code, workspace data, customer content and employee records.
  • Review surviving contracts. Find the confidentiality, deletion and use restrictions that still bind.
  • Exclude what cannot be licensed. Remove customer-owned content, third-party material and anything under a deletion duty.
  • De-identify the remainder and document the method.
  • Preserve records properly. Do not delete or alter anything that is subject to a legal hold or retention duty.
  • Take legal advice. Insolvency and privacy rules differ by jurisdiction, and a lawyer who knows the company's documents should confirm each step.

Common questions

Can a founder license the data after the company is dissolved?
Only if the founder has authority over the assets, which is not automatic. After dissolution, an assignment or a bankruptcy filing, control may sit with someone else. Evidence of authority should be confirmed with a lawyer before signing.
Who receives the money from a license?
Generally the company or its estate, for distribution under the applicable priority rules. Secured lenders and other creditors may rank ahead of shareholders. The exact order depends on the jurisdiction and the company's debts.
Does a closed company still have to follow its privacy policy?
In general, yes. Promises made to customers and employees about their data typically continue to bind the company and whoever takes over its assets. Regulators have objected to data sales that contradicted earlier privacy promises.
Is an archive worth licensing if customer content must be removed?
It can be. Code, internal documents and process records often remain after exclusions. Whether a buyer is interested depends on what is left, its volume and how clear the rights are. No outcome is guaranteed.

Find out if your data qualifies.

Eleven questions, about five minutes, no call required. You get an answer on screen and a written follow-up.

esc