Who owns a company's data after it dissolves?

Does a dissolved company still own its data?#

A dissolved company generally still owns its data, because dissolution begins the winding-up process rather than ending the company at once. State corporate and LLC statutes typically let a dissolved entity continue for limited purposes: collecting assets, selling or licensing them, settling debts and claims, and distributing what remains to its owners.

Data is treated like other company property in that process. Support tickets, CRM histories, engineering repositories and job records do not become the founders' personal property, the vendor's property or public material because the company filed a certificate of dissolution. Rules and time limits differ by state and entity type, so counsel should confirm how your state treats a dissolved entity's remaining assets.

What makes data harder than equipment is that it exists as copies. The same customer history may sit in a help desk, a CRM, a data warehouse, email notifications and an export on a former manager's laptop. The company owns all of those copies, but its control is only as good as its access to each one.

How control of company data flows in each wind-down path#

Control of company data follows whoever has legal authority over the company's assets in the particular wind-down path. In an out-of-court dissolution that is usually the board, often acting through a wind-down officer; in other paths, authority shifts to an assignee, a receiver or a trustee.

The table describes typical patterns, not rules for your case. Court orders, assignment agreements and purchase agreements define the exact scope, and some data, such as personal information covered by a privacy notice, may carry conditions on any transfer.

What happens to company data nobody claims?#

Company data nobody claims usually stays where it was last stored, under the practical control of vendors and former employees rather than anyone authorized to act. That is what abandoned company data means in practice: not data anyone may take, but data no one can lawfully license, defend or delete on the company's behalf.

Software vendors typically keep a cancelled customer's data only as long as their terms allow and then delete it. Backups on company servers disappear when hardware is sold or recycled. Copies on personal devices remain company property, yet a former employee has no authority to license them and could face claims for trying.

Once the final distribution is made and winding up is complete, restoring authority can require a revival or reinstatement process, which varies by state and adds cost. Wind-down plans therefore work best when they list data archives next to receivables, equipment and intellectual property, each with a named decision.

Owning the records is not the same as the right to license them#

Ownership of records answers who holds title; the right to license them depends on what the company promised customers, employees, vendors and partners. A dissolved company keeps every one of those promises, and whoever controls it in the wind-down inherits them too.

A rights review sorts each record family into company-owned, shared, customer-controlled and restricted before anyone discusses a buyer. Personal and confidential details are then removed from whatever is in scope, and anything that cannot be cleared is carved out rather than argued over.

• 1Customer contracts that limit use of customer data to providing the service, or that require return or deletion at termination.
• 2Nondisclosure agreements covering partner or prospect information shared in email and documents.
• 3Privacy notices that described how personal information would be used, including any statement about selling data.
• 4Software vendor terms that govern exports, especially for content the vendor generated rather than the company.
• 5Employee notices and expectations covering internal chat, email and monitoring.
• 6Client-owned deliverables, designs and code that the company held but never owned.

What can still be licensed or sold after dissolution?#

Data that can still be licensed or sold after dissolution is usually internal operating history the company created itself, with personal and customer-confidential details removed. Records that mainly describe identifiable people, or that belong to clients, are usually excluded.

Licensing and selling are different transactions. A license grants defined use for a defined purpose and term, which raises the question of what happens when the licensor stops existing; an outright sale moves title and may suit an estate that cannot stay involved. Either way, buyers expect provenance documentation. The Data & Trust Alliance Data Provenance Standards, for example, group dataset metadata into Source, Provenance and Use, and describe that metadata as needed for proper dataset selection for AI model training.

This is no longer a hypothetical question. Forbes reported on April 16, 2026 that after transcription company cielo24 was closed through the wind-down firm SimpleClosure, its remaining digital records, including years of internal chat, project-tracking tickets and emails, became items offered to AI developers. For a wind-down officer, the lesson is that these archives are treated as company assets, so authority and rights need answers before any buyer conversation.

Illustrative: a dissolved software company decides what to do with its archive#

Illustrative: Tallow Ridge Software, a fictional company that sold scheduling software to plumbing contractors, adopts a plan of dissolution after a failed sale process. The board appoints its former controller as wind-down officer. The company still holds Zendesk tickets, Jira issues, GitHub repositories and a HubSpot CRM, all on paid plans set to lapse at the end of the quarter.

The officer exports each system into company-controlled encrypted storage and confirms with counsel that the plan of dissolution authorizes the board to sell or license remaining assets. Counsel's review of customer agreements finds that support content may be used internally but not disclosed with customer identities, so names, contacts and account details are removed from the tickets in scope. HubSpot contact data is excluded entirely.

The board approves a non-exclusive license of the de-identified support and engineering history, with a named contact for notices after dissolution and a destruction duty at the end of the term. Proceeds go into the wind-down account ahead of any distribution. After delivery, the remaining copies are destroyed under a written certificate kept with the corporate records.

Questions to settle before the final distribution#

The questions to settle before the final distribution are the ones that decide whether anyone will still have authority over the data afterward. Answer them in writing while the board, officer or fiduciary is still in place.

• 1Who is authorized to sign for the company, and under which resolution or order?
• 2Does a secured lender hold a lien over general intangibles that reaches data or the proceeds of licensing it?
• 3Which vendors still hold company data, and when will each one delete it?
• 4Which archives must be retained for tax, employment or claims purposes, and who will hold them?
• 5Which archives will be licensed, sold, distributed or destroyed, and where is that decision recorded?
• 6Who receives notices and requests about the data once the entity is gone?

How SourceX approaches data in a dissolution#

SourceX treats a dissolving company's data as a transaction that must be authorized before it is scoped. In the SourceX five-step transaction (Supply, Rights, Preparation, Approval, Delivery), the Rights step confirms who can sign for the company in its current wind-down path, and nothing is shared during the initial assessment, which uses metadata only.

For any package that proceeds, the SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and release authorization. That record matters after dissolution, when the people who approved the license may be hard to reach.