Google OAuth

Sign in or sign up to Feedjolt with Google. Link Google to an existing magic-link account, manage scopes, and unlink anytime from your profile settings.

Continue with Google lets you sign in (or sign up) using a Google account.

How it works

Click Continue with Google at /login or /register.
Pick a Google account on Google's screen.
Approve the requested scopes (just email and profile).
Google redirects back to Feedjolt; you're signed in.

The OAuth flow uses Google's standard authorization-code-with-PKCE handshake. Tokens are exchanged server-side and never exposed to your browser.

What we access

Just two things:

Your email address - to identify you and send notifications.
Your basic profile - name and avatar (we don't pull your contacts, calendar, or any other data).

We don't store Google access or refresh tokens. We use Google for authentication only, not for ongoing API access.

Linking Google to an existing account

If you signed up via magic link first and want to add Google as a sign-in method:

Dashboard -> Settings -> Profile -> Sign-in methods.
Click Connect Google.
Approve.

The Google account is now linked. Either method (magic link or Google) signs you into the same account.

If you click "Continue with Google" with a Google email that already has a Feedjolt account via magic link, the two are linked automatically. You don't need to manually connect.

Unlinking Google

Settings -> Profile -> Sign-in methods -> Disconnect Google.

You must have at least one sign-in method active. If Google is your only one, add magic link first (i.e., have any email confirmation flow).

Trouble?

"This email is already in use." It is - via magic link. Sign in with magic link first, then connect Google.
Google says "this app isn't verified." Feedjolt is verified. If you see this, you might be on a different domain. Make sure you're at feedjolt.com.
Wrong Google account selected. Sign out of Google in another tab and try again.

Security notes

We use Google's email_verified flag - accounts with unverified emails are rejected.
Account linking by email match is a known phishing vector for poorly-implemented auth. We mitigate by only linking when Google's email_verified=true and only on first OAuth sign-in.