Privacy policy

The extension

FlightWifi collects no data of any kind.

• No personal information, no account, no sign-up
• No analytics, no telemetry, no crash reporting
• No cookies. The only things it stores are your per-site on/off switches and your light or dark theme choice, on this device
• No browsing history: it only runs on the flight search pages listed in its manifest

All processing happens locally in your browser. The extension reads the flight information in your own tab, compares it against a wifi registry bundled inside the package, and draws a verdict chip. It never contacts our servers while you browse; it has no server. On Skyscanner only, to name the plane on each flight in the results list, it asks Skyscanner for that flight’s details, the same request Skyscanner’s own page makes when you open a flight. That request goes only to Skyscanner and carries nothing beyond the search you are already looking at.

There is one moment it reaches our site, and it is the moment it stops running: if you uninstall the extension, Chrome opens a page here that asks why, carrying only the version number you had. That is a plain page load. Answering is optional, and nothing in it is tied to you or to anything you searched for.

Permissions

The extension asks Chrome for three permissions, plus one optional site you can allow later. None of them reads, stores or sends anything about you, and none of them shows an install warning.

• The storage permission keeps your per-site on/off switches for Google Flights, Skyscanner and Rift on this device. The popup also remembers your light or dark theme choice on this device. Nothing else is stored.
• The activeTab and scripting permissions let the toolbar popup restart the extension on a flight search tab that was already open when the extension last updated, so you do not have to reload the page. On Rift they are also how the verdicts appear when you click the icon there. They apply only to the tab you clicked the icon on, only at that moment, and never grant standing access to any site.
• Rift (rift.co) is optional. The extension runs there by itself only if you allow it from the popup, and that access covers rift.co pages and nothing else. You can take it back at any time in Chrome’s extension settings.

Beyond that, its only access is the content scripts that run on the flight search pages listed in its manifest.

This website

The pages are static files served from this domain. The one exception to “nothing runs here” is page-view counting, added on 19 August 2026 using Vercel Web Analytics.

It is cookieless. Specifically, it:

• sets no cookies and stores nothing on your device
• does not follow you across other sites, and builds no profile of you
• collects no personal information and no account is involved

What it does record is the page you viewed, the site that referred you, and coarse device and country information, so we can see which pages people find useful. Nothing about it is shared with advertisers, because there are none.

The uninstall page adds one counter to that same tool: which of the listed reasons was chosen, and the extension version it was chosen from. It is a tally and nothing more, with no way to trace a choice back to a person.

That form also has an optional box for writing what went wrong. Only what you type there is sent, only when you press Submit, and only alongside the reason and the version. Leave it empty and the tally is all that is recorded. A written note is delivered into a private Google Sheet we own, so Google holds it as our storage provider and nothing about you is attached to it beyond what you typed. If that delivery is not set up or fails, the note opens as a draft in your own mail app instead, in which case it reaches us only once you send it and then carries your address the way any email does.

Checking a flight number

The checker on the homepage answers airline and aircraft questions entirely in your browser, from a copy of the registry it downloads once. A flight number is different, because we do not hold airline schedules. If you type one, the flight number and the date you pick are sent to our server, which asks AeroDataBox, a flight-schedule provider, which aircraft is planned for that flight. That is the whole request: no cookies, no account, no identifier of yours travels with it. Our server keeps the answer for up to a day, keyed only by the flight number and date, so the same lookup is not repeated. AeroDataBox sees the request as coming from our server and handles it under its own privacy policy.

Changes

If a future version of either ever changes any of the above, this policy and the Chrome Web Store disclosures will be updated before that version ships.

Contact

Questions: open an issue at github.com/Priyansh-Jain/flightWifi.