Google User Data — Disclosures
Oracolo.ai's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
1. Data Accessed
When a user signs in with Google and grants OAuth consent, Oracolo.ai accesses the following Google user data via the corresponding scopes:
- openid, email, profile — the user's Google email address, display name, and profile picture (used to create the local user account).
- https://www.googleapis.com/auth/analytics.readonly — the list of Google Analytics 4 properties the user owns (via the GA4 Admin API,
accountSummaries.list) and read-only GA4 report data for the properties the user selects (via the GA4 Data API, properties.runReport): sessions, totalUsers, newUsers, screenPageViews, conversions, totalRevenue, averageSessionDuration, bounceRate, broken down by channel group, source/medium, country, device category, landing page.
- https://www.googleapis.com/auth/webmasters.readonly (optional, opt-in) — the list of Google Search Console properties the user owns and read-only Search Console analytics (
sites.list, searchanalytics.query): clicks, impressions, click-through rate, average position, broken down by query, page, country, device, search appearance.
- https://www.googleapis.com/auth/adsense.readonly (optional, opt-in) — the user's AdSense accounts, ad clients, sites, and read-only earnings reports (
accounts.list, accounts.adclients.list, accounts.sites.list, accounts.reports.generate): estimated revenue, page views, impressions, clicks, CTR, RPM, broken down by date, site, ad client, country.
2. Data Usage
Google user data is used only to provide and improve user-facing features inside Oracolo.ai:
- Google account identity (email, name, picture) is used to authenticate the user and personalize the user interface.
- GA4, Search Console, and AdSense data is used to display dashboards at
/dashboard/{propertyId}, generate statistical traffic forecasts at /planner/{propertyId}, and produce AI-written insights that summarize the user's site performance.
- Aggregated, non-identifying metrics (numeric values, no personal identifiers) are sent to the Anthropic Claude API to generate the natural-language insight text. Prompts and completions are not used by Anthropic to train models per our contractual arrangement.
- Google user data is never used for advertising, ad targeting, ad profiling, resale, credit scoring, or training first-party or third-party machine-learning or AI models.
3. Data Sharing
Oracolo.ai does not sell Google user data. Data is shared only with the following sub-processors, strictly to provide or improve the features above:
- Anthropic PBC (Claude API) — receives aggregated numeric metrics as prompt input to generate AI-written insight text. No email addresses, no user identifiers, no raw event-level data.
- Postmark (ActiveCampaign, Inc.) — sends transactional emails (welcome, weekly and monthly AI reports) to the user's email. Receives the user's email address and the rendered email body.
- Iubenda S.r.l. — hosts our cookie consent management widget on the front-end.
- Google LLC — receives outbound requests to the OAuth 2.0 endpoint, the GA4 Data API, the Search Console API, and the AdSense API on the user's behalf. This is the source of the data, not a separate transfer.
We do not share Google user data with advertising networks, data brokers, or any party for commercial or research use.
4. Data Storage & Protection
- All traffic is served over HTTPS with TLS 1.2 or higher. Session cookies are marked
HttpOnly and Secure.
- OAuth
refresh_tokens are stored server-side in MySQL and are never transmitted to the browser or exposed to client-side JavaScript.
- Access to the production database is limited to the developer via cPanel-authenticated shell over SSH.
- Application-level encryption at rest (AES-256-GCM with a split-key scheme: the key is derived from two parts stored in separate locations) protects OAuth tokens, the GA4/Search Console/AdSense report cache, analytics snapshots, AI reports and saved plans since August 2026. Expired cache rows are physically deleted daily.
- We do not have a Bug Bounty program, but security reports can be sent to info@oracolo.ai and are answered within 5 business days.
5. Data Retention & Deletion
- Cached GA4 report data: up to 24 hours per report key, then automatically evicted.
- Cached AdSense report data: up to 1 hour per report key, then automatically evicted.
- OAuth
access_token: retained until its expiry (typically 1 hour). Refreshed automatically as needed via the stored refresh_token.
- OAuth
refresh_token: retained until the user revokes access (via /account, via their Google Account permissions page, or by deleting their Oracolo.ai account).
- Account data (user profile, list of connected GA4 properties, saved forecasts): retained until the user deletes their account.
- User-initiated deletion: the user can go to https://oracolo.ai/account at any time and (a) download a JSON export of all their data, (b) disconnect Google (which revokes the OAuth grant with Google and deletes the stored tokens locally), or (c) delete their entire account (which cascade-deletes all user records, cached reports, saved forecasts, and revokes the OAuth grant). Account deletion is immediate; there is no soft-delete or grace period.