01 What this page covers
Everything this site could write into your browser, not only cookies. That means cookies, local storage, session storage, IndexedDB, service worker registrations and the Cache API.
A page headed “cookies” that reports none while the site keeps state in local storage would be technically true and functionally dishonest. The scope is the broader one so the answer cannot hide in the gap.
02 Nothing is stored
No cookie is set. Nothing is written to local or session storage. No IndexedDB database is opened, no service worker is registered, and nothing is put in the Cache API.
There is therefore nothing to consent to, and no consent banner on this site. If one ever appears, it will be because something on the list below stopped being empty.
Every mechanism checked
You can confirm all six in your browser’s developer tools, under Application or Storage, on any page of this site.
03 Why there is nothing
No analytics are deployed. There are no third-party embeds, no video players, no social widgets, no maps and no comment system. There are no accounts, so there is no session to keep, and no preference for the site to remember — the theme toggle was cut rather than persisted.
Fonts are served from this origin, so no font host sees a visitor. One set of outbound requests does happen and stores nothing: the footer status strip and the statistics page read figures from explorer-testnet.kronex.network and rpc.kronex.network, our own infrastructure. A visitor’s IP reaches those hosts on any page carrying the footer. A request is not stored state, and this page does not claim it is nothing — the privacy notice names both hosts.
Site search runs entirely in the browser against an index shipped with the page. No query leaves it, and nothing about a search is kept afterwards.
04 What would change this
Accounts, a saved preference, a hosted analytics product, an embedded third-party player, or anything else that needs to remember you between page loads.
If any of those arrive, this page is updated in the same release, the privacy notice with it, and the inventory above stops reading none set.
05 Consent
Whether a consent mechanism is legally required is a question for counsel in a jurisdiction that has not been chosen yet. The design position is that nothing is stored, so there is nothing to consent to; the legal position is not asserted here.
Contact
Questions about this document go to the one published address. There is no separate legal, privacy or security address.
Related