Last updated 27 August 2026.
Flywhen has no user account or server-side user profile. Your saved locations, aircraft, task profiles, limits, units and forecast cache are stored in your browser. Limited website analytics are stored on infrastructure we control, and external providers receive the data needed to return forecasts, place searches and other app data as described below.
Your complete saved settings live in your browser's local storage. They are not uploaded to a Flywhen account:
Clearing your browser data removes all of it. There is a Clear saved forecasts button in Setup that removes the cached forecast on its own.
Some limited choices, such as an aircraft ID or task ID, may also appear in the analytics events listed below. Coordinates, saved place names and numeric flight limits are not included in Flywhen's custom analytics events.
This is the part worth being direct about. To tell you the weather at a place, that place has to be sent to a weather service. There is no way around it.
When you look up a forecast, your coordinates are sent from your browser directly to Open-Meteo. They do not pass through a Flywhen application server first. When you search for a place by name, that search text goes directly to a geocoding service.
Requests are made by your browser, so those services see your IP address the same way any site you visit does. Their handling of it is governed by their own policies, linked below.
Flywhen uses Umami, self-hosted on infrastructure we control. It does not use cookies or track a visitor across unrelated websites. Its automatic page view record can include the page path and title, referrer, browser language, screen size, browser, operating system, device type and approximate country. Flywhen configures the tracker to exclude URL search parameters, because shared links can contain coordinates and a place name.
Umami documents that an anonymous session hash is generated from the IP address, user agent and website ID. The analytics service therefore processes standard connection data even though Flywhen does not create named user profiles.
Eleven custom event names are used, and each records only the fields shown below:
| Event | What it records |
|---|---|
| location_set | Only how a location was chosen: search, current position, a saved place, or a shared link. Never the coordinates. Never the place name. |
| aircraft_set | Which airframe was picked, so we know whose specifications to verify next. |
| mission_set | Which task profile was selected. |
| tab_view | Which main app tab was viewed. |
| hours_view_set | Whether the Hours screen was switched to charts or the table. |
| detail_open | Whether an hourly detail panel was opened from Plan or Hours. Not the selected time or weather values. |
| picker_open | Whether the location or aircraft picker was opened. |
| saved_place_changed | Whether a saved place was added or removed. Not its name, coordinates, or the number of saved places. |
| forecast_result | Whether a forecast loaded from the network, used a stale cached forecast, or failed. Not the location, forecast values, or error text. |
| share | That a link was created. Not what was in it. |
| content_cta | Which Flywhen page and link placement sent someone into the app, using fixed page, placement, and destination labels. |
Flywhen's analytics does not receive forecast coordinates or saved place names. The tracking module accepts only the fields listed above, and the analytics script excludes URL search parameters. Forecast and place-search providers still receive coordinates or search text as explained in the preceding section.
Forecast data. Receives the coordinates you are viewing. Terms and privacy
Turning place names into coordinates and back. Receive your search text. Nominatim policy
Geomagnetic activity, which affects GPS accuracy. Receives no location.
Satellite orbital elements, used to predict satellite visibility. Receive no location: the visibility calculation happens on your device.
Hosts the files. Serves the page to your browser. Privacy policy
A link you create contains a place and an optional name, rounded to about eleven metres. It contains nothing else: not your limits, not your aircraft, not your settings. Someone opening your link sees that place scored against their own limits, not yours, which is a safety decision rather than a privacy one. It means a link can never quietly put someone in the air on a stranger's risk tolerance.
Flywhen is a tool for operating aircraft and is not directed at children.
Privacy rights depend on where you live and may include access, correction, deletion or objection rights. Flywhen has no account or named customer profile. Your local settings can be deleted by clearing browser data. For questions or requests concerning analytics records, contact the address below. Because the analytics are not tied to a name or account, we may need information from you to determine whether a record can be associated with your request.
If what is collected or shared changes, this page will be updated and the date at the top will move. Material changes to account, location or analytics handling will be stated plainly.
Questions about this page: appsupport@deepdivesites.dev