1. Application and operator
gsc is a personal Google Search Console integration operated by the owner of this website, contactable at tianzhenyun@gmail.com. It uses the open-source mcp-gsc project to connect the operator's authorized website data to an MCP-compatible AI assistant. It is not a public signup service or a Google product. This policy covers this personal integration and its information pages on www.viagle.com, not unrelated applications that use the same open-source software.
2. Google data accessed and permissions
With Google authorization, the integration can access Search Console property URLs and permission information, search queries and page URLs, clicks, impressions, click-through rates, average positions, country and device breakdowns, URL indexing and crawl information, and sitemap details. OAuth access and refresh tokens allow the integration to make authorized API requests; gsc does not receive your Google password.
The upstream integration requests https://www.googleapis.com/auth/webmasters, which permits viewing and managing Search Console data. This is not a read-only permission. Available operations include sitemap submissions; some property and deletion operations require additional configuration. Operations remain subject to the authorizing account's Google permissions.
3. How data is used
Data is used to answer the operator's questions about website search performance, compare reporting periods, investigate indexing issues, and carry out requested Search Console operations. Credentials are used to authenticate requests and renew access. Google data is not sold, used for advertising or credit decisions, or used by the operator to train a general-purpose AI model.
4. Storage and retention
The MCP process runs on the machine where the operator installs it. OAuth tokens are saved in a token.json file in its configuration directory and remain there until removed or replaced. If the process is run on a server, that server holds the credentials. The public information website does not receive these tokens or Search Console tool results.
Results returned to the connected AI client may be retained in conversation history, exported reports, or that client's logs. Such copies remain until deleted by the operator or under the client's retention settings. There is no automatic deletion period promised for these copies. The operator is responsible for restricting access to the machine, credentials, and saved reports.
5. Sharing and AI processing
Requests and authentication information are sent to Google to provide the Search Console API service. Requested tool results are passed to the operator's connected MCP client and may be sent to its AI service provider to produce answers. That provider's privacy policy and account data controls govern its processing and retention. Data shared in a conversation may include site URLs, search terms, and performance metrics. Connecting an AI client therefore does not mean all data stays on the MCP machine.
The operator does not otherwise publish or sell Google data. Disclosure may occur when required by applicable law. The operator must choose AI service settings compatible with the Google API Services User Data Policy before transmitting Google data.
6. Google API Limited Use
gsc'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.
7. Website visits
These information pages do not implement Google login, advertising trackers, analytics scripts, or application cookies. The hosting provider, Cloudflare, may process connection information such as IP address, requested URL, time, and browser headers to deliver and protect the website, under its privacy policy. These hosting records are separate from Search Console API data.
8. Revocation, deletion, and contact
You can revoke OAuth access through Google Account connections. Revocation prevents further access through that authorization but does not erase previously saved reports or conversations. To remove stored copies, stop the integration, delete its token file and any saved exports, and delete relevant histories in the connected AI client. For privacy questions or deletion requests concerning data controlled by the operator, email tianzhenyun@gmail.com. Do not email passwords, tokens, or credential files.
9. Policy changes
Changes to the integration's data practices will be reflected on this page with an updated effective date. A change of use or permissions may require renewed consent before the new processing begins.