Privacy & data
Updated October 15, 2026
Google sign-in
We use Google to confirm your identity and receive your Google account ID, verified email and display name. We do not request access to Gmail, Drive or contacts. Google access tokens are used during sign-in and are not saved as project data.
Session cookies
A signed, HttpOnly session cookie keeps you signed in for up to seven days. Signing out removes it from this browser. We also use a short-lived cookie to protect the Google sign-in request. No advertising cookies are used.
Your page content
When you audit a URL, Cloudflare fetches the public page. When you paste HTML, it is sent to our audit service for processing. Auditing does not automatically send page content to an AI model. Choosing AI drafting separately sends the brief you supply. Avoid submitting sensitive or private HTML.
Browser-saved projects
Projects are stored in this browser and separated by your Google account ID. They do not sync across devices. You can export them or delete them using the workspace control. Clearing browser site data also removes them. Legacy guest projects are not automatically attached to an account.
Public tools and extension
Public template drafts and keyword counts run in your browser. Explicitly saved drafts remain in browser storage, separate from account projects. Page inspection sends the submitted URL or HTML to Cloudflare. Domain lookups send the domain to Cloudflare DNS and public RDAP services. The developer extension captures selected pages and search results locally when you choose inspection or capture. Choosing registration lookup sends up to five displayed exact domain names and a language code to AI Dot SEO, which queries public Cloudflare DNS, IANA and RDAP services; search terms, page URLs, result paths and captured text are not sent. The developer preview includes an explicit GEO audit: choosing Audit public page sends only the confirmed public URL and language to AI Dot SEO to fetch initial HTML and robots.txt, without browser cookies or local DOM/HTML. Review private URL parameters before submission. Registration and GEO lookups use no account session or account storage. Generic related-tool links do not carry the inspected URL. External research links open their named services. AI availability is shown in each drafting tool.
Initial and rendered HTML comparison
The comparison workbench first captures or previews HTML locally. After you review the snapshot, separately consent and submit, it sends the selected public URL, language and reviewed HTML to AI Dot SEO. A manual initial snapshot is also sent if selected. In public initial mode, the service reads initial HTML anonymously without forwarding your browser cookies; these comparisons use no AI or account project storage. Snapshot markup can include scripts and private content, so review it before transmitting. Unedited extension captures retain a local tab and document binding; those browser identifiers are not submitted. Exported reports include source metadata and snapshot receipts, not raw HTML. Local snapshot export is a separate action.
Crawler and sitemap inspection
Choosing a crawler check sends only the public page URL and report language to AI Dot SEO. The service reads the public page, the initial origin’s robots.txt and up to three selected same-origin sitemap resources without your browser cookies. The extension fills the current page URL locally but does not submit it automatically. This check sends no captured HTML or search terms, and uses no AI, account session or project storage. Review private URL parameters before submission. Results describe observed HTTP responses, declared rules and bounded XML evidence, not actual visits or indexing by the named crawlers.
Known backlink verification
CSV and text imports are previewed on this device and are not uploaded automatically. Choosing a check sends the target URL, the selected batch of source URLs, scope and language to AI Dot SEO. The service fetches public source pages without your browser cookies. The target is used for matching, without a separate read. It is read if you supply it as a source or a source redirects to it. This verification uses no AI, account session or project storage. Review private URL parameters before submitting.
Performance reports
Lighthouse report imports and pasted JSON are analyzed on this device, without automatic uploads or browser storage. The measured example loads a public, historical report from this site only when clicked. Explicit requests to /api/performance/review send the report to Cloudflare for stateless analysis, without fetching report URLs, AI processing or saving the report. This analyzer does not evaluate real-user field data.
AI drafts and request history
When AI is available and you choose it, your topic, source text, audience, keyword, tone and output language are sent to Cloudflare Workers AI. We store the generated result with your account ID, request ID, brief fingerprint, attempt state and timestamps in Cloudflare D1 to prevent duplicate model calls and enforce usage limits. The source brief itself is not stored in the request ledger. Pro monthly usage records are kept separately after response cleanup to enforce monthly limits and prevent expired attempts from running again; they contain account and request IDs, billing-period references, units and timestamps, not draft text. Results can be replayed for 24 hours from reservation. Later new attempts clear expired results and remove request records older than seven days; cleanup is not scheduled, so inactive data can remain longer. Avoid sensitive input and verify every generated claim.
Cloud-saved projects
When account storage is available and you choose Save to cloud, the current project and retained revisions are stored in Cloudflare D1 under your Google account ID, so you can open them on another device after signing in. Archiving is reversible and retains project data. Browser-local drafts are separate; cloud saving is an explicit action. Contact us about account data requests.
Website research data
Traffic, backlink and Reverse AdSense reports can be imported and analyzed locally without an account. When platform lookups are available, signing in and choosing a lookup sends the selected domain or publisher ID to AI Dot SEO; a cache miss is queried through our server-managed TabAPI credential. You do not supply a provider key. Account-bound request IDs, fingerprints, usage reservations, timestamps and results are stored in Cloudflare D1 to prevent duplicate paid calls and enforce limits. Public provider reports can be shared from the platform cache for 24 hours by default; this does not share account identities or imported files. Request results can be checked for 24 hours. Later uncached lookups clear expired request results, remove ledger records older than 90 days and clear cache records expired more than seven days ago; cleanup is not scheduled, so inactive data can remain longer. Imported files are not uploaded. No provider lookup or retry runs automatically. Provider estimates and samples do not establish complete traffic, backlink coverage or common site ownership.
First-party usage statistics
We store limited usage events in our Cloudflare D1 database to understand tool actions, Google sign-in, welcome-credit claims, completed platform research and saved upgrade interest. Anonymous activity uses a signed first-party random identifier cookie for up to 30 days. Verified account identifiers are stored as keyed hashes for deduplication and linking an anonymous journey to sign-in; shared-browser identities linked to multiple accounts are not merged. Events include time, tool category, language, predefined acquisition channel and campaign category, cache mode and selected plan interval. We do not add research domains, publisher IDs, reports, AI briefs, email addresses, raw referrer URLs, arbitrary UTM values or IP addresses to these statistics. Reports are aggregate and restricted to the owner account, with internal QA excluded by default. The dashboard shows the last 7 or 30 UTC days; event records are not automatically erased in this version. You can disable statistics using the footer control; Global Privacy Control and Do Not Track are also respected. The opt-out preference cookie lasts one year. Disabling statistics does not remove existing account or usage records or prevent tools from working.
Welcome allowance and plan interest
Claiming the welcome research allowance stores a permanent account eligibility record and its usage in Cloudflare D1. This prevents another 11-credit grant after retries, signing out or clearing browser storage; the grant is issued only once. Checking availability does not claim credits. When you explicitly choose Save upgrade interest, we store your selected monthly or annual interval, the tool category you came from, an exact local return path and the update time under your account. Research targets, query parameters, AI briefs and payment details are not part of this interest record. Saving interest does not activate Pro, send email notifications or authorize a payment. A later save updates your preference. For account data requests, contact us at the address below.
Member profile and usage history
You may save a site display name and a small PNG, JPEG or WebP avatar to your account in Cloudflare D1. They do not change your Google identity or email, and no public profile is created. The member center shows your personal research and AI accounting, separate from supplier costs. Durable allowance entries remain available; Free AI history covers the recent seven days. Expired research report content may no longer identify a tool even while its usage remains recorded. You choose when to export the visible history as CSV.
Infrastructure & contact
Cloudflare hosts this service and may process request metadata for delivery and security. Contact messages are sent through your email app to alexchen261001@gmail.com. For data questions, use the same address.