Privacy
Privacy, in plain language
This is a plain-language summary written by the developer who runs the site, not legal advice. Last updated 2026-10-22. It covers this website (flightpowers.com), the demo at demo.flightpowers.com, and the inputs our flights backend keeps when a search fails. Our MCP servers each have their own page (see the end). We do not sell your personal data.
On this site: no cookies, no third-party trackers
The site sets no cookies, loads no third-party analytics scripts, and carries no ad pixels. There is no consent banner because there is nothing to consent to.
We count page views with Vercel Web Analytics, our hosting provider's cookieless measurement, which stores no cookies and no personal identifiers.
A first-party anonymous event beacon
To learn which pages and tools are actually useful, the site records interaction events: which tool was used, which action was taken (like copying a code snippet or clicking through to a listing), and the page path. These events carry no identifiers: no user ID, no fingerprint, no cross-site anything. They answer “was this feature used?”, not “who used it?”.
Two more things ride along, and both are worth stating plainly. If you arrived through a link that carried campaign labels in the address bar (utm_source, utm_medium, utm_campaign), those labels are recorded, so we can tell whether a post we wrote actually sent anyone here. And the hostname of the site you came from is recorded, never the full referring address, which can contain a search query. To avoid counting the same visit twice, the labels are kept for the life of the browser tab insessionStorage and discarded when you close it. That is not a cookie, it is not shared between tabs or sites, and it still contains no identifier of any kind — which is also its limit: it counts arrivals, not people.
Free tools on this site
When you run a free tool on this site, your query (a route, a date, a hotel name) is sent to our API to answer that request and cached briefly in memory, keyed by the query itself, not by you, so repeated searches don't cost extra API calls. To stop one visitor from using up the day's budget, the server also counts requests per IP address in memory for the day; that count is not written to any database. This site has no accounts, so queries are not tied to one. If a flight search fails, its inputs are kept (see failed flight searches).
The demo (demo.flightpowers.com)
The demo is a separate app and works differently from this site. If you sign in with Google, we keep your name, email address, profile picture, and when you signed up and last visited.
What you type is sent to OpenAI, under OpenAI's API data terms, to turn it into a search. The conversation and its results are kept in a cache for 3 hours so the results page can load, and are not tied to your account. Flights you choose to save are kept with your account email (route, dates, airlines, stops, price and booking link) until you remove them. Price alerts you set (route, dates or nights, stops, times, airlines, your rule and the last cheapest price found) are kept with your email until you delete them; alert emails go out through Amazon SES.
The demo uses PostHog (EU servers) for analytics: it records the text of your search, the country part of your browser's language setting, and clicks on flights and sponsored links, under a random id that PostHog keeps in your browser's local storage. PostHog's script also sends its standard details (the page address, the referring page, browser, operating system and device), and PostHog receives your IP address, which it can use to estimate your location. Session recording and heatmaps are off. Signing in uses a cookie that holds your Google sign-in tokens.
An earlier version of the demo (April 2025 to March 2026) saved each search (airports, dates, nights, stops) with the signed-in account's email address, and on a small number of rows the IP address. That history is still in our database and is kept until deleted; the current demo's search page does not save searches this way. To have yours deleted, ask us (see Questions).
We may publish anonymous statistics from demo searches (counts and percentages of groups of 20 or more people, never one person's searches); write to app@flightpowers.com to object.
Failed flight searches
When a flight search fails, our flights backend saves its inputs (airports, dates, filters, currency, maximum price) together with the error, so we can find and fix the problem. This applies to every search that reaches that backend: this site's tools, the demo, the API, our MCP servers and our Apify flights actor. Your account, email address, IP address and API key are not saved with them. There is no automatic deletion yet: they are kept until we delete them.
Pasted API keys are never stored
The key checker on the pricing page forwards the key you paste once, to the live API, to see whether it authenticates. It is not stored, not logged, and not sent anywhere else.
The one thing we ask for: an email address
There is a single form on this site that asks for anything, and it asks for one field. If you give it an address, that address is stored so we can send you an email when something ships that changes what you can build: a new endpoint, a changed field, a deprecation, a price move. That is the whole purpose. It is not shared, not sold, not passed to the marketplaces, and not used to build a profile of you.
Stored with it: where you signed up from (which tool or page), when, and the campaign labels described above if your link carried any. No name, no company, no tracking pixel in the mail. Every email carries an unsubscribe link, and the unsubscribe page works without one, straight from the address. Opting out takes effect immediately and needs no reason.
Nothing on the site is withheld behind that form. The quickstart, the docs and the free tools are open to everyone, with or without an address.
Server logs
Like every website, the servers keep standard infrastructure logs (request paths, status codes, timestamps) for debugging and abuse prevention. They are ordinary operational logs, not an analytics system. Our flights API backend's logs include the search itself and are kept for about a day. The demo's own backend also logs the searches it handles and their results, kept for our hosting provider's standard log period.
The marketplaces are separate
If you subscribe to the APIs, that happens on RapidAPI or Apify, under their accounts and their privacy policies. This site never sees your card, your marketplace account, or your usage data there.
Our MCP servers
Each MCP server has its own privacy page, describing what that server keeps:
- Free MCP (with a sponsored card): free-trial.flightpowers.com/privacy
- Paid flights MCP: flights.flightpowers.com/privacy
- Paid hotels MCP: hotels.flightpowers.com/privacy
Questions
If you want to know anything about how this site or the demo handles data, or want your data deleted, ask directly: the contact page or app@flightpowers.com reaches the person who wrote this page.