Set up your bannerConfigure Your ToolsGoogle Services

Google OAuth (Sign in with Google)

How to configure Google OAuth (Sign in with Google) at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Unlock additional website features

Overview

This guide explains how to implement different privacy configurations for Sign in with Google and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. This guide covers Sign in with Google for websites, built on the Google Identity Services (GIS) JavaScript library (accounts.google.com/gsi/client): the personalised button, One Tap and automatic sign-in. Server-side OAuth authorisation for access to Google APIs is out of scope.

What the service does in this scope. The library renders the button and One Tap prompt in iframes served from accounts.google.com. When the visitor signs in, Google returns an ID token to the site. GIS integrates the browser's Federated Credential Management (FedCM) API as a privacy-preserving alternative to third-party cookies. Without FedCM, the signed-out state used to prevent automatic sign-in loops is stored in a cookie (g_state).

Configurations included.

ConfigurationSummary
Configuration A — Lower riskButton only, on the login page, loaded after consent; FedCM enabled; no One Tap, no automatic sign-in.
Configuration B — Medium riskOne Tap prompt and automatic sign-in (data-auto_select="true") on all pages, loaded after consent.

Consent. Loading the library contacts Google's account domain in the visitor's browser before any sign-in decision. Load it only after consent (or on an explicit click on a placeholder button), so that Google is not contacted for visitors who do not use the sign-in.

ActionConfiguration A — Lower riskConfiguration B — Medium risk
Where the library loadsLogin page onlyEvery page
One Tap / automatic sign-inOffOn
FedCMEnabledEnabled
Consenter Manager entriesOne entry (Google as Individual Controller)One entry (Google as Individual Controller)

Step 1 — Configure Sign in with Google

#Configuration areaWhere to configure itConfiguration A — Lower riskConfiguration B — Medium risk
1Processing purposesOperator decisionUnlock additional website features (account sign-in)Same
2Library loading<script src="https://accounts.google.com/gsi/client" async> on pages where sign-in is offeredLogin page only, after consentAll pages, after consent
3One Tapg_id_onload element / google.accounts.id.promptNot usedUsed
4Automatic sign-indata-auto_select="true"OffOn
5Sign-out handlingg_id_signout class or google.accounts.id.disableAutoSelectNot neededRequired
6FedCMuse_fedcm_for_prompt / FedCM migration settingsEnabledEnabled
7Consent screen privacy policy linkGoogle Cloud console > OAuth consent screen > Application Privacy Policy linkSetSet

Step 2 — Map the configuration in the Consenter Manager

Processing location. Google LLC is a US company and can be required to disclose data in its possession, custody or control regardless of storage location.

Configuration A — Lower risk

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesUnlock additional website featuresSign-in with an existing Google account.
Tracking methodNo trackingNo identifier is set by the site's integration when FedCM is used.
IdentifierIP address, Authentication-derived identifiersIP address on loading; ID token after sign-in.
Data categoriesIP address, Device characteristics, Authentication-derived identifiers, direct identifierThe ID token contains the Google account identifier and, depending on scopes, name and email address.
Legal role of data recipientIndividual ControllerGoogle operates the Google account and authenticates the user on its own terms.
Personalisation modelNo personalisation—
Maximum storage durationNot documentedGoogle account data is retained under Google's own policies.
Processing locationUnited States as potential processing and access locationSee note above.

Configuration B — Medium risk

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesUnlock additional website featuresAs A.
Tracking methodThird party tracking (crosssession, cross-website)On every page, Google's account domain recognises signed-in Google users to show One Tap; without FedCM the g_state cookie is used.
IdentifierIP address, Authentication-derived identifiersAs A.
Data categoriesIP address, Device characteristics, Authentication-derived identifiers, direct identifier, Browsing and interaction dataGoogle learns on which pages the prompt is shown.
Legal role of data recipientIndividual ControllerAs A.
Personalisation modelNo personalisation—
Maximum storage durationNot documented—
Processing locationUnited States as potential processing and access locationSee note above.

Privacy-policy follow-up

  • Google as independent controller for the Google account; data exchanged at sign-in; One Tap and automatic sign-in (B); US transfer and potential access by US authorities.

Verification checklist

  • No request to accounts.google.com/gsi before consent (or before the click).
  • A: library only on the login page; no One Tap prompt.
  • B: sign-out disables automatic sign-in.

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page