Privacy policy

Last updated: September 2, 2026

What we collect

Account data: your email address and, if you sign in with Google, your name and avatar from your Google profile. Usage data: the domains you trace or research, research-tool and market metadata, your credit ledger, and standard server logs. Payment data: handled entirely by Stripe — we never see or store your card number.

What we do with it

Run the service (generate reports, track credits), prevent abuse (rate limits, fair-use counters), and answer support requests. We do not sell personal data, and we do not use it for advertising.

What is public

Reports are about products, not people: the report for a domain is public, but it is never linked to the account that requested it. Your trace history is visible only to you.

Cookies

We use session cookies for sign-in. When you start a Search Console connection, we also use short-lived, HttpOnly OAuth state and PKCE cookies for up to ten minutes to protect that authorization flow. We do not use third-party advertising or cross-site tracking cookies.

Google Search Console data

Search Console is an optional, separate read-only connection. If you connect it, we read the properties you can access and Search Analytics fields such as dates, queries, pages, devices, clicks, impressions, CTR, and average position. We use this data only for your private dashboard and analyses you explicitly request. It is not placed in our shared tool cache, sold, used for advertising profiles, or used to train a general Tracetify model.

We store the Google refresh token encrypted so you can request updated data without reconnecting each time. When you disconnect, Tracetify deletes the local connection, token, properties, and imported snapshots. We do not call Google's remote revoke endpoint because the same Google Cloud project also supports ordinary Google sign-in; remote revocation could revoke those previously granted sign-in scopes as well.

AI-assisted analysis

Search Console data is not sent to an AI provider by default. Only when you actively send a request in the SEO Agent do we use server-side AI model infrastructure to process it with the model provider shown in the selector: Google, Anthropic, OpenAI, Moonshot AI, or Zhipu AI. We send only the allowlisted, minimized fields needed for that request: projected report or Site Audit summaries, selected Search Console aggregate metrics and rows, recent conversation text, and tool-result summaries. We do not send Google OAuth tokens, Google or Tracetify email addresses, raw provider responses, or internal account and property database identifiers.

AI infrastructure and model providers may retain outputs and usage metadata under their own terms for billing, security, analytics, and support. Their policies do not uniformly promise zero retention or zero training. Tracetify therefore does not make either promise; the Agent remains subject to our privacy, pricing, and commercial-use approval controls.

Shopify app

If you install the Tracetify Shopify app, we store your shop domain, an encrypted Shopify API access token, and your subscription tier. With the read_products, write_products, read_content, and write_content permissions, the app reads your product, collection, and page content to run AI visibility scans and to prepare content drafts. It writes changes back to your store only when you explicitly apply a fix or click publish on a draft — never automatically.

When you use the ghostwriting feature, the product text you selected (titles, descriptions, tags, and metafields) is sent to Anthropic's Claude model through the WaveSpeed gateway to generate the draft. The app does not request or store any data about your store's customers, so Shopify customer data requests have nothing to return or delete. When Shopify sends the shop redact webhook after you uninstall, we delete all stored data for that shop.

Browser extension

The Tracetify browser extension handles the URL and markup of the page you are viewing so it can provide its on-page SEO and GEO analysis. The URL and page fields it reads — including titles, meta tags, headings, images, links, structured data, and social tags — are parsed locally in your browser. The extension also requests that site's robots.txt directly from the site and evaluates its rules locally. Raw page markup is not sent to Tracetify.

After you connect a Tracetify account, the extension sends an in-memory API key to Tracetify over HTTPS for account features. Growth-report searches, traces, and research requests include the current domain, but not the page markup. If you click the AI brand visibility link, the extension also puts the current domain in that Tracetify page's URL so the web tool can be prefilled; nothing is sent through that link until you click it. The balance request does not include a page domain.

The Search Console overview returns data for your active connected property, which may not be the same site as the page you are viewing. The extension compares the property with the current hostname locally and shows a warning if they differ. These requests may appear in our standard server logs as described above, but we do not use them to build a profile of your browsing.

The plaintext copy of the API key stored by the extension is held only in Chrome's in-memory session storage, which is cleared when Chrome restarts or the extension is reloaded, updated, or disabled. Tracetify stores a one-way hash, prefix, and operational metadata for the key so it can authenticate and audit requests. Clearing the browser copy does not revoke that server-side key record; it remains active until it is revoked or the account is deleted. You can revoke it at any time in API key settings on tracetify.com.

Results cached by the extension use the same session-only Chrome storage. Separately, Tracetify normally attempts to cache completed research results in Upstash Redis for up to seven days so an identical lookup can be reused. A cache write can fail, so we do not guarantee that a result was cached or that retrying will be free.

During account connection, the extension also keeps the numeric ID of the tab that opened the connection page in session storage. It uses that ID only to return you to the page you were analysing after the key handoff, then deletes it. If the handoff cannot finish, the value is cleared with the rest of the extension session data.

Tracetify also keeps account-level recent-search metadata for successful research lookups, including lookups served from the server cache. That history identifies the account, research tool, normalized target domain, market where applicable, and time; it does not contain the full research result. We keep this metadata with the account until account deletion is completed under the retention policy below.

When you explicitly start a research lookup, Tracetify sends the target domain to DataForSEO for the requested rankings, keyword, backlink, competitor, or AI-visibility data. When you explicitly start a trace, Tracetify checks public evidence about that domain. Depending on the source, the domain, a derived search query, or a public URL may be sent to DataForSEO, Apify (Similarweb estimates and Google Ads Transparency), Bright Data (rendered public pricing pages and X profiles), Meta's Ad Library, Kie.ai (extracting facts from selected public-page text), and public websites or APIs such as the target site, Hacker News, Reddit, Internet Archive, TrustMRR, Cloudflare Radar, and domain-registration services. These transfers happen to provide the lookup you requested; page markup collected by the extension itself is not included.

The extension is permitted on HTTP and HTTPS pages because its user-facing analysis can be run on any ordinary website. Its content script and service worker wait for requests from the open panel or for an action you take; they do not passively build a browsing history. The extension does not inject ads, create advertising profiles, or sell user data.

Chrome Web Store Limited Use

Tracetify's use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. We use that data only to provide or improve the extension's single purpose and related security, reliability, and support functions. We transfer it only when necessary to provide or improve that purpose, comply with applicable law, protect against security threats, fraud, or abuse, or complete a merger, acquisition, or sale of assets after obtaining explicit prior user consent.

We do not use or transfer Chrome user data for personalized, retargeted, or interest-based advertising, or to determine creditworthiness or for lending. Humans do not read private data derived from the extension — such as locally handled page data, authenticated request metadata, or connected-account data — except with the user's explicit consent to inspect specific data for support, when necessary for security or abuse investigation, when required by law, or in aggregated and anonymized form for permitted internal operations. This restriction does not prevent editorial review of public web sources or public business reports that are not linked to the account that requested them.

Processors

Infrastructure and services that process data on our behalf include Vercel (hosting), Neon (database), Upstash Redis (server-side cache), and Upstash QStash (signed delivery and retry of asynchronous trace job identifiers; the worker reads the target domain from Tracetify). Stripe processes payments. Google provides OAuth sign-in, Search Console, and Gemini. DataForSEO provides search, keyword, backlink, competitor, trends, and AI-visibility data; Apify provides Similarweb estimates and Google Ads Transparency collection; Bright Data renders public pricing pages and X profiles; Meta provides Ad Library results; and Kie.ai extracts structured facts from selected public-source text for reports. Shopify provides the app platform, and WaveSpeed is the Shopify app's ghostwriting model gateway. Server-side AI infrastructure and the selected model provider also process a request when you actively use the SEO Agent. Report evidence is collected from public third-party sources.

Google API Limited Use

Tracetify's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Retention and deletion

Account data is kept while your account exists. Email support@tracetify.com to delete your account; we remove personal data within 30 days. Public reports, which contain no personal data, may remain.

Contact

support@tracetify.com