Getting Google to approve read-only analytics access for my SaaS took 4 days and 2 demo videos
I'm building Pingsold, a directory that ranks startups by traffic read directly from their analytics instead of
screenshots. The core feature is "Connect with Google", which needs the analytics.readonly scope. That scope
is sensitive, so Google has to review your app before real users can connect without a scary "unverified app"
warning.
What the review actually took:
- Submitted Oct 31 with a demo video of the full connect flow
- Google came back asking for a data-protection section in the privacy policy (how the data is stored,
encrypted and deleted) and a clearer video showing exactly what the scope is used for
- Re-recorded the video showing the consent screen, the property picker and the exact numbers we read (visitor
totals only, nothing per visitor)
- Approved Nov 3
Tips if you're building on Google APIs:
1. Record the video in one take showing the OAuth consent screen with your app name visible. They check that.
2. Say in plain words what data you read and why. Vague privacy policies get bounced.
3. Don't switch the app between Testing and Production during review.
Week 1 since launch: 6 startups listed, but only 2 have connected analytics. The trust barrier is real even
after Google approval.
If you want to see the flow: https://pingsold.com (free to list, no badge needed).
Has anyone else gone through the sensitive-scope review? Did yours take longer?

Replies
Be the first to reply
Have a question or a thought to share? Add a comment above to start the conversation.