# Data and privacy

> What QueryHippo collects and why, read-only Google access, sharing with other people, token storage and how to remove a property.

**Source:** [https://queryhippo.com/docs/data-and-privacy](https://queryhippo.com/docs/data-and-privacy)

A plain-language summary of how QueryHippo handles your data. The [Privacy Policy](https://queryhippo.com/privacy) is the authoritative version; if this page and the policy ever differ, the policy applies.

## What we collect, and why

- **Your account:** account identifiers and the profile and contact details provided through our sign-in provider, Clerk, plus details of the accounts you connect.
- **Your Search Console data:** once you connect Google, the properties you can access and their permissions, plus search queries, page URLs, dates, clicks, impressions, click-through rates, positions and the available breakdowns, such as country, device, search type and search appearance.
- **Service records:** saved history, source archives, collection status, comparisons, analysis results, access grants, and the credentials or tokens needed for connections you authorize.
- **Technical and support information:** what you send us, and operational details such as request times, IP addresses, browser details, and error and security logs.

We use this to sign you in, collect and keep the history you ask for, show reports, calculate comparisons, provide the connections you authorize, answer support requests, and keep QueryHippo reliable and secure. De-identified, aggregated statistics may also help improve QueryHippo's tools, subject to Google's data-use restrictions; the Privacy Policy explains the limits.

## Read-only Google access

QueryHippo requests read-only Search Console access. Connecting a property does not give QueryHippo permission to edit your website or your Search Console settings.

## Sharing with other people

Each owner's dataset is kept separate. A matching domain in someone else's account does not give them access to your history. Another person sees one of your properties only if you explicitly grant it to them, and the same applies to their AI assistant: a personal access token reaches only the properties its user owns or has been granted.

## Personal access tokens

QueryHippo stores a hash of each token to authenticate it, plus an encrypted copy so you can copy an active token again. You can revoke a token at any time under **Connect your AI**; revoking it also clears the encrypted copy. An AI assistant you connect handles what it receives under its own terms and privacy policy, so only connect tools you trust.

## Labelled data

Fixture and synthetic data are always labelled, including in the results your AI assistant receives, and an unavailable integration is never presented as live data.

## Removing a property or your data

- **Remove a property:** owners can choose **Remove property** in a property's Data view and confirm by typing `REMOVE`. Removal stops collection and revokes shared access immediately, then permanently deletes that property's stored history, archives and analysis evidence in the background. It can't be undone. Your other properties, Google connection and tokens are kept, and you can add the site again with fresh history.
- **Disconnect Google:** this stops future collection but does not delete history already collected. You can also review QueryHippo's access in your [Google Account connections](https://myaccount.google.com/connections).
- **Delete your account or other data:** email [support@queryhippo.com](mailto:support@queryhippo.com).