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