Last updated: 8 August 2026
sade.dev sets no cookies of its own. That is why you never see a consent banner: there is no cookie here that requires consent.
Three cases can still leave data in your browser. They are listed below.
1. Theme preference — not a cookie
Your light/dark choice is stored in localStorage under the key sade-theme.
localStorage is not a cookie: it is not sent to a server with every request, and it
is only read by the browser while the page is open. Its single purpose is to keep the
theme you picked when you come back. Clearing your browser’s site data removes it.
2. Cloudflare — technical cookies
The site is hosted on Cloudflare Pages. Cloudflare may set technical cookies such
as __cf_bm for infrastructure functions like bot protection. These are not defined or
read by us and are not used for marketing; they serve the secure delivery of the site
and are governed by Cloudflare’s own policies.
3. Comments — GitHub / giscus
Comments are stored in GitHub Discussions via giscus. The comment
component activates only on article pages, after the page itself has loaded. Once it
does, the giscus.app and github.com domains may set their own cookies; if you sign
in with your GitHub account, session cookies are added too.
On the home page, the Notes / Systems / Journal index pages, tool pages and every static page including this one, the comment component never loads — so no cookie originates from it either.
Blocking cookies
You can block or delete cookies in your browser settings. The reading side of the site works completely without them; only posting a comment is affected, because that requires a GitHub session.
If the theme preference in localStorage is cleared, the site falls back to your
operating system’s light/dark setting.