Privacy.

What you type into the form: your domain, a one-line description, and the category you want checked. This is the input to the report.

Your email, at checkout. Collected by Stripe and used to deliver and recover purchases, manage optional rechecks, and send receipts. It is not added to a mailing list, and there is no mailing list to add it to.

The report itself: the generated questions, every engine answer verbatim, the extracted results, and the scores.

Support messages, if you send one.

Accounts store your name, email, verification status, sign-in method and database sessions. Session cookies are required to keep you signed in. You sign in with Google, Apple or a short-lived email link; we do not ask for a password. Purchase recovery uses expiring proof sent to the purchase mailbox; typing a matching email never attaches a report.

Authentication and abuse protection may record IP addresses or salted network hashes. Claim proofs expire after 30 minutes. Contact support for data deletion; billing records may need to be retained for legal obligations.

Connecting Google Analytics, Google Ads or Meta Ads is optional and requires your permission. We read the properties or advertising accounts that your connected account can access so you can choose which one to use. We store that selection, its currency or time zone where relevant, the access credentials and a cached report. Credentials and cached reports are encrypted on our servers and are available through your authenticated project.

Google Analytics access is read-only. We read aggregate session counts by date and session source to show visits from AI sources for the selected property. Advertising reports contain campaign identifiers, names, status, dates and aggregate impressions, clicks, cost and conversions or actions. Reports cover a bounded date range and are fetched when you request an update. Selecting a Google Analytics property can also fetch its initial report; opening a report reads its saved copy.

Google Ads requires a permission that also allows account and campaign management, even for reporting. Connecting an account does not approve a campaign launch. Where campaign controls are available, creating and activating a campaign require separate approvals. We retain the approved content, account and budget details, provider identifiers and operation receipts to track those actions. Meta campaign controls use a separate permission flow from Meta reporting.

Connected reporting data is used to display your project's analytics. It is not sold, used to train AI models or used to build advertising audiences. Our hosting and database providers process it to operate these features. Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Disconnecting a reporting connection removes its saved credentials, account selection and cached report, and requests revocation where supported. We tell you if the provider has not confirmed revocation; you can also remove access in your provider account. Revoking Google access may disconnect other Google services you connected here. Disconnecting reporting does not stop an existing advertising campaign or erase its approvals, operation receipts and budget commitments. Pause campaigns before removing the access needed to manage them, and contact support about deleting retained campaign records.

No advertising cookies, tracking pixels, session recording or fingerprinting. We record limited first-party events: landing and sample engagement, checkout and payment status, report completion and views, and recheck lifecycle changes. Financial events come from verified server records. Browser measurement respects Do Not Track, sets no persistent identifier, and sends no email, report content, private report URL or claim token. We keep aggregate events on our own database. For aggregate page counts we also use Cloudflare Web Analytics and Plausible, both cookieless; report, tracking and verification links are redacted before they are sent, and query parameters other than campaign tags are dropped.

To see how visitors use our public pages we also use PostHog, hosted in the EU. It runs only on public pages, never on report, tracking or verification links, your dashboard or account pages, and not at all when your browser sends Do Not Track or Global Privacy Control. It records page views, time on page and clicks on page elements, never what you type, with page addresses redacted the same way. Events go through our own domain without your IP address, and it sets no cookie and stores no identifier in your browser, so each visit is anonymous. It never receives your email or report content, and session recording is off.

Card details never touch this service — Stripe handles payment end to end.

A customer can add our snippet to their own site to count visits that arrive from AI engines such as ChatGPT or Perplexity. It sets no cookies and reads no browser storage. For any other visit it sends nothing. For a visit from an AI engine it sends the site key, the engine's host name, the page path (without its query string) and the engine tag in the link, and we keep only a daily count per engine and page path. Before anything is saved we drop the path's query string and fragment, replace any part of it that looks like an email address, an ID, a number or a token, and keep at most three path segments. That cannot catch every personal detail a site puts in its URLs (a name looks like any other word), so sites using the snippet should keep personal data out of their URLs. No IP address, user agent or visitor identifier is stored with the counts. To rate-limit the counter we keep a salted hash of the sending network, and the project, for the current hour; each of those records is deleted two hours after its hour ends.

Producing a report means sending your category and generated questions to the AI providers being measured (OpenAI, Anthropic, Perplexity, Google, xAI). This is unavoidable: the measurement is what those services answer.

One-time sign-in emails and site hosting go through Cloudflare. Report and service emails go through Resend. Payments go through Stripe, and application data is stored with Supabase. If you choose Google or Apple sign-in, that provider handles authentication.

Your report lives at an unguessable URL. It is not indexed and not listed anywhere, but it is not password-protected either — anyone you send the link to can read it. Share it deliberately.

A badge verification page is deliberately public, and shows only what the badge claims: the engine, the rate, and the date.

Ask via support to request deletion of your account, reports and associated contact details. We verify ownership before acting and explain any billing records we must retain. Include the report ID if known.

support@recomention.com