Privacy statement

What we collect

Nothing. WAR CHEST has no server. There is no account, no sign-up, no email, no telemetry, no crash reporting and no analytics. We cannot see your addresses, your balances, your transactions or your IP address, because nothing in the wallet ever sends them to us.

What the wallet sends, and to whom

• To the chain's RPC node: the requests any wallet must make — your addresses (to read balances and nonces) and your signed transactions (to broadcast them). The node operator can see your IP address alongside those requests. By default that is a public node (publicnode.com and the fallbacks listed in the wallet). You can replace it with your own node at any time: dashboard → Field Comms → Use my own node.
• To dapps you choose to open: whatever you approve in the connect and signing prompts, and nothing before you approve.
• To hardware-wallet vendors: only if you use one, and only the vendor's own connector traffic (for example Trezor Connect).

What the wallet blocks

The wallet is built on the open-source Rabby engine, which ships with a portfolio backend (DeBank), Google Analytics, Matomo and Sentry. WAR CHEST removes all of them and additionally blocks their hosts in two layers of the code, so a stray call cannot reach them. Every build is started in a real browser before release and its outbound connections are logged; the log for a build must show only the wallet itself, the chain RPC and the dapp page used for the test.

What stays on your device

Your keys, encrypted with your password, in the browser's extension storage. Your settings, address book and local transaction history, in the same place. Uninstalling the extension deletes all of it. There is no backup unless you keep your seed phrase.

This website

wartime.website is static hosting. It sets no tracking cookies. The wallet never contacts this website.

Changes

If any of the above ever changes, this page and the wallet's release notes will say so before the change ships.