Cookie policy
Last updated
Comp Beast sets cookies for one purpose: keeping you signed in. It sets none for advertising, none for tracking you across sites, and none for analytics. This page lists exactly what is stored in your browser and why.
Strictly necessary: staying signed in
Sign-in is handled by Clerk. Once you sign in, Clerk sets session cookies (their names begin with __session and __client_uat, plus clerk_active_context) so that each page you open knows it is you. Without them you would have to sign in on every page. They are marked secure, are only sent to this site, and expire when your session does — sign out and they are removed. Clerk may set a small number of further cookies for its own security checks; all of them serve sign-in and nothing else.
Cookies that are strictly necessary for a service you asked for do not need your consent under the laws that govern cookies, and there is no way to use Comp Beast without signing in, so there is no switch to turn these off. You can clear them at any time by signing out or by clearing your browser's cookies for this site.
Analytics without cookies
We count page views and measure page speed with Vercel Web Analytics and Vercel Speed Insights. Neither sets a cookie, stores anything in your browser, or assigns you an identifier that persists beyond the day; they cannot recognise you on a return visit or on another site. That is why they appear on this page as a reassurance rather than as something to opt out of. If error reporting is switched on, Sentry likewise sets no cookie.
Controlling cookies
Every browser lets you see, block and delete cookies per site; look for "cookies" or "site data" in its settings. Blocking the session cookies will sign you out and stop you signing back in. For anything else, see the privacy policy.
Who runs this site
- Operator
- Comp Beast
- Contact
- Open an issue at the project's public repository.