Legacy Google Sign-In

Some websites still use legacy Google Sign-In which requires the use of privacy-harmful 3rd party cookies. Brave blocks third-party cookies by default, but if you try to login to a (rare) website that still requires 3rd party cookies for Google Sign-In, Brave will ask if you want to proceed via a permission prompt. See our blog post for more details on this feature.

Extensions

If you navigate to brave://settings/extensions on Desktop, you will see an option to enable Allow Google login for extensions:

When this option is enabled: It enables chrome.identity for extensions so extensions can retrieve an OAuth token from google to authenticate users. The OAuth token can be used to retrieve personal information like email id, profile. Please note that this is considered a 3rd party login. Extensions such as Google Keep may require a 1st party login (performed in Google Chrome) and may not work (see here for more information). You can read more about chrome.identity here: https://developer.chrome.com/apps/identity.

If you are not logged into Google, these options have no effect for you.