Security
Self-custody gives you control of your wallet and responsibility for its backup. Protect your recovery phrase and review each action you authorize.
Wallet-key protection
Recovery phrases and imported keys use Apple’s device-only Keychain. Access requires device authentication, with Face ID or Touch ID and passcode fallback. Removing the device passcode makes these protected secrets unavailable. Keep your recovery backup before changing or resetting device security.
Wallet signing uses the key after authentication. Never send a recovery phrase or private key to the assistant, a website or support.
Approval and signing
Read the transaction review before approving, whether you started the action in Wallet or through chat. Check:
- The account, recipient and network.
- The asset, amount and estimated fees.
- The spender and limit for a token approval.
- Any authority change, simulation failure or missing information.
Open the details when you need to inspect the contract or complete request. If you cannot understand the effect, cancel. Device authentication protects access to the key; you still decide whether to authorize the action.
Reviews are bound to an account, network and exact request. Changing that context or letting fee evidence expire requires fresh preparation. When a fee estimate refreshes, approval is disabled until it is ready and you must approve again. An execution-fee cap may not include every chain-specific charge; read additional-fee warnings.
Interrupted or uncertain transactions
NANI records submission attempts separately from chat history. A timeout, missing receipt, app restart or deleted conversation does not establish that a transaction failed and does not authorize an automatic resend. Check the existing attempt in Activity and reconcile its status before repeating it. A successful source transaction also does not prove that a bridge arrived or a token permission changed.
Spending permissions and account authority
Open Settings → Token spending permissions to check a token’s spender allowance and review revocation. Settings → Wallet access separates these asset permissions from account authority. A discovery scan can be incomplete; it is not a complete inventory of every approval or signed order. Revocations need network fees, explicit review and onchain confirmation.
Connected sites and services
Wallet lookups and transactions contact network services. Remote AI receives the conversation content and context sent to it. Sites you open have their own requests and policies. Use the provider settings to choose where assistant requests go, and read the mobile privacy policy for mobile data handling.
Treat requests to reveal a recovery phrase, install unfamiliar software or grant unexpected spending permission as a reason to stop and investigate.
Explore opens sites in the in-app browser. A site can see the selected public account and network after you approve its connection; signing and transaction requests still need separate native review. Inspect the requesting site and exact message or call. External WalletConnect transport is not implemented, and website requests have narrower network/RPC support than native Wallet controls.
Tracker blocking is on by default. Website & account shows its status and can pause it for the current site and browsing session. This limited list does not block every tracker or hide your IP address. Navigation, account/network changes and backgrounding can invalidate pending site approvals; review a new request rather than assuming an earlier approval still applies.
If your device or phrase is compromised
Use a trusted device and your backup to regain access. If someone may have obtained the phrase or key, consider those accounts compromised. Move remaining assets to a new wallet you control, and review token approvals and account permissions. Support can help explain the steps but cannot reverse a mined transaction or recover lost secrets.
Report a security issue
Email support@nani.ooo ↗ with a description of the issue and the affected app version. Keep sensitive details out of public bug reports. Never include wallet secrets or authentication tokens.