Security and privacy
Understand the trust boundaries before connecting a wallet.
Browse all 38 guides
Keys and recovery phrases
Never type a Ledger recovery phrase, private key, or wallet seed into XRPFrontend. There is no legitimate XRPFrontend support workflow that needs it. Wallet recovery belongs in the wallet’s own trusted recovery process.
Ledger, Xaman, and CROSSMARK sign externally. Temporary Testnet wallets are a deliberate exception: their generated signing keys live in tab memory for practice and are not saved by XRPFrontend.
Verify the action, not just the website
Confirm the website address before connecting. Verify a receiving address on your Ledger when possible. Read every approval, including the operation type, amount, recipient, and tag. Reject anything that differs from your intent.
A non-custodial interface reduces key exposure but does not make a website impossible to compromise. A malicious interface could still ask for a harmful signature. Device confirmation and careful review remain important.
Public data and session data
Addresses and transactions on the ledger are public. Public XRPL servers can observe the network connection and account queries sent to them. XRPFrontend does not promise anonymous activity.
The application does not store customer Mainnet wallet seeds. XRPFrontend’s separate automated payout Worker holds an operator signing key for company-funded affiliate payments; this key does not control customer wallets. Its database stores verified-wallet sessions, usernames, public profiles, tip activation receipts, invoices and watchlists. Private accounting annotations are saved to the verified wallet’s database records. Language and display-currency preferences are stored locally in this browser. They do not store wallet keys or transaction amounts. The documentation sidebar can store a local layout preference. Xaman’s official SDK may remember an authorization session in browser storage. Disconnect logs out of Xaman; clearing site data also clears remembered access. Public account information and signing requests pass through the Xaman platform when you use that integration. Hosting and access services have their own operational handling outside the wallet application.
Release status
XRPFrontend has not received an independent security audit. Automated tests and internal reviews do not establish that every wallet, device or transaction scenario is safe.
Testnet lets you practice without using real funds. Mainnet uses real assets. Review the network and exact transaction in your wallet before signing.
Market storage and third parties
Provider payloads are kept only in bounded session memory. The site removes obsolete market snapshots and recorded asset-value keys when market features load. Local NFT bookmarks retain identifiers only. Wallet session preferences and your private business records are separate; removing market snapshots does not delete them. A cooldown timestamp may be retained in tab storage, without market data.
Read the Privacy Policy for browser requests to market, wallet, node and media providers, account verification, public profile data and service-held records. The Developer console is paused; no public market-data integration API is offered.