When the financing comes with a data clause

Spirit Airlines needed money. Google, according to the flight attendants’ union, wanted something more interesting than interest payments.

Fortune reported last week that the Association of Flight Attendants is accusing Google of structuring a deal around Spirit’s restructuring that would hand the tech giant access to confidential airline data for AI purposes. The union’s language was blunt. “Adding insult to injury” is how they framed it: their employer is in financial distress, their jobs are uncertain, and now the data generated by their work might get folded into someone else’s model training as a side effect of a transaction they had no seat at.

Set aside for a moment whether the union’s characterization holds up in every detail. The shape of the deal is the story. And the shape is one we’re going to see again and again.

Data as the sweetener

When a company is healthy, its data sits behind contracts, policies, and a general reluctance to give anything away. When a company is desperate, all of that becomes negotiable. Data turns into an asset on the table, right next to the gates and the aircraft leases. A lender or strategic partner who wants training data doesn’t have to buy it on the open market. They can attach it to financing that the company can’t afford to refuse.

Notice who’s missing from that negotiation. The flight attendants whose schedules, communications, performance records, and operational patterns make up a real chunk of that “confidential data” were not in the room. They didn’t sign up for it when they took the job. There was no consent moment. Their information became a bargaining chip because it happened to be sitting in systems their employer controlled and their employer needed cash.

That’s the part that should make every executive uncomfortable, and not only on behalf of the workers. Flip the seats. Your company’s data is sitting in a vendor’s cloud right now. That vendor has its own investors, its own pressures, its own potential acquirers. If your vendor hits a rough patch, or gets bought, or signs a strategic partnership with an AI lab, what stops your data from becoming their sweetener?

Read your agreements. In most cases the honest answer is: less than you think. Terms of service change. “Improving our services” clauses stretch. Acquisitions transfer data along with everything else, and the successor company’s appetite may not match the original vendor’s promises.

Consent doesn’t survive the deal

Here’s the mechanism worth naming plainly. Consent, in most data arrangements, is a snapshot. An employee consents to an HR system. A company consents to a cloud provider’s terms. Then the world moves. The provider changes hands, the terms get amended, a financing deal introduces a new party with new incentives. The original consent never contemplated any of it, but the data doesn’t get re-asked. It just flows to wherever the paperwork now permits.

The Spirit situation makes this vivid because a bankruptcy court and a union give it visibility. Most versions of this story never get a headline. The data quietly gains a new downstream use, a new processor, a new training pipeline, and nobody with standing to object ever finds out.

For firms handling client files, patient records, case materials, or workforce data, this should reframe the vendor question entirely. The question is not “do I trust this vendor today.” It’s “do I trust every future owner, creditor, and strategic partner of this vendor, under financial conditions I can’t predict.” Nobody can answer yes to that honestly.

The only clean answer is architectural

You can’t contract your way out of this. You can architect your way out of it.

If the AI workload runs inside infrastructure you control, on hardware in a known jurisdiction, with models you selected and can swap, there’s nothing for a third party to acquire access to. There’s no pool of your data sitting in someone else’s cloud waiting to become deal collateral. A vendor’s bankruptcy, acquisition, or creative new financing arrangement can’t repurpose data it never touched.

That’s the entire premise behind private AI workspaces as we build them at Modular. Client data and workforce data stay inside the client’s environment. Models run locally. Nothing feeds a third-party training pipeline, not because a policy says so, but because there’s no pipe. We own the stack from the physical facility to the interface the user touches, which means there’s no intermediate layer where someone else’s business model can intervene. Your data, your rules, from dirt to desktop.

And because the pricing is fixed, there’s no meter running that tempts anyone, us included, to find secondary value in what flows through the system. The economics are aligned with the architecture. You pay for capability, not for the privilege of becoming training data.

The flight attendants understood something instinctively that a lot of boardrooms still haven’t internalized: once your data is in someone else’s hands, your interests and theirs will eventually diverge, and when they do, the paperwork will favor whoever holds the servers.

The closing thought

I keep coming back to the phrase “adding insult to injury.” The injury was the financial distress. The insult was discovering that your working life had a resale value you never agreed to. Spirit’s flight attendants at least have a union loud enough to get this into Fortune. Most employees, and most companies whose data is riding in third-party clouds, will never get the courtesy of a headline.

The uncomfortable exercise for this week: pull up your top three data-holding vendors and try to answer, from the actual contract language, what happens to your data if they’re acquired or restructured. If you’ve done that exercise, or if you think I’m overreading the Spirit deal, tell me what you found. I’d genuinely like to compare notes.