What BluBox never collects
There are no accounts, so there is nothing to sign up for and nothing to know you by. There are no analytics, no trackers, no tracking pixels, and no cookies — the app sets none, and nothing on this site phones home. BluBox never asks you to connect a wallet; a version that does is fake.
What your browser talks to
Two places, and you can watch both in your browser's own network inspector:
- blubox.watch — the app itself and its published data files (daily price closes, the staker census, gateway health). The same files are served to everyone; nothing in a request says who is asking or which addresses they watch.
- The chain gateways you select — reading a balance means asking a PulseChain or Ethereum RPC about the addresses you watch. Each watched address has its own gateway, chosen by a fixed rule from the address itself: its balance, stake and position reads go to that gateway on every visit, or, when it does not answer, to the next one in a fixed order kept for that address. None of those reads carries two watched addresses in one request, so the addresses are spread across the gateways rather than all sent to one — though two can share a gateway when the rule gives them the same one. Reads of the chain's history logs, such as the Transactions page and Your HEX Stake History, are not split this way: a gateway that answers them is sent every address they name. Each gateway sees the addresses it is asked about and your network address, the way any server sees its visitors. This is a property of reading any blockchain through a gateway, not something BluBox adds. In App Settings your own gateway takes the first seat for PulseChain reads, and the public list stands behind it as the fallback when yours does not answer — and Only my gateway, beside that setting, ends PulseChain wallet reads at your node: when it does not answer, the read stops and says so. Ethereum reads keep the public Ethereum gateways, so those gateways see any watched address that holds eHEX or Ethereum stakes. Validators reads go to your own beacon node first when one is set, then to a public beacon gateway, and carry validator numbers or keys, never a wallet address.
What stays on your device
Your watched addresses, groups, settings, and the ledger cache live in your browser's own storage, on your device. They are never uploaded — there is nowhere to upload them to. On phones, the optional BluBox-Vault encrypts the personal slots with a password that is never stored anywhere; it is the key. The Export String is the only copy of your setup that ever exists, and it exists only when you make it, only where you put it.
The Suggestion Box
The Suggestion or Correction box on the Guide and the Glossary sends exactly the text you typed — nothing more — relayed to the project's mailbox. It carries no reply address unless you include one yourself.
What the host sees
The site is served through a hosting network (Cloudflare), which — like every host on the internet — keeps standard connection logs of the requests it serves. BluBox adds nothing to those logs, reads nothing from them, and receives no analytics from the host.
Don't trust this page — verify it
Every claim above is a claim about code, and the code is checkable: blubox.watch/verify downloads the live files, hashes them in your own browser, and answers MATCH or MISMATCH against the published release fingerprints. A policy you can verify beats a policy you have to believe.
This policy ships like code — in the open, hash-covered, changed only by a new release. First published 2026-08-05.