Legal

# Privacy policy

What `gsc.k-o.pro` does with your data when you connect your Google account to it. It is written to match what the software actually does; the source is public, so it can be checked.

## Who runs this service

An instance of the open-source *gsc-mcp-remote* server, operated by whoever deployed it at `gsc.k-o.pro`. It is not operated by, affiliated with, or endorsed by Google or by Anthropic.

## What is collected

| Data | Why |
| --- | --- |
| Your Google account email address and account identifier | To recognise you across sessions and to attach your saved settings and stored credential to you |
| A Google refresh token, encrypted at rest | To call the Search Console API on your behalf without making you sign in again for every question |
| Your chosen default property, if you set one | So tool calls that do not name a property can use it |
| Irreversible hashes of the access tokens issued to your Claude client | To recognise valid requests. The tokens themselves are never stored, so a copy of the database does not yield working access tokens |
| Server logs: session open and close events, errors, timestamps | To keep the service running and diagnose failures |

## What is not collected

- **Your Search Console data is not stored.** Each question is answered by fetching live from Google's API and returning the result to your Claude client. Nothing is retained afterwards.
- Logs deliberately exclude tokens and the content of your queries.
- No advertising or analytics trackers, and no cookies for tracking. The service sets exactly one cookie, and only while you are connecting: a random value that ties the sign-in you started to the browser you started it in, so nobody else can complete it in your name. It is `HttpOnly`, scoped to the sign-in routes, expires after ten minutes, and is cleared the moment the connection finishes. It carries no identifier and is never used to track you.

## What access is requested

One Search Console permission: `https://www.googleapis.com/auth/webmasters.readonly`. This is read-only. Signing in also uses Google's basic `openid` and `email` scopes, solely to identify your account. The service cannot submit URLs for indexing, change sitemaps, modify your properties, or reach any other Google service. Google's own Search Console permissions still apply on top: you see exactly the properties Google would show you.

## How your data is protected

- Your Google refresh token is encrypted with AES-256-GCM under a key held in a file readable only by the service account, never in the database alongside the data it protects.
- Tokens issued to your Claude client are random, stored only as SHA-256 hashes, expire after an hour, and rotate on refresh. Presenting an already-rotated token invalidates every session it belonged to.
- All traffic is over HTTPS.
- Your Google credentials are never sent to your Claude client, and the tokens issued to your Claude client are never sent to Google.

## Sharing

Your data is not sold, rented, or shared with third parties. It is not used for advertising, and it is not used to train any machine-learning or AI model. The only third party involved is Google, whose API is called on your behalf with the permission you granted.

## Google API user data

This service's use and transfer to any other app of information received from Google APIs will adhere to the [Google API Services User Data Policy](https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. Data obtained through the Search Console API is transferred only to your own Claude client, in answer to the questions you ask there. It is not transferred to anyone else, not used for advertising, and not used to develop, improve or train any machine-learning or AI model.

## How long it is kept, and how to delete it

Data is kept until you remove it. You can do that at any time, in either of two ways, and doing either is enough:

- Ask your Claude client to run `disconnect_account`. This erases the stored Google credential, every token, and your saved settings, and ends your open sessions immediately.
- Remove the app at [myaccount.google.com/permissions](https://myaccount.google.com/permissions). The stored credential stops working, and the service erases it the next time it tries to use it.

Run `export_my_data` at any time to see everything held about you. Expired tokens and abandoned sign-in attempts are swept automatically.

If the operator keeps backups of the database, an erased connection can remain in those backups until they expire (up to 30 days by default). Stored credentials in a backup stay encrypted with a key that is kept outside it.

## Changes

If this policy changes materially, the change will appear on this page. The repository's history is the authoritative record of what changed and when.

## Contact

For any question about your data, or to ask for it to be deleted by hand, write to [hi@k-o.pro](mailto:hi@k-o.pro).

---

Not affiliated with or endorsed by Google or Anthropic. “Google” and “Google Search Console” are trademarks of Google LLC.