Written to be checked, not to be survived. It says what leaves your phone, when, and to whom — including the parts that are inconvenient to admit.
Your roster, your flight history and your pay figures live on your phone. There is no account, and we cannot read them. Two things do leave the phone, and only when you ask for them: a roster photo, which goes to Google's Gemini to be read; and the aerodrome codes for a briefing, which go to our own weather service. Your pay figures never leave, ever. Separately, if you join the early access list, that list holds the email, operator and seat you typed into it.
The Flight Crew App, at hello@theflightcrewapp.com. Write to that address for anything on this page, including asking us to delete what we hold.
What we keep: your email address, the operator you typed, whether you fly as pilot or cabin crew, whether you offered to help test your operator's integration, and the date you signed up.
Why: to write to you when access opens and when automatic roster import for your operator is ready, and to decide which operator to build next — which is the whole reason the operator field exists.
How many times we will write: twice. That is the promise on the form and it is the promise here.
Where it is kept: on Cloudflare's infrastructure, which is our service provider for the site. Nobody else receives it. It is never sold, and it is never shared with an operator or an airline.
How long: until access opens and your operator's import ships, or until you ask us to remove you — whichever comes first. One email to the address above and it is gone.
The legal basis is your consent, given by sending the form, and you can withdraw it at any time without giving a reason.
The app is not an account. It stores what it needs in the browser's own storage on your device: your roster, the airports you have taught it, your pay profile, and any salary tables you paste in. None of that is uploaded to us, and a backup file only exists if you export one yourself.
Reading a roster from a photo sends that photo to Google. It is processed by Google's Gemini. That is a third party handling a document with your name and your duties on it, and it is the single most important sentence on this page. It happens only when you choose to read a photo, and the app tells you so at the moment you do it. If you would rather it never happened, add your duties by hand — everything else in the app works the same way.
Fetching weather tells our service which aerodromes you are briefing. METAR, TAF and NOTAMs are requested through a service of ours, which sees the four-letter codes and nothing else — no name, no roster, no times. If you prefer, paste the bulletins in by hand and nothing is requested at all.
Your pay never leaves the phone. Salary tables are typed or pasted by you, they are not built into the app, and no part of the app sends them anywhere.
The app is behind a sign-in gate during the private beta. That gate is Cloudflare Access, and it knows the email address you use to get in.
Under the GDPR you can ask us for a copy of what we hold about you, ask us to correct it, ask us to delete it, or object to our using it. Write to hello@theflightcrewapp.com and we will answer. You also have the right to complain to your data protection authority; in Spain that is the AEPD.
Most of what the app knows about you is not ours to hand over or delete, because it is on your phone: clearing the app's storage, or deleting the app, removes it.
No advertising, no tracking pixels, no analytics that follow you elsewhere, and no cookies beyond the one Cloudflare Access sets to keep you signed in to the app.
If the app starts sending something new anywhere, this page changes on the same day the feature does, and the change is named rather than folded into a new version number.