Information we collect
We collect the information needed to provide and secure the service, which may include:
- Account and profile details such as name, email address, login and employee identifiers, domicile, seat, and fleet.
- Schedule, trip, bidding, calendar, logbook, crew, aircraft, flight-time, and related records that you upload, enter, or create in the service.
- Pay and compensation records, including payroll statements, check details, pay-period credits, and calculated reconciliations that you choose to upload or maintain.
- Fatigue records, including fatigue calls and rest or sleep dates, times, duration, and quality that you choose to record.
- ACARS images, schedule or JCT documents, extracted flight times, messages, screenshots, and diagnostic context that you choose to upload or send through support reporting.
- Operational information such as sign-in activity, an app-generated device identifier, device or browser details, IP address, app version and build, diagnostic logs, and feature usage.
Native app and offline data
The native scheduling app downloads authorized schedule, trip, logbook, pay, and related account information to private app storage so those features remain available offline. Pending changes, selected documents or images, and support reports may also remain on the device until they synchronize or you remove them.
Authentication tokens are stored using the device's secure credential storage. Face ID evaluation is performed by iOS; Flight Crew Admin does not receive or store your biometric template.
Documents, images, fatigue entries, schedule changes, and support diagnostics are transmitted only when you use the related feature or when an item you saved for synchronization is sent after connectivity returns. Diagnostic context in a support report is included only when you select that option.
Google user data
When you connect Google Calendar, Flight Crew Admin receives OAuth access and refresh tokens, the name and ID of the Google Calendar used for synchronization, and Calendar event data needed to identify synchronized events.
The recommended setup asks Google to create a separate calendar, named Flight Crew Admin by default, and grants the service permission to create, read, update, and delete events on calendars it creates. If you instead use the Advanced option to provide an existing Google Calendar ID, the service requests permission to manage events and uses that permission to synchronize schedule events with the calendar you selected.
Google user data is used only to provide the calendar synchronization you request: finding corresponding schedule events and creating, updating, or removing those events. We do not use Google user data for advertising, sell it, use it to determine creditworthiness, or use it to train general-purpose artificial intelligence models.
Flight Crew Admin's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
How information is used
- Provide schedule, bidding, trip, pay, fatigue, logbook, calendar, support, and account features.
- Authenticate users, protect accounts, prevent abuse, and troubleshoot failures.
- Maintain, improve, and communicate about the service.
- Comply with legal obligations and enforce the Terms of Use.
Sharing
We do not sell personal information. Information may be processed by infrastructure and service providers only as needed to operate the service, such as cloud hosting, email delivery, and Google when you use Google Calendar. We may also disclose information when required by law or when reasonably necessary to protect users, the service, or others.
Storage, security, and retention
Account data and Google OAuth tokens are stored in access-controlled service databases. Native app session tokens are stored in the device's secure credential storage, while offline feature data is stored in private app storage. We use reasonable administrative and technical safeguards, but no online service can guarantee absolute security.
We retain information while your account is active and as reasonably needed to provide the service, maintain security and backups, resolve disputes, or meet legal obligations. Backup copies may persist for a limited period before they are overwritten or deleted.
Support screenshots, schedule PDFs, and submitted workflow context are stored privately for troubleshooting. Support attachments are removed after the configured post-resolution retention period. Reports and attachments associated with your account are removed when the account is deleted.
Account deletion and data removal
You can disconnect Google from your Profile or Calendar Export page. Disconnecting removes the stored Google OAuth tokens from the active account database and attempts to revoke the Google authorization. You can also remove the application's access from your Google Account security settings. Disconnecting does not delete the Google calendar or its events from your Google account.
You can permanently delete your Flight Crew Admin account from Profile on the website, including from the Delete Account link in the native app. Account deletion requires your current password, attempts to revoke any saved Google authorization, and removes your account, profile, schedule, bidding, pay, fatigue, support, calendar settings, conflict, and other user-owned records from the active application database. Account deletion does not delete an app-created or selected calendar, or its events, from Google Calendar.
To remove offline copies stored on an iPhone or iPad, sign out of the native app. If the server account has already been deleted and the app can no longer verify it, use Delete Saved Data on the sign-in screen.
After deletion, Flight Crew Admin does not keep a usable copy of your information in the active application, and no new account information is saved unless you later create a new account. Limited backup copies may remain temporarily until the normal backup cycle overwrites or deletes them.
To request help with access, correction, or deletion, contact pilottripadmin@gmail.com.
Changes to this policy
We may update this policy as the service changes. The effective date above will be revised when material changes are published.
Contact
Questions about privacy or Google user data can be sent to pilottripadmin@gmail.com.