Collect the minimum needed to explain a result.

What data does a public audit retain?

AISearchOps.com stores only the target, fetch metadata, short evidence excerpts, normalized findings, and score inputs needed to explain a report. It does not expose raw crawled bodies in the application, and anonymous reports expire after 24 hours.

100 percent of anonymous audit reports are assigned a 24-hour expiry; sent email bodies are blanked after delivery. This minimization follows the principle in GDPR Article 5 principles for processing personal data.

Public audit data

Target URL, fetch metadata, minimal visible excerpts, normalized findings, and score inputs are used to build the report. Raw page bodies are not rendered into the application DOM.

Report requests and contact data

When the verified report gate is enabled, AISearchOps.com collects your name, work email, organization, requested domain, verification status, and the version of this notice you accepted. The audit does not start until the single-use email link is verified.

Report-delivery email is operational and required for that gated journey. Product or AI search updates are optional: marketing consent is recorded separately and leaving it unchecked does not prevent the report.

Retention and abuse prevention

Unverified requests are removed after 24 hours. Verified request records are retained for at most 180 days; anonymous report data keeps its existing 24-hour lifetime. Rate-limit identifiers are stored as opaque hashes with short expiries. The lead record stores only a hash of the verification token. The delivery URL is temporarily present in the worker-only email outbox until it is sent, expires, or is purged; it is never returned by the public API or written to request logs.

Provider data

Official provider calls remain disabled in production. Replay observations preserve prompts, citations, provider surface, timing, and a response digest without browser keys or consumer-interface automation.