Privacy
Last updated October 11, 2026. It changes only when what the site collects or stores changes, not when its pages do.
The short version
FlyerIntel does not require an account and does not ask who you are. It carries advertising through Google AdSense, and uses Google Analytics to count visits and see which pages are read, so Google receives a record of your visit for both purposes. Advertising cookies can follow you to other sites; the controls for turning that off are below. Nothing here is sold.
What is collected
- Server logs. Standard web server request logs — IP address, timestamp, requested URL, referrer and user agent — kept for a short period to operate the service, diagnose faults and detect abuse.
- Correction reports. If you submit a correction, we store what you write and, if you choose to provide it, your email address. It is used only to act on and follow up that report.
- Google AdSense. Ads on this site are served by Google, which may set cookies or read device identifiers to choose what to show you and to measure it. That data is Google’s, collected under how Google uses information from sites that use its services (opens in a new tab). FlyerIntel does not receive it, and gives Google nothing about you beyond the fact that the ad slot was on this page.
- Google Analytics. Pages you view, roughly where in the world you are, and what kind of device and browser you use, so we can tell which parts of the site are worth the effort. It is collected by Google on our behalf and is subject to Google’s privacy policy (opens in a new tab). We see only aggregate reports, never a name or an individual identity.
What is not collected
- No accounts, no passwords, no profiles.
- No accounts to advertise against. Ads are chosen by Google, not by us from anything we hold: FlyerIntel builds no profile of you and hands nothing to advertisers.
- No location tracking. Searching an airport tells us nothing about where you are.
- No sale of personal information, ever. Analytics data is shared with Google as the processor described above, and with nobody else.
Cookies
Google Analytics sets a cookie to tell a returning visitor from a new one; it counts rather than profiles. Google AdSense may set its own cookies to select and measure ads, and those are the ones capable of following you between sites. Every other cookie present is strictly necessary for the site to function.
Places you save with the Save button, and the pages you have viewed recently, are kept in your browser’s local storage, not in a cookie, and are never sent to FlyerIntel. The exceptions are the airport codes among them, and a saved flight’s code and number when you press its button (described under Live flight position below). The airport codes: the homepage sends those to FlyerIntel’s own status endpoint to show current conditions, and a saved airport’s own page sends that one code. Those requests, like any other, appear in the server logs described above. Delete a saved place from the homepage, or clear this site’s data in your browser, to remove all of it.
For each saved airport, the browser also keeps the last conditions it was shown for it, on the homepage or the airport’s own page, and the time it got them, in the same local storage. If your connection drops, the offline page lists your saved places from that copy and labels each reading with its age. The offline page itself is a single page of ours that your browser stores through a service worker; it holds nothing about you, reads your saved places only from your own browser, and sends nothing anywhere.
You can turn off personalized advertising at Google My Ad Center (opens in a new tab), and opt out of third-party vendors’ cookies at aboutads.info (opens in a new tab). Browser controls and content blockers stop both the analytics and the ad script without affecting anything on the site — no page here is gated behind either.
Third parties
The site is served from FlyerIntel’s own infrastructure, and fonts and assets are served from this domain rather than a third-party CDN. The exceptions are Google Analytics and Google AdSense, both of which load from Google and therefore disclose your visit to Google. FlyerIntel fetches data from public sources on a schedule; it never forwards anything about you to them.
Live flight position
A flight page has a “Show live position” button. Nothing is requested until you press it. When you do, your browser sends the airline code and flight number to FlyerIntel’s own server, where it is recorded in the server logs described above like any other request. To find the aircraft, FlyerIntel’s server then asks ADSB.lol for the matching radio callsign (for DL1052, DAL1052) and for nothing else. Your address, your browser details and the page you were on do not go to ADSB.lol, which sees only FlyerIntel’s server. Your browser makes no request to ADSB.lol, and the map is drawn from files on this domain.
The homepage’s “Your places” list does the same for flights you have saved, and only when you press a button. “Check now” sends one saved flight’s airline code and number to FlyerIntel’s own server; “Check all” does it for up to four of them, one after another. Nothing is sent when the page loads, when you return to the tab, or on a timer. The server looks each flight up exactly as above, sending ADSB.lol a callsign and nothing else. Your browser keeps the last answer for each flight, in words (for example “in the air, 410 miles to LGA”) with the time you asked, in the same local storage as your saved places. The offline page shows it labelled as an earlier check, never as where the flight is now. That answer never leaves your browser again, and removing the flight from Your places removes it.
Your requests
To ask what we hold about you, or to have a correction report and its contact address deleted, write to hello@flyerintel.com.