Skip to main content
ReachHub
GOOGLE OAUTH COMPLIANCE

Google API Data Usage Disclosure

Official Google OAuth compliance disclosure detailing ReachHub's use of Google Sign-In, Google Analytics 4, Google Search Console, and adherence to Google Limited Use requirements.

Last Updated: March 2026 • Brand: ReachHub • Jurisdiction: Chennai, India
Google API Services User Data Policy Compliance

ReachHub's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

1. Purpose of This Disclosure

This document provides full transparency for users and Google OAuth verification teams regarding how ReachHub accesses, processes, stores, and protects data obtained through Google APIs.

ReachHub provides Generative Engine Optimization (GEO) and Answer Engine Optimization (AEO) visibility tools. To offer comprehensive reporting, ReachHub supports three distinct Google integrations, each governed by the principle of minimum necessary privilege.

2. Integration Breakdown & Requested Scopes

A. Google Sign-In (User Authentication)

Authentication

OAuth Scopes: openid, https://www.googleapis.com/auth/userinfo.email, https://www.googleapis.com/auth/userinfo.profile

  • Data Accessed: Your primary Google email address, full name, Google unique account identifier (sub ID), and profile avatar picture.
  • Purpose: Authenticating your identity securely, creating your workspace account, and sending critical service notifications without maintaining password databases.
  • Data Storage: Stored securely in our encrypted customer database for the active duration of your account.
  • No Unnecessary Permissions: We do not request access to your contacts, Google Drive files, Gmail inbox, or Calendar.

B. Google Analytics 4 (GA4) Reporting

Read-Only Analytics

OAuth Scope: https://www.googleapis.com/auth/analytics.readonly

  • Data Accessed: Authorized GA4 property list, aggregate user sessions, pageview counts, referral mediums, and engagement duration.
  • Purpose: Correlating your AI engine brand visibility score with actual organic search visits and AI referral clicks (e.g. ChatGPT referral traffic).
  • Data Storage & Caching: Aggregate metric summaries are cached temporarily in encrypted databases strictly to render reporting graphs efficiently without triggering Google API rate limits.
  • Access Controls: Imported telemetry is strictly segregated by workspace and visible only to authenticated users within your organization.

C. Google Search Console Integration

Read-Only Performance

OAuth Scope: https://www.googleapis.com/auth/webmasters.readonly

  • Data Accessed: Verified domain properties, search queries, impressions, clicks, click-through rates (CTR), and average search ranking positions.
  • Purpose: Identifying high-opportunity informational keywords where optimizing content format (AEO schemas, direct answers) can increase conversational AI recommendations.
  • Strict Privacy: Search query performance is confidential to your workspace. We never pool, benchmark, or disclose proprietary keyword queries across different client accounts.

3. Affirmative Limited Use Commitments

In strict compliance with the Google API Services User Data Policy, ReachHub explicitly affirms:

1. No Sale of Google User Data

ReachHub does not sell, lease, or trade Google user data to data brokers, advertising exchanges, or any third parties under any circumstances.

2. No Advertising or Retargeting

Google API data is never used to build advertising profiles, serve targeted ads, or determine creditworthiness.

3. No Unrelated AI Model Training

We do not use customer data obtained through Google APIs to train, refine, or fine-tune public foundation AI/ML models.

4. No Human Viewing

ReachHub staff do not inspect your Google analytics or Search Console data unless explicitly requested by you for technical troubleshooting.

4. Security & Token Handling

All Google OAuth 2.0 tokens (access and refresh tokens) are protected using enterprise-grade security controls:

  • Encryption in Transit: All communication between user browsers, ReachHub servers, and Google API endpoints occurs exclusively over HTTPS/TLS 1.3 with strict HSTS headers.
  • Encryption at Rest: Refresh tokens are encrypted with AES-256 before being written to our production database storage. Decryption keys are stored in separate, isolated Key Management Services (KMS).
  • Token Expiration: Access tokens are ephemeral and automatically expired after 60 minutes.

5. Revocation & Disconnection Procedures

You maintain unilateral control over Google permissions granted to ReachHub:

  • Disconnecting from ReachHub: You can disconnect your Google account, GA4 property, or Search Console property at any time through your ReachHub workspace settings. Disconnecting immediately revokes our API tokens and purges cached telemetry.
  • Direct Revocation via Google: You can independently revoke ReachHub's OAuth authorizations at any moment by visiting the official Google Account Security Permissions Portal.

6. Data Deletion Inquiries

To request the complete deletion of all records, cached reports, and account data associated with your Google account, please consult our Data Deletion Policy or contact our compliance desk directly at support@reachhub.ai.