SaaS and software companies in bankruptcy: what data is yours to sell

Software companies are among the most common distressed businesses with valuable intangible assets: code, customer contracts, brand, and data. They're also where the line between the company's data and its customers' data matters most. A SaaS company that licenses its customers' data without permission could breach contracts and privacy law in one step. A SaaS company that licenses its own operational records, properly de-identified, may raise meaningful cash without touching a single customer's account.

General information, not legal advice. Your counsel should review your contracts and privacy commitments.

Customer data is usually not the company's to sell

Most B2B SaaS contracts say the customer owns its data and the provider processes it only to deliver the service. Data processing agreements (DPAs) usually restrict use to the customer's instructions and require deletion or return at the end of the relationship. Privacy policies for consumer apps often say data won't be sold. Under those terms, the content customers store in the product is outside any data license. It may still be estate property in a narrow sense, but the debtor's rights to use it are limited by contract, and § 365 and § 363 don't give the debtor more rights than it had.

That's not the end of the story, because SaaS companies generate a great deal of data that is theirs.

What a SaaS company usually does own

• Support tickets and help-desk conversations. Years of real troubleshooting between agents and users. Customer and user identifiers come out; the technical problem-solving stays.
• Engineering records: issue trackers, pull-request discussions, design documents, incident postmortems and runbooks.
• Sales and customer-success records: CRM notes, call summaries, renewal and churn analysis, with customer names removed.
• Internal communications: product, engineering and operations chat channels, filtered for personal and customer-identifying information.
• Product documentation and knowledge bases, including drafts and revision history.

These records describe how a software business actually works, which is what buyers of operational data want. Contracts with customers may still restrict use of information about the customer relationship (for example, confidentiality clauses covering the customer's identity and usage), which de-identification and exclusions address.

Code, IP and data: three different assets

In a SaaS bankruptcy, the code base and IP are often sold to a strategic buyer or a competitor, with customer contracts assumed and assigned under § 365. Operational data can be licensed separately on a non-exclusive basis, so the IP buyer still receives the full records. Coordinate the timing:

1. Data license first: the IP buyer acquires subject to a known non-exclusive license.
2. Combined process: bid procedures allow separate bids for a data license.
3. After the IP sale: if the records stay with the estate, the trustee or plan administrator licenses them later.

The Section 363 sale guide covers the motion. For larger venture-backed companies, many cases land in Delaware; see the Delaware guide.

Source code and open-source considerations

If engineering discussions or code snippets are part of the data set, check two things. First, whether any code is subject to open-source licenses with conditions that matter for distribution. Second, whether the IP buyer's purchase agreement restricts licensing code-related records. Many buyers of operational data prefer discussions and documentation rather than raw code, which simplifies both questions.

Security records need care

Incident reports, vulnerability discussions and security tickets can reveal exploitable details about systems still running, whether at the debtor, a customer or the IP buyer. Exclude or heavily redact them. Credentials, API keys and secrets must be scanned for and removed from every source; engineering chat is a common place for leaked secrets.

Valuation

SaaS operational data can be valuable because it's digital-native, consistent and deep: one ticketing system and one chat platform used for years. Drivers include the number of tickets and threads, the technical depth of conversations, and how much of the record survives exclusions. See valuing intangible assets in bankruptcy and use the runway calculator to see what a license could fund.

Before the systems shut off

Distressed SaaS companies often cut vendor spend fast. Ticketing, chat and code-hosting subscriptions get cancelled, and data disappears with them. If a data license is possible, preserve the accounts or export the data before cancelling. That's often the highest-return decision available. Pre-filing considerations are covered in selling data before filing bankruptcy.

A worked example: a vertical SaaS company

A 70-employee company selling scheduling software to home-services businesses runs out of runway and files Chapter 11 to sell its code and customer contracts. Customer accounts, including job records, end-customer addresses and payment data, are excluded because the customer agreements say customers own their data. What remains: six years of support tickets (about 190,000), the engineering issue tracker, product and engineering chat, incident postmortems and the internal knowledge base. Secrets scanning finds and removes several hundred API keys and passwords from chat. Customer business names are replaced with placeholders. The IP buyer is told about the planned non-exclusive license in the bid procedures and doesn't object, since it acquires the originals. The license proceeds fund the wind-down budget and a small distribution pool for unsecured creditors.

A checklist for a distressed SaaS company

• Read your customer agreements and DPAs and list what they say about provider-created data versus customer data.
• Identify every system with operational history: ticketing, chat, issue tracker, wiki, CRM, call recordings.
• Freeze cancellation of those subscriptions until the data is preserved.
• Run a secrets scan across chat and engineering systems.
• Tell any IP or going-concern buyer about the planned license early.
• Request a confidential valuation before deciding whether the data is worth separate marketing.

Frequently asked questions

Can a bankrupt SaaS company sell its customers' data?

Usually not. Most customer contracts and DPAs limit the provider to processing data for the customer. The data the company created in running its business is different and may be licensable.

Does a data license interfere with selling the software?

A non-exclusive license of a de-identified copy of operational records generally doesn't. The software buyer gets the original records. Coordinate disclosure so the buyer knows.

What about usage analytics?

Aggregated product analytics may be the company's, but they can be tied to customers and users. Treat them like other records: check contracts, remove identifiers, aggregate where possible.

Are engineering chat logs valuable?

Often, yes. They capture real technical problem-solving. They also need careful scanning for secrets and security details.

Should we cancel software subscriptions to save cash?

Export or preserve the data first. Cancelling can destroy the asset.

Do customers need to be told about a data license?

If no customer data is included and nothing identifies customers, notice under the contracts may not be required, but customers often receive notice of the sale motion anyway as parties in interest. Counsel should decide.

Can a liquidating trust license the data after the code is sold?

Yes, if the records stayed with the estate and the plan gives the trustee authority. Keep the systems or exports preserved through the wind-down.

This guide is general information, not legal, tax or financial advice, and reading it does not create an attorney-client relationship. Bankruptcy outcomes depend on the facts, the court and the parties; nothing here promises price, timing or court approval. Talk to your bankruptcy counsel about your case.