Cookie notice

Effective August 3, 2026 · Version 2026-08-03

The short version

Two kinds of cookie run here. Sign-in cookies, without which the site cannot know who you are, and two first-party analytics cookies holding random identifiers so we can see which lessons get used. There are no advertising cookies, no third-party trackers, and no cross-site tracking. Nothing here is sold or shared with an ad network.

Sign-in and security

Our authentication provider, Clerk, sets the cookies that keep you signed in and protect the session, on codewithvibes.com and on Clerk's own domain. They last for the session or until the session expires, depending on the cookie. These are essential: block them and you cannot sign in or reach anything you paid for.

Analytics

cwv_anonymous_id is first-party, holds a random identifier, and lasts up to one year. It ties page and course events from the same browser together.

cwv_session_id is first-party, holds a random identifier, and expires after 30 minutes of inactivity. It groups activity into a single visit.

Neither contains your name, email, search text, payment identifiers, or IP address. If you sign in later, activity from that browser can be connected to your account so we can follow the funnel from landing page to purchase. PostHog, our product analytics service, may set its own first-party cookies for the same purpose; it runs with autocapture off, session recording off, no profiles for anonymous visitors, and the IP address stripped from stored events. Plausible, which covers the marketing pages, uses no cookies at all.

When they get set

The analytics cookies are set when you arrive, not after a prompt. There is no consent banner on this site. If you are in a place whose rules expect one, the honest position is that we have chosen not to run one and you should use the controls below instead of relying on us to ask.

Turning them off

Every browser can block or clear cookies for a single site, and doing that here removes the analytics identifiers and breaks the link between your browsing and any later sign-in. Blocking all cookies also blocks the sign-in cookies, which means the course will not load. Most browsers also send a Do Not Track or Global Privacy Control signal, and our analytics services honour those where they support them.

Browser storage

The app uses ordinary local and session storage for interface state such as your place in a lesson and your reading preferences. That data stays in your browser, is never sent to us as analytics, and clearing site data removes it.

Changes and contact

If the cookies change, this page changes with a new effective date. Questions: privacy@codewithvibes.com. The wider picture is in the privacy policy.

Cookie notice · Code With Vibes