Privacy Policy

This Privacy Policy explains how FlightCrew Pro ("FlightCrew Pro," "we," "us," or "our"), an application by AORUX, collects, uses, and shares information when you use the FlightCrew Pro mobile application for iOS and Android and related services (the "Service"). FlightCrew Pro is a companion for airline flight crews: it turns your crew schedule into a live view of your trips, duty limits, flights, layovers, and the crew you fly with. We built it to collect only what the Service needs to function and to give you server-enforced control over what other crew can see about you.

FlightCrew Pro is a thin client: the heavy lifting — parsing your schedule, computing duty limits, tracking flights, and contacting third-party data providers — happens on our servers, and the app renders the result. Your account, schedule, and content are stored in our backend, which is hosted on Supabase (managed Postgres, authentication, and realtime).

1. Information we collect

• Account information. When you create an account we collect your email address and authentication credentials. If you use Sign in with Apple, we receive the identifier Apple provides and, depending on your Apple sharing choice, your name and a relay or real email address. Authentication and accounts are managed through our backend provider, Supabase.
• Profile information. Details you provide to set up your crew profile — your airline, crew handle or display name, employee ID, home base, seat/position, flying-since date, and preferences such as time format and appearance. We may load a profile avatar from Gravatar based on your email.
• Schedule data. With your permission, we read events from the device calendars (and, optionally, reminders) you select and relay them to our server, which parses them into trips, flights, deadheads, hotels, report/release times, and duty periods.
• Crew roster data. When you import a crew list (by pasting or forwarding roster text, or uploading a schedule/roster screenshot), we process the names, employee IDs, positions, and legs it contains so you can track who you have flown with and keep a private no-fly list. This may include information about other crew members.
• Reminders you configure. Settings you create for reminders — such as recurring bid-window schedules (open/close/award day, time, and timezone) and per-hotel reminders — are stored with your account.
• Location data. If you enable arrival or customs pre-clear reminders, we process your device location — including in the background — to detect when you reach an airport.
• Photos you provide. Images you choose to upload (such as a schedule or crew-list screenshot) are sent to our server and to our AI provider for parsing. We do not access your photo library except for images you explicitly select or share.
• Messages & content you create. Direct messages, crew-chat messages, AI assistant conversations, crew ratings and notes, hotel notes, airport tips, and CMAP contributions you submit.
• Device & push tokens. A push notification token for your device, Live Activity tokens, along with basic device information such as device model, operating system version, and app version.
• Usage & presence data. Your last-active time and activity used to power presence and the "on the app" crew badge (both subject to your privacy settings).
• Diagnostic & usage data. Crash reports, error logs, and performance and product-usage events used to keep the Service reliable and to guide improvements.

2. How we use information

We use the information we collect to:

• Parse your schedule into trips, flights, deadheads, hotels, and report times, and detect changes by comparing relayed calendar events on our server;
• Calculate flight-duty-period (FDP), flight-time, and rest limits, including FAR 117 international acclimation;
• Track your flights live (position, phase, gate, tail, delays, EDCT, and the inbound aircraft becoming your next leg) and attach weather and FAA status to the relevant legs;
• Deliver duty-limit, schedule-change, ATC-delay, arrival, hotel, bid, and crew/social notifications, Live Activities, and flight-alarm wake-ups you've enabled;
• Remind you about your recurring bid windows (opening, closing, and award release);
• Operate crew social features — follows, direct messages, per-trip crew chat, layover overlaps, and viewing crew you fly with;
• Power community features — hotel notes, airport tips and taxi trends, and CMAP access points and terminal maps;
• Run the AI assistant and AI-assisted schedule and roster parsing;
• Authenticate you, enforce your privacy settings, and secure your account;
• Maintain, secure, debug, and improve the Service.

We do not sell your personal information, and we do not use your schedule, location, messages, or content for advertising.

3. Calendar & reminders access

FlightCrew Pro requests read access to the calendars (and, optionally, reminders) you choose so it can ingest your schedule. Only the calendars you select are processed. Your device relays the raw events to our server, which parses them, detects changes, computes your duty day, and syncs a ready-to-render snapshot back to your account. On Android the app may also request calendar write access. You can revoke this access at any time in your device settings; doing so will disable schedule-dependent features. Deselecting a calendar lets you keep or remove the flights it contributed.

4. Location data

Location-based reminders are optional. If you enable them, FlightCrew Pro uses your location while in use and in the background and sets up geofences around the relevant airports so it can (a) remind you to sign in and release from your trip, and (b) remind eligible crew to pre-clear customs (e.g. Global Entry) on arrival from an international flight — even when the app is closed. We use location only for these reminder features; we do not continuously track or store your movement history beyond what is needed to trigger reminders. You can disable location access at any time in your device settings.

5. Flight alarms

If you enable automatic flight alarms (iOS), FlightCrew Pro schedules a native wake-up alarm before your report time using Apple's AlarmKit, so you don't sleep through a report. Alarms are scheduled on your device from your own schedule; enabling them does not transmit additional personal data. You can turn flight alarms off at any time in the app.

6. Bid reminders

FlightCrew Pro can remind you about your recurring monthly bid windows. If you opt in, you configure one or more bid rules — the day of month and time that bidding opens, closes, and (optionally) awards are released, read in a timezone you choose — and our server sends you reminders as bidding opens, before it closes, and when awards are released (or when the awarded month's flying appears on your calendar). Your bid rules are stored with your account and are private to you; we do not share them with other crew. Bid reminders are off by default, and you can disable them at any time in your notification settings.

7. Notifications & Live Activities

To deliver time-sensitive duty, schedule, delay, hotel, bid, and crew alerts, we register a push notification token associated with your account and device. Notifications are built and sent by our server through the Expo push service and platform services (Apple Push Notification service on iOS and Firebase Cloud Messaging on Android); iOS Live Activities are pushed directly through APNs. Live Activities may display current flight and duty information on your lock screen and Dynamic Island. Push payloads may contain flight and duty status text. Your notification preferences (including per-type toggles, mute, and quiet hours) are stored with your account, and you can turn off notifications in your device settings at any time.

8. AI features

FlightCrew Pro uses AI to parse schedules and to power an in-app assistant. Our AI processing runs on our servers and calls a third-party large-language-model provider, Groq (with DigitalOcean GenAI configured as a fallback for the assistant). AI providers act as our processors, and results are cached to minimize the volume of data sent. Depending on the feature, the following may be transmitted to the AI provider:

• Schedule parsing. When our deterministic parser can't classify a calendar event, its title and description text may be sent to be categorized. Your own trips may also be compared to detect duplicate rotations.
• Crew-list parsing. Roster text and schedule/crew-list screenshots you import — which may contain crew names, employee IDs, positions, and legs — are sent to be turned into structured data.
• AI assistant ("CrewAI"). Your messages, plus a snapshot of your own profile and schedule (next trip, block and credit hours, layovers, hotels, days off, base, and seat) and recent conversation, are sent so the assistant can answer and take actions you request (such as setting a hotel reminder). The assistant is scoped to your own data and is not designed to send other crew members' personal information.
• Flight & hotel enrichment. Live flight telemetry may be sent to help resolve flight phase; scraped hotel-website text may be sent to extract amenities. These do not contain your identity.

9. Crew social & messaging

FlightCrew Pro includes crew social features. These expose some information about you to other users, always subject to your privacy settings (Section 11):

• Follows. You can follow other crew and be followed. Following, followers, and mutual-follow relationships are derived on our server. A mutual follow unlocks direct messaging and other features.
• Direct messages. Private 1:1 messages, gated so that only people you mutually follow (or whom your settings otherwise allow) can message you. Message content is visible to you and the recipient.
• Crew chat. A group thread shared by crew assigned to the same trip and service date. Your display name and messages are visible to that trip's crew. Crew-chat messages are automatically deleted 7 days after posting; direct messages are not subject to this expiry.
• Layover overlaps & schedule viewing. If enabled, crew you mutually follow may see when your upcoming layovers overlap with theirs, and permitted followers may view your schedule. Both are reciprocal and off unless you opt in.
• Trip crew & presence. Crew you have flown with may see that you are "on the app" and your last-active status, and the date you last flew together, unless you hide it.

Please do not share classified airline security information, sensitive passenger data, or any material that violates your employer's communication policies. You can delete your own messages, and we may remove content or restrict access where necessary.

10. Community & crew-shared content

Some features let you contribute content that other crew can see:

• Hotel notes ("Crew Insights"). Notes you post about layover hotels are shared with other crew, and can optionally be scoped to your airline.
• Airport Hub. Food/transport tips you submit (and your upvotes) are shown to other crew. Taxi-time and delay trends are computed by our server from operational flight data, not attributed to you.
• CMAP. Crew-bypass access points, notes, and terminal maps you contribute are community-wide.
• Crew no-fly list. Your ratings and notes about crew are private to you. You may explicitly and revocably share only the names and positions on your no-fly list with a specific mutually-followed crew member — never your ratings or notes, and only when you both share.

11. Your privacy controls

Every way one crew member becomes visible to another is governed by a setting, and controls are reciprocal: on a given surface, what you expose about yourself is what you are allowed to see about others ("give and get"). These controls are enforced on our server, not just hidden in the app. From the Privacy & Sharing screen you can set:

• Discovery & follows. Who can find you in search and who can follow you (nobody / crew you've flown with / everyone), and which fields (email, handle, employee ID) can be searched.
• Messaging. Who can direct-message you, and read receipts.
• Presence & schedule. Whether your active status, exact times, and schedule are visible to permitted crew.
• Layover overlap. Whether you participate in layover matching, and its threshold and precision.
• Diagnostics. Whether to share usage and diagnostics (Section 12).

The app also applies screen-capture protection on crew screens (the most sensitive data) where the platform supports it.

12. Analytics & diagnostics

We use third-party tools to keep the Service reliable and to understand how it is used:

• Sentry for crash reporting, error monitoring, and performance tracing (configured not to send default personal information);
• Statsig for feature management and product usage events;
• Vexo Analytics for mobile product and usage analytics.

These tools may process limited technical identifiers and device information. They act as our processors and do not use your data for their own advertising.

13. Third-party data providers

To enrich your schedule, our servers query third-party providers. When we do, we transmit only the operational details needed to retrieve the relevant data — never your name or account:

• Flight tracking & status (ADS-B networks such as adsb.lol and airplanes.live, AirLabs, AeroDataBox, FlightAware, FlightRadar24, FlightStats, Avinor, OAG, and aircraft/airframe lookups such as planespotters and hexdb): we send flight identifiers — flight number/callsign, airline code, origin and destination airport codes, aircraft registration or hex, and date.
• Airspace & airport status (the FAA, NAV CANADA, and NATS): we send airport codes to retrieve delay and status information.
• Weather (Open-Meteo, and AviationWeather.gov/NOAA): we send layover airport coordinates or station codes.
• Hotel & map data (OpenStreetMap Nominatim, OSRM, Brave Search, and hotels' own websites / Wikimedia): we send a hotel name, coordinates, or website URL to resolve address, phone, location, drive time, and amenities. Some of these requests are routed through our own egress proxy.
• Push & email (Expo, Apple/Google push, and Resend for transactional and crew-list-forwarding email).

These providers operate under their own privacy policies and terms, and FlightCrew Pro is not affiliated with or endorsed by them.

14. How we share information

We share information only as needed to run the Service:

• Service providers. Infrastructure and processing partners acting on our behalf under appropriate agreements — including Supabase (authentication, database, realtime), our application API host, the Expo push and update services, Apple (Sign in with Apple and push delivery), our AI providers (Groq, and DigitalOcean GenAI as a fallback), Resend (email), Sentry, Statsig, and Vexo Analytics.
• Data providers. As described in Section 13, to retrieve flight, airspace, weather, and hotel information.
• Other users. Your display name, content, and the social/presence signals described in Sections 9–10 are shared with other crew as governed by your privacy settings (Section 11).
• Legal & safety. When required by law, or to protect rights, safety, and the integrity of the Service.
• Business transfers. In connection with a merger, acquisition, or sale of assets, subject to this Policy.

15. Data retention & security

We retain personal information for as long as your account is active or as needed to provide the Service, then delete or de-identify it within a reasonable period unless a longer retention is required by law. Some data has shorter, purpose-specific lifetimes — for example, crew-chat messages are deleted 7 days after posting, and cached third-party data expires on a rolling basis. We use industry-standard safeguards: encryption in transit (HTTPS/TLS), encrypted on-device storage of credentials through the platform keychain or keystore, and row-level security in our database that scopes each user to their own data. No method of transmission or storage is completely secure, however, and we cannot guarantee absolute security.

16. Your rights & choices

Depending on where you live, you may have the right to access, correct, export, or delete your personal information, and to object to or restrict certain processing. You can:

• Revoke calendar, reminders, location, photo, or notification permissions in device settings;
• Control what other crew can see about you from the Privacy & Sharing screen (Section 11);
• Delete your own messages, notes, ratings, and contributions;
• Delete your account from within the app, which removes your associated personal data subject to legal retention;
• Request access to or deletion of your account data by contacting us.

17. Children's privacy

The Service is intended for aviation professionals and is not directed to children under 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect personal information from children. If you believe a child has provided us information, contact us and we will delete it.

18. Changes to this policy

We may update this Privacy Policy from time to time. When we make material changes we will update the "Last updated" date and, where appropriate, provide additional notice. Your continued use of the Service after changes take effect constitutes acceptance of the revised Policy.

19. Contact us

Questions about this Privacy Policy or your data? Contact us at contact@aorux.com.