Service information
Privacy Policy
Effective date: October 5, 2026
This policy covers the Vosik Signals public website and its Google Search Console Connector and Google Analytics Connector. Vosik Signals is an independent personal software project. The Search Console-specific sections below describe that connector; the Google Analytics section describes its different implementation. For privacy questions or requests, contact vosikvos@gmail.com.
Search Console: Google sign-in and permissions
The service uses Google OAuth and OpenID Connect to authenticate you and obtain permission to access Google Search Console. It requests basic OpenID authentication and the Google Search Console read-only permission (webmasters.readonly). Your Google account's stable subject identifier is used to derive an internal account identifier; your email address is not used as the account identity. The service does not receive your Google password.
Search Console: information accessed
When your connected MCP client requests a tool, the service may access properties and permission levels associated with your Google account; search analytics such as search queries, page URLs, dates, countries, devices, clicks, impressions, click-through rates and positions; URL inspection and indexing information; and submitted sitemap information. Requests may include property URLs, inspection URLs, date ranges, dimensions and filters. The information returned depends on your permissions and Google's API availability.
URL inspection responses may also include links to inspection results, crawl dates and crawler type, robots and indexing decisions, page-fetch status, coverage and index verdicts, user-declared and Google-selected canonical URLs, referring page URLs and sitemap URLs. When supplied by Google, they may include AMP status and issues, mobile usability issues, and rich-result or structured-data item names, types, issues and severity. The service passes these Google API responses through rather than reducing them to a status alone.
Sitemap responses may include sitemap paths and types, submission and download times, processing and index-file flags, warning/error counts, and content types and submitted or indexed URL counts. Search analytics keys may include search appearance or hourly/date values as requested. URLs, query text, referring pages or structured-data names can themselves contain personal information. Batch inspection results also include the requested URL, a success indicator, and an error message if a request fails.
Search Console: how information is used and shared
Account identifiers and OAuth credentials are used to authenticate your connection and call Google's APIs on your behalf. Search Console information is used only to provide the MCP functionality you request. Results are returned to the MCP client you authorize. If that client is an AI service, it may process those results under its own privacy policy and settings. Choose your client carefully; this service cannot control how a separate client handles results after receiving them.
Cloudflare Workers hosts the service. Google credentials, access-token caches, internal account identifiers and MCP authorization records are stored in Cloudflare Workers KV. Cloudflare processes this information and technical metadata to operate the infrastructure; this policy does not promise storage in a particular country. Google processes authorization and API requests. Data may also be disclosed where necessary to comply with law or investigate security incidents. User data is not sold, rented or used for advertising.
Search Console: credentials, storage and security
The service stores Google refresh tokens and temporarily caches access tokens for each internal account so your connection can continue functioning without signing in for every request. It also stores MCP authorization grants and short-lived authorization transaction information. Credentials are not intentionally included in tool results. HTTPS is used for connections to the service and Google's APIs, and credential access is restricted by the authenticated account.
Search Console results are fetched to answer requests; the service does not maintain a separate analytics database of those results. Infrastructure may process technical request metadata and operational logs, such as timestamps, network information and error status. No system can guarantee absolute security.
Search Console: retention and deletion
Google refresh-token records have no automatic expiry set by this application and remain until removed, even if Google invalidates them. Access-token caches expire after the lifetime returned by Google (with a minimum cache-record lifetime of 60 seconds), and authorization transactions expire after ten minutes. MCP grants and tokens are governed by the OAuth provider's configured lifetimes and revocation behavior; reconnecting may replace prior grants for the same client. No fixed deletion schedule is configured for operational infrastructure records. Revoking Google access prevents future authorized API use but does not automatically delete every stored record or data already received by your client. To request deletion of service-held connection records, email the contact address above. You may be asked to verify control of the account before a request is processed. The service does not promise automatic deletion on a fixed schedule; legal or security obligations may require some records to be retained.
Google Analytics: information accessed and used
The Google Analytics Connector uses Google OAuth with openid, userinfo.email and the read-only analytics.readonly permission. It retrieves Google user information to identify the account and uses the stable Google subject identifier as its OAuth user identity. Google’s user-information response may include an email address; the reviewed application uses the subject identifier and does not persist an email profile. The service does not receive your Google password.
It accesses account summaries, account and property identifiers and names, and GA4 report data requested through dimensions, metrics and date ranges. Reports may include traffic sources, landing pages, dates, sessions, active users, key events and other supported reporting values. Returned reports include Google’s headers, rows and report metadata. Reporting values and URLs may contain personal information depending on the property’s configuration. Access is necessary to identify available properties and answer requested reports; it does not modify Google Analytics accounts.
Google Analytics: credentials, sharing and storage
Each MCP user authorizes their own Google account. Google access tokens, refresh tokens when supplied by Google, and access-token expiry information are attached to that user’s OAuth authorization grant. The OAuth provider encrypts these credential properties before storing them in Cloudflare Workers KV. Credential properties are encrypted using AES-GCM. The encryption key is separately wrapped using the OAuth token-protection mechanism rather than being stored alongside the credentials in plaintext. OAuth authorization codes and related token secrets are protected using cryptographic hashing and key-wrapping mechanisms. The provider decrypts credential properties only when processing an authenticated request associated with the corresponding authorization grant. Report calls use those credentials, including that grant’s refresh token when a new Google access token is needed. The current application does not read or write the previous shared Google token store.
Connections between users, the service, Google authorization endpoints, and Google Analytics APIs use HTTPS/TLS. Google Analytics access is limited to the read-only analytics.readonly OAuth scope. The connector does not use this permission to modify Google Analytics accounts or properties. Google OAuth credentials are not intentionally included in tool results and are used only to authenticate requests necessary to provide the user-requested Analytics functionality.
A refreshed Google access token is used for the current request; the application does not persist that refreshed token or update the grant’s original expiry information. If no Google refresh token is available, you must reconnect when access expires.
Google processes authorization and Analytics API requests. Cloudflare hosts the connector and stores its OAuth records. Results and Google API error messages are returned to the requesting MCP client, which may process or retain them under its own terms and settings. The application does not write account summaries or report results to a separate results database.
Google Analytics: retention and deletion
Google credentials are retained within the OAuth provider’s grant and token records, rather than a separate permanent Google-token record. In the reviewed provider version and default configuration, authorization transactions and unexchanged authorization grants expire after ten minutes, MCP access-token records expire after one hour, and MCP refresh grants have a thirty-day lifetime. Refresh-token use does not extend that grant lifetime in the current configuration. Dynamically registered client records have a ninety-day default lifetime. These are application/provider record lifetimes, not a promise that every infrastructure record or backup is deleted on the same schedule.
Google revocation prevents future authorized Google API use but does not immediately delete service-held OAuth records or results already received by a client. Disconnecting a client is also separate from Google revocation. Email support to request deletion of connection records; verification of account control may be needed. There is no public application endpoint that automatically deletes all records following Google revocation.
Cloudflare observability is enabled. Some failure paths log Google token-endpoint or user-information error responses, and Google API errors may be passed to the MCP client. Infrastructure log retention, filtering and administrator access have not been verified; no claim of zero logging or a fixed log-deletion schedule is made. Any records left in the former shared token store are not used by the current application; their removal is an operational action that has not been verified.
Google user data sharing and disclosure
Google user data may be shared or disclosed only to the following parties and for the following purposes:
- Google — to authenticate users and make authorized Google Search Console and Google Analytics API requests.
- Cloudflare — as the infrastructure provider hosting the service and storing or processing OAuth credentials, authorization records, and technical service data necessary to operate the connectors.
- The MCP client authorized by the user — Google Search Console and Google Analytics results requested by the user are returned to that client so the requested functionality can be provided. If the authorized MCP client is ChatGPT or another AI service, that service may process or retain the returned data according to its own privacy policy and user settings.
- Legal or security recipients — information may be disclosed when required by applicable law or when necessary to investigate abuse, fraud, or security incidents.
Vosik Signals does not sell Google user data, share it for advertising, use it for data brokerage or credit decisions, or use Google user data to train generalized AI models.
Except for the parties and purposes described above, Vosik Signals does not share, transfer, or disclose Google user data to third parties.
Google API information and Limited Use
The service's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google API information is used to provide the visible, user-requested MCP features. Transfers are limited to delivering those features with your consent, necessary security purposes or legal compliance. It is not used for advertising, data brokerage, credit decisions or training generalized AI models by this service.
Human access is limited to your affirmative permission to examine specific data, necessary security investigations, legal requirements, or other access expressly permitted under that policy. A transfer following a merger, acquisition or asset sale would require your prior explicit consent as required by the policy.
Revoking access
You can remove the service's access through your Google Account's third-party connections settings. You can also disconnect the MCP server in your client. Disconnecting a client may not revoke Google's grant; use Google's settings to revoke Google access. Your client may retain previous conversations or results according to its own policies.
Public website
This public website has no analytics scripts, advertising, signup forms or application-set cookies. The connectors’ OAuth authorization flows use short-lived cookies to bind authorization to your browser. Cloudflare may process network metadata or apply infrastructure security measures when serving either the website or the MCP service.
Changes and contact
Updates will be published here with a revised effective date. Material changes in Google data use will require appropriate notice and renewed consent before the new use begins. Contact vosikvos@gmail.com with questions about this policy or your connection.