Read How FxAeon handles your data for the privacy disclosure. This guide explains the practical difference between local records, wallet information, and public chain data.
Records on this device
FxAeon uses browser storage for transaction settings, wallet preferences, display caches, draft inputs, and recovery records. They help restore the workspace; they do not authorize a transaction. Clearing site data can remove those local records.
Wallets and sign-in
Connecting a wallet shares its public address and selected network with the app. Privy handles built-in wallet and sign-in services; the chosen method can share email or Telegram account information with Privy. FxAeon does not ask you to enter a seed phrase or private key.
Disconnecting stops use of the selected wallet. It does not erase blockchain records or revoke token approvals already granted onchain.
Public records and external services
Reading balances, positions, prices, and transaction status involves blockchain and data providers. Requests can include public wallet addresses and transaction hashes. Hosting and service providers also receive ordinary connection information when your browser contacts them.
Transactions on public blockchains are publicly visible. A local History record is separate from that public record; deleting one does not delete the other. Consult the privacy disclosure and the policies of the wallet, authentication, and network services you use.
Protect the action you sign
Check the full address, network, asset, contract, amount, and recipient when relevant. Read Wallets & signing for requests and allowances. For economic and protocol risks, use the separate Risks & rebalancing guide.