According to Bramble’s documentation, users explicitly move public funds into the STRK20 privacy pool, where they become encrypted notes held separately from the ordinary wallet balance. Private transfers conceal the amount and counterparty from public observers.
That privacy has defined limits. Starknet’s compliance documentation says deposits expose the depositor’s address and describes a viewing-key mechanism that lets a designated auditor trace funds in response to a lawful request.
Bramble’s account-abstraction features use programmable smart contract accounts. Its guide lists OpenZeppelin and Argent account contracts, Ledger hardware signing and Argent multisig accounts, where a specified number of participants must sign a transaction. New users set a local password, back up a recovery phrase and fund their account before deploying it.
Shielding and Shadow Accounts Are Different
Starknet’s shadow accounts provide a separate, persistent identity for each user and application, hiding the link to the user’s main wallet. The shadow account’s balances, calls and protocol positions remain public, according to the network’s integration guide.
That guide specifies Wallet API 0.10.4 and wallet support for STRK20 shadow-account methods, including `shadow_account_invoke`. Bramble’s launch documentation describes balance shielding but does not specify support for those methods or session keys. For applications using shadow accounts, wallet-level shielding alone does not establish compatibility.