Contents
QueryTrove privacy policy
Last updated: 16 November 2026
1. Who we are
QueryTrove is operated by crissidea OÜ, a private limited company registered in the Estonian Commercial Register under registry code 17640749, Sepapaja tn 6, 15551 Tallinn, Estonia ("we", "us"). Contact for anything in this policy: hello [at] crissidea [dot] com.
We are the controller of the personal data we process to run your account, sign you in, bill you, send you alerts and keep QueryTrove secure.
For the Search Console data of the sites you connect, you (or the organisation you act for) decide why and how it is processed, and we process it on your instructions to provide QueryTrove. For any personal data inside that Search Console data (for example a person's name in a search query or a page address), you are the controller and we are your processor under the Data Processing Addendum in our Terms of Service.
We are not required to appoint a data protection officer, and as a company established in the EU we do not need an EU representative.
2. What we access from your Google account
When you sign in with Google and grant access, QueryTrove receives:
- Basic profile (the standard
openid,emailandprofilepermissions): your Google account identifier, name, email address and profile picture address. - Search Console, read-only (
https://www.googleapis.com/auth/webmasters.readonly): the list of Search Console properties you can access and your permission level for each, and, for each site you choose to connect, its search performance data: daily clicks, impressions, click-through rate and average position, broken down by search query, page, country, device and search appearance. QueryTrove cannot change anything in your Search Console account. - Access and refresh tokens issued by Google, so the daily sync can run while you are away.
3. How we use Google user data
We use Google user data only to provide and improve the features you see in QueryTrove: your account, loading your sites' history, the daily sync, the dashboard and comparisons, annotations, drop alerts, CSV exports, and billing for paid sites.
- We do not sell Google user data.
- We do not use it, or transfer it, to serve advertising.
- We do not use it to train or improve artificial intelligence or machine-learning models, including foundation models.
- We do not use it to determine creditworthiness or for lending.
- No person at QueryTrove reads your Search Console data unless you ask us to (for example for support) and agree, unless it is needed for security purposes (such as investigating abuse) or to comply with the law, or unless the data has been aggregated and is used for internal operations.
QueryTrove's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
4. What we store, why, and on which legal basis
| Data | Purpose | Legal basis (GDPR) |
|---|---|---|
| Google account identifier, name, email, profile picture address | Create and run your account, contact you about it | Contract (art. 6(1)(b)) |
| Google access, refresh and ID tokens, granted scopes | Read your Search Console data for the daily sync | Contract (art. 6(1)(b)) |
| Session records: a session token, the IP address and browser user agent of the sign-in, expiry | Keep you signed in, protect your account against misuse | Contract (art. 6(1)(b)); security: legitimate interest in protecting accounts (art. 6(1)(f)) |
| Connected sites and their Search Console performance data (queries and pages with no click and only a few impressions on a day are stored as one combined "long tail" figure) | Provide the service | Contract (art. 6(1)(b)); for personal data inside it, your instructions as controller (art. 28) |
| Annotations you write, drop alerts we compute | Provide the service | Contract (art. 6(1)(b)) |
| Alert email preference, and the alert emails we send (recipient, site, figures) | Send the drop alerts you can turn off at any time | Contract (art. 6(1)(b)) |
| Stripe customer and subscription identifiers, plan of each site | Billing for paid sites | Contract (art. 6(1)(b)); accounting law (art. 6(1)(c)) |
| Order records of a paid site: date of the order, cancellation and withdrawal dates | Show your orders, handle withdrawals and refunds | Contract (art. 6(1)(b)); consumer law (art. 6(1)(c)) |
| Technical logs: requests, errors, scheduled job results (account and site identifiers, site addresses; not your email address) | Run, debug and secure the service | Legitimate interest in operating a reliable and secure service (art. 6(1)(f)) |
| Messages you send us | Answer you | Contract (art. 6(1)(b)) or legitimate interest in answering (art. 6(1)(f)) |
We do not make decisions about you based solely on automated processing that have legal or similarly significant effects. Providing your Google data is necessary to use QueryTrove; without it we cannot provide the service.
5. Who receives the data
We use these service providers (processors) under data processing agreements, only to run QueryTrove:
| Provider | What it does | Location of processing | Transfer safeguard |
|---|---|---|---|
| Neon (Databricks, Inc.) | Database | AWS Frankfurt, Germany (region eu-central-1); the provider is a US company | EU-US Data Privacy Framework or Standard Contractual Clauses in the provider's data processing agreement |
| Cloudflare, Inc. | Hosting of the application, scheduled sync, logs | Worldwide network, logs possibly in Cloudflare's core data centres | Data Privacy Framework and Standard Contractual Clauses in Cloudflare's data processing addendum |
| Resend (Plus Five Five, Inc.) | Sending alert emails, purchase confirmations and withdrawal acknowledgements | United States | Data Privacy Framework certification and Standard Contractual Clauses (Resend DPA) |
Payments. Paid plans are sold through Link, Stripe's merchant-of-record service: the seller of record is Sold through Link, LLC, a Stripe company, and payments are processed by Stripe. Stripe and Link process your payment, billing address, tax and transaction data as independent controllers under their own privacy policy (link.com/privacy). They send receipts and invoices to you directly. We receive your customer and subscription identifiers, the status of your subscription and the amounts paid; we never receive your card details.
Google provides the data you ask us to read, under Google's own terms and privacy policy.
AI apps you connect yourself. If you connect an AI app such as Claude or ChatGPT to QueryTrove (our MCP server, see /docs/mcp), you first sign in to QueryTrove and approve that app on a consent screen. The app then receives, each time you ask it a question, the stored Search Console data needed for the answer, plus your name and email address. It can only read. That app's provider handles what it receives as a separate controller under its own terms and privacy policy. You can see and disconnect connected apps on your account page at any time; deleting your account removes every connection.
We do not share Google user data or other personal data with anyone else, except with an AI app you connect and approve yourself as described above, or where the law requires it, to protect our rights in a legal claim, or as part of a merger, acquisition or sale of assets, and in that last case only after asking for your explicit consent for Google user data.
Transfers outside the EU. Where a provider above processes data outside the European Economic Area, the transfer relies on the EU-US Data Privacy Framework (Commission Decision (EU) 2023/1795) for certified US companies, or on the European Commission's Standard Contractual Clauses (Decision (EU) 2021/914). You can ask us for a copy of the relevant safeguards at hello [at] crissidea [dot] com.
6. How long we keep data
| Data | Kept for |
|---|---|
| Account and Google tokens | Until you delete your account. Revoking our access at Google stops the sync but keeps your stored history until you delete it |
| Session records (incl. IP address and user agent) | Until you sign out or the session expires (7 days after last use); expired records are deleted by the next scheduled job (every 10 minutes) |
| Sign-in state records | A few minutes, during sign-in; deleted by the next scheduled job once expired |
| Search Console data, annotations, alerts and order records of a site | While the site is connected. Deleted at once when you disconnect the site or delete your account (Stripe and Link keep their own transaction records) |
| Technical logs | 3 days (7 days if we move to Cloudflare's paid plan) |
| Database restore history | Deleted data can remain in our database provider's restore history for up to 6 hours (up to 7 days on a paid database plan) before it is overwritten |
| Emails at Resend | As long as Resend keeps sending logs under its terms; we do not keep copies |
| Our accounting records (identifiers, amounts, dates) | 7 years from the end of the financial year, as Estonian accounting law requires |
| Messages you send us | Up to 2 years after the conversation ends, unless needed for a legal claim |
7. Deleting your data and revoking access
- Disconnect a site: "Disconnect and delete data" on the site's page deletes all its stored data, alerts and annotations at once and cancels its subscription.
- Delete your account: on your account page. This cancels your subscriptions, revokes QueryTrove's access to your Google account, and deletes your account, sessions, tokens, every site and all stored data at once.
- Revoke access at Google at any time: myaccount.google.com/permissions. The sync then stops.
- Alert emails: use the unsubscribe link in any alert, or the switch on your account page.
8. Security
All traffic is encrypted in transit (HTTPS). The database provider encrypts stored data at rest. Google access and refresh tokens are encrypted in our database. Access to production systems is limited to the company's operator and protected by individual credentials.
9. Cookies
QueryTrove sets only cookies that are strictly necessary for the service you ask for, so it does not ask for cookie consent:
| Cookie | Purpose | Duration |
|---|---|---|
__Secure-better-auth.session_token | Keeps you signed in | 7 days after last use, or until sign-out |
__Secure-better-auth.state and related sign-in cookies | Protect the Google sign-in against forgery (state and PKCE) | Minutes |
Cloudflare security cookies such as __cf_bm or cf_clearance (only if bot protection or a challenge is triggered) | Tell people from bots, protect the service | Up to 30 minutes of inactivity for __cf_bm; set by Cloudflare |
We do not use analytics, advertising or tracking cookies, and we do not store anything else in your browser.
10. Your rights
Under the GDPR you can ask us to give you access to your personal data, correct it, delete it, restrict its processing, and receive it in a portable format (the CSV export and the account deletion are self-service). You can object at any time to processing based on our legitimate interests (art. 21). Write to hello [at] crissidea [dot] com; we answer within one month (art. 12(3)). We may ask you to confirm your identity.
For personal data contained in your sites' Search Console data, people other than you should address their requests to you as controller; we will help you answer them.
You can complain to the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon), Tatari 39, 10134 Tallinn, Estonia, info@aki.ee, www.aki.ee, or to the data protection authority of the EU country where you live or work.
11. Children
QueryTrove is a business tool and is not meant for anyone under 16.
12. Changes
We will post changes here and update the date above. We will tell you in the app or by email before a material change applies. If we ever want to use Google user data in a new way, we will ask for your consent first.