Cookie policy

This page lists cookies and similar storage for ai-visibility-tracker.com. It also clarifies how cookies and tokens typically appear in full AI visibility tracking deployments, because practitioners often confuse “cookies on a marketing site” with “authenticated sessions inside a monitoring product.”

Current stance for this domain

The static build ships minimal JavaScript for navigation. If Rankscale adds analytics, consent banners, or embedded widgets, update this page with exact cookie names, lifetimes, purposes, and any consent management platform identifiers. Until then, expect at most first-party infrastructure cookies from the hosting stack, depending on provider defaults.

Browser storage

This site does not require local storage for core reading behavior. If experiments add client-side preferences, document the key names and provide a reset path.

How production AI visibility trackers use sessions

When teams monitor consumer chat UIs, their tooling may authenticate with vendor accounts and therefore rely on session cookies or OAuth tokens managed by the vendor’s domain—not by this site. Those mechanics belong to the monitoring provider’s security documentation: how tokens rotate, how multi-factor authentication is enforced, and how session hijacking is mitigated. Readers evaluating software should ask vendors for a clear data flow diagram from prompt execution through storage.

Third-party analytics on outbound links

Links to Rankscale may include UTM parameters. Those are query strings, not cookies, but analytics on the destination may set cookies when you land. Review Rankscale’s cookie policy when you leave this domain.

Updates

Material changes to cookie use on this domain should be reflected here with an effective date and, where required by law, consent flows before non-essential cookies activate.

Consent logging in downstream products

If you later integrate Rankscale or another AI visibility tracker, your organization may need consent logs showing which users accepted analytics or marketing cookies inside those applications. This static site may remain minimal while the product console is not. Compliance teams should map each surface separately rather than assuming one cookie policy covers both.

Technical note on SameSite and embedded frames

Should this site ever embed third-party frames (for example a booking widget), those frames may introduce additional cookies governed by the third party’s policy. We will list them explicitly if that happens, because cross-site cookie behavior is exactly the sort of invisible mechanic that breaks auditors’ spreadsheets.

Do Not Track

Historically some browsers sent DNT headers; industry adoption was uneven. If regulators in your region require honoring similar signals for analytics cookies, ensure your operational analytics vendor documents behavior; this informational site may remain static without ad-tech trackers even as your product environment grows more complex.