Last updated: 8 August 2026

sade.dev is a static site. There is no server-side application, no database, no account system and no form infrastructure. Most of this policy is therefore about what is not collected.

What is not collected

  • No analytics. No Google Analytics, Plausible, Fathom or any other measurement tool. Page views, sessions and visitor counts are not recorded.
  • No tracking cookies. The site sets no cookies of its own. See the Cookie Policy for detail.
  • No ad network, no behavioural profiling.
  • No accounts, no sign-ups, no newsletter. There is no form anywhere that asks for your name or email address.
  • No requests to Google Fonts. Typefaces are served from this site, so your IP address is never passed to a third-party font host.

What stays in your browser

None of the following leaves your device:

  • Theme preference. Your light/dark choice is stored in localStorage under the key sade-theme. It is not a cookie and is never sent to a server; clearing your browser’s site data removes it.
  • Search. On-site search runs on Pagefind. The index is downloaded to your browser as static files and the query is executed there. What you search for is never sent to any server.
  • Tools. The JWT Decoder, .env Parser, JSON Formatter and every other tool run entirely in your browser. Whatever you paste — tokens, configuration, passwords included — never goes over the network.

Hosting

The site is hosted on Cloudflare Pages. When you open a page your request passes through Cloudflare’s infrastructure, and Cloudflare may process technical data such as IP address, browser information and request time in its own logs, for service delivery and infrastructure security. Those logs are governed by Cloudflare’s own policies; they are not produced, stored or viewed by us.

Comments

Comments on article pages are stored in GitHub Discussions via giscus. That component:

  • loads only on article pages, and lazily, after the page itself has loaded;
  • never loads on the home page, index pages, tool pages or static pages, this one included;
  • requires you to sign in with your own GitHub account in order to post.

When you comment, your comment and your GitHub username are published in a public discussion thread on GitHub. That data never touches our infrastructure at any point. Once the comment component loads, GitHub’s privacy policy and terms of service apply; you can edit or delete your comment through GitHub.

Articles link to third-party sites. We are not responsible for the content or the privacy practices of those sites.

Your rights

Because no record constituting personal data is created here, there is nothing held by us for you to access, correct or delete. If you have a question about this policy, you can still write: [email protected]

For data processed by Cloudflare and GitHub, those providers’ own privacy policies and request channels apply.

Changes

This policy is updated whenever the site’s technical behaviour changes. The date of the most recent update appears at the top of this page.