Single-user Tasks read-only desktop app: publishing blocked by unspecified Branding requirements

Hello,

I use a desktop OAuth app solely to read my own Google Tasks for a personal report. It has one user—me—and requests only https://www.googleapis.com/auth/tasks.readonly.

The app is External and currently in Testing. Its app name, user support email, and developer contact email are populated and saved. It has no logo, website, privacy-policy URL, terms URL, or authorized domain.

On the Audience page, Publish app is disabled. The message says I must complete the Branding configuration, but Branding shows no field-level errors or pending changes.

I want to move the publishing status to In production to avoid Testing’s seven-day authorization expiration. I do not intend to distribute the app or expand its permissions.

Google’s OAuth policy excludes personal-use apps from its definition of production apps, and the verification guidance describes a personal-use exemption. Could you clarify:

  1. Is there a supported way to enable Publish app for this personal-use app without creating a website or completing full OAuth verification?
  2. Which exact Branding field or requirement is blocking publication?
  3. If website URLs or domain verification are mandatory even for this personal-use case, which requirement applies, and what is the simplest supported remedy?

Please distinguish publishing status from brand verification and sensitive-scope verification.

References:

Thank you.