Your account. Your roster. Your choices.
Privacy information
Updated 15 October 2026
This page explains how Crew It Up handles information used for your account, roster workspace, personal planning, and optional Google Calendar import.
Your account and workspace
Crew It Up uses Clerk for sign-in. Signing in with Google shares basic account information, such as your name, email address, and profile information, with Clerk. Crew It Up uses your verified account identifier and display information to open your workspace and check which workspace records you can access.
Calendar access is optional and requires an additional Google permission request. Basic Google sign-in does not require you to connect a calendar.
Your member profile and family sharing
New accounts choose Crew or Family member. Crew profiles store the selected airline name and IATA code. Family profiles store the connection to the crew workspace whose code they enter.
Crew members can create an optional family code in Settings. Anyone you share the code with can sign in and view your roster dates, duty labels, flight routes and schedule times. They cannot edit your roster. Sleep records, health details, personal plans, private notes and stored source documents are not included in family access.
A separate Share planning estimates setting is off by default. If you enable it, connected family can see estimated leave-home and home-arrival times, a sleep-by target, a possible window together and a shortfall against your saved sleep target. These estimates use your schedule and saved planning inputs; they are not records of actual location or sleep. Your sleep logs, health records and plan details remain private. Turning this setting off stops further planning reads. These estimates are not saved for offline use.
Only a hash of the family code is stored. Creating a new code stops new joins with the old code; family members already connected keep access. Remove family access in Settings to disconnect them and turn off the code. Family devices can save the shared roster and permitted completed flight paths for offline access, without Crew health records or private notes.
Your home location and journey estimates
Every member can optionally save a home address, home base airport and a confirmed map pin, and change or remove them later. This location belongs to your profile. It is not shared with other members or included in offline roster copies. A Family member uses their own saved location, never the crew member’s private address.
Searching or confirming a location uses Apple Maps. For the final sector returning to your saved home base, we send your saved pin (or address when no pin is saved), the airport departures terminal and expected departure time after debrief to Apple Maps for a driving estimate. Available arrival evidence and a recorded or explicitly estimated debrief allowance determine departure readiness. Future departures are projections that can change. A terminal-level route does not identify your exact pickup curb. An ambiguous terminal or unavailable route stays unavailable.
At a layover, hotel arrival uses a fixed 45-minute transfer allowance after debrief. It does not use a hotel address or measured road traffic. Neither estimate establishes your actual arrival or tracks your device. Journey results are not stored for offline use.
Apple Maps features are subject to the Apple Maps terms and Apple Maps privacy information.
Optional satellite maps
Choosing Satellite in a Crew or Family flight map loads Apple Maps in your browser. Apple receives the map areas requested and normal connection information, including your IP address. We do not request your device location or send your home address, roster documents or account identifier to load satellite imagery. Flight overlays use information already available in your authorized map view.
Satellite imagery needs an internet connection. The existing vector map remains available offline. We do not store Apple imagery in offline roster copies or the app's offline cache. Satellite imagery is photographed at different times and is not a live view; detail varies by location and zoom.
See the Apple Maps privacy information and our terms of use.
Optional Google Calendar access
When you choose to connect Google Calendar, Crew It Up requests read-only permission to list your calendars and read calendar events. You choose a calendar and date range to import into your roster workspace. The Google permission can cover calendars your Google account can access; your selection determines what you import into Crew It Up.
Importing copies selected event data into Crew It Up. It does not edit, create, or delete events in Google Calendar. Connected imports can refresh automatically in the background, and you can also refresh them in the app. Personal plans saved in Crew It Up are not written to Google Calendar.
Direct Crew Portal
Direct Crew Portal offers optional login setup for Star Air. Choosing Save login stores your User ID, password and Star Air company code encrypted in your private Crew It Up workspace. The encryption key is held separately as a server secret. Saved login details are not returned to the app, shared with family members or included in offline roster copies.
You can replace or remove the saved login in Settings. Removing it deletes the saved encrypted login; it does not change your airline account or delete previously downloaded roster history. Saving a login alone does not sign in to the portal or download a roster.
When downloads are enabled, choosing Download preview sends your saved login to Star Air through a private browser service. Each download uses a separate browser session which is closed afterward. The original PDF and parsed source are retained privately with your workspace records. The preview includes roster dates, duty codes, flights and training details; it excludes crew names and employee IDs. A preview does not replace your current roster. Choosing Import this roster adds its entries to your roster. Dates covered by another roster source need review; you can choose to import only new dates. Refreshes update this portal source while preserving your corrections and other sources. Original downloads and import history remain in your private workspace records.
Information kept with your roster
Crew It Up stores the roster information you submit or choose to import, together with source references and import history. This lets the app show where an entry came from and distinguish source information from the roster values displayed in your workspace.
Imported source history is retained with your workspace records. Disconnecting Google Calendar or revoking permission does not delete records that have already been imported into Crew It Up.
Apple Health in the iPhone app
Apple Health is optional. Choosing On in the iPhone app requests read access to sleep and sleep stages, heart rate and heart rate variability (HRV), and enables private account syncing for these readings. Existing partial connections require an explicit On selection before sharing expands. Apple lets you choose permission for each type; completing its permission sheet does not prove every type was allowed. The app does not write to Apple Health.
Sleep starts with the last 31 days and refreshes when the app opens and when iOS delivers updates. Recorded times, stages and source information are encrypted on this device for your Crew It Up account. This copy is excluded from device backups and offline rosters. Normalized sleep times, stages, awake periods, date range, sync time and wearable/manual/unknown classification are sent over an encrypted connection to your private account and workspace in Cloudflare D1, so web and iPhone can use the same observations. Raw Health sample identifiers and device or source-app names stay on the iPhone.
Heart readings include heart rate in beats per minute and HRV as SDNN in milliseconds. The app reads the latest 48 hours of heart rate and 35 days of HRV when reopened or refreshed. Normalized values, observation times, method and source classification are privately synced; these samples are not retained in the native archive or browser storage. Health readings are excluded from Family access, offline rosters, notifications and logs, and are not used for advertising, marketing or data brokerage.
A saved manual sleep total always takes priority for its selected date. Clearing it restores available Apple Health observations; values from the two sources are never added together. Overnight sleep is credited once on its wake date. Timed manual edits retain their explicit interval handling. Empty Health results cannot distinguish denied permission from no recorded observations and never establish zero sleep or complete coverage. A successful full refresh updates the readable copy, including changes and deletions; a failed sync retains the last successful copy. iOS controls background update timing.
Experimental Recovery compares HRV during recorded wearable sleep with a personal baseline alongside duty load and recorded sleep. It requires readable sleep details and enough comparable history; absent readings are not invented. Existing imported history counts without a fixed connection wait. This is not WHOOP or NOOP’s score or a clinical or fitness determination. Duty load combines observed cardiovascular intensity and planned aviation workload on an experimental 0–21 scale, using the maximum-heart-rate reference you explicitly save in private planning preferences. Gaps remain incomplete coverage. The reference is excluded from offline rosters.
Off pauses new reads and uploads on this iPhone while retaining saved history. Signing out pauses access; another signed-in account cannot read the device copy. Turning On in a different workspace creates a fresh connection there after pausing the earlier one; previously synced history remains in its original workspace. Web displays account history, while the iPhone controls HealthKit access. You can change permissions in Apple Health. Your original Health records are unchanged. For deletion of retained account records, use the contact details below.
Airline sign-in on your iPhone
The iPhone app signs in to iCrew on this device for your Crew It Up account. Successful sign-in details are saved in the iPhone's secure, account-scoped Keychain and reused when you choose Sync data. Passwords, cookies and sign-in tokens are not exported to Crew It Up's server or web interface. You personally approve any Microsoft Authenticator request. After sign-in, the app downloads the requested published roster CSV and automatically saves it to your protected Crew It Up source records. Sync data automatically applies roster differences to your shared phone and web account, leaving unchanged entries intact. Conflicts or uncertain source details remain for review. Closing the import discards its temporary attempt and captured file while retaining saved sign-in details. Clear saved sign-in removes that account's saved credentials and airline browser data from this device.
iPhone notifications
When native notifications are available and you enable them, we store a device notification token and installation identifier with your account, workspace and verified sign-in session. Apple Push Notification service delivers roster-change, review-needed and reconnect messages. These messages use public duty details and exclude health observations, fatigue findings, private notes and source documents. You can turn them off in the app or iPhone Settings. Native notification delivery requires an active sign-in session and current workspace access.
Your personal planning and daily records
If you use personal planning, Crew It Up stores the preferences you save: your home airport, commute and recovery buffer, sleep opportunity goal, preparation time before report, family-time window, and project duration. It also stores tentative family, project, or recovery plans with their date, times, and title.
Optional energy check-ins record how your energy compares with your usual level and any category you select for context, such as sleep, night duty, workload, or personal circumstances. Daily logs can contain the sleep, family, and personal hours and short note you enter. Missing records remain unknown; a suggested window is not a record of actual sleep or time spent with others.
These records are stored per account and workspace in Cloudflare D1, alongside your roster data. Other workspace members cannot view your personal planning records or daily logs through the app. You can change your preferences, remove saved plans, update check-ins, and update or remove daily logs. Saving these records does not change your roster source or Google Calendar events.
Your sleep diary and crew health context
Insights can store the main sleep and nap intervals you enter, your explicit observation-coverage confirmations, your crew role and operation, and optional private duty-context notes. These records are stored per account and workspace in Cloudflare D1. Other workspace members cannot read them through the app. They are separate from the existing daily sleep totals used by candidate models; no episode times are invented from daily totals.
Sleep episodes, coverage and duty-context notes are not added to the offline device copy. You can edit or remove episodes and clear the diary and context notes in the orb → Regulatory → Sources & Privacy. Clearing these records keeps your crew profile, existing daily totals, energy check-ins and saved plans. Emptying a context note removes that note. Deletion from the app cannot be undone.
The report preview contains only the fields you select. Copying it places that text on your device clipboard, where your device's clipboard features may retain or sync it. Crew It Up does not send the report, select an employer recipient or issue background health notifications. You decide whether to share the copied text.
Optional calendar subscription links
When you connect an Apple or other supported iCalendar subscription, Crew It Up reads the feed on the refresh interval you select. Subscription URLs can grant access to calendar data: we store them encrypted on the server and do not include them in roster responses or offline storage. Imported event source stays in source-record storage; public roster views receive derived fields and calendar timing only.
You can pause refresh or disconnect in Settings. Disconnecting removes the saved URL and stops future fetches; imported roster records and source history are retained. This integration never changes events in the source calendar.
Offline access on this device
While you are signed in, Crew It Up saves a device copy of your roster so you can reopen the app without internet. Crew copies also include daily logs, planning preferences and saved plans; Family copies include only the shared roster and permitted completed flight paths. The roster covers the previous 31 days and next 30 days. The saved view shows when it was downloaded and is read-only. It contains no Google access tokens or original imported source descriptions.
This copy remains available on this browser or installed app until you sign out, change account or workspace, remove it in the saved view's Settings, or clear browser storage. Anyone with access to this device and browser can open the saved view. Device copies do not receive updates or access changes while disconnected. Browser storage management can also remove them.
Completed flight paths download during an online sync without requiring you to open the map. Each path keeps its provider and expiry time. Live aircraft observations are not saved as an offline live feed. An open app removes expired paths; a closed or suspended device can perform this cleanup only when the app runs again. Each device must reconnect to receive newer paths or access changes.
Services used to provide the app
Cloudflare hosts Crew It Up and its application database, D1. Clerk handles authentication and the connected Google account. Google processes the sign-in and Calendar permission requests. These services process information needed to provide those functions. Imported event data, daily logs, and saved personal planning information are stored in Cloudflare D1.
You can read more in the Clerk privacy policy, Cloudflare privacy policy, and Google privacy policy.
Aircraft observations
Aircraft observations use the provider enabled for the background recorder. Supported sources include Flightradar24 under its API terms of service and ADSB.lolunder the Open Database License (ODbL 1.0). Requested flight numbers, callsigns, aircraft registrations, transponder identifiers or airport areas are sent through our server to the enabled provider. Provider credentials remain on the server. Your account identity, workspace identifier and roster source documents are not sent with these requests.
Observations are cached briefly on Cloudflare, separately from your roster. Their timestamps and any stale or missing information stay explicit. These observations do not change your roster times or candidate calculations. The app uses provider APIs and does not depend on a home receiver. Source links on each map identify the provider of its observations; changing provider does not relabel older saved paths.
Supported flights in saved Crew rosters are recorded automatically by our server, including while the app is closed. No map opening or Save action is required. Flightradar24 collection normally runs every 15 minutes. Opening a shared Family flight map requests a fresh position through the same server recorder and targets 30-second updates while the map is visible. Short-lived viewing sessions expire after a disconnect; multiple viewers share one collector and its provider limits. Maps read the observations saved by that recorder. Matching uses the stored flight number, airline, dated sector and route context; it is not an airline assignment or confirmed flight status. A bounded matching buffer is kept separately in D1. Captured ADSB.lol paths expire 90 days after scheduled arrival. Flightradar24 paths expire no later than 30 days after first receipt, following its storage rules. Syncing or opening a path does not extend its expiry. A saved path keeps its original route and schedule when the roster is later corrected. Expired paths are unavailable immediately and removed by hourly cleanup. Deleting the linked roster entry also removes its saved paths.
Automatic collection starts before roster departure and continues through the flight tracking window, subject to provider availability and a supported aircraft match. Reception gaps, unmatched callsigns, late roster imports and service limits can leave missing positions; a complete flight path cannot be guaranteed. Opening a saved path reads that archive without requesting current aircraft observations. When aircraft sharing is enabled, currently connected Family & Friends can see saved observations during the flight and completed paths for the current shared sector. Crew sees completed paths, including permitted earlier schedule versions. Family responses omit aircraft identifiers, operational details and source-record provenance. The app provides these roster-linked views; it does not offer redistribution or export of the provider’s raw aircraft feed.
After Flightradar24 reports a completed flight, we retrieve its post-flight summary and historical observations. Crew can view the saved actual takeoff and landing times, airborne duration, distances, aircraft, airline, airports and runways where supplied. Missing values remain unavailable; these provider observations do not replace your roster or logbook. The summary shares the saved route’s expiry and deletion rules and is included in the Crew device’s completed-flight offline download. Operational summary details are omitted from Family responses and downloads.
We use each dated roster flight's number, route and times to automatically look for its aircraft in Flightradar24. When the aircraft can be identified, the same shared collector requests its registration's position to show the incoming status. Registration is not entered manually. Ground status and calculated arrival estimates are labelled as position-derived; unavailable assignments and old observations remain explicit. The matched registration and latest incoming status are stored separately from your roster source, expire within 30 days, and are removed with the linked roster entry. A changed aircraft clears the previous cached status. Incoming aircraft details are Crew-only and are not included in Family responses or offline downloads.
When you choose Find registration for a future roster flight, our server sends its flight number, route, scheduled departure and departure-airport date to Google's paid Gemini API with Google Search. Your account identity, workspace identifier and submitted roster documents are not included. The answer, its sources and Google Search suggestions appear together for your review, under Google's Gemini API terms. Searches run only when requested and may return no registration or information that is out of date. These answers are not used to set an aircraft assignment, trigger a swap alert or establish live arrival status.
Search answers remain in the open view and are not saved to our database, offline storage or Family views. Our shared spending guard stores only anonymous request times and estimated charges for a rolling 31-day window; expired accounting records are removed when another lookup is requested. Credentials remain on the server.
Aircraft tracking is a separate, optional Family & Friends sharing choice in Settings, off by default. When enabled, connected viewers can open maps for shared roster flights. Turning it off stops further tracking reads without removing their shared roster. Removing family access also stops tracking access. These maps show aircraft observations, not a crew member’s personal location.
Airport reference data
Airport names and locations come from OurAirports. Time zones use timezone-boundary-builder (© OpenStreetMap contributors) and mwgg/Airports. This reference is bundled with the app; airport lookups do not send your roster or device location to these sources.
The combined airport directory is available under the Open Database License. See its source credits and licence notices.
Changing Google permissions
You can review or revoke Crew It Up's Google access in your Google Account connections. Revoking Calendar access prevents further Calendar reads using that permission. Previously imported roster records and their source history remain in Crew It Up.
Questions about your information
For questions about information stored in Crew It Up, or to ask about access or deletion of your workspace records, contact palprthi@gmail.com.