Legal

Privacy Policy

How Crew handles your account, your flights, and, if you choose to connect it, your Gmail.

Draft for owner review

This policy is a working draft. It has not been reviewed by legal counsel and is not final. The operator's legal identity and data-retention details still need owner confirmation before publication or Google verification.

1. What Crew stores

2. Optional Gmail import

Connecting Gmail is optional and separate from signing in to Crew with Google. Each signed-in user chooses their own mailbox and grants permission on Google's consent screen. You can use Crew without connecting Gmail.

Permission requested: https://www.googleapis.com/auth/gmail.readonly. This permission allows read-only access to Gmail messages and mailbox information; it does not permit Crew to send, edit, or delete email. The scope is broader than a flight-only permission because Google does not provide a flight-confirmation-only Gmail scope. Crew's importer limits its requests to the workflow below.

How Crew uses this information

3. Google API Services: Limited Use

Crew's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

4. Sharing with friends

Flight visibility follows your audience and trip-sharing selections. Friends you exclude cannot view the affected flights, including through shared trip groups. Imported flights are saved with a private audience unless you subsequently share them or explicitly contribute them to a shared trip. Sharing an imported flight does not share your Gmail messages, mailbox address, or Google credentials with friends.

Service providers and website visits

Crew uses service providers for hosting and database storage, account authentication, flight information, and push notification delivery. These include Replit, Clerk, FlightAware, Expo, and Apple. Google provides the optional Gmail connection. Providers receive information needed to perform their functions; raw Gmail messages are not sent to the flight-information provider by the import pipeline.

The Gmail-import backend runs on Replit. Clerk stores the encrypted Gmail connection in your account's private metadata; it is not included in the public profile or shared flight data. The importer does not send raw Gmail message bodies to advertising services or an external AI service.

Visiting this website may generate technical request logs, such as browser and network information. This website loads fonts from Google Fonts, which receives the browser requests needed to deliver those fonts.

Storage, retention, and deletion

The retention and erasure rules for unlinked imported-flight records, technical logs, and service-provider backups still require owner confirmation before this draft can be finalized. No fixed backup-deletion deadline is represented here.

5. Security

Google authorization and Gmail API requests use HTTPS. Stored Gmail connection information is encrypted on the server using AES-256-GCM before being written to private account metadata. Gmail imports require an authenticated Crew account, and the authorization response is bound to the account that initiated it. No method of storage or transmission is completely secure, and we cannot guarantee absolute security.

6. Your controls

Disconnecting Gmail requests revocation of the Google grant and removes the stored Gmail connection. For privacy, access, correction, or deletion questions, contact the support address below. We may need to confirm your account identity before handling a request.

7. Changes to this policy

If this policy changes materially, we will update this page and, where appropriate, notify you in the app.

8. Contact

For privacy questions or support, contact jusleen1114@gmail.com.

Owner action required. The legal operator's identity and data-retention details still need confirmation before publication or Google verification.