Privacy Policy
This policy explains what QueryAction collects, why, who helps us process it, and the choices you have.
What we collect
- Account. When you sign in, your name, email address, profile picture and a stable account identifier from your sign-in provider, and the network address and browser of each session.
- Google credentials. When you connect Google Search Console or Google Analytics, the OAuth tokens Google issues so QueryAction can read the properties you choose. We store those tokens encrypted. See Google user data for scopes, use, retention and deletion.
- Sites and context. The Sites you add, their public addresses, and the business context you or your authorized apps provide.
- Data sources you connect. When you connect a source such as Google Search Console or Google Analytics, the reports QueryAction collects for the properties you choose, for example clicks, impressions, queries, pages, users, sessions and events. We store them as Evidence for your Site.
- Research. The queries and pages you ask QueryAction to research, the results, and the recommendations created for your Sites.
- Apps and agents you authorize. The apps and agents you connect to QueryAction, the permissions you grant them and when you grant or revoke them, and server logs of tool calls (tool name, outcome and timing, without their content).
- Billing. Your plan, usage and payment status. Payments are processed by our payment provider; we do not receive or store your full card details.
- Technical data. Cookies that keep you signed in, and server logs of requests to the service, used for security and troubleshooting. On QueryAction’s own public pages, such as the home, pricing, agents and legal pages, Google Analytics measures visits and Founder purchases. In the European Economic Area, the United Kingdom and Switzerland, a banner lets you accept or reject its cookies, and we remember your choice in your browser. There, Analytics cookies stay off until you accept (our legal basis there is your consent). If we cannot tell where you are, we treat you the same way. Elsewhere we show no banner and Analytics cookies are on; you can block them in your browser or with Google’s Analytics opt-out add-on. Google Signals and ad personalization are off. Google receives the page address, the page you came from, your browser and device data, and a location derived from your IP address. We do not load it on account, connection or authorization pages, except the payment confirmation page, where it records the purchase with a fixed address, never the real page address. When a Founder payment is confirmed, our server also reports the purchase to Google Analytics (an order reference derived from the checkout, the amount and the currency, and, if you allowed Analytics cookies, the Analytics identifiers already in your browser; never your name, e-mail or account), so it is counted once even if the page does not load. To do that, we store those Analytics identifiers with your checkout when you start it, only if the purchase report is allowed, and delete them as soon as the report is sent, or after 7 days if no payment follows. It follows your choice: nothing is sent if you rejected Analytics cookies, or if you made no choice in a region where they are off by default. Analytics uses Google’s Consent Mode: until you accept, Google may receive cookieless measurement pings from our public pages, without Analytics cookies.
How we use it
We use this information to provide the service you ask for: to sign you in, collect and show your data, run the analyses and research you request, bill your plan, protect the service against abuse, and answer support requests. We do not sell personal information, and we do not use your data for advertising.
Google user data
QueryAction reads Google Search Console and Google Analytics only for the properties you authorize, and only to show metrics and reports in the web app and in MCP tools you authorize, to e-mail you a weekly report for each Site at the verified e-mail address on your account (weekly report e-mail is on by default unless you turn it off), summarizing stored Search Console and Analytics metrics and naming top search queries and pages from your connected sources, with an unsubscribe link in each message, and to answer your growth questions about your Sites using that stored data. We do not use Google user data for advertising, we do not sell it, and we do not use it to develop, improve or train generalized AI or machine-learning models. QueryAction’s own servers do not send your Search Console or Analytics data to third-party AI model providers; weekly reports and tracking views are computed from stored data without calling an external model. If you authorize an external app through MCP, that app can read only what its granted Site permissions allow; its provider then handles that data under its own terms.
Google API scopes. QueryAction requests these Google OAuth scopes:
- openid, email and profile — to sign you in and identify your account.
- https://www.googleapis.com/auth/webmasters.readonly — when you connect Google Search Console, to read Search Console reports for the properties you choose.
- https://www.googleapis.com/auth/analytics.readonly — when you connect Google Analytics, to read Analytics reports for the properties you choose.
Search Console and Google Analytics connect flows request only the read-only data scope for that source, plus the sign-in scopes above. QueryAction does not request https://www.googleapis.com/auth/analytics.edit or any other Google write scope during connect. If a separate “Create Google Analytics” feature is enabled for your account and you choose it, QueryAction may additionally request https://www.googleapis.com/auth/analytics.edit only for that action, to create one GA4 property and one web data stream for your Site (and, if you have no Analytics account, to start account creation at Google, which you finish by accepting Google’s terms). QueryAction never edits, deletes or shares your other Analytics settings, properties or users with that permission.
QueryAction’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Protection and access
Communication between your browser and QueryAction uses HTTPS (TLS). Google OAuth access and refresh tokens are encrypted with an application key before they are stored in our Cloudflare D1 database (Better Auth OAuth token encryption). Cached Search Console and Analytics report data, including Evidence and daily metrics, is stored in D1 without an additional application-layer encryption step; Cloudflare encrypts D1 storage at rest as part of its platform.
The Site owner and people the owner has granted access to the Site can read that Site’s Google-derived data through the QueryAction web app.
Google-derived data also appears in weekly report records and collection results in the database; all are deleted when you remove the Site. During Google Analytics property selection, QueryAction may keep a short-lived edge cache (about one minute) of Analytics property lookups. Service logs and traces are kept for about 7 days. Routine telemetry lines record event names, outcomes, durations and similar fields, without Google report content. Failure log lines can include a Site id and an error message cut to 160 characters, plus a short stack trace; they do not include report bodies or tokens. Cloudflare database backups can retain deleted data for a limited time (up to 30 days).
Retention and deletion
We keep Google-derived Site data while the Site remains in your account. There is no automatic expiry for that history while the Site exists.
Google OAuth tokens. Stored Google tokens are shared by your Sites that use the same Google account. They are kept after you disconnect a data source or after you revoke QueryAction in your Google Account. Tokens from a data-source connection are not used to create or refresh your QueryAction sign-in session, and they may still be used for other Sites that share the same Google authorization. After you revoke QueryAction in your Google Account, stored credentials stop working for new Google API access and collection for affected connections shows needs reconnection; we do not automatically delete those credentials or the Google-derived Evidence already saved for your Sites. When you connect a data source, the Google authorization screen may show permissions QueryAction was previously granted, because a single Google authorization can accumulate scopes over time.
When you disconnect Search Console or Google Analytics for a Site (from the Site settings page in the browser, or by confirming a disconnect link your authorized app started, or one you open from Site settings), QueryAction stops collecting new Google data for that source on that Site. Stored Evidence and metrics already collected for the Site stay until you remove the Site or we complete an account-deletion request you send us. You can revoke QueryAction’s access to your Google data at any time at https://myaccount.google.com/permissions.
When you remove a Site (from its settings page or by confirming a removal link your authorized app started, or one you open from Site settings), QueryAction deletes that Site’s connections, collections, Evidence, context, grants, research and opportunities from our database, typically when you confirm removal; cleanup may continue briefly in the background until removal is completed. Usage and security-audit records for that Site are kept in anonymized form; stored Google OAuth tokens are not deleted. Removing a Site does not revoke the Google authorization in your Google Account.
To ask for deletion of your account or other personal data, e-mail hi@queryaction.com; we handle those requests manually. When we complete an account-deletion request, we delete your account, sign-in sessions, stored Google OAuth tokens, connections, Evidence and Sites from our database. Billing and usage records and security-audit records are kept, as described elsewhere in this policy.
Apps and agents you authorize
You can connect AI assistants and other apps to QueryAction through the Model Context Protocol (MCP). An app you authorize can read Search Console and Analytics metrics, queries, pages and reports for the Sites you selected when you approve it, and the Sites it adds for you, and can do what the permissions you grant allow: add Sites, update context, connect Google sources and request collections, request research, and prepare disconnect and removal links that you confirm in the browser. Once an app has read your data, its own provider handles it under that provider’s terms and your agreement with it, not ours. You can revoke an app’s access at any time on the Connected apps page of your account (Site data access ends at once; a token the app already holds stops working within 15 minutes).
Who processes data for us
We use service providers. They process data on our behalf and only to provide those services to us.
- Cloudflare hosts QueryAction, stores its data and sends the service e-mails you receive, such as trial notices and weekly Site reports (on by default for your verified e-mail address unless you turn them off) that summarize stored Search Console and Analytics metrics and name top search queries and pages from your connected sources, each with an unsubscribe link.
- Stripe processes payments and subscriptions. It receives your billing details; we do not receive or store your full card details.
- DataForSEO provides web data. When you or your authorized app request a search, keyword, competitor, backlink or AI visibility analysis, the query or question, the location and language and, for competitor and backlink analyses, your Site’s domain and the competitor domains are sent to DataForSEO, and it returns the results. For page reads and backlink checks you request, QueryAction fetches the public pages involved directly. For an AI visibility check, DataForSEO sends the question you choose to ChatGPT Search or Gemini and returns the answer; QueryAction adds no Site name, domain or Google data to it.
- Google signs you in and provides the Search Console and Analytics data you connect. When you request a page speed audit, the public page address is sent to the Google PageSpeed Insights service. Google Analytics measures visits to our public pages and Founder purchases, as described under Technical data.
Apart from that AI visibility check, QueryAction sends no data to an AI model provider. The apps and agents you authorize are separate from QueryAction and are described above.
How long we keep it
We keep your data while your account is active. When you disconnect a data source, we stop collecting from it, and the data already collected stays as history for that Site. When you remove a Site, we delete that Site’s data; usage and billing records stay, but no longer name the Site. Disconnecting a source or removing a Site does not revoke the Google credentials, which can serve your other Sites; revoke them in your Google Account. When a trial or paid plan ends, research and new Sites need an active plan at once. For 30 days, daily Search Console and Analytics collections continue; after that they stop. Your saved data stays readable, and your Sites and history stay until you remove them or we complete an account-deletion request you send to hi@queryaction.com. We keep some records, such as billing and usage history and security logs, for as long as accounting, dispute handling and legal obligations require.
Your choices
- Disconnect a data source or remove a Site from its settings page, or ask your authorized app to start that flow.
- Turn off weekly report e-mails using the unsubscribe link in each e-mail.
- Revoke an authorized app’s access to your QueryAction account at any time.
- Revoke QueryAction’s access to your Google data at any time in your Google Account at https://myaccount.google.com/permissions.
- Reject Analytics cookies in the banner on our public pages (European Economic Area, United Kingdom and Switzerland), or block them in your browser anywhere. To change your choice later, clear this site’s data in your browser and choose again.
- Stop Google Analytics on our public pages by installing the Google Analytics opt-out browser add-on, or by blocking Google Analytics with a content blocker.
- Ask for a copy, correction or deletion of your personal data, or for deletion of your account, at hi@queryaction.com.
Children
QueryAction is a business service for adults. It is not directed to children.
Changes
If we change this policy in a way that matters, we update the date above and, when appropriate, tell you before the change takes effect.
Contact
Questions about privacy: hi@queryaction.com.