Horizen Wallet extension privacy policy

Effective 21 October 2026. Publisher: Kotav Labs. Horizen Wallet is a community project and is not an official Horizen Foundation product.

Horizen Wallet has no accounts and sends no analytics, telemetry or crash reports. It never sends your recovery phrase, keys or password anywhere, and Kotav Labs receives no browsing history from the extension. To do what you ask, it does send some data off your device: your public address and the transactions you approve go to blockchain RPC providers, and every service it contacts sees your IP address. The details are below. None of this data is sold or used for any other purpose.

What stays on your device

• Your encrypted wallet (recovery phrase and keys encrypted with your password), your contacts and your transaction records, in the extension's local storage.
• The sites you connected (origin, public address, chain id, a random session id), the sites you blocked and the wallet mode (mainnet or testnet).

Removing the extension deletes all of it. Keep your recovery phrase and encrypted backup elsewhere.

What leaves your device, and to whom

Every request below also reaches the receiving service with your IP address, as with any website or wallet.

• Blockchain RPC providers (Caldera for Horizen and Horizen Testnet; PublicNode and Base for Base; PublicNode for Ethereum mainnet reads when you recover a bridge transfer) receive the read requests the wallet makes, which include your public address, and the signed transactions you approve.
• The hosted Horizen Wallet service (horizenvew.kotavlabs.com, run by Kotav Labs) receives requests for public encrypted private-asset state and for price history. These requests do not contain your address.
• WalletConnect (Reown). If you pair an app with a WalletConnect link, WalletConnect's relay carries the encrypted messages between the wallet and the app, and its verify service checks the app's domain. The wallet turns WalletConnect's telemetry off. Reown's own privacy policy applies to its services.
• Sites you connect receive your public address and the results of the requests you approve. A site receives nothing before you approve the connection.
• Private assets (pilot). Private payments are processed by an operator-trusted Vela installation without hardware attestation; its operator can read private-payment contents. Deposits, withdrawals, timing and other metadata can be public on chain. If you do not use private assets, nothing is sent for them beyond the public state request above.

Public blockchains are public: transactions you send, and the addresses involved, are visible to anyone.

Changes and contact

Changes to this policy are published at the same address with a new effective date. Contact Kotav Labs through the contact listed on the store page.