Effective 16 October 2026
Privacy, in plain language.
Blame the Fare uses the minimum data needed to run accounts, interpret trip requests, search flight inventory, monitor saved searches, and send alerts. We do not sell personal information.
What we collect
- Account details such as email address, password credential, and home airport.
- Your trip conversations, constraints, saved searches, and alert settings.
- Technical and usage data needed for security, reliability, and product analytics.
- Product analytics: the pages you view, the actions you take (for example starting signup or opening checkout), and — on some visits — a replay of the page with form inputs masked.
- First-touch campaign labels and the referring site hostname, when available.
- Delivery records for account emails and fare alerts.
- Subscription status and Stripe customer, payment, and invoice references.
How we use it
We use this data to authenticate you, turn natural-language requests into structured searches, query flight providers, rank matching fares, maintain saved searches, send requested alerts, prevent abuse, diagnose failures, and improve the service. We do not use a model-generated price as a fare; prices must come from a connected flight provider.
Services that process data
To understand which pages help people join, we link that limited visit information to account confirmation, saved Watches, and membership payments. This measurement does not store search queries or full referrer URLs. Short campaign labels and the referring hostname are kept in local storage so the first visit is not replaced by a later direct visit. Account deletion removes linked account records; you can clear the browser value by clearing site data.
Product analytics runs separately from that visit record. It counts page views and funnel actions, and on some visits records a replay of the page with form inputs masked. Its identifier lives in session storage for the current tab only: no cookie, no cross-site or cross-device tracking, and it disappears when you close the tab. It is not used to make decisions about you. Browsers that send Do Not Track are excluded, and anything URL-shaped is stripped of its query string before it is sent, so confirmation and reset links never leave the site.
Depending on which feature you use, data may be processed by Vercel (hosting, analytics, and workflows), PostHog (product analytics and masked session replay), Supabase (accounts and database), DeepSeek (trip-language interpretation), Duffel (flight search), Stripe (checkout, subscriptions, tax calculation, and receipts), and Resend (transactional email). Stripe receives billing details directly; we do not store your full payment-card number. Each service processes only the data needed for its role and under its own terms.
Retention and control
You can pause or delete saved searches in your account. Deleting your account permanently removes the account and cascades deletion through its saved searches, private offers, scan history, and alert records. Limited security or delivery logs may remain for their normal operational retention period. Never put passport, payment-card, health, or other sensitive personal details into the trip chat.
Your choices
You can disable alerts per search, remove searches, or delete the account. For an access, correction, or privacy request that cannot be completed in the product, reply to an account email with the subject “Privacy request.”
Changes
Material changes will be dated here and, when appropriate, communicated through the account email. See the related terms.
This notice describes the product as built. The operator should have counsel review it for every country in which the service is launched.