Privacy

When you tap Use my current location, your browser sends your coordinates to our server so we can ask a routing service how long the drive to the airport currently takes, and again each time an open result refreshes. We do not write your location to a database, and we do not keep it after each calculation. If you enter a postcode or address instead, it is used the same way, and the planner also keeps it in your own browser with your flight, as set out under Cookies.

There are none. PlanMyFlight has no sign-up, no login and no saved profile.

We record which steps of the flow people reach — a search starting, a flight being confirmed, a leave time being shown, and which of the two planners it happened in — so we can see where the tool is failing people. These records can include the flight number, the airport, the travel date, your bags and how long until you leave. Your device’s coordinates are never sent to analytics. If you accept Google Analytics, it records the web address of each page, and a result’s address holds any postcode or address you typed.

Two tools do the counting. Vercel’s visitor counting uses no cookies and runs for everyone. Google Analytics sets cookies, so it runs only if you accept them; if you decline, it never loads.

To answer a question we pass what it needs to these services, and nothing more:

• Flight data. AeroDataBox (through RapidAPI) and, for pick-ups, Flightradar24 receive the flight number, route or date being looked up. They never receive your location, and they are the source of the flight times we show. The “Follow this flight live” link on a result opens Flightradar24’s own website in a new tab, with the flight number in the address and no referrer; from then on its own privacy policy applies.
• Drive time. Google’s routing service receives your starting point and the airport. A UK postcode is turned into a point on the map by postcodes.io, a free postcode service; any other address you type goes to Google for the same job, and so does a postcode postcodes.io cannot place.
• Describing a flight in your own words. Anthropic’s language model reads the text you typed, your time zone and the current time. It never sees your coordinates or postcode, and it is not the source of any flight information you see. It also reads a question typed in the “Find an answer” box, but only when our own matching cannot tell which airport or topic you mean.
• Hosting and counting. Vercel, which is based in the United States, serves the site, counts visits without cookies and keeps its standard server logs (such as your IP address, the number that identifies your internet connection, and your browser type) for a short time under its own policy. A shared link, or Open on the “Your flight” card, carries any postcode or address you typed in its web address, so opening one puts it in those logs too. Our own short log lines about a search hold the flight, airports and date, never your postcode.
• Running counts and reports. Upstash, a database service, holds the counts described under “Keeping the site working”, the click counts described under Partner links, the question box’s daily counts of airports, topics and outcomes (never the question) and, if you use “Spotted a change?”, what you send, for up to 90 days.
• Email. Resend delivers a message sent through the contact form to our inbox.

Partner links and Google Analytics have their own sections.

Every page shows adverts for independent companies, marked “Ad”. We earn a commission if you book through one. Nothing is sent to them unless you click.

• airport transfers abroad, on a departures result
• airport parking and hotels in an airport page's parking section
• a partner's own banner in the empty margins either side of every page, on a wide screen
• a partner's own banner under the top of every page, on phones, tablets and smaller laptops

A partner link goes first to our own address (PlanMyFlight’s /go/ page), which sends you straight on and sets no cookies. It counts the click, and the count holds only the day, which partner, where the link was (a result, an airport page, the side rails or the banner under the top of a page) and the airport where it was on an airport’s page or result — not your IP address, your browser, your flight, your leave time, your postcode or your location. The counts are deleted after about 13 months. As on the rest of the site, a short count per internet address, kept for ten minutes, stops abuse; it is never joined to the click counts.

From there the link passes through Awin, the affiliate network that tells the partner the booking came from us, and opens the partner’s own website. It tells Awin where the link was on our site and the airport, nothing about you or your search. Awin and the partner may set their own cookies once you have clicked, so that a booking can be credited to us; from then on their own privacy and cookie policies apply.

PlanMyFlight sets no advertising cookies and no tracking cookies of its own. The only cookies that can be set are the analytics ones described above, and they are not loaded at all unless you agree to them — declining means the script never runs, rather than running quietly in the background.

Partner links set no cookies on this site. What Awin and the partner may set on their own sites after you click is under Partner links above.

Google Analytics, if you accept it, sets cookies named _ga and _ga_ followed by an identifier, which Google keeps for up to two years. Declining, or changing your answer later, also removes any of them an earlier “yes” left in your browser.

Your answer is remembered in your browser’s local storage, not in a cookie. If your browser sends a Global Privacy Control signal we treat that as a decline and do not ask.

If you work out a leave time, the planner also keeps that flight, with the postcode or address if you typed one (never your device’s location), in your browser’s local storage, so it can offer it again when you come back. Each of the two planners keeps one. It stays on your own device and is not sent to us unless you press Open, which looks the flight up again like any other search, with any postcode or address in the web address. “Forget” on the card removes it, and so does opening that planner more than six hours after the flight. A newer flight replaces it, and it is removed if a later check shows that flight as cancelled, possibly cancelled or diverted. Otherwise it stays until you clear your browser’s site data.

Change your cookie choice

The paid flight, routing and email services are shared by everyone, so we keep short running counts against your IP address to stop one person using them up: for ten minutes for searches, drive-time checks and partner-link clicks, and for an hour for the contact form and “Spotted a change?”. A daily search limit uses a scrambled code made from your address and the date, kept for about a day; it cannot be turned back into your address, and it is different tomorrow. The counts hold no flight, postcode or message, and are never joined to anything else.

If you use “Spotted a change?” on an airport guide, we keep only what you write and any link you add, for up to 90 days, so we can check it against the airport’s own website; we don’t keep your name, email or IP address, and nothing you send is shown on the site.

When you ask a question in the “Find an answer” box, the words you type are sent to our server so we can work out which airport and which topic you mean. If our own matching cannot tell, a language model (Anthropic’s, a United States company) reads the question to choose from a fixed list of airports and topics. It sees only what you typed, never your location, and it writes nothing you see: every answer is a row of the airport guide, with the airport’s own words, the page they are on and the date we read it.

We do not keep your question. We keep a count for each day of how often each airport and topic was asked about and whether the guide had an answer: no question text, no IP address and nothing that identifies you. Those counts are deleted after about 13 months. To stop one person using the box up, it also counts your questions against a scrambled code made from your internet address and the date, kept for about a day; the code cannot be turned back into your address, is different tomorrow, and is never joined to those counts. The box sets no cookies and stores nothing in your browser. Its analytics events never carry what you typed: they say how the question was sent and what came back and, only if you accepted Google Analytics, which airport and topic the guide matched.

The contact form collects your email address, your message and a name if you give one. We use them only to reply, and we do not add you to any mailing list. The message reaches our inbox through Resend, which also keeps a copy for a limited time under its own policy. We keep the message only as long as we need to reply and deal with it.