Cookie Policy

Short version: if you are reading this site without logging in and without subscribing, we set no cookies at all. This page explains what that means and the narrow cases where it changes.

What we set for an ordinary reader: nothing

You can verify this rather than trust us. Open your browser’s developer tools, go to the storage or application tab, load any page on this site, and look at the cookie list for this domain. It is empty. We have no analytics product, no advertising network, no session tracking and no consent-management platform — and a consent banner would itself be the thing most likely to set a cookie.

Why there is no cookie banner

Because there is nothing to consent to. Cookie banners exist to obtain permission for non-essential cookies, overwhelmingly advertising and analytics ones. We run neither, so a banner would be theatre: an interruption that implies tracking is happening in order to look compliant.

Your theme preference is not a cookie

The light/dark toggle stores your choice in localStorage, under the key bl-theme. This is a meaningful distinction rather than a technicality: localStorage stays in your browser and is never transmitted to our server, whereas a cookie is attached to every single request you make. We cannot see your theme preference. Clearing site data in your browser removes it.

The narrow cases where a cookie does appear

• If you submit the newsletter form. The form carries a security token to prevent forged submissions from other sites. Depending on your browser this may involve a short-lived cookie tied to that form submission.
• If you log in. Only the site’s own editors do this. WordPress sets authentication cookies so the session persists. If you are not an editor here, this never applies to you.

Both are strictly functional: they exist to make a specific action work or to keep it secure, and neither is used to build a profile of you or to follow you to other sites.

Third-party cookies: none, by architecture

The live Bitcoin data on this site — price, fees, mempool, hashrate, halving countdown — is fetched by our server and rendered into the page before it reaches you. Your browser never contacts a data provider, so no provider can set a cookie on you or observe that you visited. This is enforced at the HTTP level by a Content-Security-Policy header with connect-src 'self', which instructs your browser to refuse outbound connections to other origins.

We embed no social widgets, no comment platform, no video players, no font CDN and no advertising tags. Fonts are served from this domain.

What our server records regardless

Like essentially every web server, ours writes access logs: the requesting IP address, timestamp, the URL requested, the referring page if the browser sends one, and the user-agent string. These are not cookies and are not used to identify you personally — they exist for security, abuse mitigation and diagnosing faults, and are rotated on a routine schedule.

If this changes

Adding analytics is under consideration and would change this page. If we do it, we will say so here with the date, we will name the tool, and we will prefer a configuration that does not set cookies or collect personal data at all. We would rather have worse measurement than quietly become the thing this page currently gets to say we are not.

Questions go to the contact page. See also our privacy policy.