Privacy policy

Shield with checkmark suggesting privacy protections and policy scope.

This page describes privacy practices for ai-visibility-tracker.com as a static reference site. It also explains, in plain language, what data a full AI visibility tracking product typically touches so readers can separate “reading this domain” from “operating a monitoring program,” which has very different privacy implications.

What we collect on this site

The HTML you load does not require an account on this domain. If you only read pages, we do not operate first-party forms on this site by default. Like any website, requests hit web servers or content delivery networks that may write standard access logs (IP address, user agent, URL path, timestamp, HTTP status). Those logs are operational artifacts of hosting, not part of an AI visibility measurement pipeline.

How that differs from an AI visibility tracker product

When organizations deploy an AI visibility tracker, they intentionally process prompts that may contain brand names, competitor names, and sometimes sensitive commercial questions. The product stores model outputs, which can include personal data if prompts were poorly curated. Vendor privacy programs therefore need data retention limits, role-based access control, encryption at rest and in transit, subprocessors lists, and customer agreements that define lawful bases or business purposes. None of that processing happens automatically simply because you read this informational site.

Hosting and analytics

Your browser talks to our hosting provider and may write logs there. If the operator adds analytics or tags later, this page should list vendors, purposes, retention, and opt-out steps. Legal should confirm the final list before launch. If embedded widgets appear (for example chat support), their controllers must be named here with links to their policies.

Third party sites

When you leave this domain for a vendor signup flow, that vendor’s privacy policy governs data you submit there. Outbound product links are labeled and use campaign parameters so vendors can attribute traffic; those destinations set their own cookies and forms.

Children and sensitive categories

This reference content is aimed at professionals evaluating measurement practice. It is not directed at children. Do not submit health, financial, or other special-category data through email unless your jurisdiction permits and you have a lawful basis.

Contact

Use the contact page for privacy questions related to this domain. For questions about Rankscale product data handling, use the addresses published in Rankscale’s product privacy documentation.

Data minimization for prompts

Even when this site does not collect prompts, your internal AI visibility tracking program should minimize personal data in prompt baskets: avoid customer names, ticket numbers, or health details unless legal approves a purpose limitation and retention schedule. Pseudonymize competitor codenames when possible. The mechanics of good tracking include operational hygiene, not only parser accuracy.