What we process
- Account details: your email and a sign-in identity, handled by WorkOS.
- Google connection: your Google account identifier and email, the Search Console, Google Analytics or Google Ads permission you approved (each product is a separate connection), and encrypted access credentials needed to keep the connection working.
- Property and account list: the Search Console properties, Google Analytics 4 properties (with their Analytics account names) and Google Ads accounts (with their customer ID, currency, time zone and manager account name) your Google account can read, and the local show/hide preference you set.
- Search performance, URL inspection, Google Analytics report data and Google Ads report data (such as campaign, keyword and search term performance) you ask your assistant for. It is fetched from Google when requested and returned to the assistant you chose (for example ChatGPT, Codex or Claude). We keep it only in a short-lived cache (15 minutes) to avoid repeat calls; realtime Analytics reports are not cached at all. We do not keep a performance, analytics or advertising archive.
- Billing: subscription status and identifiers. Payment details are handled by Polar and never reach QuerySail.
- Operational logs: request ID, tool name, outcome, latency and error category, kept for about 30 days. We do not routinely store raw search queries from your data in logs.
- Usage counters per account to enforce fair-use limits.
- Cookies and hosting logs: when you sign in, the site sets a session cookie that keeps you signed in. Our hosting provider (Vercel) records request details such as IP address and user agent in its own infrastructure logs.
- Website analytics: our public pages (not your account pages) use Google Analytics to count visits and see which sites and campaigns send people here. It sets cookies named
_gaand_ga_*. In the EEA, the UK and Switzerland it runs only after you accept it. Elsewhere it runs unless you decline. Change your choice at any time with "Cookie settings" at the bottom of every public page. We use no advertising cookies, and no Search Console, Google Analytics or Google Ads data from your connected accounts is ever sent to our website analytics. - Sign-up source: when analytics is allowed, a cookie named
qs_srcstores the site that first sent you here and the page you landed on, for up to 90 days. If you create an account, we save these two values on it to learn which listings bring people to QuerySail. They are included in your data export and deleted with your account.
What we do not do
- We do not collect your assistant conversations or transcripts.
- We do not use your Google data to train models, and QuerySail does not call a model with your data.
- We do not sell your data or use it for advertising.
- We never write to your Google account. QuerySail requests read-only Search Console access and read-only Google Analytics access.
- We never change your Google Ads account. Google offers no read-only permission for Google Ads, so the permission Google asks you to approve also allows changes. QuerySail only uses it to read reports and account details, through Google's reporting methods, and has no feature that creates, edits, pauses or deletes anything.
QuerySail's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Who else handles data
We use WorkOS (sign-in), Google (Search Console, Analytics and Google Ads data, and Google Analytics for our own website), Polar (payments), Vercel (hosting for the website and the MCP endpoints) and Convex (database and backend). Data you ask for is returned to the assistant host you connect, which has its own privacy terms.
How we share, transfer or disclose Google user data
Google user data means the Search Console, Google Analytics and Google Ads data, Google account identifier and email, and Google access credentials described above. We share it only in these cases:
- With the assistant you connect. When you ask a question, we send the Search Console, Google Analytics or Google Ads data that the request needs to the assistant you authorized (for example ChatGPT, Claude or Codex), so it can answer you. We send nothing to an assistant you have not connected.
- With our service providers. Convex stores the encrypted Google credentials, your property and account lists and the 15-minute cache. Vercel runs the MCP endpoints that pass requests and responses between Google and your assistant. They process this data only on our behalf, to run QuerySail.
- When the law requires it, for example to comply with a valid legal order, or to protect the security of QuerySail and its users.
- In a merger or sale of QuerySail, only to the new operator, under this policy, and after we tell you.
We do not sell, rent or transfer Google user data to anyone else, including advertisers, data brokers and information resellers. No person at QuerySail reads your Google data, except with your permission to fix a problem you report, to investigate abuse or security issues, or when the law requires it.
How we protect your data
- All traffic between your browser or assistant, QuerySail and Google uses HTTPS (TLS).
- We encrypt Google access credentials with AES-256-GCM before we store them. Each encrypted value is bound to its owner. The encryption key is a server secret and is not stored in the database.
- Google credentials never leave our servers. Your assistant gets its own QuerySail token, which you can revoke at any time, and never sees your Google credentials.
- Every request checks that the signed-in account owns the Google connection and the property or ad account it asks for.
- We request a separate permission for each Google product, and read-only scopes wherever Google offers one. Google Ads has none; see above.
- We keep Google data only as long as described under Retention, and delete it when you disconnect Google or delete your account.
Your controls
- Disconnect Google in Account → Connections. Stored credentials are deleted immediately and we ask Google to revoke the token. Cached data for that connection is purged, and a report that was still being fetched when you disconnected is not stored.
- Revoke plugin access in Account → Settings. This stops the assistant from reading your data without touching your Google connection.
- Hide a property or ad account from the assistant in Account → Connections.
- Export your account metadata in Account → Settings.
- Delete your account in Account → Settings. Access stops immediately. Your Google credentials are deleted and we ask Google to revoke the token, your connections and other account data are removed promptly and in any case within seven days, your sign-in is deleted from WorkOS, and active subscriptions are cancelled. If WorkOS or our payment provider is unreachable, we keep only your account ID and subscription ID, plus your sign-in ID until WorkOS confirms its deletion (and the deletion record described under Retention), and keep retrying until those steps succeed.
Retention
- Short-lived cache: 15 minutes. Expired entries are never served and are removed by a cleanup that runs every 15 minutes.
- Operational logs: about 30 days.
- Usage counters: about 3 days.
- After deletion: backups roll off on the hosting providers' backup schedules. Billing records are retained by Polar where the law requires.
- To stop repeated free trials we keep one-way hashes of the email address (ignoring any +tag) and the Google account that used a trial, together with the date and an opaque identifier of the account that used it, without any other account data.
- Deletion records: an opaque account ID and the status of each cleanup step, for about 30 days after the deletion finishes.
- From the moment you delete your account until 24 hours after cleanup finishes, we keep a one-way hash of your sign-in ID, so a session that was already open cannot quietly recreate the account.
Detection of Google permission changes
If you remove access to a property or ad account, or revoke QuerySail in your Google account, QuerySail notices within about 15 minutes at most and stops serving that data, including from cache.
Contact
QuerySail is operated by Gidian Bateman in South Africa, who is responsible for your information under this policy. Questions or requests: support@querysail.com.