Wallet privacy policy.
Last updated 18 October 2026. This policy describes the Shield Wallet web app version 0.1.0 at wallet.tryshield.me and desktop browser extension versions 0.1.1 and 0.1.2. Both are wallets for BNB Smart Chain. It covers data processed on your device and requests sent to network services.
Your keys and account data
Your recovery phrase, private keys and password remain in the wallet's local context. They are not sent to Shield, an RPC provider, a price service or a recovery service. Transactions are signed locally.
The browser stores your account vault, last-known balance display and pending signed transaction records encrypted. Public token listings, public prices and public blockchain event-history caches are stored locally without encryption. These records let the wallet restore your account display and resume its checks.
The web app and extension version 0.1.2 store a non-secret, versioned privacy-consent flag after you agree to their data disclosures. The web app uses its own flag; an earlier extension agreement does not authorize the app's disclosure. These flags contain no wallet identifier or agreement timestamp.
Closing or locking the wallet removes live key references, and the wallet locks after inactivity. JavaScript cannot guarantee immediate erasure of every copy held by cryptographic libraries or the browser.
Network requests and service providers
Both wallets need network access to read BNB Smart Chain, check the Shield deployment and note state, load public prices and broadcast transactions you approve. The web app also downloads its interface and app assets from its HTTPS host. These services can see your IP address and the requests sent to them.
| Service | Information sent and purpose |
|---|---|
App hostingwallet.tryshield.me | The web app requests its interface, scripts, fonts, icons, public chain configuration, snapshots and proving files. The host receives ordinary asset-request information, including your IP address and request metadata. Wallet keys, passwords, recovery phrases, private notes and encrypted vault records are not uploaded to the host. |
BSC RPCbsc.rpc.blxrbdn.com | Public chain and contract queries; your public BSC address for balance and nonce checks; token addresses from public lists or explicitly chosen lookups; and approved signed transactions for broadcast. The provider can associate requests with your IP address. |
Public pricesapi.dexscreener.com | Token addresses from public candidate lists and tokens you explicitly add, to obtain public prices. The wallet does not automatically send token addresses found only in your private notes for pricing. |
| Configured indexer, if present | Requests for public commitment and nullifier event history. Web app 0.1.0 and extension versions 0.1.1 and 0.1.2 do not configure a separate indexer. The wallet independently checks feed roots and spent claims if an indexer is configured in a future release. |
The wallets use these responses for the features described here. Hosting, RPC and price services operate their own infrastructure and may retain network logs under their own policies; this wallet cannot delete their logs or control their retention. The extension's permitted network hosts are listed in its manifest.json. The web app's network destinations are restricted by its Content Security Policy.
Limited use of user data
Shield Wallet uses user data only for the wallet features described in this policy. User data is not sold or used for advertising, creditworthiness or lending decisions. These limits apply to both the web app and extension. The extension's data-use commitments follow the Chrome Web Store User Data Policy, including its Limited Use requirements; this does not mean the extension or web app has received store review or approval.
What is public on the blockchain
Your public BSC account, public transfers, network fees and submitted transactions are visible on BNB Smart Chain. Deposit and withdrawal amounts, public addresses and transaction timing can reveal information. These releases pay their own gas from your public BSC account and do not use a relayer, so gas payments can link activity.
Private Shield account data is processed locally to generate proofs. Zero-knowledge proofs do not hide all network or blockchain information. Blockchain records cannot be removed by deleting your app or extension or asking Shield to delete them.
Browser permissions and tracking
Neither wallet has page-reading content scripts, browsing-history collection, an injected wallet provider, externally connectable messaging, advertising or analytics. Other websites cannot ask these wallets for arbitrary signatures. The extension's background service worker only opens or focuses its own wallet window. The web app is an app window or browser tab, not a Chrome toolbar extension.
The extension includes its proof WASM, proving key, JavaScript, token icons and fonts in its installation package. The web app downloads its own complete release from wallet.tryshield.me and verifies its static files against that release's hashes before opening the wallet. Neither wallet fetches executable JavaScript dependencies from third-party CDNs. Circuit hashes and the deployed verifier identity are also checked before use.
Web app caching, updates and hosting trust
The web app's service worker caches only the release's approved static files. It does not cache RPC responses, price-service responses, transactions, passwords, recovery phrases or wallet account storage. The encrypted vault and wallet records are stored separately from this static app cache.
Cached app files allow the interface to open offline while they remain available. Blockchain checks, current balances, prices and transaction broadcasting need a network connection. Browsers can remove site storage; a cached app is not a recovery backup.
App updates are delivered by wallet.tryshield.me and wait until all windows using the previous wallet have closed. An update does not force an active wallet to reload. Installation does not turn the hosted app into an independently signed browser extension or give it Chrome Web Store review.
Installing and verifying app files cannot protect against a compromised hosting account that replaces the app and its verification code, or against a compromised browser or operating system. You continue to trust the HTTPS host for the app's code and future updates.
Backups, storage and deletion
The web app stores its account on the dedicated wallet.tryshield.me origin. The main Shield website, the web app and each extension identity have separate local storage; they cannot automatically read one another's vaults. Local records remain in the browser profile until that data is removed. You can export an encrypted backup to a location you choose. If you copy a backup into cloud storage or send it elsewhere, that transfer is your choice and the destination's policies apply.
Removing extension data, clearing wallet.tryshield.me site data, choosing to remove app data when uninstalling, or deleting the browser profile can erase your local account records. Export a usable encrypted backup and save your recovery phrase offline before doing so. There is no recovery service holding your keys. Losing the phrase and any usable backup and password can make funds unrecoverable.
Moving an account requires manually importing its Shield recovery phrase or encrypted backup. Finish any pending transaction in the original wallet first: these recovery methods do not transfer its signed pending-transaction record. Confirm the restored account before removing the original wallet.
Deleting local data does not erase exported backup files, a device's backups, provider logs or public blockchain records.
Questions and changes
For questions about this policy, use Shield's existing support channel, @tryshieldbnb on X, or visit the Shield documentation. Never send a recovery phrase, private key, password or unencrypted account data to support.
This page will be updated when the wallets' data handling changes. Check the policy and permissions for the version you use. The main download website, external links and any browser store you visit also receive ordinary web requests and operate their own server or account systems.
Web app 0.1.0: corresponding source download · third-party licenses and notices.