Supported production OAuth setup for a single-user private CRM using the owner's Gmail account

We run a privately hosted Windows/Node.js CRM for one business owner, connecting only that owner’s existing consumer gmail.com mailbox. It is not a multi-tenant product or a public sign-up service.

The integration already uses the official Gmail API and a Desktop OAuth client with the existing gmail.readonly and gmail.send scopes (sending is individually confirmed by the owner). The OAuth application is External / Testing. A refresh attempt recently returned HTTP400 invalid_grant, expired_or_revoked; normal same-client reauthorization restored receiving. We understand that Testing refresh tokens with Gmail scopes have a seven-day lifetime, and want the supported durable setup rather than repeated reauthorization.

  1. Does Google’s personal-use verification exception apply to this single-owner, own-business-mailbox CRM, or does the business use require a different verification route despite there being only one user?
  2. Is moving to In production and then reauthorizing the existing Desktop client the supported way to remove the Testing-specific seven-day expiry, while retaining ordinary revocation/security controls and the same scopes?
  3. Audience → Publish app is disabled with a request to complete Branding. App name, support email and developer contact are populated; homepage/privacy-policy/terms URLs and authorised domains are blank. Which fields are actually required for this private, single-user production setup? Is a public app homepage/privacy disclosure required even if the verification exception applies?
  4. Is there a simpler officially supported Gmail integration route for this kind of private CRM? We are not seeking to reuse ChatGPT/Claude connector tokens or bypass OAuth.

Please point us to the applicable Google documentation or the correct specialist support channel. No tokens, client secrets, project/account IDs or email contents are included here.

I am experiencing the same publishing blocker with a desktop app used only by me, connecting only my own Gmail account.

Google Auth Platform has an External audience and Testing publishing status. The app name, user support email, and developer contact email are saved. There is no app logo. Homepage, privacy-policy, terms URLs, and authorized domains are blank. Publish app is disabled with: “To publish your app, you must complete your configuration on the Branding page.” Re-saving Branding and refreshing the console did not enable it.

Google’s OAuth 2.0 policy excludes personal-use apps from its definition of production apps for some requirements, and the verification documentation describes a personal-use exemption. What is the supported way to change the publishing status to In production for this exempt single-user desktop app, without publishing a website or policy page? Which exact Branding fields are mandatory in the current console, and is there a support route if the UI prevents this?

The aim is to remove the Testing-specific seven-day refresh-token expiration, while keeping ordinary Google authorization and revocation controls. No credentials, project identifiers, email contents, or client data are included here.