Privacy policy
Effective
This policy covers the FlyETA app for iPhone, iPad and Android, and the website at flyeta.app. It is written to be read, not to be survived.
The short version
The FlyETA app records your flight on your phone and leaves it there. The app has no accounts, no analytics, no advertising, no crash reporting and no tracking of any kind. The app uploads nothing you record. Your phone's own backup to your Google or iCloud account can include your flights, if you use one. If you look up a flight number during setup, the app contacts one third-party service. With a connection, the app also asks our own server for recent real flights on your route, sending the two airport codes, and downloads detailed terrain for the route of a flight, a simulation or a replay, sending the names of the map squares it needs. These requests also name the app's version and build and your phone's system version. Use the app without a connection and it contacts nothing.
The website counts visits with Umami, sets no cookies and stores nothing that identifies you.
Store privacy labels
The app's App Store label declares Data Not Collected and no tracking. Its Google Play Data safety section declares one data type as collected: the flight number you type into the optional lookup, listed as in-app search history. It goes to the lookup service named below, not to us, and the app shares no data. No data is linked to you, because none of it is kept: the developer's one server, tower.flyeta.app, receives the two airport codes of a route, the names of the terrain squares it crosses and the version details named below, answers, and keeps no record of them. No server receives your flights, your location or an identifier for your device.
Who is responsible
The controller for the purposes of the GDPR is Mykola (Nick) Bubelich, in Vienna, Austria. Write to support@flyeta.app with any question about this policy or about your data.
What the app processes on your device
All of this is read, used and stored on the phone itself. The app transmits none of it. A file leaves the phone only when you share it yourself, as described under GPS tools below.
- Precise location. Your phone's GNSS receiver gives position, ground speed and a timestamp. This is what draws the map and the track. The app asks for location While Using the App, and never asks for background location. While you record a flight, the phone keeps giving it position with the screen locked or another app open. iOS shows the blue location indicator. Android runs a location service for the recording and shows a FlyETA notification until you stop it.
- Altitude and cabin pressure. GPS altitude from the same receiver, and cabin pressure from the barometer where the phone has one.
- Motion sensors. The accelerometer and gyroscope, used for the turbulence reading and to log pitch and turn rate with the track.
- Flight logs. A JSON file per recorded flight in the app's
Documents/flightsfolder, which the iOS Files app shows under On My iPhone → FlyETA → flights. On Android the app keeps its own copy in private storage and a readable copy in Android/media/app.flyeta/flights, which a file manager can open. You can read, copy and delete these files yourself. - Phone backups. Your phone's own backup can copy the flight logs and settings to your account: iCloud Backup on iPhone and iPad, and Google's Android backup on Android. The backup goes to your account with Apple or Google, under their terms, and we cannot read it. You can turn it off in the phone's settings.
- GPS tools recordings. The recorder in GPS tools saves every raw position fix and pressure reading to a JSON file on the phone. It has a Share button that opens your phone's share sheet; the file goes only where you send it from there, and the app never sends it on its own.
- Settings. A few of the app's own flags, such as whether a hint was already shown, kept in the system preferences store.
- Downloads. The recent flights on a route and the detailed terrain the app downloaded, kept in its own storage so later flights can use them without a connection.
What leaves your phone, and to whom
Only what is listed below. No request includes an account, a device identifier or your location.
- tower.flyeta.app, our own server, receives the two airport codes of your route, such as VIE and JFK, when you set up a flight or a simulation with a connection. It answers with recent real flights between those airports, from adsb.lol data (ODbL 1.0), which the app uses to forecast your path and arrival and to play simulations. If the phone already holds that route, the request also carries the version tag of its copy, so the server can answer that nothing changed.
- tower.flyeta.app also receives the names of the terrain squares your route crosses, such as n36e000, and the version of the map the app was built with, when you start following a flight, start a simulation or open a replay. It answers with detailed terrain for those squares, which the app keeps for later. The download uses Wi-Fi or mobile data as you choose in Settings (Always, Wi-Fi only or Never). It waits under Low Data Mode or Data Saver, and while roaming on Android, never starts on its own in the air, and goes on in the background until it finishes or the connection is gone. It never includes the airports, the flight or your position.
- Only if you look up a flight number: api.adsbdb.com receives the flight number you typed, and answers with the airline's callsign and the two airports. The operator publishes no privacy policy or terms that we could find; the service is open source at github.com/mrjackwills/adsbdb.
Every request names the app in its user agent. To tower.flyeta.app that is the app's version, your phone's system version and the app's build number, such as FlyETA/2.0.0 (iOS 26.5; build 20000; +https://flyeta.app) or FlyETA/2.0.0 (Android 16; build 20000; +https://flyeta.app), so a fault can be traced to a release. api.adsbdb.com gets the app's version only, such as FlyETA/2.0.0 (+https://flyeta.app). Neither includes your phone's model or any identifier.
The server does not write the airport codes or the square names to any log or record. Each request also carries your device's IP address, as every internet request does. We do not control how adsbdb handles its logs. You can avoid all of them: use the app without a connection, for example in airplane mode, and pick your departure and destination airports by hand. The app then sends nothing at all, and records the flight exactly the same way; without recent flights on the route, it forecasts along the shortest route instead, and the globe draws the terrain that comes with the app.
The app never sends a recorded flight anywhere.
After a flight you recorded has landed and the phone is online again, the iPhone and iPad app may ask you once per version to rate it, and Settings in both apps has a Rate FlyETA link. The rating window and the store page belong to the App Store or Google Play: what you rate or write goes to Apple or Google under their terms and can appear as a public review. The app learns nothing about it.
FlyETA 1.x, the version before 2.0.0, works differently in two ways. It does not download terrain. Its flight-number lookup also sends the callsign and the departure airport's coordinates from adsbdb's answer to api.adsb.lol, and the identifiers of up to four aircraft flying the route to globe.adsb.lol, to draw the route. These are the airport's coordinates, not yours. adsb.lol states that it keeps its log files for less than 30 days; its privacy and licence page is at adsb.lol/docs/privacy-license. iPhone and iPad builds up to 1.0.0 (10) send the callsign and coordinates to api.airplanes.live instead, whose privacy policy is at airplanes.live/privacy-policy.
What the website and our server process
The website loads no advertising and sets no cookies. Your browser sends its IP address and user agent with each request, as every browser does; the server uses them to answer and does not keep them.
Visit counts. The website counts its visits with Umami Cloud, run by Umami Software, Inc. in the United States. On each page your browser loads Umami's script and sends Umami the page's address and title, the page that linked to it, your browser's language and your screen size, and with the request your IP address. Umami uses them to count visits and says it stores nothing that identifies you (umami.is/privacy). It sets no cookie and does not follow you to other websites. The script reads one setting from your browser's storage, umami.disabled: set it and the website is not counted in that browser. Umami receives the data under its data processing terms, with the EU Standard Contractual Clauses for the transfer to the United States (umami.is/dpa).
Server logs. The software on our server keeps a short technical log to run the website and the app's server. It holds no IP address, no page or request address and no user agent, with one exception: when one client sends too many flight searches, the log notes its network, such as 203.0.113.0/24, not its address. The log is deleted after 7 days.
Hosting. The website and tower.flyeta.app run on servers of Hetzner Online GmbH in Germany. Apart from the visit counts above, we send no personal data outside the European Union.
Why we may process it
What stays on your phone is processed by your phone, for you; we never receive it. For the little our server does handle - the IP address of a request while it is answered, the airport codes, square names and version details it answers, and the short log above - the legal basis is our legitimate interest under Article 6(1)(f) GDPR: answering the requests you make from the app and the website, and keeping the service working and protected from abuse. The visit counts rest on the same legitimate interest: knowing how many people find the website and which pages they read.
Do Not Track
Neither the app nor the website tracks you across other apps or websites. The website's visit counts do not read a browser's Do Not Track or Global Privacy Control signal; the umami.disabled setting above turns them off.
No accounts, analytics or ads in the app
The app has nothing to sign up for. It has no advertising, no advertising identifier and no profiling. Your data is never sold or shared with anyone, for any purpose, and there is no mechanism by which it could be - it is on your phone.
Children
FlyETA is not directed at children under 16 and we do not knowingly process any data from them. Since the app collects nothing, there is nothing about a child to hold.
How long anything is kept
Flight files and settings stay on your phone until you delete them - by removing a flight in the app, deleting the file in the Files app or a file manager, or deleting the app, which removes all of it. The only other copy is your own phone backup, if you use one, which you manage in your Apple or Google account. Our server's technical log is deleted after 7 days.
Your rights
Under the GDPR you have the right to access, correct, delete, restrict and object to the processing of your personal data, and to receive it in a portable form. You can also lodge a complaint with a supervisory authority: in Austria the Datenschutzbehörde, Barichgasse 40-42, 1030 Vienna (dsb.gv.at), or the authority where you live or work. These rights apply wherever you live.
In practice, most of these you exercise directly and without asking anyone: your data is in your hands. To see it, open the flight files in the Files app or, on Android, a file manager. To delete it, delete a file, or delete the app. For anything else - including a question about server logs - write to support@flyeta.app and we will answer within a month.
Changes to this policy
If the app or the site starts doing something this page does not describe, this page changes first, with a new effective date. A change that would mean collecting data we do not collect today would be announced in the app before it took effect.
