Privacy Policy

This policy describes how the BeeWallet Chrome extension (“BeeWallet,” “we,” “us”) handles information when you use the extension. BeeWallet is built for self-custody: your keys and vault stay on your device unless you explicitly move funds or data through public networks you choose to use.

Effective date: replace this sentence after upload with your publication date. Contact: replace this line with your support email or issue tracker URL.

1. What we do not collect

BeeWallet does not operate a centralized account service for the extension. We do not receive your seed phrase, private keys, or vault password on our servers. There is no BeeWallet login that sends your wallet secret to us.

2. Data stored on your device

The extension stores data locally in Chrome’s extension storage (for example chrome.storage.local and session storage where applicable), including:

• Encrypted vault — cryptographic material needed to use your wallet, protected by the password you set.
• Settings — such as Bee API base URL, Relay slippage preferences, and auto-lock options.
• Optional local metadata — information the UI needs for uploads and stamp-related features, as described in the extension.

Removing the extension or clearing extension data from Chrome deletes this local storage according to Chrome’s behavior.

3. Data sent over the network

When you use wallet or Swarm-related features, the extension initiates connections you would expect from a wallet client:

• Blockchain RPC — HTTPS JSON-RPC requests to public endpoints to read balances, estimate gas, broadcast and monitor transactions, and read on-chain state needed for supported chains.
• Relay — HTTPS to Relay services (for example api.relay.link) when you request cross-chain quotes, swaps, or bridge status.
• Swarm / Bee — HTTPS to your configured Bee API and related gateway hosts (such as bzz.link) for uploads, downloads, and stamp flows.

Those third-party operators may process connection metadata (such as IP address and TLS logs) under their own policies. BeeWallet does not add separate analytics telemetry in the extension package described by this policy.

4. Optional host access

If you configure a custom Bee API URL, the browser may prompt you to grant access to that specific origin. That permission exists so your node can be reached; it is not used to read unrelated websites for advertising or tracking.

5. Security

Extension pages use a restrictive Content Security Policy. Sensitive requests use HTTPS where the remote service supports TLS. You are responsible for device security, strong passwords, and verifying transaction details before signing.

6. Children

BeeWallet is not directed at children. Do not use the extension if you are not old enough to agree to terms in your jurisdiction.

7. Changes

We may update this policy when the extension or legal requirements change. The “Effective date” at the top should reflect the latest version. Continued use after an update means you accept the revised policy.