AISEOLab
FeaturesPricingBlogDocs
Sign inStart free

Legal

Cookie Policy

Every cookie we set, what it does, and how to turn it off.

Effective: 3 May 2026Last updated: 3 May 2026Entity: AISEOLabJurisdiction: United Kingdom

Working draft — under legal review.

This document reflects how we currently operate. It is shared in good faith but has not yet been reviewed by qualified counsel. If anything here is inaccurate or ambiguous, please email privacy@aiseolab.ai.

1. The short version

We don’t use tracking cookies, advertising cookies, or analytics cookies that profile you. Every cookie listed below is either functional (the site needs it to work) or security (Cloudflare uses it to keep abuse off public endpoints).

2. What cookies are

Cookies are small text files stored by your browser when you visit a site. They let the site remember things about your visit (like whether you’re signed in or what theme you prefer).

Cookies are first-party (set by us) or third-party (set by services we use, like Cloudflare). Both kinds are listed below.

3. Cookies we use

The complete list of cookies you may encounter on the Service:

NamePurposeTypeDurationSource
themeRemembers your light/dark theme preference.Functional1 yearFirst-party
sb-access-tokenAuthenticates your session with our backend (Supabase). Set after sign-in.Authentication1 hour (refreshed automatically)First-party
sb-refresh-tokenLets us silently refresh your access token without requiring re-login.Authentication30 daysFirst-party
cf_clearanceSet by Cloudflare Turnstile after passing a bot challenge on the public scan endpoint.Security30 daysThird-party
__cf_bmCloudflare bot management cookie used during browsing sessions.Security30 minutesThird-party

4. What we don’t use

We deliberately do not use:

  • Google Analytics, Mixpanel, Segment, or other tracking SDKs.
  • Advertising or remarketing cookies (Facebook Pixel, Google Ads, etc.).
  • Browser fingerprinting techniques to identify visitors across sessions.
  • Cross-site tracking pixels of any kind.

Server-side, we measure traffic by counting requests in our hosting provider’s standard logs (paths, response codes, durations). We hash IP addresses with SHA-256 before storing them, so we cannot identify individual visitors.

5. Managing cookies

Most browsers let you view, delete, or block cookies through settings. Be aware that blocking authentication cookies will prevent you from staying signed in. Blocking Cloudflare’s security cookies may cause repeated bot challenges.

Useful guides: Chrome · Firefox · Safari · Edge

6. Changes to this policy

When we add or remove a cookie type, we update this page and the “Last updated” date at the top. For substantive changes affecting authenticated users, we email a notice in addition.

7. Contact

Questions about cookies on the Service: privacy@aiseolab.ai. For our broader data practices, see the Privacy Policy.

On this page

  1. 01The short version
  2. 02What cookies are
  3. 03Cookies we use
  4. 04What we don’t use
  5. 05Managing cookies
  6. 06Changes
  7. 07Contact
AISEOLab

Make your site visible to AI engines, navigable by AI agents.

hello@aiseolab.ai

Product

  • Features
  • Pricing
  • Compared with
  • AEO & GEOOptimization
  • Agent Readiness
  • Agentic Commerce

Resources

  • Blog
  • Docs
  • API reference
  • Scanner checks
  • Changelog
  • llms.txt

Company

  • About
  • Contact
  • Security
  • Status

Legal

  • Privacy
  • Terms
  • Cookies
  • DPA

\u00A9 2026 AISEOLab. All rights reserved.

Built for the AI era \u00B7 v1.0