OAuth branding verification stuck — "homepage purpose" + "app name mismatch" — findings unchanged after fixes, no Trust & Safety email received

My OAuth branding verification is stuck with the same two findings, unchanged

across multiple resubmissions, even after fixing everything they describe:

1. "Your homepage does not explain the purpose of your app."

2. "The app name 'PowerFlowGEX' configured for your OAuth consent screen does

not match the app name on your homepage."

`Project name: (PII Removed by Staff)

`Project ID / Project Number: (PII Removed by Staff)

`Registered homepage: (URL Removed by Staff)

Scopes requested: userinfo.email, userinfo.profile, youtube.readonly

What I've verified and fixed, each time re-confirmed before resubmitting:

- Homepage <title>, <h1>, application-name, apple-mobile-web-app-title,

og:site_name, og:title and twitter:title all say exactly "PowerFlowGEX",

matching the OAuth consent screen App name field exactly (plain text, no

HTML tags splitting the string).

- Homepage explicitly explains the app's purpose (what it does, for whom)

and separately explains why it requests each piece of user data (Google

account to identify the user and save their configuration; YouTube

subscription check — read-only, to confirm the user is subscribed to our

channel as an access requirement, nothing else is read from their YouTube

account).

- HTTP 200, no redirects, publicly accessible without any login wall.

- Privacy Policy (https://gex.powerflowsuite.com/privacidad.php) and Terms

of Service (https://gex.powerflowsuite.com/terminos.php) both resolve

correctly on the same domain, matching the URLs configured on the consent

screen exactly.

- Domain powerflowsuite.com is verified in Search Console.

Despite the above, resubmitting returns the identical two findings every

time. I never received any Trust & Safety email (checked inbox, spam, and

all folders on the developer contact address). The appeal ("the finding is

incorrect") was also instantly rejected pointing back to that non-existent

email thread.

I found other reports of this exact same pattern in this forum (identical

wording, unrelated tech stacks, no email thread ever created), where

posting here appears to have prompted a manual review that resolved it.

Could someone from the team manually re-check the current live homepage, or

help me reach Trust & Safety given no email thread exists?

Thank you.

1 Like