Spirit Airlines' debtors held a virtual auction for the airline's "Deidentified Data" on August 14, 2026, and filed the results the same day: Google LLC the successful bidder at $10,000,000, Mercor.io Corporation the alternate at $7,500,000 (Case No. 25-11897 (SHL), Dkt. 1463 (opens in new tab)). The asset schedule attached to the filing marks every one of these lines Included:
- Commercial agreements (licenses, master service agreements)
- Agreements with redlined "draft to final contract" histories
- AP and vendor information: 97,603 vendor IDs
- Invoices: 851,590
- Data room materials and due diligence review reports
- Legal memos and litigation case files, with privileged material carved out
- Emails: 100,000,000 across 80,000 accounts
- Teams items: 500,000,000
Read the list the way a counterparty would. If you ever sold Spirit a service, your contract is on the first line and the record of what you conceded to get it signed is on the second. Your remittances are on the third and fourth. Whatever your account team put in writing about pricing or a renewal, on the assumption it'd stay between two companies, is probably somewhere in the last two. Skift reported (opens in new tab) that Google plans to use the data to improve its own AI models and products, and a contributed piece on TNW (opens in new tab) says Google has said a third party will remove personally identifiable information before delivery.
The sale has a privacy process, and it's a serious one. It just wasn't built for you. It protects travelers, and the vendors that wanted their own material handled differently had to go to court and ask. That's the gap I'd look for in a vendor file, and it has a mirror image inside your own Microsoft 365 tenant.
Deidentified for whom
The sale agreement does its scoping in the definitions. Personal Data is information that "relates to, describes, or is reasonably capable of being associated with a consumer," or that data protection law treats as personal. Deidentification transforms data elements so the data "cannot be associated with, reasonably used to infer information about, or otherwise linked to, a particular consumer." Every privacy commitment in the agreement points at an individual or a household. Nothing in it protects a counterparty's confidential information.
Two more clauses set the frame. The work is done by a Deidentification Agent, a third party "acceptable to or designated by Buyer." And the agent's certification has to hold "while preserving referential integrity across the data set." The Association of Flight Attendants, in its explainer for members on the objection (opens in new tab), says what that phrase does: linkages across records are maintained. It also makes the sharper point. Deidentification addresses whether a record can be traced to a named individual. It "does not address whether the contents of the record are confidential."
Run a vendor's file through those terms and here's what I'd expect to survive. Strip the travelers out of an invoice and it still carries the price. Strip the names off a redline and it still shows which liability cap moved and which indemnity got narrowed, linked to the vendor record and to the thread where somebody agreed to it. Referential integrity is a large part of what I'd expect a buyer to be paying for. It's also what keeps a counterparty's deal history readable.
The data room line works the same way. A data room is an argument assembled to close one deal, and this schedule offers it, review reports and all, to a buyer who wasn't party to that deal.
The statute points in the same direction. Section 363(b)(1) (opens in new tab) of the Bankruptcy Code restricts selling "personally identifiable information about individuals" when the debtor's privacy policy promised not to transfer it, and the main route around that restriction runs through a consumer privacy ombudsman and the court.
According to Stretto's docket summary (opens in new tab), Spirit's Ombudsman filed a supplemental report on October 5, 2026 (Dkt. 1684) recommending approval, after the parties pulled the structured passenger databases out entirely and engaged Tonic.ai as an independent deidentification agent for the unstructured data, corporate email included. The report says she was given a draft revised asset schedule that remains subject to revision, so the August 14 version is the public record of what was offered, not a final list of what transfers. The same summary says she expressly didn't investigate risks to employees or third parties, because her mandate under section 332 runs to consumers. She did the job the Code gave her. That job doesn't include your MSA.
The vendors had to file
Business counterparties got their protection the old way, by filing. Per the same summary, Springshot, Inc. objected on vendor-data grounds (Dkt. 1508). International Aero Engines and the Navitaire and Amadeus parties each paired a limited objection with a cross-motion to enforce confidentiality agreements (Dkt. 1538 and 1602). The privacy review, by its own terms, wasn't going to raise their issue for them.
Springshot's papers are the most specific, and they read like a vendor doing the debtor's data mapping. The contract language it relies on, as reported in the same TNW piece (opens in new tab), reaches "any data or information generated by the Service or Software." Springshot asked for a court-run forensic review to separate its IP from Spirit's business records before any transfer. Its supplemental limited objection on October 9, 2026 (Dkt. 1693) said it had no wish to derail the sale, but that the debtors negotiated the transaction without accounting for third-party vendor data that isn't estate property, and hadn't shown they knew where Springshot's proprietary data sat.
Then it told them where to look: data shared through email, Teams and SharePoint, data its platform pushed daily to Spirit's own URLs, and Spirit's internal analyses derived from both. It supplied sample reports and data payloads so the debtors could find the material and exclude it. Look at where that material lived. Mailboxes, chat, document libraries and the customer's own analysis are the same places the August 14 schedule lists by the hundred million.
Set that next to Section 6 of the sale agreement, where the seller represents that it's "the sole and exclusive owner of the Assets." Springshot's filings are, in effect, an argument with that sentence.
The sale hearing was first noticed for August 19, 2026, and had been adjourned five times by October 9. The fifth notice (Dkt. 1695), filed that day, moved it to 11:00 a.m. on November 6 in White Plains, set the debtors' reply for November 4, and said the debtors were continuing to work with objecting parties toward a consensual resolution. The record I'm working from ends with that notice, so the ruling, and whatever the court did with each vendor's papers, is on the docket at dm.epiq11.com/SpiritAirlines (opens in new tab). The argument doesn't wait on it. By October 9, a counterparty that wanted its confidential material treated differently had already had to say so in a filing, at its own expense.
The exit your vendor file doesn't have
Bank regulators' guidance already names most of the pieces. The 2023 Interagency Guidance on Third-Party Relationships (opens in new tab) from the Fed, FDIC and OCC lists contract provisions that "provide for the timely return or destruction of the banking organization's data, information, and other resources" under default and termination. Separately, it raises whether a contract lets the bank move its accounts, data or activities to another provider without penalty "in the event of the third party's bankruptcy, business failure, or business interruption." It even says provisions on whether data generated by the third party becomes the bank's property "help avert misunderstandings," which is Springshot's clause seen from the customer's side of the table.
Read together, they're about a vendor that fails and a vendor you leave. Spirit's schedule is a third case. The counterparty's own records are the thing being sold, and your material is inside them. Working the IT side of an IPO and an acquisition at Starwood Waypoint showed me how far a company's records travel once a transaction starts. A bankruptcy sale sends them to a buyer you never vetted, on a timeline you don't control. What I'd add to the file:
- Return or destroy, with evidence. I'd want the clause to name where your material actually lands at the counterparty (mail, chat and document libraries included), because Springshot's list shows that's where it ends up, and to require a certificate of destruction from a named officer that covers backups and the collaboration tenant. Spirit's own sale agreement shows the shape: privileged materials transferred by mistake go back or get destroyed at the seller's election, with destruction conforming to a confidentiality agreement between the buyer and Spirit. The seller knew how to write that clause. It wrote one for its own privilege and none for anybody else's confidences.
- A map of what each vendor holds about you. Per counterparty: the contract and its redlines, pricing, your security questionnaire answers and audit reports, architecture diagrams, incident correspondence, and anything their platform generated from your data. Rank it by what you'd least want in a training set or a competitor's hands. Springshot had to build its version of this map in a court filing, after the auction. If you're a vendor to financial institutions, run it in the other direction too, because when you're the third party, your answers sit in your customers' tenants.
- Questions for counsel. The answers turn on contract language and facts I can't see from here, so these belong with your lawyers.
- If a counterparty sells its records under section 363 "free and clear of all liens, claims, encumbrances and other interests," which of your confidentiality terms still reach the buyer?
- Does your definition of confidential information cover analyses the counterparty derived from your data, the category Springshot pointed to in its own filing?
- How would you learn a sale was coming, and how long would you have? Spirit's notice of auction results was filed on August 14 and set objections due by 4:00 p.m. on August 17.
One question belongs inside the firm rather than with counsel: who watches bankruptcy dockets for your critical counterparties, and which counterparties are on that list. Every item on that list uses the exit muscle you'd already build for context and memory in an AI contract, pointed at a counterparty's failure instead of your own decision to leave.
Your retention schedule is the asset list
Everything so far concerns other people's tenants. Turn it around. Exhibit A asked for Microsoft 365 data to be retained and transferred "within the native Microsoft 365 environment," mail, OneDrive, SharePoint and Teams together. Section 3(e) makes it a closing condition that no part of the assets has been "deleted, modified or removed" outside the ordinary course consistent with the seller's past practice, apart from deidentification and de minimis privilege removals. Under terms like those, the only deletion that's left is whatever the retention schedule was already doing.
The pattern I'd look for in a review is collaboration retention set to keep everything, because nobody wanted to own the decision to delete. Mail that's been kept since the tenant was stood up, and Teams chat that's never had a policy. It's the default that feels safe, and nobody gets blamed for a record they kept. On a schedule like Spirit's it's inventory, and every vendor thread in it is someone else's confidential material held at your risk.
Microsoft makes the argument in its own documentation. The data minimization section of its semantic indexing page for Copilot (opens in new tab) says "deleting content that no longer has business value also helps you manage risk and liability," and points to Microsoft Purview Data Lifecycle Management, licensed separately, to delete what's no longer needed with retention policies at scale and retention labels for exceptions. Microsoft wrote that about what Copilot can reach. It reads just as well as a description of what a buyer could reach.
Some of it you're required to keep, and counsel and records management own that list. The rest is a choice somebody made by not making one. In their motion to participate as amici (Dkt. 1677), as Stretto summarizes it, the Electronic Privacy Information Center and Professor Seema N. Patel argued that approving the sale as proposed would give employers nationwide an incentive to collect and retain as much worker data as possible against their own potential bankruptcies. I'd add the commercial version of that incentive. Every year of vendor correspondence you keep without a reason is a year a buyer can price and a counterparty may have to litigate over.