> For the complete documentation index, see [llms.txt](https://doc.lockerprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.lockerprotocol.com/reference/privacy.md).

# Privacy

What leaves your browser, and what never does.

## Never leaves any device

* Private keys and secret phrases (they exist only on the offline Vault).
* Your master password and your wallet password.
* The Vault's signature journal.

## The Vault sends nothing

It has no network. Its only output is QR codes on its screen.

## What the extension fetches, and from where

The extension needs the internet to show balances and to send transactions. What it sends is your **public address**, the transaction you asked to broadcast, and - when you open those screens - the pair and amount of a quote.

| Purpose                           | Where                                                                                                                   | When                                       |
| --------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------ |
| Balances, transactions            | Public nodes of each network (see [below](#which-nodes)), or the **custom endpoint** you set                            | Always                                     |
| Block explorers (links, activity) | Etherscan-style explorers, mempool.space, Solscan, Tronscan, Suiscan, stellar.expert, Mintscan, Aptos Explorer, XRPScan | When you open Activity or an explorer link |
| Prices                            | CoinGecko, DefiLlama                                                                                                    | Only if **Show fiat values** is on         |
| Token lists and logos             | CoinGecko token lists and bundled lists                                                                                 | On demand, cached                          |
| Swap and bridge quotes            | LI.FI, Jupiter, SunSwap, Stellar path payments                                                                          | Only when you open Swap or Bridge          |
| Buy                               | The on-ramp provider you choose                                                                                         | Only when you tap Buy and continue         |
| Hyperliquid                       | Hyperliquid API                                                                                                         | Only when you use Perps                    |
| Local AI model                    | lockerprotocol.com, checked against built-in hashes                                                                     | Only if you download it                    |

**No account.** You never sign up to use the extension.

## Which nodes

Every mainnet chain ships with at least two nodes, from two different operators wherever a second one exists; when one fails, the next takes over. Each node sees the public address it is asked about and your IP address.

* **EVM networks, Solana, Sui:** public RPC endpoints.
* **Stellar:** public Horizon and Soroban RPC servers.
* **Bitcoin:** blockstream.info and mempool.space, then the public Bitcore and BlockCypher indexers. Before a send, the Xverse ordinals indexer is asked which coins carry inscriptions.
* **Litecoin:** litecoinspace, then Bitcore and BlockCypher.
* **Dogecoin:** public Blockbook indexers, then Bitcore and BlockCypher.
* **Tron:** TronGrid, then the public full nodes of PublicNode and TronStack.
* **Cosmos chains:** cosmos.directory, PublicNode, Polkachu, Ecostake, the Osmosis LCD and the Injective sentry.
* **Aptos:** the Aptos Labs fullnodes and Sentio.
* **XRP Ledger:** xrplcluster.com, xrpl.ws, xrpl.link, Ripple's s1 and s2 servers, and dRPC.

The [privacy policy](https://lockerprotocol.com/privacy-policy) is the reference and names them the same way.

## Consent, on Firefox

Firefox treats financial data as something you must agree to send. The add-on declares it, and:

* **Firefox 140 and later:** the browser shows the declaration in its own install prompt. Installing *is* the consent; the wallet asks nothing more.
* **Older Firefox:** the wallet asks by itself, in a tab, before its first request: *Data sent by this wallet*. Decline and it sends nothing at all - no balance, no broadcast - until you change your mind.
* **Settings → Data sent to third parties → Withdraw** takes the consent back at any time, and every request stops again.

Chrome, Edge, Brave and Safari builds never show this screen. The rule is enforced at the network call itself, not screen by screen, so a request nobody thought to guard is refused too.

## Clear caches

**Settings → Clear caches** deletes prices, token lists, logos and balance snapshots stored locally. Accounts and settings stay.

## Policy

The full [privacy policy](https://lockerprotocol.com/privacy-policy) is the one linked from the store listings and from **About** in the extension.
