QueryAtlas
Start free

Privacy & data access

Last updated

QueryAtlas is operated by ChromeStats LLC. This policy covers our dashboard, query tools, MCP access, and all connected reporting services, along with account, billing, and product-usage data. Google sign-in provides your verified identity, name, and email address. Connecting a reporting service separately authorizes access to that service; signing in alone does not grant access to your reports.

Reporting services and data we access

Each Google product is connected in its own consent request, and QueryAtlas asks only for the permissions that product needs. Bing is connected separately through Bing Webmaster Tools. We access these services only for the accounts and resources you connect and enable:

  • Google Analytics: your GA4 account and property names, and reports such as sessions and page views for the properties you enable.
  • Google Search Console: your verified sites, search performance reports, URL inspection results, and sitemap processing status. If you enable sitemap submissions, QueryAtlas can submit sitemap or RSS/Atom feed URLs for the sites you select, when you request it.
  • Google AdSense: your account names and earnings, impression, and click reports.
  • Google Ad Manager: saved reports and their results, and hidden measurement reports that QueryAtlas creates at your request.
  • YouTube: your channel's name, image, and all-time totals; the titles, thumbnails, status, and view counts of your uploads; and YouTube Analytics views and watch time. Revenue is not accessed.
  • Bing Webmaster Tools: your verified sites and search performance reports, including clicks, impressions, search queries, and pages. You can connect with Bing OAuth, which requests the read-only webmaster.read permission by default, or webmaster.manage when you select Allow sitemap submissions. Legacy API keys also support sitemap submissions. QueryAtlas submits sitemap or RSS/Atom feed URLs only for selected sites at your request; it does not change site settings. Microsoft's handling of your data is described in the Microsoft Privacy Statement.

Google Analytics, AdSense, and YouTube permissions are read-only. Search Console defaults to read-only access; Allow sitemap submissions requests Google’s broader webmasters permission, which QueryAtlas limits to reporting and sitemap submissions. Ad Manager requires a broader Google permission to create reports. QueryAtlas uses it only to run reports and create fixed hidden measurement reports; it does not change ad serving settings.

Chrome User Experience Report (CrUX)

For a site you enable in Search Console, you can also request performance history from Google's Chrome User Experience Report. CrUX provides public, aggregated Chrome performance measurements, such as loading speed, responsiveness, and visual stability. QueryAtlas sends the requested page URL or site origin to Google's CrUX API using an application API key; this does not require a separate Google account permission. These reports do not identify individual visitors, and data may be unavailable for sites or pages without enough eligible traffic.

How we use connected-service data

We use data from Google and Bing only to provide the features you use: listing the properties, sites, accounts, and channels you can enable, showing reports on your dashboard, answering queries you run, and returning results to AI clients you configure, and submitting sitemaps you request. We do not sell this data, use it for advertising, or use it to train AI or machine-learning models. People at ChromeStats do not read your connected-service data except with your permission for a specific support request, when needed for security or to comply with law, or when it is aggregated and anonymized for internal operations.

What is stored

We store your name and email address, connected accounts, selected reporting resources, encrypted Google and Bing connection credentials, records for issued QueryAtlas access tokens, the AI apps you approve (each app's self-reported name and return address), and sign-in sessions. We also record the name, time, and outcome of each query or submission for up to 30 days; these records do not contain query arguments or report results. Submitted sitemap URLs remain with Google or Bing. Provider report results, including CrUX results, are fetched on demand and are not saved. Measurement reports created through QueryAtlas remain hidden in your Ad Manager network. Dashboard preferences, such as the reporting period and card layout, are saved only in your browser.

We record visits to QueryAtlas pages to understand product usage. These records include a fixed page route and title, the visit time, temporary session and visitor identifiers, browser details, and approximate location. They do not include your IP address, provider report data, account details, URL query strings, or referrers. Page-view records are retained for 30 days.

Who we share data with

We do not sell your data. We share, transfer, or disclose account information or connected-service data only in these cases:

  • Reporting providers. QueryAtlas sends authenticated reporting requests and the parameters needed to fulfill them to the service you use. Google and Microsoft process these requests under their own privacy policies. CrUX requests include the page URL or site origin you ask about.
  • Billing services. When you choose a paid plan, we send your account email and an account identifier to Chargebee to manage your subscription. Chargebee and its payment gateway handle checkout, payment details, and invoices. QueryAtlas stores your subscription status and plan; it does not store card details or send reporting data or connection credentials to Chargebee. Chargebee's Privacy Policy describes its handling of billing data.
  • AI clients you configure. When you approve an AI app or configure a QueryAtlas MCP token in an AI client, that client can receive reporting data for resources you enable. Its provider handles the results under its own terms and privacy practices. QueryAtlas does not itself send reports to a model provider.
  • Infrastructure providers acting for us. OVH hosts the QueryAtlas servers and database in the United States. Cloudflare delivers and protects network traffic, so encrypted traffic between your browser and QueryAtlas passes through its network. They process data only to provide these services to ChromeStats.
  • Legal requirements. We may disclose data when required by law or legal process, or when necessary to protect the security of QueryAtlas and its users.

How we protect your data

  • Traffic between your browser, QueryAtlas, and the Google and Microsoft APIs we use is encrypted in transit with HTTPS (TLS).
  • Google and Bing OAuth refresh tokens, and Bing API keys, are encrypted at rest with AES-256-GCM. The encryption key is kept separately from the database, and each credential is bound to its account and connection.
  • Sign-in session tokens and MCP access tokens are stored only as one-way SHA-256 hashes. Session cookies are HTTP-only and secure, and sessions expire after 7 days. MCP tokens expire after 90 days and can be revoked at any time.
  • AI apps you approve receive access tokens that expire after one hour and refresh tokens that rotate on each use. An approval ends after 90 days without use, and you can disconnect an app at any time on MCP / API.
  • Google sign-in uses OAuth with PKCE and a sign-in state tied to your browser. Changes require a per-session request token.
  • Every report request is checked against your account and the resources you have enabled, so one user cannot access another user's data. Report results are kept in memory only while a request is processed.
  • Server and database access is limited to authorized ChromeStats personnel and to a dedicated service account restricted to QueryAtlas data.

YouTube API Services

QueryAtlas uses YouTube API Services to show your channel details, videos, and analytics. By connecting YouTube, you agree to be bound by the YouTube Terms of Service. Google's handling of your data is described in the Google Privacy Policy. You can revoke QueryAtlas's access to your YouTube data at any time from the Google security settings page.

Your controls

Newly discovered sources are selected by default when you connect or refresh an account. You can deselect individual sources or all sources under an account on the Connections page. Refreshing preserves existing deselections. MCP tokens and approved AI apps can access all selected sources, including newly discovered ones.

You can disable resources, revoke MCP tokens, disconnect approved AI apps, disconnect provider accounts, or delete your account. Account deletion first cancels an existing subscription and then ends access and removes your saved identity and related records. We retain a minimal deletion record to keep the account from being restored; re-enrollment requires assistance. Disconnecting an account removes its stored credentials. You can separately revoke Google access in your Google Account, or revoke Bing OAuth access or rotate your Bing key in Bing Webmaster Tools. Google and Bing permissions are separate from QueryAtlas MCP access: revoking an MCP token or disconnecting an approved app stops that client's access, while disconnecting a provider account removes QueryAtlas's stored credentials for that connection.

Use of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Contact

For questions or requests about your data, email [email protected].

Return to workspace