A traveler trying to book a JetBlue flight to attend a funeral watched the fare jump $230 in a single day. JetBlue's response, before it was deleted: "Try clearing your cache and cookies or booking with an incognito window. We're sorry for your loss."
That exchange now opens a proposed federal class action. The lawsuit alleges JetBlue uses tracking technology on its booking site and shares customer data with third-party vendors, including FullStory and PROS Holdings. The theory is straightforward: FullStory captures behavioral analytics, PROS supports real-time pricing, and JetBlue failed to adequately disclose that customer data was feeding into what each shopper sees.
JetBlue denies the core allegation. The company says it does not use personal information or web browsing history to set individual prices, and that fares are based on demand and seat availability. That denial matters. It also draws the line that every company using AI in its pricing stack now has to understand.
Dynamic Pricing Is Not Surveillance Pricing
The two get conflated, and they should not be.
Dynamic pricing responds to market conditions. Hotel rooms cost more during a convention. Rideshares surge in a thunderstorm. Airline seats get more expensive as the plane fills up. The price moves because the market moved. Everyone shopping at the same moment sees the same number.
Surveillance pricing responds to you. Your device, your browsing history, your past purchases, your inferred urgency, your zip code, the fact that you searched the same flight three times in two hours. The price moves because of signals collected about you specifically. Two people shopping the same product at the same moment can see different numbers.
That distinction is where regulators and lawmakers are now focused. New York now requires businesses using personalized algorithmic pricing to disclose, in plain language: "THIS PRICE WAS SET BY AN ALGORITHM USING YOUR PERSONAL DATA." More than 40 bills across at least 24 states have been introduced this year targeting personalized algorithmic pricing. California's AB 2564 would go further, banning retailers from engaging in surveillance pricing entirely, with civil penalties up to $12,500 per violation.
The FTC opened a study into the practice in 2024. The questions it asked vendors are pointed: what data goes in, what prices come out, and how is any of that disclosed to the consumer.
The Mechanism the Lawsuit Is Targeting
The JetBlue case is interesting less for its specific facts than for the alleged liability mechanism it is testing in court: behavioral data flowing into pricing systems without clear disclosure.
That mechanism does not require malice. It requires a stack. A session-replay vendor here, a price-optimization vendor there, a cookie banner that says "we use cookies to improve your experience," and a privacy policy written before any of these tools existed. Each piece is unremarkable in isolation. Together, they describe a pipeline where what you do gets converted into what you pay.
If your company uses AI or automated tools anywhere in pricing, two things are worth checking now:
- What data your pricing tools actually consume — directly or through vendors.
- Whether your privacy policy, cookie banner, and vendor disclosures accurately describe that use.
The legal exposure is not theoretical anymore.
The Bigger Pattern
Surveillance pricing is one visible symptom of a broader arrangement most consumers never explicitly agreed to: their behavior is the input, and the output is increasingly something done to them rather than for them. Ad targeting was the first wave. Dynamic feed ranking was the second. Pricing is the third, and it is the one where the cost is no longer abstract. It shows up on the checkout page.
The defensible position for consumers is the same one regulators are starting to demand from companies: data minimization. The less behavioral exhaust you generate, the less of it can be turned into a profile, and the less that profile can be priced against you.
That principle scales down to the tools you use every day. Every cloud-based service that processes your input — your voice, your documents, your search history, your drafts — is a potential entry point into a behavioral graph you do not control. Most of the time the trade is invisible. Sometimes, like in the JetBlue allegations, it shows up as a $230 surcharge on a funeral flight.
Where TypeSay Fits
We built TypeSay around a single idea: your voice is yours alone. Speech-to-text does not need the cloud. It does not need an account. It does not need telemetry, analytics, or a vendor pipeline. Whisper runs locally on your machine. Your audio is captured, transcribed, and discarded in memory. Nothing is saved. Nothing is sent.
That is not a marketing posture. It is an architectural choice with a downstream consequence: there is no behavioral data for us, or anyone we contract with, to feed into a pricing system, an ad network, or a profile of you. There cannot be, because the data never leaves your hardware.
One-time purchase. No subscription. No cloud. The cases like JetBlue's are a reminder of why that combination matters.
TypeSay is private, local-first speech-to-text for Windows, macOS, and Linux. $199, one time, forever.