Nagara Wallet
Privacy Policy
Last updated 22 September 2026
Nagara Wallet is a self-custody wallet. Your recovery phrase and private keys are encrypted with your password and never leave your device. Some information does leave it, and this policy says exactly what, to whom, and what you can switch off.
You are asked about this once, before the wallet is set up, and the optional part can be changed at any time in Settings → Data sharing.
What is sent
rpc1.nagara.network (mainnet), testnet.nagara.network (testnet)Required- What is sent
- Your wallet address, and transactions you have signed
- Why
- Reading balances, estimating fees, and broadcasting a transaction to the blockchain
- Note
- A wallet cannot reach the chain without it
indexer.nagara.networkOptional- What is sent
- Your wallet address
- Why
- Listing transactions made outside this extension
- Note
- Off by choice, and then only transactions made here are listed
explorer.nagara.network- What is sent
- The selected network name. No wallet data, no address
- Why
- Reading the NGRX price in rupiah
- Note
- No user data is involved
All three are operated by Nusameta. Nothing is sent anywhere else. There is no analytics, telemetry, crash reporting or advertising code in this extension, and no data is sold or shared with any third party.
What stays on your device
Wallet data — encrypted seed, accounts, approved sites, preferences, and the transaction records the extension writes as you send — is stored only in the browser's local extension storage (chrome.storage.local), on your device.
It is deliberately not placed in chrome.storage.sync— that area is replicated through the browser vendor's servers to your other devices, which is not where an encrypted seed belongs. Earlier versions used sync by accident, inheriting a library default. On first run this version copies that data into local and then deletes it from sync, so any previously synced copy is removed rather than merely ignored.
Your password is never stored, and your recovery phrase is never transmitted.
dApp connections
When you connect the wallet to a decentralized app (dApp), the extension injects an EIP-1193 provider (window.ethereum, also announced via EIP-6963) so the site can request account access and transaction signatures. This requires broad host permissions so the provider is available on any site you choose to connect from.
A site is told your address only after you approve that site by name. Until then the wallet reports no accounts to it. Approvals are listed under Settings → Connected sites and can be revoked there; revoking moves no funds — the site simply has to ask again. The extension does not read or transmit page content beyond the provider bridge, and does nothing on a site unless you approve a connection or a signature there.
Withdrawing consent
Turning off Transaction history in Settings stops the address being sent to the indexer immediately. The chain-node traffic is not optional; to stop it, log out — that removes all wallet data from your device — or uninstall the extension.
Contact
Questions about this policy: nagara@wir.group.