Cookies & local storage
Last updated Aug 10, 2026
One cookie, for your light/dark preference. No tracking cookies, no advertising cookies, no analytics cookies, no third-party cookies, no pixels, no fingerprinting, and no consent banner — because there is nothing here to consent to.
You do not have to take that on faith. Open your browser's storage inspector on any page of this site and compare it against the table below.
Cookies, in full
| Name | Purpose | Type | Lifetime | Attributes |
|---|---|---|---|---|
| botid-theme | Stores light or dark. Read on the server during render so the first paint already matches your preference instead of flashing the wrong theme and correcting itself. | Strictly necessary | 1 year | path=/; SameSite=Lax |
That is the entire list. The value is the literal string light or dark — no identifier, no session token, no hash, nothing that could distinguish you from anyone else who prefers the same theme. It is set by your own click on the theme toggle and by nothing else.
It is classified as strictly necessary because it carries no identifier and is used for no purpose other than delivering the display setting you chose, which is why no consent is required for it under the GDPR or the ePrivacy Directive. If it ever came to carry anything else, it would stop being strictly necessary and this page would say so before that shipped.
Local storage and session storage
Empty. This interface does not use either. An earlier version of this page listed four localStorage keys — a theme preference, a feed pause state, a watchlist and an RPC override. None of them exist in the code, and the page was describing an intention rather than a build. It has been corrected rather than quietly amended, because a privacy disclosure that overstates what it collects is still an inaccurate privacy disclosure.
If watchlists or an RPC override are added later they will live in localStorage under a botid. prefix, will stay on your device, and will be listed here before the feature ships.
What we deliberately do not load
| Analytics | None. No Google Analytics, no Plausible, no Fathom, no Vercel Analytics, no self-hosted alternative. |
| Tag managers | None. Nothing on this site can inject a script we did not write. |
| Advertising and conversion pixels | None, from anyone. |
| Social embeds | None. No Twitter/X widgets, no Discord embeds, no YouTube players — all of which set third-party cookies on load. |
| Third-party fonts | None. Fonts are self-hosted and served from the same origin, so no font provider learns that you visited. |
| Third-party CDNs for code | None. Every script and stylesheet comes from our own build. |
| Session recording / heatmaps | None. Nobody is watching your cursor. |
| Cross-site tracking | None. There is nothing for Do Not Track or Global Privacy Control to switch off. |
This is a security property as much as a privacy one: the supply chain you inherit by loading this page is our build and nothing else. Frontends in this industry are usually compromised through a third-party script, and the cheapest defence is not to have any.
Things that see you anyway, and are not cookies
Blocking cookies does not make a blockchain interface private. Two disclosures happen regardless of your cookie settings, and they are more revealing than the cookie above:
- Your RPC provider sees your IP address and every call your browser makes on your behalf — which agents you looked at, which executions you opened, and when. We do not operate those endpoints and cannot limit what they log. Use your own endpoint if this matters to you. Where a page is rendered on our server instead, our host makes those calls and the provider sees us rather than you — the watcher changes, not the fact of being watched.
- Your hosting path — our provider and every network between you and it — sees the ordinary web request that fetched this page: IP, user agent, path, timestamp.
Your wallet, if you connect one, is governed by its own policy and sees the connection request and everything you sign. The privacy policy covers all of this in more detail.
How to remove the cookie
Clear site data for this domain in your browser settings, or block cookies for it outright. The only consequence is that the theme resets to the default and the first paint may briefly show the wrong one. Nothing else on the site depends on it, and no feature will stop working.
If that ever changes
A consent banner, should one become necessary, will be a bottom-anchored bar with equal-weight Accept and Decline buttons, no scrim, no scroll lock, no pre-ticked boxes, and it will never cover content on mobile. Declining will be exactly one click and will be respected — non-essential cookies will not be set before you choose. We would rather add a banner honestly than quietly reclassify a tracking cookie as necessary, which is the standard trick.
Material changes move the “Last updated” date at the top of this page. Questions: chidileozoemena@gmail.com.