Cookie Policy
Last updated: 24 September 2026
We set no analytics or advertising cookies, which is unusual enough to be worth a page of its own. This one explains what we store instead, the single security cookie the network in front of us may issue, why the difference matters to you, and how to clear it.
1. Why we set none of our own
A cookie is a small file a site stores on your device and sends back to its server on every later request. That round trip is what makes cookies useful for logins and carts, and it is also what makes them useful for tracking: anything in a cookie travels back to whoever set it.
This site has no accounts, no logins, no carts and no personalisation, so there is nothing for a cookie of ours to carry. The analytics we use are cookieless. That leaves no reason to set one, and we do not.
One cookie does reach you, and it is not ours. Cloudflare, the network that serves and protects the site, runs a short script in your browser to tell a real visitor from automated traffic, and that script issues a cf_clearance cookie. It exists for security, carries no profile of you, and we cannot read it. It is the only cookie associated with this domain, and it is why this page says we set no analytics or advertising cookies rather than claiming none exist at all.
2. What we store instead
Two values live in your browser's local storage. Local storage differs from a cookie in the way that matters here: it is never attached to a request, so it does not travel to us or to anyone else. It stays in the browser that created it.
- Consent choice: a flag recording that you have dismissed the notice, so it does not reappear on every page.
- Terms acknowledgement: a flag recording that you have acknowledged the terms notice.
Both are true-or-false markers. Neither holds an identifier, and neither is ever sent to us: the script that reads them runs in your browser and keeps the answer there.
3. How to clear what is stored
Clearing site data for crypto-investing.page removes both values; the two notices then appear again on your next visit. It also clears the offline cache the site keeps so pages still open without a connection, which rebuilds itself as you browse. In most browsers this sits under privacy settings as "cookies and site data", which covers local storage despite the name.
Blocking cookies alone will not affect these values, because they are not cookies. A browser set to block all site data is different: it blocks local storage too, and then both notices reappear on every page. Private browsing keeps them only until you close the window.
4. Third-party services
Two third parties see something as you read, and it is worth naming both. Plausible Analytics is the analytics one: cookieless by design, recording page-level usage without personal identifiers, and not following visitors between websites — which is why we chose it over the alternatives that would have required this page to say something less comfortable.
The second is the content delivery network the site is served through. Your request reaches its edge server before it reaches us, and when that server already holds the page it answers you without us seeing the request at all. That is how most sites on the public internet work, and the privacy policy sets out what the edge sees.
5. Consent
There is no tracking to consent to. The notice you saw is an acknowledgement rather than a permission request, which is why dismissing it changes nothing about what is collected. That is not the same as nothing being collected at all: page-level analytics and ordinary server logs are described in the privacy policy, and neither waits on the notice.
Your rights of access, correction and deletion still apply to anything we do hold, and the privacy policy sets out how to exercise them and how long a reply takes.