Self-custodial
Wallet keys are kept on the user device. Ondex does not need seed phrases or private keys to render the website, publish content, or prepare account identity surfaces.
Ondex Security
Security first
Ondex is built around a simple custody boundary: wallet control belongs on the user device, not on a marketing site, admin panel, or backend service.
End-to-end encryption
Transaction approval is designed around device-side signing, so sensitive wallet authorization is separated from public website content and backend draft workflows.
Biometric authentication
Privacy and communication surfaces are designed to minimize unnecessary exposure while still giving users clear controls and public policy references.
What Ondex can never access
Ondex does not need your recovery phrase, private key, PIN, backup password, or hardware-wallet secret to render public pages, prepare dApp requests, provide support, or operate backend services.
What Ondex does process
Ondex may process app telemetry, push registration data, support tickets, provider/ramp status, compliance-relevant provider data, public profile data, and public blockchain references where those surfaces are used.
How transaction signing works
XRPL transaction approval is reviewed in the app and signed on the user's device. Backend services can deliver payloads or notifications, but they do not receive seeds or private keys for signing.
WalletConnect safety model
WalletConnect and one-shot payload requests are delivery mechanisms. Ondex validates account, chain, transaction type, fees, memos, expiry, and high-risk operations before signing where supported.
Backup safety model
Users are responsible for maintaining access to their self-custodial wallet backup. Ondex support cannot reconstruct a lost recovery phrase or private key.
Known limitations
Public blockchain transactions are irreversible, third-party provider flows can add their own requirements, and public safety signals should not be treated as investment, legal, or formal audit advice.
Audit status
Ondex is preparing an external audit scope for wallet key storage, unlock and signing flows, payload validation, WalletConnect handling, deep-link sanitization, backup boundaries, and wallet-authenticated backend flows. Public copy will link to a report or scoped summary only after an audit is complete.
Public references
Public safety claims should link to this page, the privacy policy, the terms, or product pages. Internal repository paths must stay out of published copy.