Privacy

Trace stores your Google account identifier, email, name, session token hash, submitted public URLs, generated report records, unlock state, notification requests, and operational metadata such as timestamps and report generation status.

Trace may store a hashed IP-derived value for quota and abuse prevention. Trace does not ask you to submit private credentials, private documents, or non-public customer data.

Trace uses this data to authenticate you, generate reports, show previews, send a report-ready email when you request one, prevent abuse, debug failures, improve report quality, and operate the invite-only preview.

Submitted public URLs are reviewed with AI systems and supporting tools that inspect public evidence. Report output should be treated as AI-generated analysis.

Your completed reports are private to your account by default. Trace only serves a report on the public report route after it has been explicitly marked for publication.

If you request diagnosis for the same normalized public URL as another report, Trace may copy a cached completed report during the cache window to reduce duplicate generation.

Trace keeps account, session, URL, report, and operational records as needed to provide the preview, debug reliability, prevent abuse, and support commercial follow-up.

You can request deletion or correction through the invite, sales, or support thread where you received Trace access.

Trace uses Google for sign-in, Cloudflare for hosting, data storage, Resend for requested transactional notification emails, and AI tooling for report generation. Payment providers may be used if a paid unlock flow is offered.

Trace uses account-gated report access, private-by-default report routes, hashed session tokens, and operational controls for the report engine. No internet service can guarantee perfect security.