Before you submit to Google

Find the missing pieces in your OAuth release.

Enter scopes and release context. Get a conservative route, the artifacts to prepare, and the official sources to verify.

Do not paste secrets. Use scope strings and public URLs only. Never enter a client secret, token, password, private code, or user data.

Your release

Five inputs. No Google account connection.

App audience Release state Expected users

Does your server store or transmit Google user data? No / browser or device only Yes / server or third party Not sure

Requested scopes One per line or separated by spaces. Unknown scopes stay unknown.

What is already prepared? Public homepage explains the app Public privacy policy is linked from the homepage Authorized domain ownership is verified Console name and branding match the live app Demo shows consent and every requested scope in use Production code and Console request the same scopes

LIKELY ROUTE

Add your scopes to begin

Not assessed

Your result will distinguish self-reported checks, possible gaps, manual review, and items outside this preflight.

Prepare

OAuth consent screen details
Production homepage and privacy policy
A demo that shows how each scope is used

Verify manually

Scope classification in Cloud Console
Authorized domains and redirect URIs
What the production build actually does

Next action Paste the exact scopes requested by your production client.

FOUNDING PILOT

A human-reviewed submission packet — $99 if accepted.

Receive a scope-to-feature map, homepage and privacy consistency review, reviewer-demo storyboard, and prioritized gap list.

Requests are temporarily paused while we establish a dedicated service inbox. When reopened, requesting the pilot will not charge you; deliverable, payment method, and terms will be confirmed first. Approval is not guaranteed.

INPUTProcessed in this browser

CLAIMPreparation aid, not approval

RELATIONSHIPIndependent from Google