Who we are and what this policy covers
This policy explains how the Monero Wallet · Standalone browser extension (“Monero Wallet”, version 2.3.0) and this website handle information. Both are published by the Monero Wallet Standalone project and its contributors (“we”, “us”). Monero Wallet is an independent open-source project released under the MIT license. It is not affiliated with or endorsed by the Monero Project.
Because the wallet works locally, most of this policy is about what the extension stores on your own device and what a Monero node can observe when you connect to it. We do not collect, receive, sell or share personal data.
Effective date: 2026-09-24.
What the extension stores, and where
Everything below lives in your Chrome profile or in files you choose to save. None of it is sent to us.
| What | Where | Encrypted? | How long | Who can access it |
|---|---|---|---|---|
| Wallet vault: keys derived from your recovery phrase, addresses, account and subaddress labels, address book, transaction notes and history, balances, the selected node, your custom nodes, wallet settings (auto-lock time, password confirmation for payments) and the restore height | IndexedDB database monero-extension-encrypted-vaults, one vault per wallet | Yes: AES-256-GCM with a key derived from your password (PBKDF2-SHA256, 600,000 iterations) and a fresh random salt and IV on every save | Until you remove the extension or clear its data | Only someone who knows your password |
| Vault metadata: vault ID, wallet name, network, created and updated times, revision number | The same database | No, so your wallets can be listed before you unlock one | As long as the vault | Anyone with access to your browser profile |
| Pending-transfer record: a transaction hash and the time it was created | chrome.storage.local, key unresolvedTransfer | No | From just before a payment is broadcast until its success is confirmed or you verify the outcome | Anyone with access to your browser profile |
| Interface preferences: theme, “hide balances”, last opened page, selected account number with its vault ID, last opened wallet ID | The extension’s localStorage | No | Until you clear the extension’s data | Anyone with access to your browser profile |
| Decrypted keys while the wallet is unlocked | Memory of the extension’s hidden (offscreen) document and its WebAssembly worker | Held in memory only | Until you lock the wallet, the auto-lock timer runs out (1–60 minutes of inactivity, 5 by default, once active work finishes), you delete the wallet, or the browser restarts | The extension on your device |
Files you export: encrypted backup (.monero-vault.json), transaction history (CSV), QR code (SVG) | Wherever you save them | The backup is encrypted. The CSV and QR files are not. | Until you delete them | Anyone who can open those files |
| Clipboard | Your system clipboard | No | Until something else is copied | Other apps on your device may read it |
Interface preferences never include addresses, amounts, recovery phrases or passwords. Your password is never saved. Your recovery phrase is not stored in plain text and is displayed only when you ask for it.
About exports. The CSV history is plain text. It contains transaction IDs, amounts, fees, dates, destination addresses and your notes, so treat it like a bank statement. An encrypted backup can only be opened with the password it was created with.
About the clipboard. The extension writes to the clipboard only when you press a Copy button (addresses, payment links, transaction IDs, signatures, transaction keys). It reads the clipboard only when you press Paste on the Send page.
Network connections and Monero nodes
To see incoming payments and to send, a wallet needs blockchain data. Monero Wallet gets it from one Monero node that you explicitly select, after you acknowledge a privacy notice: either a node from the built-in list below, or a node you add yourself (for example your own monerod). It does not contact any other server.
- Cake Wallet: mainnet, HTTPS
- Seth for Privacy: mainnet, HTTPS
- HashVault: mainnet, plain HTTP
- Seth for Privacy: stagenet, plain HTTP
- Seth for Privacy: testnet, plain HTTP
The extension contacts that node only when you:
- check a node (a single
get_inforequest); - synchronize (blocks are downloaded and scanned locally, on your device);
- send a payment (decoy outputs and fee data are fetched, then the already signed transaction is relayed);
- rescan the wallet from a chosen height or date.
Unlocking the wallet does not start a sync, and nodes are never polled in the background.
Your own node. In Settings → Node you can add up to 16 nodes of your own. Their addresses are stored encrypted inside that wallet only. Adding a node contacts nothing. When you select it, Chrome asks you to allow access to that single address, and the wallet then checks it with a get_info request. Your own node is the most private choice: no third party sees your IP address or your transactions.
| Information | Visible to the node? |
|---|---|
| Your IP address and when you connect | Yes |
| Which range of blocks you download (the restore height hints at when the wallet was created) | Yes |
| That a transaction was broadcast from your IP address | Yes |
| Your recovery phrase, private spend or view keys, or password | No |
| Your wallet addresses and balances | No |
| Amounts and recipients of your transactions | No. Monero hides amounts (RingCT) and recipients (one-time stealth addresses). |
| Your labels, contacts and notes | No |
With a plain-HTTP node, network intermediaries such as your internet provider or Wi-Fi operator can see the same things the node sees.
A malicious node cannot steal funds. It can, however, serve bad decoy data that weakens the privacy of a transaction. To limit what nodes learn, use a VPN or Tor for your browser. Running your own node gives the strongest privacy.
No accounts, analytics or remote code
Monero Wallet has no accounts and no sign-up. It contains no analytics, telemetry, crash reporting, advertising or tracking of any kind. Its content security policy allows only the extension’s own bundled scripts plus WebAssembly, so it cannot load code from the internet.
The project operates no servers that receive wallet data, and we never receive any user data. The extension does not check for updates by itself; if you installed it from the Chrome Web Store, Chrome handles updates. External websites, such as the Monero documentation or a node’s source page, open only when you click a link.
Chrome Web Store Limited Use. The use of information by Monero Wallet complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. All wallet data is processed locally, solely to provide the wallet’s single purpose. No data is sold or transferred to anyone. None is used for advertising, or to determine creditworthiness or for lending.
Browser permissions, in plain language
- storage: save your encrypted wallet and a few settings inside your browser.
- unlimitedStorage: the encrypted wallet cache grows with your history, and this keeps Chrome’s default storage quota from blocking a save.
- offscreen: run the wallet engine in a hidden extension page, so synchronization and an already confirmed payment continue after you close the popup. This page cannot see the websites you visit.
- Access to the built-in node addresses: connect to the public nodes listed above.
- Optional access to a node you add: when you select your own node, Chrome asks you to allow that one address. Nothing is granted in advance, and you can revoke it in Chrome’s extension settings. The extension never uses this to reach any other website.
The extension does not ask for access to your tabs, your browsing history or the websites you visit, and it does not inject code into web pages.
Your control and deleting your data
Your data stays under your control. It never leaves your device, so we cannot view, correct, export or delete it for you: there is nothing on our side to access. For the same reason there is no password reset. If you lose both your password and your recovery phrase, nobody can restore access.
To delete your data:
- Lock the wallet. This removes decrypted keys from memory immediately.
- Remove the extension in
chrome://extensions, or clear its data in Chrome’s settings. This deletes the encrypted vaults, your preferences and the pending-transfer record. - Delete exported files (backups, CSV history, QR codes) wherever you saved them, and clear your clipboard if needed.
Before you delete anything, make sure you have your 25-word recovery phrase, or an encrypted backup together with its password. Removing the extension or clearing its data erases saved wallets. Your funds stay on the Monero blockchain, and only that phrase or backup can restore access to them.
This website
This website is static. It sets no cookies, runs no analytics and makes no third-party requests; even the fonts are served from this site. If you use the theme switch, your choice is saved in your browser’s localStorage. Nothing else is stored.
Like any web server, our hosting provider may keep standard access logs (IP address, time, requested page and browser user agent) for operation and security. We do not use them to track visitors.
Children
Monero Wallet and this website are not directed to children under 13, or under the higher minimum age that applies where you live. We do not knowingly collect information from anyone, including children.
Changes to this policy
If this policy changes, we will update the effective date on this page and describe the change in the version history below. Changes that affect how data is handled will be explained in plain language.
- 2026-09-24: updated for version 2.3.0: your own nodes (stored encrypted in the wallet, with per-address Chrome permission), configurable auto-lock and optional password confirmation for payments.
- 2026-09-23: first published for version 2.2.
Contact
Questions about this policy or about privacy in Monero Wallet: support@xmrtab.com. Never send your recovery phrase, private keys or password to anyone, including us.
See also the Terms of Use and the Security page.