Why We Need These Permissions — SeeMeNow.AI


Google OAuth — Permissions

Why We Need These Google Permissions

When you connect your Google account to SeeMeNow.AI, we request access to four specific Google APIs. This page explains exactly what each permission does, why it’s needed, and what we will never use it for.

🔒
Google API Services User Data Policy
SeeMeNow.AI’s use of information received from Google APIs adheres to the
Google API Services User Data Policy, including the Limited Use requirements.

📊
Google Analytics 4 API
Read Your Analytics Data
Read-only access to your Google Analytics 4 properties so we can surface traffic, conversion, and audience insights.
Scope: https://www.googleapis.com/auth/analytics.readonly
📈
Performance dashboards — we read sessions, users, pageviews, traffic sources, and conversion data to populate your project dashboards and reports.
🎯
Opportunity detection — we analyse traffic trends, landing page performance, and goal completions to identify growth opportunities and flag decaying content.
📋
Automated reports — client-facing performance reports are generated using your GA4 data, saving your team hours of manual reporting each month.
🔗
Property discovery — on first connection we read your GA4 account summaries so you can select which property to connect to each project.
✓ We will never use this permission to


🔍
Google Search Console API
Read Your Search Performance Data
Read-only access to your Google Search Console properties to analyse keyword rankings, impressions, and organic search performance.
Scope: https://www.googleapis.com/auth/webmasters.readonly
🏆
Keyword rankings — we read search query data including impressions, clicks, and average position to track how your pages rank over time.
📉
Content decay detection — we identify pages losing rankings or impressions so you can prioritise refresh opportunities before traffic drops.
🕳
Keyword gap analysis — we compare your ranking queries against competitors to find high-opportunity keywords you are not yet targeting.
🌐
Site discovery — on first connection we list your verified Search Console properties so you can select which site to link to each project.
✓ We will never use this permission to


📄
Google Docs API
Create & Read Content Documents
Access to create and read Google Docs as part of the content drafting and review workflow — used only when you actively generate content inside the platform.
Scope: https://www.googleapis.com/auth/documents
✍️
Content draft creation — when you generate a blog post or content expansion inside SeeMeNow.AI, the draft is automatically created as a Google Doc in your connected Drive for easy editing and collaboration.
🔄
Two-way sync — when you or your team edit a draft in Google Docs, the platform detects the change and pulls the updated content back into SeeMeNow.AI so your records stay current.
💬
Comment synchronisation — review comments added in Google Docs are pulled into the platform, and feedback added in the platform is pushed back to the Google Doc, keeping both sides in sync.
✓ We will never use this permission to


📁
Google Drive API — File Scope
Save Files Created by SeeMeNow.AI
The most restrictive Drive scope available — gives us access only to files that SeeMeNow.AI itself creates. We cannot see, read, or touch any other files in your Drive.
Scope: https://www.googleapis.com/auth/drive.file
📤
Saving content drafts to your Drive — when a blog post or content brief is generated, it is saved as a Google Doc in your Drive using this permission. The document belongs to you and lives in your Drive.
🖼
Uploading AI-generated images — when the platform generates a featured image for your content, it is uploaded to your Drive so you can use it directly in your CMS.
🔗
Setting share permissions on created files — when a document is created for team review, we set it to “anyone with link can comment” so your team can collaborate without needing a Google account login.
⏱
Checking file modification time — to power the two-way sync, we periodically check when a linked document was last modified so we only pull content when something has actually changed.
✓ The drive.file scope strictly limits us — we cannot

Our Data Principles

These four commitments govern everything we do with your Google data.

🎯

Minimum Necessary Access

We request only the four scopes listed above — nothing more. Every scope maps directly to a feature you use. We use drive.file instead of drive precisely because it’s the most restrictive option.

🚫

No Data Sales or Sharing

Your Google data is never sold, rented, or shared with any third party for any reason — including advertisers, data brokers, or analytics providers.

🧠

No AI Training

Your Google data — including your analytics, search performance, and document content — is never used to train machine learning or AI models, ours or anyone else’s.

🔐

Encrypted & Secure

Your OAuth access tokens are encrypted at rest using AES-256 and transmitted only over HTTPS. Access is restricted to authorised systems only.

How to Revoke Access

You can remove SeeMeNow.AI’s access to your Google account at any time — no questions asked. There are two ways to do it:

Option 1 — From inside SeeMeNow.AI

1Go to Account Settings in your SeeMeNow.AI dashboard
2Find the “Connected Accounts” section
3Click “Disconnect Google Account” — access is revoked immediately

Option 2 — Directly from your Google Account

1Visit your Google Account’s Third-Party Apps & Services page
2Find “SeeMeNow.AI” in the list of connected apps
3Click “Remove Access” — all tokens are immediately invalidated

🔗 Manage Google Account Permissions →

After revoking access, SeeMeNow.AI will no longer be able to read your analytics, search, or documents data. Any Google Docs previously created by the platform will remain in your Drive and are not affected.

Questions about how we use your data?

🔒 Privacy Policy
📄 Terms of Service