Cookie Policy

Last updated: 2026-10-06

This page explains what cookies agenticcli.dev sets, why, and how you can manage them.

Essential cookies

WorkOS authentication session. When you sign in, WorkOS AuthKit sets a session cookie to keep you authenticated. This cookie is strictly necessary for the service to work. It is first-party (set on agenticcli.dev) and expires at the end of your session or after a set period defined by WorkOS.

You cannot opt out of essential cookies while using the service — they are required to authenticate you. If you sign out, the session cookie is removed.

Analytics cookies on every public page (Google Analytics)

Google Analytics runs on every visit. We use Google Analytics 4 to count visits and see which pages people read. It runs on every visit to our public pages, for every visitor, as soon as the page loads. It does not wait for the cookie banner, the banner does not turn it off, and it runs even if your browser sends a Do Not Track or Global Privacy Control signal. It never runs on the dashboard, sign-in or CLI login pages.

What it collects. The pages you view, the page or site you came from (the referrer), your browser and device type, and an approximate location that Google works out from your IP address. Google says Google Analytics 4 does not log or store IP addresses. It sets two first-party cookies on agenticcli.dev, _ga (a random id that tells visits apart) and _ga_<id> (keeps the current session together), each for up to 2 years. Google processes this data for us as our processor. Google signals and ad personalisation are switched off. Google keeps this data for the period set in our Google Analytics settings. See how Google uses data from sites that use its services.

How to opt out. Install Google's Google Analytics Opt-out Browser Add-on, which stops Google Analytics on every site, including this one. A content or tracker blocker also works. Clearing your site data for agenticcli.dev deletes the _ga cookies, but they come back on your next visit unless you use one of these.

Session analytics (your choice on the banner)

Consent banner. On your first visit a banner asks whether to allow PostHog session analytics. The banner controls PostHog only, not Google Analytics (above). Until you choose, PostHog sends nothing. If your browser sends a Do Not Track or Global Privacy Control signal, the banner does not show and PostHog sends nothing, with no action needed from you. Your choice is remembered in a first-party cookie, sg_analytics_consent, for 12 months.

If you accept. PostHog stores a random id in your browser's local storage and we record the pages you visit and what you click. We also record sessions (session replay), with what you type in form fields and other sensitive values masked. Requests go through agenticcli.dev itself (a same-origin /ingest path).

If you decline. PostHog stores nothing in your browser. We still count your visit anonymously, without cookies: PostHog computes a hash that changes every day, so there is no identity, no replay and no location.

Signed-in account holders. Product events (sign-in, checkout, purchases, CLI login, scans) are recorded on our servers as part of running the service, whatever you chose on the banner. PostHog is our processor for this, and we send no email address or name. See our Privacy Policy.

You can change your mind at any time: choose Cookie settings in the footer of any page to bring the banner back. Declining there stops PostHog's id and replay and resets the identifier PostHog had stored. It does not stop Google Analytics; use the opt-out above for that. Clearing your cookies also brings the banner back. You can also exercise your rights under our Privacy Policy.

How to manage cookies

All major browsers let you view, block, or delete cookies via their settings menus. Note that blocking essential cookies (the auth session) will prevent you from signing in. The analytics consent cookie (sg_analytics_consent) can be cleared the same way, which brings the banner back so you can choose again.

Because PostHog data is stored in local storage rather than a cookie, and is sent same-origin (not to a separate third-party domain), a browser's “block third-party cookies” setting will not stop it on its own. Use the consent banner above, or clear your browser's site data for agenticcli.dev, which removes both the consent cookie and any local storage PostHog had stored.

The Google Analytics cookies are first-party too, so blocking third-party cookies does not remove them either, and the cookie banner does not control them. To stop Google Analytics, use Google's opt-out browser add-on or a tracker blocker.

Changes to this policy

We may update this policy if we add or change the cookies we use. Updates will appear on this page with a revised “Last updated” date.

Questions? Email [email protected]. For broader privacy matters, see our Privacy Policy.