Cookie Policy
The cookies this site sets, what each one is for, and how to control them. Three are strictly necessary; analytics is set only if you accept it.
1. What cookies are
Cookies are small text files stored on your device when you visit a website. They help the site work, remember your preferences, and understand how it's used. Similar technologies (e.g. local storage, pixels, SDKs) are covered by this policy too.
2. Your consent
Analytics cookies are set only if you accept them. The first time you visit, a panel at the foot of the page asks whether we may count your visit with Google Analytics. Until you answer, and if you answer no, no analytics cookie is set and your browser makes no request to Google Analytics at all — the tag is not put on the page in the first place, rather than placed there and asked to hold back.
You can change your mind at any time using the Cookie settings link at the bottom of every page. Choosing "Reject" stops any further collection; to remove analytics cookies already stored, clear cookies for this site in your browser (section 5).
The other cookies below are strictly necessary and are set without asking: one keeps you signed in, one remembers which country you appear to be browsing from so the site can show you nearby airports, and one records the answer you gave to this very question. None of them is used to profile you, and none is shared with anyone.
If we ever add advertising or other non-essential cookies, we will ask for your consent separately and update this page before any of them are set.
3. The cookies we use
This is the complete list. The three strictly necessary ones are set by WhatFBO itself, are SameSite=Lax, and are sent only over HTTPS. The first two are also marked HttpOnly, so page scripts can't read them; wf_consent is not, because the banner has to read your answer in order to know not to ask again.
| Name | Category | Purpose | Consent needed? | Duration |
|---|---|---|---|---|
whatfbo_site |
Strictly necessary | Keeps you signed in and protects forms against cross-site request forgery | No | 30 days |
wf_cc |
Strictly necessary | Stores the two-letter country code we derived from your IP address, so the homepage can suggest airports near you without repeating the lookup on every page | No | 30 days |
wf_consent |
Strictly necessary | Records whether you accepted or rejected analytics cookies, so we honour your answer and stop asking. It holds one word — granted or denied — and no identifier of any kind |
No | 180 days |
_ga |
Analytics | Google Analytics. Assigns a random identifier to your browser so repeat visits are counted as one visitor rather than several. Set only after you accept | Yes | 2 years |
_ga_<container> |
Analytics | Google Analytics. Keeps the state of your current session so a set of page views is counted as one visit. Set only after you accept | Yes | 2 years |
We use no advertising or marketing cookies at all, and we have not enabled Google Analytics' advertising features, Google Signals or ad personalisation. The analytics data is used to see which airports, services and pages people actually use, so we know what to build next — not to target you.
4. Third-party cookies
Google Analytics is the only third party that sets a cookie here, and only with your consent. The _ga cookies are written by Google's tag running on our pages, and the measurements are held in our Google Analytics property. The country lookup behind wf_cc runs against a copy of the DB-IP database held on our own server, so your IP address is not sent to a geolocation service.
Two further things on our pages are loaded from Google rather than from us: the web fonts, and the satellite images shown on airport pages. Neither sets a cookie, but because your browser fetches them directly, Google receives your IP address and the page you were on. That is covered by Google's own privacy policy — and it happens whether or not you accept analytics.
If we later embed content or use a provider that does set cookies — a payment page, for instance — we will list it here and, where it isn't strictly necessary, ask for your consent first.
5. Managing cookies in your browser
You can also control cookies in your browser settings, including blocking or deleting them. Note that blocking our own cookies will sign you out, stop the site remembering where you are, and lose your answer to the analytics question — so the panel will ask again. Guidance for common browsers is available at aboutcookies.org or allaboutcookies.org.
6. Changes
We'll keep this current. As we add or change cookies we'll update this policy and, where required, ask for your consent.
7. Contact
Questions about cookies? Email fly@whatfbo.com.
The other policies
