Stuck on Google OAuth Branding Verification – AI NCII / Google APIs Terms of Service Error (PII Removed by Staff)

Hello everyone,

I’m facing an issue with Google OAuth branding verification for my application, Void Agent, and I’m hoping someone from the Google team or someone who has experienced a similar issue can help me understand what exactly needs to be fixed.

Project details

  • Application name: (PII Removed by Staff)

  • Google Cloud Project name: (PII Removed by Staff)

  • Project ID: (PII Removed by Staff)

  • Homepage: (URL Removed by Staff)

  • Privacy Policy: (URL Removed by Staff)

  • Terms of Service: (URL Removed by Staff)

The issue

During Google OAuth branding verification, I repeatedly receive the following rejection:

Your app has not met branding guidelines requirements. Please resolve the following issues:

Your application is not compliant with the Google APIs Terms of Service.

We were unable to confirm your app’s compliance. Please update your home page to clearly outline your application’s purpose and ensure it does not use Google APIs for AI NCII (AI-generated Non-Consensual Intimate Imagery), then retry.

What I have already completed

I have carefully reviewed my Google Cloud OAuth configuration and website.

  1. Homepage requirements – Verified successfully.

  2. Privacy policy requirements – Verified successfully.

  3. Domain ownership – Verified successfully in Google Search Console.

  4. Application branding – Configured with the same product identity and logo used on my website.

  5. OAuth scopes – Only the standard non-sensitive scopes are requested:

    • openid

    • userinfo.email

    • userinfo.profile

  6. No sensitive or restricted OAuth scopes are listed.

Void Agent is an AI-powered development and productivity platform. Google OAuth is implemented for basic user authentication and profile identification.

My Terms of Service also explicitly prohibit non-consensual intimate imagery (NCII), including synthetic media depicting real people’s likenesses without their consent. This is documented under Section 9.2 – Deception & Fraud, in the Prohibited Conduct section.

What I have tried

I selected “The finding is incorrect” in the appeal process and submitted an explanation clarifying the application’s purpose, OAuth scopes, and existing safety restrictions.

However, the same compliance issue continues to appear.

Another problem: Trust and Safety email

The verification progress page explicitly instructs me:

Resolve all the issues below. Reply to your email thread with our Trust and Safety team after you have resolved the issues. The Trust and Safety team will continue the verification process once all issues are resolved.

However, I have not received any email thread from the Trust and Safety team, including in my spam folder.

Furthermore, I no longer see an option to request re-verification, so I am currently stuck and cannot determine what the next step should be.

What I need help understanding

  1. If my homepage and privacy policy have already passed verification, what specifically is still causing the Google APIs Terms of Service / AI NCII rejection?

  2. Is this an automated false positive triggered by the application’s AI-agent positioning?

  3. Does Google require a specific AI NCII disclosure on the homepage, even when the application already prohibits NCII in its Terms of Service?

  4. How can I contact the assigned Trust and Safety team if I never received their email?

  5. Is there another way to request manual review or restart the branding verification process?

I want to resolve this properly and comply with Google’s requirements. I don’t want to keep making unnecessary changes to an application that already appears to meet the published branding and OAuth requirements.

Any guidance from Google representatives or developers who have successfully resolved this exact issue would be greatly appreciated.

Thank you!

Hi Ibrahim, this pattern is common for AI agent apps, and the key point is that the reviewers check the homepage itself, not only the Terms of Service.

Your Terms of Service prohibiting NCII is good, but it is not enough on its own. Add a clear statement on the homepage itself, visible without scrolling or clicking through, that says in plain language what Void Agent does and does not do. For example: Void Agent is an AI coding and productivity assistant, Google sign-in is used only for authentication, and the app does not generate images, video, or intimate imagery of any kind. Then link that statement to the matching section of your Terms of Service. The review appears to be triggered by the AI-agent positioning, so the homepage has to make that boundary explicit for a reviewer who only looks at that page.

On the missing email: the Trust and Safety thread is normally sent to the developer contact email and the user support email listed on the OAuth consent screen, not necessarily to the project owner or to the Search Console owner. Check those two inboxes, including spam, and check that they are not group inboxes or addresses that drop mail from Google. If no thread exists, there is no address you can reply to directly.

While the re-verification button is missing, the only route back in is a Google Cloud support case. Open one from the project, choose the OAuth consent screen and branding verification issue, and ask support to confirm the exact homepage wording that failed and to reopen the verification so you can resubmit. In the case, state that you have added the NCII statement to the homepage and ask them to confirm the wording is sufficient before you resubmit, so you do not get the same rejection again.

Do not keep resubmitting the same homepage. Make the homepage change first, then get the case opened.