Privacy Policy
Last updated: 25 October 2026
Almighty shows live public data on a globe. It runs as an app on iPhone and iPad (and Mac), as an app on Android phones and tablets, and as a web app in your browser. It works without an account. To keep it free, it shows ads from Google: a small banner in a few places in the apps (Google AdMob), now and then a full-screen ad at a pause, and a slim strip along the bottom of the web app (Google AdSense). The iPhone and iPad app tracks you across other apps and websites only if you allow it when your iPhone or iPad asks. This page explains the little information Almighty handles, and why. Where something differs between the iPhone/iPad app, the Android app and the web app, we say so.
Who we are
Almighty: World Tracker ("Almighty", "we", "us") is made by Bonny James, an individual developer in the United Kingdom. We are the controller of the personal data described here. Contact: bonnyjames0@gmail.com.
In short
- No account is needed to use Almighty, and everything is free. If you choose to sign in (with Sign in with Apple, Sign in with Google or an email code, where the app offers them), your flight log, tracked flights, saved views and Sky lists are kept with your account, so they're on every device you sign in on. Contributing data needs an account.
- Your location and camera picture are used on your device. Your approximate location is sent to our server to find aircraft near you, and is not stored.
- If you turn on earthquake alerts or the morning briefing in the iPhone, iPad or Android app, we keep a rough location (to about 11 km) so we can send them, until you turn them off.
- Your voice is turned into text by your device's speech service (Apple's on iPhone and iPad, Android's on Android, your browser's on the web). We never receive the audio.
- Questions the app can't answer itself go to a third-party AI service, only after you agree.
- The apps show a banner ad from Google AdMob on a few screens and, now and then, a full-screen ad at a pause; the web app shows a slim ad strip from Google AdSense. Google personalises ads only with your consent where the law asks for it, and on iPhone and iPad uses your device's advertising identifier only if you allow tracking.
- No selling of data and no analytics.
- If you track a flight, our server keeps the flight (and, if you allow notifications, your device's notification token) so it can notify you and keep it on your lock screen, until a week after the flight.
- On-board chat goes from phone to phone over Bluetooth, end-to-end encrypted. Your chats and their keys stay on your phone; we can't read them.
- You can download or delete your app ID, and everything linked to it, from Settings in the app.
What we handle, and why
An app ID, only if you use a feature that needs one
Browsing Almighty needs no ID at all. The first time you ask the AI a question, report a news story, track a flight, send feedback or turn on alerts near you, our backend gives the app a random ID (sharing a tracked flight with Share my journey uses the same ID). It is not linked to your name, and we don't use it to track you. We use it to keep the service fair and working: to count how many AI questions have been asked each day (there is a daily limit), to attach your reports and feedback, and to keep the flights you track and your alert settings. After that, the app's requests to our server include the ID; our server doesn't log it.
So that only genuine copies of the app can use the AI, track flights and turn on alerts, the app proves it is genuine:
- iPhone and iPad: your device creates a security key with Apple's App Attest service, and we store the public part of that key with your app ID. It can't identify your device or you, and it's deleted with your app ID. Reports and feedback signed with it are marked as coming from a genuine copy.
- Android: the app asks Google Play's Play Integrity service for a one-off token for that request. Google Play makes it from information about the app and your device (for example the app's name, version and signing certificate, whether Google Play installed it, and a device check made by Google Play services), under the Play Integrity API terms. Our backend sends the token to Google to read the verdict ("this app, a genuine device") and keeps nothing from it.
- Web app: a browser can't prove this, so the AI helper isn't available on the web, and tracked flights are followed only while the page is open.
Legal basis: our legitimate interest in running the service securely and fairly.
Your location
Almighty asks for your location only when you use a feature that needs it (for example "Use my location" in the sky view, "nearest plane", or centring the map on your area), and only while you're using it: never in the background. Approximate location is enough. On iPhone, iPad and Android the system asks your permission; in the web app, your browser does. The sky above you is worked out on your device. To show aircraft near you, the app sends a position rounded to about 1 km to our server, which uses it to answer that request and does not store it. Legal basis: providing the feature you asked for.
When the app opens, the globe turns to roughly where you are: from your device's location if you have already allowed it (it never asks just for this), otherwise from your time zone. In the web app only, without a location, it asks our server instead, which answers with the approximate place (a city, rounded to about 11 km) that our hosting provider Cloudflare works out from your connection's IP address. Nothing of it is stored. Legal basis: legitimate interest (starting the globe over your part of the world).
Earthquake alerts and the morning briefing
In the iPhone, iPad and Android apps you can turn on "Strong earthquakes near me" and a morning briefing notification in Settings. Both are off unless you turn them on. To send them, we store with your app ID: your location rounded to a tenth of a degree (about 11 km), the country there, your time zone and the time you chose for the briefing, the smallest earthquake and the distance you chose, whether you prefer miles, your device's notification token, and which alerts have already been sent (so none is sent twice). The rounding happens on your device before anything is sent, and nothing finer can be stored. The app updates the stored location when it opens and you've moved more than about 20 km, and otherwise checks in about once a week. Our server compares new earthquakes with it and sends the notifications through Apple Push Notification service (iPhone and iPad) or Firebase Cloud Messaging (Android), as for tracked flights below.
The briefing itself is a short AI-written summary of public data (earthquakes, weather warnings, news, fires and storms) for a whole region, a country or a 5° square of a big one, shared by everyone there. Nothing about you goes to the AI service to write it. If notifications are off, or in the web app (which has no notifications), the briefing is shown when you open the app in the morning and the app only asks our server for your region's briefing; no location is kept.
The stored location and settings are deleted when you turn both alerts off, when Apple or Google tell us the notification token no longer works (for example the app was removed), 60 days after the app last checked in, or when you delete your app ID. Legal basis: your consent (you turn the alerts on, and can turn them off at any time).
The area of the map you're looking at, and searches
To load live data, the app tells our server which part of the world is on screen, and sends what you type into search. These are used to answer the request straight away. Our server's logs record only which kind of request was made and when, not the map area, search text or your IP address. Legal basis: legitimate interest (delivering the data you look at).
Camera
If you turn on the camera in the sky view, the picture is shown on your screen behind the stars. It never leaves your device and is never recorded.
Motion sensors
The sky view follows how you hold your phone, and when you're on a flight with no connection the app can tell when it took off from your phone's motion (the push of the take-off run), only from boarding until an hour after the planned departure. Both are worked out on your device; motion readings never leave it. On iPhone and iPad (and in Safari) you're asked first.
Voice and typed questions
When you tap or hold the microphone button, your device's speech service turns your words into text. Almighty never receives the audio, only the text.
- iPhone and iPad: Apple's speech recognition. Depending on your device, Apple may process the audio on its servers, under Apple's Privacy Policy.
- Android: Android's own speech recogniser, which on most phones is Google's. It may send the audio to its maker's servers to recognise it, under that company's privacy policy (for Google, the Google Privacy Policy).
- Web app: your browser's speech recognition, where it has one. Many browsers send the audio to their maker's servers (Google for Chrome, Apple for Safari), under the browser maker's privacy policy.
Most requests ("take me to Paris", "show earthquakes") are then handled in the app itself.
In the iPhone, iPad and Android apps, a request the app can't handle can be sent to an AI service. The first time, the app asks for your permission. You can withdraw it at any time with the AI answers switch in Settings; the app then asks again before sending anything. If you agree, the text of your question and a description of what's on screen (the map area and the layers shown) go to our server, which passes them to OpenRouter (OpenRouter, Inc., a US company), which passes them to the AI model, Qwen3.8 Flash, run by Alibaba Cloud. OpenRouter can send each question to either of Alibaba Cloud's two services for this model: one in the United States and one based in Singapore, which may use Alibaba's data centres in Singapore or China. So your question may be processed in the USA, Singapore or China. We ask OpenRouter to use only AI providers that don't collect what they're sent for their own use or train on it. That doesn't mean nothing is kept: OpenRouter says it doesn't keep the text of a request once it's answered unless its customer turns on logging (we keep that off), and Alibaba Cloud says it keeps the questions and answers sent to its models for up to 30 days. Please don't include personal details in questions. We don't store the text of your questions; we keep a count and size of each request (for the daily limit and to manage costs). (What OpenRouter and Alibaba Cloud say about this was checked on 24 October 2026.) Legal basis: your consent.
News reports
If you report a news story as misplaced, misleading or offensive, we store the story, its link, the reason and your app ID so we can review it. On iPhone and iPad we also store which App Attest key signed the report (above): a story is hidden automatically once several different genuine copies of the app have reported it. Reports from Android and the web app are kept for review in the same way, but don't count towards hiding a story. Legal basis: legitimate interest (keeping content accurate and appropriate).
Saved flights and settings
Flights you save, recent searches and your settings are stored on your device (in the web app, in your browser's storage for this site). To show a saved flight's status, the app sends the aircraft's identifier to our server, which does not store it against you. Saving a flight with the star also tracks it (below).
Map files you add
GeoJSON, KML, KMZ and GPX files you add to My files are read and kept on your device only (in the web app, in your browser's storage for this site) until you remove them, and are never uploaded to us or anyone else.
Tracked flights and notifications
When you track a flight in the iPhone, iPad or Android app (the star on a flight, or "Track this flight" in search), we store with your app ID: the flight number and the call signs it flies under, the day, its airports and their time zones (worked out on your device, so times can be given in local time), the aircraft once our server has matched it, whose flight it is (yours, or someone else's under the name you give it, such as "Mum"), whether you want its notifications and its lock-screen view, which notifications have been sent, and whether you prefer a 12- or 24-hour clock and feet or metres. If you allow notifications, we also store the notification token your device's push service gives Almighty:
- iPhone and iPad: a token from Apple Push Notification service (APNs). With the flight on your lock screen (a Live Activity), also the token Apple gives that Live Activity and, on iOS 17.2 and later, the token that lets our server start it before departure while the app is closed.
- Android: a registration token from Google's Firebase Cloud Messaging (FCM). The app doesn't ask for one until you allow notifications, and Firebase's analytics are switched off.
Our server follows the flight using public flight-tracking data and sends the notifications (leaving the gate, take-off, cruising, about 10 minutes before landing, landing, diversions and emergencies) through Apple or Google, which receive the token and the notification's text to deliver it. The lock-screen view (a Live Activity on iPhone and iPad, an ongoing notification on Android) is kept up to date the same way, with the flight's stage, times, gate and progress. The path the flight took (public flight data, filed under the tracked flight's random ID) is kept for a week so you can see and replay your journey. We don't use the token for anything else: not to identify or track you, and not for advertising. You can turn notifications off in your device's settings (Settings on iPhone and iPad; App info or the notification settings on Android), stop tracking a flight in the app (its record and token are deleted), or delete your app ID and everything linked to it.
The web app has no notifications: a flight you track there is followed in your browser only while the page is open, and nothing about it is stored on our server. Legal basis: providing the feature you asked for (performance of a contract).
Your flight log (the flights you've been on, and friends' and family's under the names you gave them) and the My flights home-screen widgets on iPhone and iPad are kept on your device. If you sign in, the flight log is also kept with your account (below).
Share my journey
If you share a tracked flight, our server makes a link that carries, signed so it can't be changed: the flight (number, call signs, day, airports and the aircraft once known), the name you chose to show (kept on your device for next time), a random ID, a scrambled form of your app ID (so only you can stop the link; your app ID itself isn't in it) and when it expires (three days after the flight's day, or a day after it lands). We don't store the link: only, if you stop it, its random ID until it would have expired. Anyone you give the link to can see the flight and the name, and apps that show link previews fetch a page saying, for example, "Sam is flying FUE → MAN". Opening it adds the flight to their own My flights. Legal basis: providing the feature you asked for.
On-board chat
In the iPhone, iPad and Android apps, two people you pair (with an invite link or a 6-character code) can message each other without the internet. Messages go phone to phone over Bluetooth, and between iPhones also over peer-to-peer Wi-Fi. Each pairing makes new keys on both phones and every message is end-to-end encrypted. Your chats, the names in them and the keys are stored on your device only, and "Forget this person" deletes them. The phones advertise only random IDs that change every 10 minutes, never your name.
- Permissions: iPhone and iPad ask for Bluetooth, and for the local network for Wi-Fi between iPhones. Android asks for Nearby devices; Android 11 and earlier also ask for location, which those versions need before any Bluetooth scan: Almighty doesn't use it to find your location.
- Other passengers' phones: with "Help pass on others' messages" on (by default whenever on-board chat is on; you can choose only while you're on a flight, or never), your phone may carry other people's sealed messages, and theirs yours. Nobody passing a message on can read it or see who it's from.
- Via the internet: where we've switched it on, when both phones are online but out of range, sealed messages wait on our server (Cloudflare) for up to 24 hours or until the other phone fetches them, in a mailbox only the pair can name. We can't read them, and they carry no names or app ID.
- Invites: an invite link holds the pairing secret, your chosen name and the flight after the "#", the part browsers don't send to any server, so our website never receives it; whoever you send it to (and the app you send it with) can see it. If someone without the app taps Google Play on the invite page, the invite goes through Google Play's install referrer to the app they install, so Google sees it. On iPhone and iPad, the App Store button copies the invite to the clipboard, and the newly installed app reads the clipboard only when they tap Paste invite.
- A message that arrives while the app is in the background shows as a notification made on your device, only if you already allow notifications; no push service is used.
The web app can't use Bluetooth, so on-board chat isn't available there. Legal basis: providing the feature you asked for.
3D Google Maps
Google's photorealistic 3D cities are shared out a few a day. Before loading them (when you choose 3D Google Maps as the Earth map, or in the cockpit and 3D follow views), the app asks our server whether there's room today. It sends a random ID made when the app was installed (in the web app, when you first opened it in that browser), which isn't linked to you or your app ID. The server counts against it until midnight US Pacific time, to allow 3 a day, and then deletes it. The 3D imagery then loads directly from Google, which receives your IP address and the area you're looking at, under Google's Privacy Policy. Legal basis: legitimate interest (keeping a paid service within its budget).
Content loaded from other services
Some pictures and map imagery load directly from the organisations that publish them, including NASA (satellite imagery, cloud and rain maps, planet maps, space pictures and videos), Wikimedia Commons and Wikipedia (aircraft and other photos), the Lunar and Planetary Institute and the Apollo Lunar Surface Journal (Apollo photos of the Moon), the public road, volcano and weather camera operators whose cameras are shown (for example Transport for London, US state transport departments, Sweden's Trafikverket and the US Geological Survey: camera pictures and video clips), news publishers (the preview picture of each story in the news list), and YouTube, when you play a rocket launch webcast, the space station's video or a live stream, and for a live stream's preview picture (in YouTube's privacy-enhanced mode where YouTube offers it; the Google Privacy Policy applies). Almighty uses YouTube API Services; our server asks YouTube which streams are live, which sends nothing about you. Like any website, these services receive your IP address when your device requests the file.
To tell you when an update is available, the iPhone and iPad app asks Apple's App Store for the latest version number; this sends the app's identifier and your country, not anything about you. The Android app asks Google Play (its in-app updates service) whether a newer version is available for your device; Google Play uses information about your device and the installed app version for this, under the Google Privacy Policy. The web app simply loads the newest version itself.
News articles and other links open at the publisher's own website, whose privacy policy then applies: in Safari inside the app on iPhone and iPad, in a Chrome Custom Tab (your default browser's in-app view) on Android, and in a new tab in the web app. We can't see what you do there.
Advertising
Everything in Almighty is free, and ads pay for it. No ad unlocks anything, and there is nothing to buy. The ads are chosen and shown by Google; we never see who you are or what you do on other apps and websites. Active feeders (someone signed in whose ADS-B or AIS receiver sent data in the last 7 days) see no ads at all, and for them the ad code isn't started or loaded.
In the iPhone, iPad and Android apps (Google AdMob)
- Where: a single banner along the bottom of the screen on a few screens (an airport's departures board, My flights and your flight log, search results, and an aircraft's card), and now and then a full-screen ad at a natural pause, after you close something. Never when the app opens, while you follow a flight (including the cockpit and route views), in on-board chat, while you sign in or while you contribute data; at most one full-screen ad every 10 minutes and three a day.
- Consent: the first time an ad is due, if you're in the UK, the EEA, Switzerland or another place whose law asks for it, Google's consent form lets you choose whether Google may use your data for personalised ads. You can change your choice at any time in Settings → Help & legal → Privacy choices (ads).
- Tracking (iPhone and iPad): then your iPhone or iPad asks whether Almighty may track you (Apple's App Tracking Transparency). Only if you allow it does Google receive your device's advertising identifier (IDFA) to personalise ads and measure them. If you don't, the ads are non-personalised. You see the same number of ads either way.
- Advertising ID (Android): Google's ads SDK reads your device's advertising ID, which you can reset or delete in your phone's settings (Settings → Privacy → Ads, or Google → Ads). Where the law asks, it's used for personalised ads only with your consent.
- What Google receives when it shows an ad, under the Google Privacy Policy and how Google uses information from sites or apps that use its services: your IP address (and the approximate location Google works out from it), information about your device and the app (model, system version, language, app version), the ad requests and whether you saw or tapped an ad, and the advertising identifier (on iPhone and iPad only if you allowed tracking). Google may use it to show, limit, measure and improve ads and to prevent fraud.
In the web app (Google AdSense)
- Where: one slim ad strip along the bottom of the web app (web.almighty.live), marked "Ad". It's never shown over Contribute, sign-in or on-board chat, and the app's buttons move up so it never covers them. This website (almighty.live) has no ads.
- Consent: in the UK, the EEA and Switzerland, Google's consent message (a certified consent management platform) asks before any cookies or identifiers are used for ads; if you don't agree, Google shows non-personalised ads, using cookies only for frequency capping, fraud prevention and measurement where the law allows. In US states with privacy laws, Google's message offers "Do not sell or share my personal information". Change your choice at any time with Ad choices on the ad strip, or Settings → Help & legal → Privacy choices (ads).
- Cookies: Google sets advertising cookies and similar storage on the web app's address (see the Cookie Policy).
- What Google receives: your IP address, your browser and device, the page address, its cookies (if you allowed them), and whether you saw or clicked an ad, under the Google Privacy Policy. You can also manage Google's ad personalisation at My Ad Center.
Almighty doesn't send Google your location, searches, flights or anything else you do in the app, and ads are limited to content suitable for teenagers.
Legal basis: your consent for personalised ads and for using your device's storage, cookies and identifiers where the law requires it; otherwise our legitimate interest in funding a free app with non-personalised ads.
Feedback and emails to us
If you use Send feedback in Settings, we store your message, the reply address if you give one, the app version, and your system and device model as the form shows them before you send (for example "iOS 26.0.1, iPhone", "Android 16, Google Pixel 8" or "web, browser"), with your app ID. Each message is also emailed to us. If you email us instead, we keep your message and email address. We use these to reply and to keep a record of the conversation. Legal basis: legitimate interest (supporting you).
If you sign in (optional)
You never need an account: every feature works as a guest, and everything in Almighty is free. If you choose to sign in, in Settings → Account (iPhone and iPad, Android or the web app), you can use whichever of these the app offers there:
- Sign in with Apple: Apple gives us a user identifier for Almighty and your email address (or, if you choose Hide My Email, a private relay address that forwards to you), and your name the first time if you choose to share it. So that we can revoke Almighty's access with Apple when you delete your account (as Apple requires), we keep a token Apple gives us for that.
- Sign in with Google: Google gives us a user identifier for Almighty, your email address, your name and a link to your profile picture. We don't use the picture.
- An email code: we email a 6-digit code to the address you type, and typing it in signs you in. The address is all we get.
We keep with your account: its ID, your email address, your name if a service gave it, which ways you sign in, and when you last signed in (with the IP address, in our account service's security logs). And, so they follow you to every device you sign in on: your flight log, the flights you track, your saved views, and the sky view's observing list and observation log (with any photos you add to it). If you were using Almighty as a guest on that device, what you saved there becomes part of your account; if the account already had its own, the app asks first. Signing out takes your flight log, saved views and Sky lists off that device (they stay in your account); flights you're tracking there stay until they're over.
We use your email address only to run your account: sign-in codes, and messages about your account if we ever need to send one. No marketing, and it's never shown to anyone. You can see everything with Download my data, and delete the account and everything in it with Delete account, both in Settings → Account. Legal basis: providing the account you asked for (performance of a contract).
If you contribute data (Almighty Contribute)
Contributing your own receivers, sensors, live streams, reports or photos is optional. It needs a signed-in account, made in the app (iPhone and iPad, Android or the web app) with Sign in with Apple or a code sent to your email; you can't contribute as a guest, and you must be 16 or older. The Almighty Contributor Terms apply.
We keep: your account ID and sign-in email; your display name; the version of the contributor terms you accepted, and when; your stations (their kind, name, exact location and public location, the hash of each station key, when each was last seen, and the data points they send); your submissions (streams, reports and photos); the reports you make and the contributors you block; and a log of moderation actions, each with its reason.
- A station's exact location is never shown. The public sees it blurred to about 1 km.
- Your display name is shown publicly next to your contributions. Your email address never is.
- Reports are placed where you choose, rounded on your phone to about 1 km (or 10 km, if you pick that) before they're sent: the exact place never reaches us. Photos are redrawn on your phone and again on our server with their metadata removed (location, camera details, the time). Each photo is checked automatically for illegal or harmful content by an AI model, Google's Gemini 2.5 Flash-Lite, through OpenRouter (USA) and Google's Gemini API, and then by a person before anyone else sees it. Google says it doesn't use what it's sent to improve its products, keeps it for up to 55 days to detect abuse, and may process or briefly store it in any country where Google or its agents have facilities (checked 24 October 2026).
- How long things are kept: a report leaves the map after a few hours (1 to 24, by its type) and its record is deleted 30 days after that; a photo's file goes 30 days after its report left the map, or 7 days after it was rejected or taken down; the automatic photo checks' records after 90 days. A photo held as possibly illegal is kept, out of everyone's sight, for up to 1 year, as the law requires, even if you delete your account. Live stream links stay until you or a moderator remove them, or the stream is off air for 7 days.
- Station keys are shown to you once and stored only as a hash.
- Anyone can report a contribution or a contributor, and block a contributor so their content no longer shows to them. Something reported by 3 different people is hidden until a moderator reviews it.
- What you contribute is shared publicly under the CC BY 4.0 licence, credited as "Almighty contributors". Copies others have already made can't be recalled.
- Your public profile shows your display name, the month you joined, the countries and kinds of your stations with how many there are, how many of your submissions were approved, and your badges: never a place finer than the country. You can hide it in Settings → Contribute → Your public profile.
- Leaderboards (per kind of station and country) list only contributors who choose to appear; it's off until you turn it on. They show your display name and how much your stations sent in the last 30 days.
- Feeders can choose to have their display name listed on the Feeder coverage map, with the other feeders in the country of their ADS-B receiver ("Show my name on the coverage map", off until you turn it on). It shows only your display name and that country: never a town, a place or which station is yours.
- The latest readings from contributors' sensors are published as open data (CC BY 4.0), with the station's name, your display name and the place rounded to about 1 km.
- If you turn on notifications for Contribute (a station offline for more than 2 hours, what happened to your submissions, and for moderators the review queue), we keep this device's push token with your contributor account until you turn them off, remove the app, or delete your contributor data. Emails about these go to your sign-in address only if you turn them on. We also note the country your station's data comes from, to place it on the leaderboards.
- Feeders' perks: to give active feeders no ads and early access, we check whether one of your ADS-B or AIS stations sent data in the last 7 days. Your device keeps the answer (yes or no, and when it expires) until it expires. No new data is collected for it.
- Your feeder dashboard's statistics (planes and messages counted per hour, and the furthest distance heard in each direction, measured from your receiver, for the range plot) are kept on our feed server for 7 days.
- If you apply for a free receiver kit, we keep what you enter (the town or area you type, and a place rounded to about 10 km; why there; whether you can reach a roof or loft; your type of internet; whether you agree to be contacted) with the review status and the moderators' notes. Only Almighty's moderators see it. We use it to decide who gets a kit and to contact you, by your account's email address and only if you agreed. It's kept until 12 months after the decision (24 months at most), or until you delete your contributor data or your account, and it's in Download my data. So that "one application a year" holds, we keep your account's ID and when you last applied for a year, even if you delete the application.
Settings → Account → Download my data includes your contributions. Settings → Contribute → My contributions → "Delete my contributor data" deletes your contributor profile, stations and submissions, with the reports you made and your blocks; deleting your account does too. Moderation records about removed content are kept for up to 1 year. Legal basis: performance of a contract (running your contributor account and showing your contributions); legitimate interests (safety, moderation and preventing abuse); legal obligation (dealing with illegal content).
What we don't do
- We don't let ads track you without your say: Google personalises ads only with your consent where the law asks for it, and the iPhone and iPad app uses your advertising identifier only if you allow tracking (see Advertising above).
- We don't sell your personal data, and we don't give Google anything about you beyond what it receives to show an ad.
- We don't use analytics or crash-reporting tools that collect personal data.
Who else is involved
We use these service providers, who process data for us under contract:
| Provider | What for | Data |
|---|---|---|
| Supabase | Database, app IDs, accounts if you sign in, AI question handling, tracked flights, alerts near you, feedback, contributor accounts and sign-in emails | App ID, account (sign-in email, name, sign-in methods) and, if you sign in, your flight log, saved views and Sky lists, AI usage counts, news reports, feedback, tracked flights, alert settings with a rounded location, notification tokens, contributor data (display name, sign-in email, stations, submissions, reports, blocks), IP address (security logs) |
| Cloudflare | Hosting our live-data server (which follows tracked flights and sends notifications), the web app and this website; emailing feedback to us | Requests and IP address, in transit (and, in the web app, its estimate of your city when the globe opens); tracked flights, alert settings and notification tokens while they're in use; feedback messages on their way to us; on-board chat's sealed messages for up to 24 hours, where that's switched on |
| Apple (Apple Push Notification service) | Delivering notifications and Live Activity updates on iPhone and iPad, if you allow them | Notification and Live Activity tokens, and the text shown |
| Google (Firebase Cloud Messaging) | Delivering notifications and the ongoing flight notification on Android, if you allow them | Notification token and the text shown |
| Apple (Sign in with Apple) | Signing you in, if you choose Sign in with Apple | Your Apple sign-in; Apple tells us your user identifier, email (or relay address) and name if you share it |
| Google (Sign in with Google) | Signing you in, if you choose Sign in with Google | Your Google sign-in; Google tells us your user identifier, email, name and profile picture link |
| Google (Play Integrity) | Checking a request comes from a genuine copy of the Android app | The one-off integrity token (made by Google Play from app and device information) |
| Google (AdMob) | Showing the ads in the iPhone, iPad and Android apps (the banner and full-screen ads), and its consent form | IP address, device and app information, ad requests and interactions, your consent choice, and the advertising identifier (on iPhone and iPad if you allow tracking). Google acts as an independent controller for personalised ads |
| Google (AdSense) | Showing the ad strip in the web app, and its consent message | IP address, browser and device information, the page address, advertising cookies (with your consent where the law asks), ad views and clicks, your consent choice. Google acts as an independent controller for personalised ads |
| OpenRouter (USA), and the AI model providers it passes requests to: Alibaba Cloud (Qwen3.8 Flash; USA, Singapore or China) and Google (Gemini 2.5 Flash-Lite, for photos) | Answering questions, if you agree; writing the regional briefings; the automatic check of contributed photos | Question text and on-screen map description; for briefings, public data only; contributed photos (with their metadata already removed). Sent only to providers that don't collect it for their own use or train on it; Alibaba Cloud may keep questions for up to 30 days, Google photos for up to 55 days (to detect abuse) |
| Resend | Sending sign-in codes by email, if you sign in with an email code; emails about your contributions, if you turn them on (a station offline, what happened to your submissions) | Your sign-in email address and the message |
Apple (App Attest, speech recognition, the App Store) and Google (Android's speech recogniser, Google Play) also handle some data as described above, under their own privacy policies.
Some of these providers are in the United States or other countries outside the UK and EEA. Where that happens we rely on the legal safeguards the law provides, such as the UK International Data Transfer Addendum, the EU Standard Contractual Clauses, or an adequacy decision. OpenRouter's data processing agreement includes the EU Standard Contractual Clauses with the UK Addendum. AI questions may also be processed in Singapore or China, for which there is no UK adequacy decision. Our database (Supabase) is hosted in the EU, in Frankfurt, Germany.
We may also disclose information if the law requires it.
How long we keep it
- App IDs, and everything linked to them: until you delete them in Settings → Account, or automatically after 12 months without use.
- An account you signed in to, with your flight log, saved views and Sky lists: until you delete it in Settings → Account. Sign-in codes stop working after an hour. Apple's revocation token: with the account.
- AI usage counts: 90 days.
- News reports: 12 months.
- Feedback sent from the app: 12 months (emails: as long as needed to deal with them).
- Tracked flights and notification tokens: until you stop tracking the flight, or 7 days after the flight (at most 9 days after its day). A token Apple or Google reports as no longer valid is deleted straight away. When you stop tracking a flight, a note that it was removed (without the flight details) is kept for 2 days. Recorded flight paths: 7 days. Live Activity tokens: with the tracked flight, or until the Live Activity ends.
- Share my journey: links aren't stored; a stopped link's random ID is kept until the link would have expired.
- On-board chat's sealed messages on our server (where that's switched on): until fetched, at most 24 hours.
- Earthquake alert and briefing settings, with the rounded location and notification token: until you turn both off, the token stops working, or 60 days after the app last checked in, whichever comes first. A note that they were removed (without the details) is kept for 2 days.
- 3D Google Maps install IDs: until midnight US Pacific time.
- Security logs at our providers: up to 30 days.
Your rights
Depending on where you live (including under UK and EU data protection law, and California law), you can ask to access, correct, delete or receive a copy of your personal data, object to or restrict how we use it, and withdraw consent at any time. In the app (on iPhone, iPad, Android and the web), Settings → Account → Download my data gives you a copy of what our servers hold for your app ID, and Delete my account and data deletes your app ID and everything linked to it straight away. For anything else, email bonnyjames0@gmail.com; we'll reply within one month. If you are unhappy with how we handle your data, you can complain to the UK Information Commissioner's Office (ico.org.uk) or your local data protection authority.
A summary of these rights under the UK and EU GDPR, with the legal basis for each use of your data, is on Your data rights. The cookies and browser storage the website and web app use are on Cookies & storage.
Children
Almighty is suitable for a general audience but is not directed at children under 13. We don't knowingly collect personal data from children under 13; if you believe a child has given us personal data, contact us and we will delete it.
Security
Data is encrypted in transit, access to our systems is limited, and our database lets each user read only their own records.
Changes
If we change this policy, we'll update the date at the top, and tell you in the app if the change is significant. If we add other kinds of sign-in or ads, we'll update this policy first and ask for your consent where the law requires.