I maintain a private local Desktop OAuth application used exclusively with my own Google account. It reads a fixed Google Sheets master register using only this scope:
https://www.googleapis.com/auth/spreadsheets.readonly
The application is not commercially distributed and does not offer a public service. Credentials are stored in the macOS Keychain and access tokens are renewed locally.
Current configuration:
- OAuth client type: Desktop.
- Audience: External.
- Publishing status: Testing.
- One test user: my own account.
- App name, support email and developer contact email are populated and saved.
- No logo, homepage, privacy-policy URL, terms URL or authorized domain is configured.
- “Publish app” is disabled with a message to complete Branding, but no field-specific validation error appears.
- Authorization and refresh work, but Testing imposes the seven-day lifetime.
Google’s OAuth documentation provides a personal-use exception to verification requirements. The Branding help also says URLs are required for external production apps. I would like to clarify the supported configuration for this private, single-user Desktop case:
- Are public homepage, privacy-policy and terms URLs mandatory to switch to In production despite the personal-use verification exception?
- Which exact field or completion state causes “Publish app” to remain disabled?
- Is there an official way to remove Testing’s seven-day authorization lifetime without publishing a website or replacing the existing OAuth client?
- If public pages are required, is a free Firebase Hosting subdomain with ownership verified in Search Console acceptable, or is a separately registered domain required?
- After switching to In production, must I repeat consent to replace a refresh token originally issued in Testing?
Please provide the applicable official procedure. This request contains no credentials, account identifiers, client IDs or private application data.