What Crew GO! keeps, and where.

Effective 28 October 2026 · applies to the test builds of Crew GO! for iPhone and Android and to crewgotravel.com

Crew GO! is made by airline crew, for airline crew who commute. The short version: nearly everything you type stays on your phone. Crew GO! does run one small server of its own, at crewgotravel.com — it holds the paid flight providers' keys so they are not sitting inside the app on your phone, it checks that you really do hold an airline email address, and it passes load requests and answers between crew. What it keeps is listed below, and it is less than you would expect. The app also talks to a few outside services for flight and weather data, and emails you only when you choose to send something.

What stays on your phone

• Your profile. Work email address, airline, base and home airports, pilot or flight attendant, how often you commute, and your plan. Stored only on the device.
• Your searches, watched routings, and commute setup. Report time, primary and backup routings, and the snapshots you keep.
• Loads you mark from your own airline's system. Never shared with anyone. The app says so on the screen where you enter them.
• The error log. Up to fifty recent problems with a short code, kept so that Settings, Diagnostics can show them. They leave the phone only when you tap Send.

Settings, Reset erases all of it. Deleting the app erases all of it.

Permissions the app asks for

• Face ID, Touch ID, or fingerprint. Used only to unlock the app. The check happens on the device through the operating system. The app never sees or stores biometric data.
• Calendar. Writes one event per flight when you tap Add to calendar. If you connect your work schedule, reads trip report times from the one calendar you choose, on the device, whenever Search opens, so report times fill in for you. Schedule details stay on the phone and are never sent anywhere. Disconnect it in Settings at any time.
• Notifications. Not requested in the test builds.
• Location. Never requested.

Outside services the app contacts

Flight data comes from several places. Some the phone asks directly; the rest it asks through crewgotravel.com, which holds the keys so they are never inside the app. Either way the request carries an airport code, a flight number or a date — never your name, your email, or your token.

• crewgotravel.com — our own site, for boards, searches, filed schedules, the load exchange, crew verification and news. It is the only one that knows your verification token, and it sees it because that is what proves you are crew.
• adsb.lol, asked by the phone itself, for where aircraft are right now from the open ADS-B network. The request carries an airport code and the app's own contact address, so the volunteers running it can reach us. Your phone's address reaches them, as it does any site it opens.
• nasstatus.faa.gov, run by the United States government, asked by the phone, for ground stops, ground delay programmes, closures and deicing. The request carries nothing but the page address.
• aviationweather.gov, also United States government, for airport weather. The request carries the airport code.
• FlightAware, Flightradar24 and aviationstack, asked through our site, never by the phone, when you open a single flight to see how it has been running. The request carries that flight number and date.
• Expo for app updates. The update check carries the app version and platform so the right build is served.
• Apple or Google when you tap Rate, through the standard in-app rating prompt.

Aviation Edge was the app's board provider until 12 October 2026 and is no longer contacted at all. The timetable it filed before then is still used, and is labelled as a timetable wherever it is shown.

The app shows no advertising and contains no advertising or analytics software.

Loads shared between crew

When you ask other crew for the loads on a flight, or answer someone else's request, the flight number and the numbers you type are shared with verified crew inside the app. Answers show without your name. Loads are what a crew member's screen showed at the time and are never verified by the app or by any airline. Do not rely on them alone. Requests and answers pass through crewgotravel.com so they can reach the right airline. We keep the flight, the route and time you asked about, the numbers answered, and your airline and role (for example "AS flight attendant"). You are identified only by a scrambled code tied to your crew verification, never by name or email. Requests stop being listed after a day.

What you send us

Rate and feedback, Send report in Diagnostics, and the crash card all open your mail app or the share sheet with a message addressed to us. Nothing goes until you send it. The message includes the app version, your phone model and system version, and recent error codes, so we can find the problem. The form on this site sends your name, email, and message to us by email. We keep those emails to answer you and delete them when you ask.

What we do not do

• Sell, rent, or trade anything about you.
• Track you across other apps or sites.
• Show your name on a load answer.
• Post anything publicly.

Cookies and tracking

This website sets no cookies. There is no analytics, no advertising, no Tag Manager, no Meta pixel, no session and no fingerprinting, so there is no cookie banner here and there is nothing for you to consent to or opt out of.

One page does keep something in your browser, and only one: the tester instructions at /testers remember which step of each checklist you have ticked off, as entries named cg-steps-… in that browser's own storage. They hold a step number and nothing else, they never leave your device, and we cannot read them. Clearing your browser data removes them.

The one Set-Cookie header the site ever sends is a deletion: the testers page used to remember that you had entered the code, and now it deliberately clears that old cookie so every visit asks again. It sets nothing in its place.

Two things do see a request, because they have to:

• Cloudflare hosts the site and so receives your IP address, your browser type and which pages you asked for, to serve them and to stop abuse. We do not keep that in a database of our own.
• Google Fonts serves the two typefaces, so your browser fetches them from Google and Google sees your IP address when it does. No cookie is set by it, and we send Google nothing about you.

Your browser's "Do Not Track" and "Global Privacy Control" signals need no action from us: there is no tracking to switch off, and we treat them as an opt-out anyway.

The app is a different matter from this website. It keeps your profile, searches and watched routings on your phone, not in a cookie and not on a server — the sections above say exactly what and where.

What we hold on our own server, and for how long

The site's own database holds very little, and the email you type into the sign-up form is not part of it:

• Sign-ups: your email address is turned into a one-way fingerprint and the address itself is never stored — it exists only to stop the same person being counted twice. The airline, role, platform and base you pick are stored next to that fingerprint.
• Crew verification: the code, a one-way fingerprint of your token rather than the token itself, and a one-way fingerprint of your personal email, with the airline and the method. We check you hold a working airline email address; we do not store that address either.
• Loads you ask about and answer: held so other crew can see the answer, without your name attached.
• Feedback you send: your stars and your words, with the airline and role you chose to include.
• Flight lookups: a flight you look up is cached for 20 minutes so a busy morning does not re-ask a paid provider, and the copy is then kept for up to 30 days as a fallback for when the month's allowance with that provider runs out — after which it is deleted. It holds the flight, not you, and is not linked to you.
• Faults in the site itself: when something breaks on our side we record which address failed, the error message and a short code for where in the program it happened, so it can be fixed. Tokens and email addresses are stripped out of the message before it is written. No request body is ever kept. These are deleted after 30 days.
• A fingerprint of your network address, in two places and for one reason — stopping one person asking for hundreds of codes, or guessing at the founder key. It is a one-way fingerprint, never the address itself, and nothing else is recorded against it. When you ask for a verification code it is written on that code's row and counted over the last day; when you finish setting up your account it is overwritten by the fingerprint of your personal email, so it survives only on codes nobody finished. A founder-key attempt is kept for seven days and then deleted.

Email support@crewgotravel.com to see, correct or delete any of it, and we will reply within 30 days.

How long it is kept

Being straight about this: most of it is kept for as long as the test runs. Three things are deleted automatically, and they are deleted by the code that writes them rather than by a nightly job, so there is no schedule to forget to switch on. Everything else waits on you asking or on the test ending.

• Flight lookups go stale after 20 minutes and are deleted once they are 30 days old.
• Faults in the site are deleted once they are 30 days old.
• Founder-key attempts are deleted once they are seven days old.
• Your sign-up has no address in it to keep — only the one-way fingerprint and the airline, role, platform and base you chose.
• Everything else — verifications, loads, feedback — is kept while the test runs, and deleted when you ask or when the test ends, whichever comes first.

Ask us to delete yours and we will, within 30 days. When Crew GO! leaves testing this section gets a real schedule with code behind it, and the date at the top will change.

Email from us

We send no marketing email — no newsletter, no promotions, no "we miss you", and your address is not on a mailing list anywhere, because the sign-up form never stored it.

What we do send is service email: the verification code you asked for, a reply to something you sent us, and occasional announcements to testers about a build that matters. Those go to people testing the app, about the thing they are testing.

Want them stopped? Email support@crewgotravel.com and say so, and they stop — no form, no preference centre, no arguing. If we ever do start sending something promotional it will carry a one-click unsubscribe link and our postal address in every message, as US law requires, and you will have to opt in first.

Children

Crew GO! is for working airline crew and is not directed at anyone under 18.

Changes

When this policy changes, the date at the top changes and the app's Settings screen links to the new version. Big changes are also announced to testers by email.

Contact

Crew GO! · support@crewgotravel.com · or the form on the support page.