Who is responsible
Kristian Popovic, Brace Pesel 3, 52210 Rovinj, Croatia. Email: privacy@nimbo.fly (data controller).
The short version
- Nimbo works fully without an account. Your flights, notes, ratings, photos and settings stay on your phone.
- There are no ads and no advertising trackers. Anonymous crash reports are on by default and can be switched off; anonymous usage statistics are sent only if you opt in (Settings → Privacy).
- All other online features are off until you turn them on, and you can switch them off and delete the server copy at any time in Settings → Privacy.
- The app is not directed at children. You must be 16 or older to create an account.
What is stored on your phone
Flights, trips, notes, memories and photo copies, seat and flight ratings, booking references, cached flight data and your settings. Your sign-in session is kept in Android's encrypted storage. Nothing of this is sent to us. Android device backup (Google's automatic backup of app data) is switched off for all of this. The only exception is one small file with the Pro trial start date and a "purchased" flag, which Android may include in your own Google backup so that reinstalling does not restart the free trial; it contains no flights or personal details. Use Settings → Export / backup to keep a copy of your data. "Wipe this phone" in Settings → Privacy deletes it.
Nimbo Pro (one-time purchase)
The basic app is free forever. Optional Pro extras come with a 7-day free trial and can then be unlocked with a one-time in-app purchase. Payment is handled entirely by Google Play under Google's own privacy policy; the app never sees your card or payment details, and we receive no personal data from the purchase. To remember the trial the app stores only its start date and a "purchased" flag on your phone (not sent anywhere). On start the app asks Google Play which purchases this Google account owns ("restore"). No purchase analytics are added. Ending the trial never deletes or locks your data: your flights, backups and all exports (CSV, JSON, GDPR export) stay free. Live tracking of upcoming flights (background status checks, gate/delay alerts) is a Pro feature; without Pro the app makes no background live lookups, so no flight numbers are sent to the live-data service for that. If you use the optional friends feature and have bought Pro, your profile stores a "Pro" flag so friends can see a PRO badge next to your name. Only accepted friends can see it; switch off "Show Pro badge to friends" in Settings and the flag is set to false. Trial users are never shown as Pro. Your colour theme choice is stored only on your phone.
Optional online features
Account, friends and sharing (Supabase). If you create an account we store your email address and a hashed password, your handle, display name and emoji avatar, your friend connections and privacy choices, the statistics you publish to friends (totals, routes, stickers and – unless you switch it off – your flight log without notes, seat, booking reference, ratings or photos), emoji reactions you give to or get from friends on recent flights (visible only to the two of you; deleted when you unfriend or delete your account), and flights you send to a friend (route, date, airline, flight number, aircraft, times – never notes, seat, booking reference, ratings or photos). Legal basis: your consent at sign-up and providing the service you asked for (GDPR Art. 6(1)(a) and (b)). Meet-up alerts (off by default) are computed on your phone from data friends already share; nothing extra is sent.
Trip links (Supabase, only when you tap Share trip while signed in). We store, per flight of the trip: flight number, airline, departure and arrival airport, scheduled times and date, plus an optional name you choose to show (e.g. "Kristian"). Anyone who has the link can see this and the live status (times, delays, gate, terminal) on a web page at nimbo.fly until the link expires 12 hours after your last flight lands (we use the latest known arrival time; if unknown, the scheduled one). You can turn a link off at any time in Settings; it stops working immediately. Expired and turned off links are deleted automatically. Notes, seat, booking reference, ratings and photos are never included. To show live status our server asks AeroDataBox (via RapidAPI) for the flight number and date only – no data about you or the viewer. The web page uses no cookies, trackers, analytics or third-party fonts; GitHub (which hosts the page) and Supabase see the viewer's IP address in their server logs, and we keep a shortened hash of it for one hour to prevent abuse.
Cloud backup (Supabase, only when you turn it on or tap "Back up now"). A copy of your flights including notes, memory text, seat, booking reference and ratings, readable only by your account. Photos are not uploaded.
Anonymous statistics (Supabase, only after you agree in a dialog). Per flight: origin and destination airport, month, distance, aircraft type and airline – not linked to your account, filed under a random code kept on your phone. Switching it off deletes what you contributed. Only flights marked Verified (matched against flight data) or Evidence (boarding pass or booking import) are sent, together with that level, which the server checks and does not store. The app also leaves out flights that fail plausibility checks (overlapping, impossible duration, not flown yet, same airport twice, more than 8 a day); those checks run on your phone and nothing about them is uploaded.
Flight verification. To mark a flight Verified, its flight number and date are looked up once through our flight-data service (the same lookup used for live status; the provider sees the flight number and date, not who you are). The result is stored only on your phone.
Supabase Inc. hosts this data as our processor under its Data Processing Addendum. Region of the server: AWS eu-west-2 (London, United Kingdom); the UK is covered by an EU adequacy decision. Supabase may use sub-processors outside the EU under Standard Contractual Clauses.
Live flight data (via the app's server). When you look up live times or gates, the app sends the flight number and date (or an airport and a short time window) to our Supabase Edge Function. That server holds the AeroDataBox API key and asks AeroDataBox (via RapidAPI) on your behalf. You do not enter your own API key. AeroDataBox / RapidAPI may be located in the USA and act under their own privacy policies. Your IP address may appear in our server logs and theirs for security and rate limiting.
Aircraft photos (can be switched off in Settings). The aircraft type or registration is sent to Planespotters.net, Wikipedia and Wikimedia Commons to find a photo. These services see your IP address; no account data or personal details are sent. The app identifies itself to them with the developer's contact address, not yours.
Sharper satellite detail when zoomed in (off by default; Settings → Map imagery). The satellite map is bundled with the app and works offline without sending anything. Only if you switch this on, zooming in close downloads extra map tiles of the area you are looking at from NASA GIBS (Global Imagery Browse Services, gibs.earthdata.nasa.gov), run on US government servers in the USA. This is a transfer of your IP address to a third party outside the EU/EEA, which you consent to by switching the setting on (GDPR Art. 49(1)(a)); US government servers are not covered by an EU adequacy decision for this purpose. NASA then sees your IP address and which map tiles (area and zoom level) are requested, plus a generic app User-Agent. Nothing else is sent: no account, flights or location. Tiles are cached on your phone (at most 200 MB) and can be deleted with "Clear map cache"; switching the setting off stops all requests. Imagery (bundled and downloaded): NASA Earth Observatory – Blue Marble Next Generation (Reto Stöckli), July 2004, public domain.
Crash reports (on by default, can be switched off)
If the app crashes or hits an unexpected error, it sends a technical report to Sentry (Functional Software Inc.), which stores it in its EU region (Frankfurt, Germany) as our processor under its Data Processing Addendum. A report contains the error message and code location (stack trace), the app version, the phone model, Android version, screen size, language setting and a short list of preceding app events (for example "screen opened" or "network request failed with status 500").
Before anything is sent, the app removes flight numbers, airport codes, dates, email addresses, web addresses with their paths and parameters, share-link codes, sign-in tokens and file names. Reports contain no account, no user or device identifier, no screenshots and no IP address (the app does not send it and Sentry is set not to store it). Network request bodies are never included.
Legal basis: our legitimate interest in finding and fixing bugs (GDPR Art. 6(1)(f)). You can object at any time: switch off Settings → Privacy → Send crash reports and nothing more is sent from that moment. Sentry keeps reports for up to 90 days.
Usage statistics (only if you opt in)
Off by default. If you switch on Share anonymous usage statistics (on the first-start screen, in a one-time card, or in Settings → Privacy), the app counts on your phone, per day, which screens and main features are used (for example "Stats opened", "Poster exported") and roughly how long screens stay open, in four ranges only (under 10 seconds, under a minute, under 5 minutes, longer), never the exact time. Once a day it sends the counts of past days to our own server (Supabase), with the app version, the platform and the language and country from your phone's language setting (not your location).
There is no account, user or device identifier, no flights, airports, flight numbers, text you type or exact times. The server only accepts a fixed list of event names and adds the counts to daily totals for all users, so a single person's use cannot be picked out. To prevent abuse it uses a hash of your IP address with a key that changes every day; the IP address itself is not stored and the hash is deleted within a day.
Legal basis: your consent (GDPR Art. 6(1)(a) and, for reading the counts on your device, Art. 5(3) ePrivacy Directive). Switching it off stops counting and deletes the counts not yet sent; totals already added cannot be linked to you and so cannot be removed individually.
Boarding-pass scanner (Google ML Kit)
Reading text from boarding-pass photos and tickets happens on your phone with Google's ML Kit. Your images and the recognised text are not sent to Google or to us. ML Kit may send Google technical diagnostics (for example performance, errors and an installation identifier used for these diagnostics) under Google's own terms and privacy policy.
How long we keep data
- Account data: until you delete your account; accounts without a sign-in for 2 years are deleted automatically.
- Shared flights: 90 days.
- Trip links: until 12 hours after the trip's last arrival, or until you turn them off (then deleted within a day); live-status cache: 3 days.
- Cloud backup: until you delete it or your account; markers of deleted flights are removed after 180 days.
- Anonymous statistics: until you withdraw them.
- Crash reports: up to 90 days at Sentry.
- Usage statistics: daily totals for all users for up to 26 months; IP-hashes for rate limiting deleted within a day.
Your rights
You can access and export (Settings → Privacy → Export all my data), correct, and delete your data (Delete my cloud backup / Delete my account and all server data), withdraw consent at any time (this does not affect processing before withdrawal), object, restrict processing, and complain to a data protection authority in your EU country.
Changes
We will update this page and the date above when the app's data handling changes.
Terms of Service
Use of Nimbo is also governed by the Terms of Service, under Settings → About and at https://nimbo.fly/terms/.