Google access disclosure

Exactly what SurfStats Studio asks Google for

Normal Sign in with Google is used only to authenticate your SurfStats Studio account. It requests the basic identity scopes openid, profile, and email. It does not request YouTube, Google Drive, Gmail, Calendar, upload, publishing, edit, or delete permissions.

Current sign-in scopes
Basic identity only
openid profile email

Google access/refresh tokens saved by normal sign-in
No
Current implementation

What is received, retained, and not requested

Received for sign-in

  • Google account identifier
  • Primary email address
  • Basic profile name when Google supplies it
  • Email-verification status used during authentication when available

Retained by SurfStats

  • Your SurfStats user/account record
  • Your email and display name
  • The external Google account identifier needed to recognize future Google sign-ins
  • Normal Google access/refresh tokens are not persisted by the sign-in handler

Not requested at login

  • YouTube channel or Analytics access
  • YouTube upload, publish, edit, or delete permissions
  • Google Drive files
  • Gmail messages
  • Google Calendar data
  • Background Google account-management permissions
Sign-in flow

What happens when you choose Google

1
You choose Sign in with Google
SurfStats starts Google's authentication flow. Google is shown as a separate sign-in option; email/password remains available.
2
Google asks for basic identity consent
The configured scope list is limited to openid, profile, and email. SurfStats also requests Google's account chooser so users can select the intended account.
3
SurfStats validates the returned identity
SurfStats requires a usable Google account identifier and primary email and rejects an explicitly unverified email response.
4
Your SurfStats session is created
SurfStats creates or finds the matching account/workspace and signs you into SurfStats. The temporary external-authentication cookie is then cleared.
Reviewer facts

Google OAuth implementation summary

Purpose
Account authentication
Scopes
openid profile email
Callback path
/signin-google
Token persistence
Disabled for normal Google Sign-In
YouTube OAuth
Disabled in this build
Drive/Gmail/Calendar
Not requested

Open app/reviewer information
YouTube separation

Google Sign-In is not YouTube access

The current build keeps YouTube channel OAuth disabled. You can create scripts, images, thumbnails, audio, clips, videos, ads, and campaigns without connecting a YouTube account.

SurfStats' Publishing Hub can organize delivery, approvals, and record live URLs/results. Its presence does not grant SurfStats YouTube permissions and does not change the Google Sign-In scopes above.

Read YouTube Data Use
Future integrations

Additional permissions require a separate choice

If SurfStats later enables a Google or YouTube feature that needs additional scopes, it should be presented as a separate connection action with the exact permission and purpose explained before consent. Those permissions should not be silently added to normal account sign-in.

User control

How you control Google-related data

Review Settings

See whether Google sign-in is linked and access the connected-data controls.

Open Settings

Remove connected channel data

The Settings cleanup control removes stored connected Google/YouTube channel tokens and related channel data if any exist. It does not by itself delete your SurfStats account.

Delete your account

Delete the SurfStats account and stored account/project data through the in-app deletion control.

Deletion instructions

Revoke at Google

You can remove SurfStats from the permissions attached to your Google Account at any time.

Google permissions
Limited Use

Google API data commitments

SurfStats Studio's use and transfer of information received from Google APIs is intended to follow Google's applicable user-data and Limited Use requirements.

  • Google user data is not sold.
  • Google user data is not used for advertising.
  • Google API data is not used to train generalized AI or machine-learning models.
  • Human access is limited to support, security, abuse prevention, legal compliance, or help requested by the user.
Security & retention

Account data is kept only for the service

SurfStats stores the account information needed to provide account access and the projects/workspaces you choose to keep. Normal Google Sign-In access and refresh tokens are not persisted by the Google authentication handler.

Separate connected-channel credentials, if present from legacy or future optional integrations, are handled through the connected-data deletion/revocation controls. See the Privacy Policy for broader retention and security information.

Frequently asked questions

Google access FAQ

No. Normal Google Sign-In requests only openid, profile, and email. YouTube OAuth is disabled in this build.

Not for normal Google Sign-In. The Google authentication handler is configured with token persistence disabled. SurfStats retains the external account identifier and account information needed to recognize your login.

No. Those scopes are not requested by the current Google Sign-In configuration.

Yes. SurfStats also supports its normal email/password account flow.

No YouTube permission is granted by normal Google Sign-In. In the current build, Publishing Hub organizes approved delivery and records publishing results/live URLs; it does not turn basic Google authentication into YouTube channel access.

You can revoke SurfStats from your Google Account permissions page. You can also use SurfStats Settings to remove connected Google/YouTube channel data, and use the account-deletion controls when you want to delete your SurfStats account and stored data.

Any feature requiring additional Google scopes should use a separate explicit connection/consent step and explain the additional permissions before you authorize them.

Use the public Support page and identify the request as a Google access, OAuth, privacy, or data-deletion question.