Privacy Policy
The short version: Jetbrief has no accounts, no ads and no tracking. Your flights and your journal live on your devices and in your iCloud. To forecast a flight and notify you, our server receives that flight and a random identity of your iPhone. Where your plane is during a flight is worked out on your iPhone and never leaves it. The server forgets your flights 7 days after you land and your iPhone 180 days after it last checked in, and you can delete everything it holds about you at any time in Settings → Delete my server data.
Who is responsible
The data controller is Stepan Manzurov, an individual entrepreneur registered in Georgia (Fonichala settlement 3, building 5, entrance 2, floor 4 (auxiliary storage), Krtsanisi district, Tbilisi, Georgia). Contact: contact@manzurovstepan.com. Jetbrief is offered in the European Economic Area and elsewhere; for people in the EEA the General Data Protection Regulation (GDPR) applies and this page follows it.
What stays on your iPhone
- In-flight tracking. During a flight the app reads your iPhone's barometer, motion sensors and, if you allow it, its location, to place the plane on the route and to show what is ahead. These readings are used on your iPhone and are never sent to us or anyone else.
- Your journal and saved forecasts. They are stored on your iPhone and, if iCloud is on, synced through your own iCloud account (Apple CloudKit). We cannot read your iCloud data. Apple operates iCloud under its Privacy Policy.
- Reminders you set for a flight are scheduled on your iPhone.
What our server receives
Jetbrief needs a server because the forecast is computed there and a notification has to reach you while the app is closed. There is no sign-up.
- A random identity of your iPhone. On first use the app creates a random install id and an App Attest key (Apple's proof that requests come from the genuine app) and receives a random device token. The server also stores your iPhone's time zone, language, iOS version and app version, so that times and notifications are right.
- An account key. A one-way (HMAC) value of the app transaction id from your App Store purchase record, the same on all your devices, so that Unlimited follows you. The app transaction id itself is not stored. When you buy Unlimited, the id of that purchase transaction is stored on your account record.
- Flight look-ups. The flight number or call sign and the date you type, to find the flight.
- The flights you add: the flight (or the route and time you enter by hand), when you want to be reminded, and the forecasts sent to you.
- Notification addresses: the push address of your iPhone and, for Live Activities, the address Apple gives each activity, so the server can update them.
- The time your flight took off, when your iPhone's barometer detects it, so the server can time the next updates. Never a position.
- How the flight felt, if you answer the short questions after a flight, linked to the forecast you saw. The answers may include the area of the cabin you sat in, whether the plane on the map and the flight phases matched what you saw, and rounded statistics of the in-flight session on your iPhone (such as how many GPS fixes it got, or how far the shown position was off, in ranges); never your location or any position.
- Usage events: for example "a flight was added" or "a forecast was opened", with coarse labels such as a distance bucket and, per batch, the app and iOS version, the device type (iPhone or iPad), the language, the App Store country and whether you have Unlimited; never free text, positions, airports, flight numbers or exact times, under a random identifier the app replaces every 13 months and on reinstall. This identifier is never stored with your device record or account key.
The app's server does not log your IP address: its web proxy keeps no access logs for the app's requests, our logs drop IP addresses, and rate limits hold IP addresses in memory only for the current minute or day. The website jetbrief.app keeps a shortened IP address in its web server's visit log, and counts visitors with a daily-changing hash of the IP address that is not stored; see "Website" below.
How long the server keeps it
Linked to you:
| What | Kept until |
|---|---|
| A flight you add, its reminder and notification jobs, its Live Activity addresses | 7 days after the flight lands, or when you delete it in the app, or when you delete your server data. A flight you delete more than 10 minutes after adding it still used a free forecast; that registration stays, without notifications, until 7 days after landing so the count stays right. A Live Activity's address is removed 7 days after the activity ends. |
| Your device record (random identity, notification address, time zone, language, iOS and app version) | 180 days after the app last contacted the server, or when you delete your server data. A notification address Apple reports as no longer valid is removed 180 days later. |
| Your account record (account key, Unlimited status and its transaction id, the number of free forecasts used) | for as long as one of your devices is registered; it goes with the last one. |
| After your account record is gone: the account key and the number of free forecasts used, nothing else | indefinitely, so that deleting and reinstalling does not hand out the free forecasts again |
| App Store notifications about your purchase (refunds, for example) | 90 days; the account key and transaction id are removed from them when your account record goes |
| Single-use App Attest challenges; repeat-request keys | 1 hour; 24 hours |
| Encrypted database backups (they contain the records above) | 90 days |
Not linked to you: these carry no device identity, account key or notification address, and we cannot find them by person.
| What | Live store | Archive |
|---|---|---|
| Flights as public schedule facts (airline, number, route, times, status) and the forecasts computed for them | 2 years | kept indefinitely, to compare what was forecast with what happened |
| Flight-data provider responses | 7 days | not kept |
| How a flight felt (the link to your registration is cut when the flight is purged or you delete your data) | 2 years | kept indefinitely, to calibrate the forecast |
| Usage events under the rotating random identifier | 13 months | kept indefinitely |
| Operational records (request samples, notification counts without device ids) | 13 months | kept indefinitely |
| Technical logs and metrics, with no IP address and no identifiers | 14 days | not kept |
| Website visit log (shortened IP address, see "Website") | 30 days | not kept |
| Website page statistics (daily hash, no IP address, see "Website") | 180 days | daily counts and a unique-visitor estimate derived from the hashes, no IP addresses or user agents, kept indefinitely |
Data we use that is not about you
The forecast is computed from public weather data (ECMWF, NOAA), pilot reports and the public ADS-B history of aircraft positions published by adsb.lol, which shows the routes airlines usually fly. These are about aircraft and the weather, not about passengers; we never match them to you.
Website
The website jetbrief.app keeps minimal statistics so we can see which pages are read, where visitors come from, whether the map runs well in your browser and whether people reach the App Store, and fix what breaks. There are two parts, and both are ours alone: no third-party service sees your visit.
1. The web server's visit log. For each request the web server records:
- the time, the page address and the response status (a link to a shared flight is recorded without its code:
/f/only, and addresses are recorded without query strings); - the referring site's address, cut to the site name (for example
www.google.com); - your browser's user-agent string, from which our statistics keep only a coarse device class (phone, tablet, computer or bot);
- your IP address, shortened before it is written: the last part is replaced with zeros (an IPv4 address to its first three numbers, /24; an IPv6 address to its first 48 bits), so it no longer points to one connection.
This log is deleted after 30 days. The statistics sent by the page (below) are not written to it.
2. Page statistics from the site's own script. Each page runs one small script that we serve ourselves. It sends the following to our own server, jetbrief.app/a, and nowhere else:
- the page (without its query string), the page language, the site you came from (its name only) and the campaign tags in the address if there are any (
utm_source,utm_medium,utm_campaign,ref); - a coarse device class (phone, tablet or computer), your browser's family (for example Firefox or Safari, no version), and your time zone (for example
Europe/Berlin), from which we work out a country, so we never look up your location from your IP address; - what you do on the page: which links you tap (the App Store button and where it was, links to other sites and pages, the language menu), how far down the page you scroll (25, 50, 75 or 100 %), how long the page was open and visible, which map layers you switch on, whether you play the forecast or share a view, and the two airport codes of a route you check (never a flight number or a position);
- how well the page ran: the three Core Web Vitals (load time, layout shift, responsiveness) and, on the map, the median frames per second, the picture quality the map chose and the window size it drew at.
To count visitors without cookies, the server computes a keyed hash (HMAC-SHA256) of your IP address, your browser's user-agent string and the site name. The key is random, kept only in the server's memory and replaced every day at midnight UTC; the old key is gone, so the hashes of two days cannot be linked and nobody can recompute a hash from an IP address. Your IP address and user-agent string are used for this and for the abuse limit and are not stored. The page statistics hold the daily hash, the items above and the time.
The script sets no cookies and uses no local storage, session storage or other identifier on your device. It sends nothing if your browser sends Global Privacy Control or Do Not Track, or is automated. The site does no fingerprinting, loads no third-party scripts, fonts or trackers, does no tracking across sites, and we do not combine these statistics with the app's data. Individual page statistics are deleted after 180 days. Daily counts made from them (pages, referring sites, countries, device classes, browsers, languages, taps on the App Store button), including a mergeable unique-visitor estimate derived from the hashes, are kept indefinitely; they hold no IP address and no user agent. The website is hosted by Hetzner with the rest of the service.
Deleting your data
Choose Settings → Delete my server data in the app. The server then deletes this iPhone's record with its notification and Live Activity addresses, its notification jobs, and, when it is your last device, your flights and your account record, keeping only the account key with the number of free forecasts used (listed above). If Jetbrief is also registered on another device of yours, your flights stay with that device; delete there as well to remove everything. When your account record goes, answers about how flights felt lose their link to you; usage events were never linked to you, so they stay in anonymous form (Article 11 GDPR). Your journal on your devices and in iCloud is not touched; the flights saved at that moment stop getting forecast updates.
Deleting a single flight in the app also deletes it from the server (when you are offline, as soon as the app is back online).
If you write to us instead, we will ask you to confirm the request from inside the app, because the app, not your name, is the key we can find your data by. You can also complain to your data protection authority.
Who processes data for us
- Hetzner Online GmbH (data centres in Germany and Finland): hosts the server, the website, the database, the archive and the backups.
- Apple: push notifications and Live Activity updates (APNs), App Attest, the App Store purchase record, and iCloud for your journal.
- AeroDataBox, reached through its marketplace API.market, which relays the request: they receive a flight number or call sign and a date when a flight is looked up or its status is refreshed. They never receive your device or identity.
- Grafana Labs (Grafana Cloud): receives service metrics and logs without personal data.
- Healthchecks.io: receives "the service is alive" pings, nothing else.
We do not sell data and we do not share it for advertising.
Feedback and tips
When you send feedback from Settings, the app sends your message, its category, an optional contact address and attachments, and technical details (app version, build, iOS version, device model, locale, and whether Unlimited is active) to our feedback server (Hetzner, EU), which delivers a copy through Discord. Attachments are removed from our server after delivery; feedback records are deleted after 24 months. After a tip, the app reports the tip tier, locale, time, and whether Unlimited is active to the same server, without your Apple Account, transaction id or any device identifier. Nothing unlocks from a tip. Apple processes all payments; we never see your card.
Why we may do this (GDPR)
- Art. 6(1)(b) GDPR, contract: registering your flights, computing forecasts and sending the notifications and Live Activity updates you asked for.
- Art. 6(1)(f) GDPR, legitimate interest: first-party usage events, the website's visit statistics, protection against abuse, and comparing forecasts with what happened. We weighed these against your interests: the events are coarse, carry a rotating random id, are not linked to you and cannot be traced to a person; you can delete everything linked to you at any time.
We do not show a consent dialog for the usage events because they follow the conditions the French data protection authority (CNIL) sets for audience measurement without consent: first-party only, no linking across apps, no sharing, and an identifier that lasts no longer than 13 months.
What we do not collect
Names, e-mail addresses (unless you type one into the feedback form), contacts, photos (unless you attach them to feedback), your location or any position, advertising identifiers, identifierForVendor, or anything from third-party analytics or advertising SDKs.
Forecasts are not flight advice
Jetbrief's forecasts are a planning aid and not for flight decisions. See the Terms of Use for more.
Changes
If this policy changes in a way that matters, the date at the top changes.