SHIELD WALLET — DATA AND PERMISSIONS

Recovery phrases, private keys and passwords stay in the wallet's local context.
The browser stores the account vault, balance display cache and pending signed
transaction records encrypted. Public listing, price and event-history caches
are stored locally without encryption. Closing or locking the wallet removes
live key references; JavaScript cannot guarantee immediate zeroization of every
copy inside cryptographic libraries. The wallet locks after inactivity.

The extension has no content scripts, website wallet injection, externally
connectable messaging, remote JavaScript, analytics, advertising, native code,
OS installer or executable download. Websites cannot request arbitrary signatures
from this release. Its service worker only opens/focuses its own wallet window.

Network requests go to the HTTPS RPC/indexer hosts listed in manifest.json and
api.dexscreener.com for public prices. These services see requests and IP
addresses. The RPC receives the public BSC gas address when a user loads its
balance and receives signed transactions for broadcast. Onchain transactions,
network fees and public transfers are visible. Price requests use public token
candidates; private held-token addresses are not automatically sent for pricing.
Explicit token searches query the address the user chooses.

Proof WASM, proving key, JavaScript, token icons and fonts are bundled locally.
Circuit hashes and deployed verifier identity are checked before use. Roots and
spent claims from feeds are independently checked. These checks do not protect
against a compromised operating system or browser.

No recovery service holds your keys. Losing both your recovery phrase and usable
encrypted backup/password can make funds unrecoverable. Removing the extension
or deleting its browser profile can erase local account data.
