The proposed purchase matters well beyond the collapse of one U.S. airline. WION’s reporting describes a dataset that reaches deeply into a former enterprise’s everyday operations: Teams conversations, Outlook-era communications and calendars, OneDrive and SharePoint material, engineering repositories, technical logs, scheduling, finance, HR records, and operational history. Google says it acquired part of an enterprise dataset to improve its products and AI models, and says a third party will rigorously remove personally identifiable information before Google receives it.
For Microsoft 365 administrators, the uncomfortable lesson is that a tenant’s collaboration archive can remain an asset with commercial value long after the business itself stops operating. Deleting a user account, moving content into retention, or treating chat history as ordinary operational exhaust are very different things from deciding the future ownership and permitted uses of that material during a sale or insolvency proceeding.
The sale is about operational exhaust, not merely email
Axios reported that the auction package includes emails, calendars, chats, documents, spreadsheets and other business data. WION’s account, citing the bankruptcy case documents, puts more shape around the records: more than 17 million OneDrive files, over 20 million SharePoint documents, 516 engineering repositories containing nearly 30 million lines of code, technical logs, employee and payroll records, booking and flight-scheduling information, board presentations, audits, and budget walkthroughs.
That is a much more consequential collection than a mail archive. Taken together, those systems capture how an organization assigns work, resolves incidents, forecasts demand, shares operational reports, authorizes changes, responds to disruptions, and records decisions. A polished policy manual shows what a company said it did; Teams conversations, spreadsheets, repository history and operational logs can show what staff actually did under pressure.
Microsoft’s own documentation makes clear how closely these systems interlock. Teams is where groups coordinate; SharePoint provides the team’s shared document libraries; OneDrive stores individual work files that can be shared into team workflows. In a mature Microsoft 365 deployment, a document may be technically held in OneDrive or SharePoint while its meaning is found in a Teams thread, a calendar invitation, an email discussion, a project tracker or a code commit.
That linkage is why the raw count of 500 million Teams messages should not be read as a pile of isolated chat text. It potentially preserves relationships among documents, schedules, people, projects, technical problems and business decisions. Google has not publicly described the precise models or individual products it expects to improve with the Spirit material, so claims that the records will train a particular Gemini release or power Google Flights would be speculation. The company has said only that the dataset can help improve its products and AI models.
“No PII” and “will be scrubbed” are not the same assurance
The most important unresolved point in the public descriptions is how the promised privacy boundary will be implemented. Axios cited a filing by Spirit investment banker Dylan Friesner saying the data does not contain personally identifiable information. Yet Google’s statement says that a third party will scrub any personally identifiable information before Google receives the dataset.
Those statements may be consistent: the sale package may be contractually defined to exclude PII, while a third-party process removes remaining personal data from the underlying material. But they are not interchangeable. One describes the dataset’s claimed condition; the other describes a future processing step. Neither public account identifies the de-identification vendor, the technical standards it must meet, how accuracy will be tested, how exceptions will be handled, or whether an independent party will audit the result.
The distinction is significant for enterprise data because personal information is rarely confined to clean database columns. Names, email addresses, phone numbers and employee IDs can be detected relatively directly. Identity can also appear in meeting context, signature blocks, filenames, free-form incident notes, travel details, job titles, unique shift patterns, internal nicknames and combinations of otherwise ordinary operational events.
The buyer has reportedly agreed not to attempt re-identification. That is an important contractual restriction, but it does not explain the controls around the dataset before and after transfer, nor does it make de-identification an automatic guarantee. A corpus can be stripped of direct identifiers while still retaining highly specific business context. The bankruptcy court will therefore be approving more than a conventional sale of inactive IT assets; it will be assessing a proposed handoff of an unusually rich organizational record for AI development.
Customer profiles are excluded, but the boundary needs closer scrutiny
Both Axios and WION report that passenger profiles and frequent-flyer information are excluded from the transaction. Google likewise says it will not receive personal information. That exclusion is the central privacy safeguard in the proposed deal, particularly given that Spirit’s historical records include booking-related and operational data.
But the public reporting also describes more than 190 million booking records in the broader set of documents. The filings, as characterized by WION, appear to distinguish the airline’s internal business data from passenger profiles and loyalty records. What remains unclear is whether the booking material transferred to Google will be aggregated, redacted, transformed, or limited to operational fields such as route, date, fare category, load factor and disruption status.
That detail should not be treated as a minor footnote. Booking data can be valuable for AI work without containing a traveler’s profile, but the security and privacy properties of a dataset depend on its fields, granularity and linkability. A row with no name can still become sensitive if it contains enough unusual combinations of travel timing, origin, destination, purchase details and service events.
There is also an employee dimension. WION reports that personnel, payroll and tax materials dating as far back as 1986 form part of the documents described in the case. Google’s public statement promises the removal of PII, but neither Google nor the available reporting has provided a public data dictionary showing exactly which HR, payroll, tax, communications and source-control fields will be supplied after processing.
For former Spirit workers, the practical issue is not whether an account remains active. It is whether historic records created during their employment are included in a court-approved dataset, and what de-identification standards will apply to them. The answer is not yet public.
Update: Court hearing set as filing reveals tighter data-transfer terms (August 19, 2026)
Spirit’s proposed sale is scheduled for a U.S. Bankruptcy Court hearing at 11 a.m. Eastern on August 19. The filing also specifies that Microsoft 365 content will be retained and transferred in its native environment, rather than as a simple bulk export. The asset schedule lists 100 million emails from 80,000 accounts, 500 million Teams records, 17,082,644 OneDrive items, 20,577,677 SharePoint items and 667,563 ServiceNow tickets.
The agreement adds more detail on de-identification: it requires the data to be transformed so it cannot reasonably be linked to or used to infer information about a consumer, while preserving referential integrity across the dataset. Spirit must use de-identification agents acceptable to or designated by Google; Google may review and comment on the process and is covering its cost. The filing requires certification of compliance with applicable law, relevant California de-identification standards and prevailing industry standards before delivery.
