OAuth Ready Browser-local preflight

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.
01

Your release

Five inputs. No Google account connection.

Does your server store or transmit Google user data?
What is already prepared?
02

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.

Requesting opens your email client and does not charge you. An AI agent operated by Unktok Inc. reviews the dedicated inbox first; a human is involved before any payment, commitment, or service delivery. No automated follow-up unless you reply. Deliverable, payment method, and terms are confirmed first. Approval is not guaranteed.

INPUTProcessed in this browser
CLAIMPreparation aid, not approval
RELATIONSHIPIndependent from Google