Skip to main content
Question

OAuth data-access verification under review since 4 Oct — no Trust & Safety contact, no reply path (sensitive scope: script.external_request)

  • October 6, 2026
  • 2 replies
  • 18 views

Vikrant SINGH
Forum|alt.badge.img

Project ID: wixtoproject Project number: [removed by moderator] App: StoreToSheet — a published Google Workspace Marketplace add-on Submitted: 4 October 2026

WHAT'S HAPPENING

I submitted OAuth data-access verification on 4 October. The Verification Center stated a first email from Trust & Safety within 3–5 days and a decision within 4–6 weeks. No email has arrived at the registered developer contact address — I've checked spam for [removed by moderator] — and the Verification Center provides no reply or contact control of any kind.

CURRENT PANEL STATE

  • Homepage requirements: Approved
  • Branding guidelines: Verified and shown to users
  • Privacy policy requirements: Under review
  • App functionality: Pending
  • Appropriate data access: Pending
  • Request minimum scopes: Pending

SCOPES — TWO ONLY, NO RESTRICTED SCOPES

The restricted tier is empty, so no CASA assessment applies. The Apps Script manifest pins UrlFetchApp to a single host, so the sensitive scope physically cannot reach any other destination.

EVERYTHING REQUESTED WAS SUPPLIED AT SUBMISSION

  • Scope justification (910/1000 characters)
  • Unlisted YouTube demo video showing the OAuth consent flow and in-product use
  • Domain verified in Search Console under the same account that owns the Cloud project (this had previously caused a "homepage URL not registered to you" rejection, since fixed)
  • Authorised domain configured; publishing status In production
  • Live privacy policy naming both scopes, with Google API Services User Data Policy and Limited Use disclosures, a retention table and a deletion process, linked from the homepage

The Marketplace listing itself was reviewed and approved by the GWM Reviews Team on 19 September 2026.

WHAT I'VE ALREADY TRIED

  • Emailed [removed by moderator] (6 Oct) — no response yet
  • Emailed [removed by moderator] — hard bounce, address does not exist. Worth noting, as this address is still being recommended in threads here
  • Asked the GWM review team whether they can refer the case internally
  • Cloud Customer Care: not available. This project has no billing account, and there is no "OAuth Consent Screen" case category under IAM & Admin, so even a paid Standard plan has no documented route to the Trust & Safety queue
  • Workspace developer support states verbatim that review-process issues are out of scope

WHY THIS IS URGENT

Unverified sensitive scopes are capped at 100 users for the lifetime of the project, and Google's own wording is that this "cannot be reset or changed". So every merchant onboarded while unverified spends irreversible inventory behind an "unverified app" interstitial. The Marketplace listing is live and approved, but unusable in practice — merchants are waiting and we can't accept them.

MY ASK

Could a community manager or staff member pass project [removed by moderator] to the OAuth Trust & Safety team?

I'm happy to provide the developer contact address, OAuth client ID or demo video link privately rather than in a public thread. And if something is genuinely outstanding on my side, I'd rather know that than keep waiting — there's currently no channel through which anyone can tell me.

2 replies

ErikaB
Community Manager
Forum|alt.badge.img+13
  • Community Manager
  • October 6, 2026

Hi ​@Vikrant SINGH 

I’m sorry to hear you are going through this. The Managers/Admins/Moderators of this community do not have any visibility or ability to escalate issues with the Trust and Safety team or Appeals. 

Do to the many posts our community has received on this topic, we’ve put together an article which walks you through the process and explains what to expect.


Vikrant SINGH
Forum|alt.badge.img
  • Author
  • New Member
  • October 6, 2026

Thanks ​@ErikaB for responding, the issue is resolved, had some folks there who helped escalating this issue