Privacy
Privacy policy
Last updated: November 18, 2026
Account and workspace data
When you create an account, we store your email address, optional display name and avatar, session records, workspace timezone, site domains, and the key-page URLs you choose to monitor. Email sign-in uses one-time links; AllSites does not store an account password.
First-party analytics and monitoring
If you install the AllSites script on a site you control, we store privacy-limited page, source, country, device, and custom-event measurements after bot and human-activity checks. Query strings are removed except campaign parameters. We also store homepage uptime checks and daily snapshots of public title, description, H1, canonical, robots directives, and HTTP status for the homepage and key pages you configured.
Google Search Console data
If you choose Connect Google, we request only webmasters.readonly access. We store the Search Console resources you can access, the resource you match to each site, daily clicks, impressions, click-through rate, average position, limited query/page/country/device summaries, and URL Inspection results for your configured key pages. Google can omit anonymous or rare queries. We do not edit your website or Search Console settings.
Google credentials
The Google refresh token is encrypted at rest using AES-GCM. Short-lived access tokens are kept only in memory and are not written to the database. You can disconnect Google in Settings; AllSites attempts to revoke the token and deletes the stored refresh token and resource mappings. Historical reports remain until you delete the related site or account. Deleting your account deletes the whole workspace and its stored data.
How we use and share data
We use data only to provide, secure, troubleshoot, and improve the portfolio monitoring features you requested. We do not sell personal information or Google user data, and we do not use Google user data for advertising. Service providers such as Cloudflare may process request and storage data to operate and secure the service. Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Subscriptions and Dodo Payments
Dodo Payments acts as Merchant of Record for paid subscriptions. Dodo processes checkout, payment methods, applicable taxes, invoices, renewals, cancellations, and refunds under its own privacy terms. We receive identifiers, customer email, subscription status, billing period, payment status, and refund status needed to provide access. We do not store complete card numbers.
Public-page checker and technical logs
The public checker fetches the URL entered, its robots.txt, sitemap files, and homepage. It stores the checked domain and result category, not the full submitted URL or query parameters. Cloudflare may process request metadata, including IP addresses, to deliver and secure the site. We use IP-based rate limits but do not add raw IP addresses to product analytics tables.
Retention and requests
Raw first-party analytics events are retained for up to 90 days and detailed uptime checks for up to 30 days; daily aggregates and connected-service history may remain while your account is active so trends can be compared. If a trial ends without payment, the workspace becomes read-only and monitoring and sync pause. Workspace data is kept for at least 30 days; we send another reminder after 30 days and do not automatically delete it. You can disconnect Google or delete the account in Settings. For access, correction, or deletion questions, use the contact form.