Signing In with Google

AeroCopilot supports signing in and signing up with your Google account, powered by the Better Auth authentication layer. This is the only third-party social provider currently enabled on the platform — the OAuth provider list (NEXT_PUBLIC_AUTH_OAUTH_PROVIDERS) is configured to google.

What you see on the sign-in screen

On both the sign-in and sign-up pages, in addition to the email-and-password form, you will see a "Continue with Google" button. Selecting it triggers the standard Google OAuth2 consent flow:

1. You are redirected to Google's accounts.google.com consent screen.
2. Google displays the AeroCopilot OAuth client name and the scopes being requested (your basic profile and email address).
3. After you approve, Google redirects you back to AeroCopilot.
4. Better Auth completes the token exchange, creates a session, and either signs you in to your existing account or provisions a new one.

You do not need to enter a password when using Google sign-in. Your AeroCopilot account is bound to your Google account ID; signing out and signing back in with the same Google account always lands you in the same AeroCopilot account.

When to use Google sign-in

Google sign-in is the fastest path for pilots who already use Gmail, Google Workspace, or another Google product. It avoids creating and remembering a separate AeroCopilot password. It also inherits the security posture of your Google account — including any two-factor authentication, hardware security keys, or device-trust policies you have enabled there.

If you sign up with Google and later want to sign in with email and password instead, you can set a password from your account settings and use either method afterward.

Account linking

If you initially signed up with email and password, then later choose Continue with Google using the same email address, Better Auth will link the Google identity to your existing AeroCopilot account rather than creating a duplicate. Both methods will then work for that account.

Privacy and data shared with AeroCopilot

The only data AeroCopilot receives from Google is the standard OpenID profile payload:

• Your email address
• Your display name
• Your profile picture URL (if set)

AeroCopilot does not request access to your Gmail, Google Drive, Google Calendar, Google Contacts, or any other Google service. No Google API tokens beyond the initial sign-in token are stored, and no background access to your Google data is performed.

Revoking access

You can revoke AeroCopilot's access to your Google account at any time from your Google account settings, under Security → Third-party apps with account access. Revoking access from Google's side will not delete your AeroCopilot account or your data — it only prevents future Google sign-ins. If you also want to delete your AeroCopilot account, do so from the AeroCopilot account settings page.

Troubleshooting

If the Continue with Google button is missing, the deployment you are using has not enabled the Google provider in NEXT_PUBLIC_AUTH_OAUTH_PROVIDERS. Self-hosted operators should set that environment variable and configure the corresponding Better Auth Google client credentials.

If sign-in fails after Google consent, the most common cause is a mismatch between the OAuth callback URL configured in the Google Cloud Console and the deployment URL. The callback URL must match exactly, including the protocol (https://) and the trailing path expected by Better Auth.

Related

• API Library Overview
• Account Settings
• Sign-Up Flow