Cookie Policy

Last updated: September 30, 2026

This page explains the cookies CircuitEdge uses and why.

The short version

  • We only use cookies that keep you signed in and keep the site secure.
  • No analytics, advertising, or tracking cookies.
  • That's why there's no cookie banner. If that ever changes, we'll ask first.

This summary is for convenience. The full text below is what applies.

1. What cookies are

Cookies are small text files a website stores in your browser. Some are needed for a site to work, such as remembering that you're signed in. Others are used for analytics or advertising. CircuitEdge only uses the first kind.

2. Cookies we use

CookieSet byPurposeDuration
sb-<id>-auth-token (may be split into .0, .1, …)CircuitEdge (via Supabase)Keeps you signed in. Only set after you sign in.Until you sign out, or it expires
sb-<id>-auth-token-code-verifierCircuitEdge (via Supabase)Secures the GitHub/Google sign-in processRemoved after sign-in completes
__cf_bm and similarCloudflareProtects the site from bots and abuseUp to 30 minutes

3. Cookies we don't use

No analytics cookies, no advertising cookies, and no social-media tracking pixels. Because every cookie we use is strictly necessary for the site to work, we don't show a cookie consent banner. If we ever add optional cookies, such as analytics, we'll update this policy and ask for your consent first.

4. Third-party sites

When you sign in with GitHub or Google, or pay on Stripe's checkout page, you're briefly on their websites, and they may set their own cookies there under their own policies. Those cookies belong to those sites, not to CircuitEdge.

5. Managing cookies

You can view and delete cookies in your browser settings. If you block CircuitEdge's cookies, you'll still be able to read free courses, but you won't be able to sign in, save progress, or use Premium.

6. More information

See our Privacy Policy for how we handle personal information, or email alfredrnavarro@gmail.com with any questions.