What we store, what we send, and who else is involved
FlyGamma has no accounts or sign-in. It counts visits two ways. Cloudflare Web Analytics counts everyone and stores nothing on your device — no cookie, nothing that could recognise you again — so it is not something you are asked about. Google Analytics needs a cookie that lasts two years, so it runs only if you press Allow. Send Do Not Track and neither runs. The rest of this page is mostly still a list of things that do not happen.
This notice was last changed on 6 October 2026 to explain the optional answer-page action counts. Earlier changes clarified subject links in error reports and saved preferences. Since 30 September, the phone map has used location already allowed by the browser for its opening view. It describes the site as it behaves on that date, checked against the code rather than summarised from memory. An earlier version said this site ran no analytics; that changed when analytics was added. The location behaviour is explained below, including what happens when the browser has no location to offer.
The Calm Focus Journey Desk launched on 2 October 2026. Its home page uses
the same consent-gated analytics loader for page views. Saved flight numbers use the
existing flygamma.watch preference; its appearance uses
flygamma.calm.theme. Both stay in your browser. flygamma.calm.library stores the last known route, status, arrival and departure times, gate and check time for saved flight numbers, plus airports, airlines, routes and aircraft types you choose to save. It also stores whether you want saved-flight change messages while the page is open. These messages compare available feed snapshots; they do not run in the background, request notification permissions or send your saved list anywhere. You can remove saved items in Saved, or clear this site’s browser data. Search suggestions use the directory already loaded in the page and send no keystrokes to a service. A flight number
submitted for a timetable lookup, or an airport code selected for arrivals or
departures, is sent to our same-origin API and then to the configured flight
supplier. General list searches and filters stay in the page. The classic map
at /map and written pages retain the analytics and location
behaviour described below.
Explore opens within a 500 km radius of your location only if your browser has already granted this site location permission. Opening Explore never asks for new permission. If permission is absent, denied, unsupported or the location lookup fails, it opens on a busy region measured from reported airborne positions. Once you move the map or choose a result, a late location answer cannot reset your view. Coordinates remain only in the page’s map camera: they are not saved, put in the URL, logged, or sent to our servers, counters or Google. A location-centred view therefore uses locally served geography in both Flat and Globe modes.
When Google Maps is configured, Flat views other than device-location views use Google's Maps JavaScript API. Google receives your IP address, browser information, the site's origin and the map area you view to deliver its map. This map service is separate from optional Google Analytics. The mobile globe and the standard fallback map use our locally served geography. We do not request your device's location for Google Maps or send your saved list or search keystrokes to it. See Google's privacy policy. Switching to Flat can load this service; returning to Globe stops displaying it.
The main Journey Desk and the classic live map at /map run map applications. The airport, airline, method and monthly-log pages run the analytics file described below. The flight and route answer pages also load a small checker; it contacts the flight-data endpoint only after you press Check. Map-specific behaviour described on this page does not apply to those written pages.
These preferences are kept by your own browser on your own machine, none of them ever sent anywhere:
| Name | What it holds | Written when |
|---|---|---|
| flygamma.theme | The word light or dark | You change the theme |
| flygamma.units | Your unit and clock choices — feet or metres, knots or km/h, and which clock to show | You change a unit |
| flygamma.calm.library | Saved journey summaries, favourite airports, airlines, routes and aircraft types, and the in-page update preference | You save or remove an item, change the preference, or the available feed updates a saved journey |
| flygamma.watch | The flight numbers you saved, as a plain list | You save a flight |
| flygamma.zones | Up to four world clocks you added | You add a clock |
| flygamma.projection | The word globe or flat | You switch the map projection |
| flygamma.consent | The word granted or denied — your answer to the cookie question | You answer it |
| flygamma.home | The name of one country, such as United Arab Emirates, so the airline list can put that country’s carriers first. It is worked out inside the page from the position the locate button read, by measuring against the airport table already loaded here — the position itself is not kept, and nothing is asked of any service | You press the locate button and allow it |
| flygamma.density | The word compact, or nothing, for how tightly the flight list is drawn | You press compact |
| flygamma.seen | The word 1, meaning the one-line greeting beside the name has been shown once | Your first visit |
| flygamma.start | The word 1, meaning the opening sheet that asks what you want has been shown once | Your first visit |
None of these is an identifier. Nothing here is random, generated, or capable of linking one visit to another or one device to another — every value is either a word from a fixed list or something you typed in yourself. The greeting flags may be written on a first visit; other preferences are written when you choose them. An older visit may have left a flygamma.location-prompted flag. It contains no location and is no longer read or written.
We never delete them, because they are yours: they last until you clear this site's data in your browser, which you can do at any time without breaking anything. If your browser refuses storage — private browsing, or site data blocked — the site works normally and simply forgets your preferences.
We use no session storage, no databases in your browser, and no service worker.
If you press Allow, Google Analytics sets two cookies on flygamma.com: _ga and _ga_QJH1D1K3T4. They hold a randomly generated number that distinguishes your browser from another one, they last two years, and they are what makes a returning visit countable as the same visit rather than a new one. They are the one thing on this site that can link two of your visits together, which is exactly why they are behind a question.
Press No thanks and neither is ever set. Nothing is loaded at all, so there is nothing to opt out of afterwards.
Two things worth naming, because they are easy to overlook and they are not in our control:
The Journey Desk, classic map and written pages contact Cloudflare for visit counts and Google Analytics if you allow analytics. On a flight or route answer page, pressing Check also requests the relevant report from our flight-data endpoint. If you allowed analytics, the Check press and a click on the airline-status link are counted as described below. When configured, the Journey Desk's Flat map contacts Google Maps for map scripts, fonts and imagery. This map service is separate from analytics consent. The site's Content-Security-Policy limits external resources to the services described here.
This runs for everyone, and it is why you are not asked about it: it stores nothing at all on your device. No cookie, no identifier, nothing that could recognise you on a later visit or link one page to the next. It counts a visit and forgets you.
Cloudflare receives the page address, the page you came from, your browser and device type, and — unavoidably, as with any request to any server — your IP address, which it uses to derive an approximate country. Cloudflare states it does not use this to build profiles of individuals or to track people across sites, and it is not sold. It is what tells us how many people really came, which the Google figure cannot, since that one only ever sees the visitors who said yes.
Do Not Track or Global Privacy Control switches this off too, even though it stores nothing: somebody who has asked not to be measured has asked for that whether or not the measuring is anonymous.
Since 3 September 2026, when something on the map fails, the page sends a short report to this site's own server so we can find out. Before that the site had no way of telling us it was broken, and three faults that affected every visitor went unnoticed for weeks.
A report contains four things and nothing else:
At most five reports are sent per page load. They contain no identifier of their own and are not stored by us — they are written to our hosting provider's log, described below. One caveat we would rather state than omit: if you have allowed analytics, the Google cookies are set on flygamma.com, and your browser attaches them to every request to this site, including these reports. So while we put no identifier in them, one rides along, and reports from the same browser could in principle be matched to each other. Decline analytics and they carry nothing.
These are not only crashes. A file that fails to load counts too, so a report can arrive from a page that looked perfectly fine to you.
If your browser sends Do Not Track or Global Privacy Control, none of this happens at all. No error reports are sent and no watcher is installed.
Only if you pressed Allow. It tells us how many people visit, which pages they read and roughly where in the world they are — the things that decide whether any of this is worth continuing.
On the written flight and route answer pages, we also count a press of Check now and a click on Confirm with airline where that link appears. Google receives the event type, whether it was a flight or route page, and that page's address without query text. The address itself identifies the flight number or airport pair on that page. No supplier response, typed search, or visitor location is added to these events. These counts cover only visitors who allowed analytics; they are not a count of everyone who used the buttons.
What Google receives when you view a page:
What you search for. When you pick a result from the search box, the words you typed are sent as part of that event, along with what kind of thing you chose — a flight, an airport, a carrier. Typing alone sends nothing; only choosing a result does. If you would rather it did not, decline analytics and none of it happens.
What Google does not receive: the running filter text beside the flight list. That lives in the part of the address after the ? and is stripped from everything sent, so a half-finished word is never reported. Google's own “site search” measurement, which would have collected it automatically, is switched off.
Google is a company in the United States and processes this on servers around the world, so allowing it means your visit is recorded outside your own country. Google states that it does not log or store individual IP addresses of visitors from the EU, Switzerland and the UK, using them only to derive a location and then discarding them. For visitors elsewhere, Google receives the IP address.
How long Google keeps it. The detailed, visit-level records are deleted after 14 months — the longest the free tier allows, chosen so this year can be compared with last. The headline totals that survive that (visits per day, popular pages, countries) are aggregate counts with nothing in them about any individual.
We keep no copy of any of it. We see only Google's reports, we have not enabled advertising features, so none of it is used to target ads at you, and we have switched off Google's “site search” measurement so that what you type into the filter box is never collected as a reportable term.
Searching the list filters data your browser has already downloaded, and sends nothing. But if you type a flight number and choose Look up, that flight number is sent to our server and passed on to the aviation data suppliers named below, because that is the only way to answer the question. It is the one place on this site where something you typed reaches another company.
These companies are contacted by our server, never by your browser, so they see our server's address and not yours. We send them aviation codes — an airport, an airline, a flight number, a date — and never anything about you.
| Who | What for |
|---|---|
| AirLabs | The worldwide flight positions the map draws |
| AeroDataBox, reached through RapidAPI | Airport boards and flight records |
| NOAA / aviationweather.gov | Airport weather reports |
| Logostream | Airline logos |
| Wikimedia Foundation | The paragraph shown when you press “About this airport” or “About this airline”. We send the name of the airport or airline and nothing else, and only when you press it |
| Vercel | Hosting, and the storage our observation archive is kept in |
| Cloudflare | Counting visits, on every page. Contacted by your browser, so it sees your IP address. Stores nothing on your device. |
| Maps when the configured Flat view is opened; analytics only with your consent. Also contacted by your browser, so it too sees your IP address. |
Vercel serves every request to this site and therefore sees it, and may keep its own logs of that independently of anything our code does. That is ordinary for any hosted website, and it is the one place where something identifying — your IP address — is necessarily involved. Our own code never reads your IP address, your user agent, your referrer or any cookie; the only request header it looks at is the length of an error report.
We keep a permanent archive of what the feed has observed: flights, routes, airports, aircraft types and aircraft registrations, with counts and dates. None of it is about visitors — there is no visitor record, no session record and no request record anywhere in it.
One part of it deserves naming plainly. Aircraft registrations — tail numbers — are published, on the airline pages and through the site's public archive endpoint, together with the aircraft type and how often it was seen. A tail number can be looked up in public aircraft registers, which in some countries will name an owner. We publish what a widely-used commercial feed reported was flying; we do not attempt to identify anyone, and if you believe a specific registration should not appear here, write to us and we will look at it.
Some pages link out — to Wikipedia, to our map data source, and to travel booking sites. Following a link takes you to a company we do not control, and their own privacy policy applies from that moment. Our links carry no information about you, and no referrer beyond the fact that you came from this site.
FlyGamma is built to carry affiliate links for flights, hotels, airport transfers, parking and lounges — links that may pay us a commission if you book through them. Travelpayouts links for flights and transfers are switched on. They are marked Sponsored and open the partner’s site in a new tab. Hotel links are hidden until a suitable partner is connected. No partner code runs, loads or stores anything before you click.
What travels with a click is a code identifying FlyGamma — the same fixed value for every visitor — plus a fixed SubID naming the placement, such as the travel tab, flight detail or airport page. These links open a general partner search, not a prefilled route. Never anything about you.
FlyGamma is run by one person. Questions about this notice, or about anything on the site, go to support@flygamma.com.
The site is operated from Pakistan. Our hosting provider processes requests on servers in Europe and serves cached copies from locations worldwide.
If what this site does changes, this page changes on the same day, and the date at the top changes with it. It is written from the code rather than about it, which is the only way a page like this stays true.
The short version. No accounts, no sign-in, nothing sold. Two counters: one that stores nothing and counts everybody, and Google's, which needs a cookie and so only runs if you say yes. Your preferences live in your browser and stay there. General search typing stays in the page; an explicit flight or airport timetable lookup sends its code to the flight supplier. Do Not Track switches both off without asking you anything.