Privacy Policy

0xio software is designed as a self-custodial wallet. Your keys are encrypted on your device, including the EVM (0x) key a wallet holds for Ethereum and other EVM networks. We, the developers, do not have access to your funds or any database of your private keys.

Extension (Chrome & Firefox): an encrypted JSON vault in browser local storage; decrypted keys live in volatile session memory only while unlocked, and the optional passkey unlock is checked by your device's own authenticator. Mobile: keys held in the iOS Keychain, readable only while the phone is unlocked, or encrypted under an Android Keystore key, and never synced or included in backups, with biometrics for local authentication. Desktop: an AES-256-GCM encrypted vault file, Touch ID / Windows Hello, key zeroing on lock. SDK: a bridge between dApps and the wallet that requests only your public address and signatures, and cannot access data without your approval.

On the Extension and Desktop, the vault is encrypted with AES-GCM (256-bit) under a key derived from your password with PBKDF2 (SHA-256): 900,000 iterations on the Extension, 600,000 on Desktop. On Mobile, keys stay in the Keychain or Keystore and your PIN is checked against a PBKDF2 (SHA-256) hash with 100,000 iterations. Each wallet locks itself after a set time, by default 5 minutes on the Extension and Mobile and 15 minutes on Desktop; the Extension and Desktop then clear the decryption keys from memory.

To function, 0xio communicates with an Octra Network RPC node: octra.network on mainnet, devnet.octrascan.io on devnet, or a node you add yourself. When you check a balance or send a transaction, your IP address and public wallet address are visible to that node's operator. The rpc-proxy.0xio.xyz relay we operate is used for Octra RPC calls only when you turn it on in settings, for mainnet and devnet. It is never used as a fallback, and a node you add yourself never goes through it. On EVM networks the Extension reads balances and sends the transactions you sign through each network's public RPC endpoint, or an RPC you add, so that operator sees your IP address and your EVM address in the same way.

We minimize external dependencies. Code may contact: GitHub and jsDelivr (token lists, logos and the dApp directory), octrascan.io (explorer and the devnet RPC), rpc-proxy.0xio.xyz (optional Octra relay, off unless you turn it on; it also carries any-chain bridge quotes, bridge signer requests and NFT and logo images), oracle.0xio.xyz (OCT prices, and EVM history, NFTs and held tokens), indexer.0xio.xyz (the list of known NFT collections), bridge.0xio.xyz & solver.0xio.xyz (cross-chain), public EVM RPC endpoints such as publicnode.com (EVM balances and sending), Blockscout explorers (EVM history, contract names and call details where the oracle has none), api.relay.link (the public chain list used to check bridge quotes), coins.llama.fi (EVM token prices), chainlist.org (the network list when you add an EVM network), IPFS gateways (NFT media), push.0xio.xyz + Expo (mobile notifications), 127.0.0.1 (extension<->desktop FHE compute), WalletConnect (relays encrypted messages between the wallet and a dApp you connect) and Sentry (crash and performance reports from the desktop and mobile apps, set to carry no personal information; on mobile you can turn it off under Crash reports in Settings). We run no advertising, analytics profiling or cross-app tracking, and we do not sell or share data.

In crypto, "Don't Trust, Verify" is the golden rule. We are committed to transparency and have open-sourced our core cryptographic libraries.

The mobile wallet has no account and asks for no name, email address or phone number. Push notifications are optional: when you turn them on, the app registers your wallet address, the network, any token contracts you imported, a push token for your device and your wallet's public key with push.0xio.xyz so it can tell you about incoming transactions; turning notifications off or removing the wallet unregisters it. Crash reports and a sample of performance measurements go to Sentry, hosted in the European Union, with the app version, device model, operating system version and the technical details of the error, never keys, recovery phrases or PINs; you can turn them off under Crash reports in Settings. The camera is used only to scan QR codes, on the device; nothing is stored or sent. Face ID, Touch ID and fingerprint checks are done by the operating system, and the app learns only whether the check passed. Sites opened in the in-app browser receive what any browser sends them, searches typed in its address bar go to the search engine picked in its settings (DuckDuckGo unless you change it), and a dApp learns your address only when you approve its connection.

The Extension has no account, asks for no name, email address or phone number, and sends no API key or service key with its requests. It contains no analytics, advertising or crash reporting code. Your recovery phrase, private keys, password and decrypted private balances stay on your device, and the balances, history, tokens and NFTs it caches are kept in browser storage separately for each address and network. On Octra, your address and the transactions you sign go to the network's RPC node, or to rpc-proxy.0xio.xyz when you turn the proxy on; a node you add yourself is reached only after the browser asks you to allow it. When you turn on EVM for a wallet, on the EVM networks it uses (Ethereum and Robinhood Chain, or their testnets on devnet, plus any network you add, each of which you can turn off), your EVM address and the network's chain id go to oracle.0xio.xyz to read your history, NFTs and held tokens; to the network's public RPC endpoint for balances and sending; and, where the oracle has no route or cannot be reached, to a Blockscout explorer, which needs no key, for history, contract names and call details. A bridge quote from another chain goes through rpc-proxy.0xio.xyz with your EVM address and your Octra address, and the proxy requests it from Relay; the Extension also reads Relay's public chain list at api.relay.link to check each quote before you sign. EVM token prices come from coins.llama.fi and carry only token contracts, and the search in Add a network loads the public list from chainlist.org. NFT images and token logos from other hosts on EVM networks load through the 0xio image proxy, so those hosts do not see your IP address. When 0xio Desktop runs on the same computer, the Extension connects to it on 127.0.0.1 and passes it the private balance key it needs to compute encrypted amounts, never your signing key; this connection does not leave your device. Living NFTs are programs stored on chain: they run in a sandboxed page with no access to the wallet, its keys or the browser's extension features, and can reach only the RPC of the network the token lives on. A site learns your address only when you approve its connection, and every signature or transaction needs your approval.

Push registrations are kept until you turn notifications off or remove the wallet. Crash and performance reports are kept for up to 90 days. Our services keep no accounts and no user profiles. The 0xio oracle keeps a request log of the route called, the response status and the time taken, with no IP address or wallet address, for up to 90 days. The RPC proxy writes short-lived operational logs that can show the network, the method, the first characters of a wallet address and, when a caller goes over the rate limit, its IP address; these logs are kept only as long as needed to run the services and prevent abuse, and are never used to profile users. Each service limits requests per IP address with counters held in memory and cleared within minutes, and answers for an address are cached for a few minutes at most. Data recorded on the Octra Network and on EVM networks is public and permanent by design, except the amounts and balances you keep private with the Octra network's encryption.

You can use every wallet without notifications, you can turn EVM, or any single EVM network, off in the Extension, and you can erase a wallet and all its data from a device at any time in Settings. Depending on where you live, you may have the right to ask what data we hold about you and to have it corrected or deleted. Because we do not link data to your identity, we may need your wallet address or device details to find it. Write to team@0xio.xyz.

The 0xio Ecosystem is not intended for anyone under 18.

We post changes on this page and update the date above.