Cookie Policy for StackClock

Last updated: October 4, 2026 Short version: StackClock uses only the cookies needed to sign you in. No analytics, no ads, no tracking. That's why there's no cookie banner. 1. Essential cookies __Secure-sc.session_token Keeps you signed in. It only holds a random session ID. It expires after 3 days of inactivity, 30 days at most, or when you sign out. __Secure-sc.state Only when you sign in with Google. It protects the sign-in from forgery. Lasts 5 minutes. __Secure-sc.better-auth-passkey Only while you add or use a passkey. Lasts 5 minutes. Other short-lived __Secure-sc. cookies may appear during a sign-in step (like two-factor verification) and are removed right after. These are first-party, HTTPS-only and not readable by scripts. 2. No cookies if you don't sign in Browsing the site, the free tools and the vendor deprecation feed sets no cookies at all. Neither do our badges embedded on other sites. 3. What we don't use No analytics, advertising or social media cookies. No tracking pixels in our emails. No third-party scripts or fonts. Your theme follows your device setting and isn't stored. 4. Other services Stripe (checkout and billing) and Google (if you sign in with Google) set their own cookies on their own sites, under their own policies. 5. Managing cookies You can delete or block cookies in your browser. Blocking ours means you can't sign in, but the public pages and free tools still work. 6. Changes If we ever add optional cookies like analytics, we'll ask for your consent first and update this page. OhMyLabs runs StackClock. Contact us at [email protected]