Privacy Policy

BKC Wallet browser extension · Effective 23 September 2026

This policy explains what the BKC Wallet browser extension ("the extension") stores, what it sends, and what it never collects. It is published by BKC Network ("we", "us"), which develops and distributes the extension.

In short: we collect nothing. The extension has no backend of ours, no account system, and no analytics, telemetry, advertising or crash reporting. Your keys and your settings stay in your browser.

1. Information we do not collect

We do not operate any server that receives data from the extension. We therefore hold no personal information about you: no name, no email address, no wallet address, no transaction history, no IP log, and no device or usage analytics. Because we collect nothing, we sell nothing, share nothing, and transfer nothing to third parties for advertising, profiling or any other purpose.

2. Information stored on your device

The extension writes the following to your browser's local extension storage, on your own device. It is never transmitted to us.

Keys. Your recovery phrase and private keys, encrypted with the password you choose. The password is not stored in plain text, and unlocking the wallet is required to use a key.
Accounts and addresses derived from those keys.
Address book entries you create: label, address and optional memo.
Site permissions — which websites you have allowed to see an address.
Preferences — language, display currency, hidden assets, and any custom network or token contract you have added.
Cached chain data — balances, token lists and transaction records read from the network, kept so screens load without querying repeatedly.

3. Connections the extension makes

The extension contacts the BKC network node and three public services that answer questions a node cannot. Each connection, and what it carries, is listed below. As with any request over the internet, the operator of each service can observe your IP address.

Destination	Purpose	What is sent
BKC network node	Read balances and transaction history; broadcast transactions you approve	Your account address, and the signed transaction when you send one
Custom networks you add	The same functions on a network you configure yourself	The address belonging to that network
`open.er-api.com`	Daily US dollar exchange rates, so balances can be shown in your chosen currency	Nothing about your wallet. A request for a public rate table, cached for six hours
`www.4byte.directory`	Resolve the readable name of a smart-contract function, shown on the approval screen so you can see what you are signing	The first four bytes of the call data only. No address, no amount, no other part of the transaction
`ipfs.io`	Retrieve NFT metadata and artwork stored on IPFS	The content identifier of the asset being displayed

Reading a balance or broadcasting a transaction necessarily tells the node which address is asking; that is inherent to how a public blockchain works, and it is a matter between you and whoever operates the node you use.

4. Permissions the extension requests

Access to websites you visit. The extension places a wallet object on the pages you open, which is how a web application discovers that a wallet is installed. It does not read page content, and a site learns nothing about your wallet until you approve a connection. Approval is granted per site and can be revoked in settings.
Storage. To keep the encrypted keys, accounts and preferences described above.
Tabs and side panel. To open the approval window for the site that requested a signature, and to show the wallet in the browser's side panel.

5. Retention and deletion

Data stays on your device until you delete it. Removing an account within the extension erases its stored keys, and uninstalling the extension removes everything. Neither we nor anyone else can recover it afterwards: if you lose your recovery phrase, the funds it controls are permanently unreachable.

6. Security

Keys are encrypted at rest and the extension requires your password to unlock. The protection this gives depends on the password you choose and on the security of the device you run it on. Anyone holding your recovery phrase controls the funds, regardless of any password.

7. Children

The extension is not directed at children under 13, and we do not knowingly collect information from them. As stated above, we do not collect information from anyone.

8. Changes to this policy

If this policy changes, the revised version is published at this address with a new effective date. Material changes will be reflected in the extension's release notes.

9. Contact

Questions about this policy can be raised at github.com/bkc-network.