What gets stored in your browser, and what does not.
Last updated 2 September 2026
No cookies at all. Reading StackKit sets nothing in your browser. There is no analytics cookie, because there is no third-party analytics — we removed Google Analytics rather than put a consent banner in front of it. Signing in stores one token, which is not a cookie and is described below.
Signing in stores sb-<project>-auth-token in local storage,
not in a cookie. The difference matters if you are trying to get rid of it: clearing cookies
will not touch it, and blocking cookies will not stop it being written. It is removed when you
sign out, or by clearing site data for stackkit.site in your browser settings.
One thing on the page is fetched from somewhere other than our own servers: video in the feed, which is hosted by Cloudinary. It sets no cookie, but Cloudinary receives your IP address when a video loads, because that is what making a request involves. Fonts used to work this way too — they came from Google — and are now served from our own domain, so Google no longer sees anything.
No advertising cookies, no cross-site trackers, no advertising pixels, and no social embeds that watch you. Video in the feed is played from a file rather than an embedded player, so no player sets anything on our behalf.
There is no analytics to refuse. The only thing stored in your browser is the sign-in token above, and you get it only by choosing to sign in.
The sign-in token is a different matter: it is the session. Clearing it means you can read the site but are no longer signed in, so saving tools and replying will not work until you sign in again.
Separately from cookies, we log page requests at our CDN — including IP address — for up to 30 days. That is described in the Privacy policy. It does not involve storing anything in your browser and cannot be refused with cookie settings.
Questions: [email protected]