OAuth branding verification stuck — privacy policy content issue already fixed, no email received

Google Cloud Cloud Foundations & Onboarding
1

Hi,

Our OAuth app “Replyqo” (Project ID: [PII Removed by Staff], User type:
External, Publishing status: In production) is stuck on branding
verification for the business.manage scope.

The Verification Center flags: “Your privacy policy page at
(URL Removed by Staff) does not have sufficient
content.”

This is already fixed. Our privacy policy page comprehensively
discloses what Google user data we access, how we use it, with whom
we share it, our data protection measures, and our retention/deletion
policy. We also added a dedicated English-language summary section
covering all five categories, in case the automated check has
trouble parsing our primary-language (Turkish) content.

We clicked “I have fixed the issues” → “Proceed” multiple times, with
no change in status after waiting several hours. We have never
received any email from api-oauth-dev-verification@google.com or
google-cloud-compliance@google.com (checked inbox, spam, and all
folders on both our developer contact and support email addresses).

Could someone from the Trust & Safety team please manually re-review
our privacy policy page, or let us know what specific content is
missing?

Thank you.

2

Update: Since posting this, we found the “I have fixed the issues” →
“Proceed” quick-fix loop indeed doesn’t trigger a real re-review (as
several other threads here confirm). Instead, we went through
Verification Center → “Submit for verification” → filed a formal
appeal on the “does not have sufficient content” finding (reason:
“The finding is incorrect”, explanation restating the disclosures
already present on the page), then completed the Verification
Questionnaire (confirmed the app is not for personal/internal/
dev-testing-only use).

After submitting, the Branding status changed from the static
“does not have sufficient content” message to “Your branding is
currently under review” — a genuinely different state, so the appeal
does appear to have entered a real review queue this time.

Still no email from Trust & Safety, but will update this thread once
we hear back, in case it helps others hitting the same dead end with
the Proceed button.