Hello,
Project number: (PII Removed by Staff)
Project ID: (PII Removed by Staff)
App name: Uplace
Homepage: (URL Removed by Staff)
Summary
The blocking step for us is the branding verification, not the scope review. Our brand verification was approved on 17 August 2026 (confirmation email from the Third Party Data Safety Team, subject “API OAuth Dev Verification”), after a previous thread in this category where the exact same false finding was cleared through a manual re-review. Thank you again for that.
As instructed (“You will need to submit a new verification request for access to new scopes”), we then submitted a new verification request to add the Google Calendar scopes. The branding check was rejected almost immediately with the identical finding as before:
“The app name shown on your OAuth consent screen does not match the app name on your home page.”
So the request never reaches the scope review stage. Everything is blocked on a branding finding that was already examined and approved.
Why this finding is incorrect
- Nothing changed on the OAuth consent screen branding or on the homepage between the 17 August approval and this new submission. Only the scope list changed.
- The consent screen app name is “Uplace”.
- The homepage title tag, og:title and og:site_name all read “Uplace”.
- The site is a fully server-rendered static Astro build, so the name is visible to any crawler without JavaScript.
- “Uplace” appears in the visible page content and in the site logo.
- The homepage describes the app’s functionality and links to our privacy policy and terms of service, matching the URLs configured on the consent screen.
- The authorized domain is verified in Google Search Console with a project owner account.
What we have already tried
- Resubmitting several times. Each submission is rejected within minutes with the identical finding, which again suggests an automated gateway rather than a manual review.
- Filing the in-console appeal, referencing the 17 August approval email.
- Previously, submitting without the Calendar scopes to clear branding first. Branding was then approved, but the finding returns as soon as scopes are added.
- We still have no Trust and Safety email thread to reply to. The Verification Center tells us to “Reply to your email thread with our Trust and Safety team after you have resolved the issues”, but no such thread exists. We checked the inbox and spam folders of the developer contact address, the user support address and all project owner accounts.
Our scope justification and demo video are already attached to the submission, so the scope review has everything it needs once branding is unblocked.
Request
Could a community manager or the Third Party Data Safety team trigger a manual re-review of the branding for this submission, and confirm whether an already approved brand verification is expected to be re-evaluated when only the scope list changes? If it is, we would like to understand how to avoid this loop, since this false finding blocks every future scope request. We are happy to provide side-by-side screenshots of the consent screen configuration and the live homepage.
Thank you very much for your help.