In short
- The desktop wallet never connects to the internet. Your recovery phrase stays on your computer unless you choose to import it from your phone or browser.
- Sync and backup never hold your keys or recovery phrases, except Travel Keys you choose to share, locked with your travel password.
- There are no accounts: no email, no name, no password. No analytics, crash reporting, ads or advertising IDs in any app.
- The phone and browser apps talk to public blockchain nodes to read balances and send the transactions you sign.
- With 0xStealth Pro, sync goes through our server encrypted end to end. We can't read it.
- We don't sell your data or share it for advertising.
The desktop app
0xStealth for desktop is the wallet. It never connects to the internet and sends nothing to us or to anyone else. It talks only to the phone and browser apps you pair with it: by QR code, by file, over a link on this computer, over your own network, or by Bluetooth. Wallet updates reach it the same way, from a paired app or a file you give it.
Downloading the desktop app from GitHub is a visit to GitHub, and GitHub's privacy statement applies to it.
The phone and browser apps
The iPhone app, the Android app and the browser extension do the online work. This is everything they send off your device, and who receives it.
Blockchain nodes
- What
- The addresses you add, balance and token lookups for them, and the signed transactions you choose to send. Like any server, a node sees your IP address.
- Who
- The public nodes built into the apps (PublicNode, dRPC, PulseChain, BNB Chain, Arbitrum, Optimism and Base), or a node you add yourself. We have no agreement with these providers; their own policies apply.
- Why
- To show your balances and put your transactions on the network.
Our sync server, with Pro
- What
- Your synced data (your addresses, custom chains and tokens, settings, your account list, your list of devices and your account backup), encrypted on your device with a key made from your 12-word sync key. We never get the sync key, so we can't read any of it. It never holds your keys or recovery phrases, except Travel Keys you choose to share, locked with a travel password we never get. Alongside it: a group ID and a Pro ID, two different one-way hashes of the sync key.
- Why
- The group ID tells our server which records belong together. The Pro ID lets it check that Pro is on.
Our price service
- What
- The tokens to price: each one's network and contract address. No wallet addresses and no balances.
- Why
- To show values. The list is handled in memory and never logged.
RevenueCat
- iPhone
- Android
- Browser checkout
- What
- On the phones, a random anonymous ID from first launch. Once you buy Pro or use a sync key that has it, your Pro ID instead. Your store receipts and purchase history.
- Why
- RevenueCat checks purchases for us and tells our server whether Pro is on. It doesn't get your addresses or your synced data.
Apple, Google and Stripe
- What
- On a phone, Apple or Google takes the payment for Pro under your store account. If you buy Pro on this website from the browser extension, Stripe takes the payment through RevenueCat's checkout. Your card details go to them, never to us.
- Why
- To bill the subscription.
Reown's relay
- What
- Only when you connect a site by scanning its code: a relay client ID and your IP address. The messages between you and the site are encrypted end to end, so the relay can't read them.
- Why
- It carries a site's requests to your phone (WalletConnect). Its telemetry is turned off.
Google ML Kit
- What
- When you scan a QR code on Android, Google's barcode scanner sends Google device and app details, performance figures and a per-installation ID. The camera picture is decoded on the phone and never sent.
- Why
- Google collects this to run and improve the scanner. The iPhone app uses Apple's own scanner and sends nothing.
Sites you open
- What
- A site you visit in the phone app's browser, or with the extension, sees what any site sees. When you connect, it gets the address you choose. Searches in the phone app's browser go to DuckDuckGo.
- Why
- Because you opened it. Each site's own policy applies.
Our network list, update files and logos
The apps fetch our signed network list from registry.0xstealth.app, and desktop wallet update files from GitHub to hand to your desktop app. The extension loads token logos from the public Trust Wallet assets collection on GitHub. These requests carry no data about you beyond the IP address every request has.
Cloudflare, which runs our server
Our sync, price and network services, and this website, run on Cloudflare. Like any host, Cloudflare handles the IP address each request comes from, and its request logs can include it. Our own logs record the kind of request, its size, the time and the result. They never hold record contents, your addresses or your sync key.
What stays on your device
- Bluetooth and QR traffic goes only between your own devices.
- Camera frames are decoded on the device.
- On the phones, your saved addresses are locked behind Face ID or your fingerprint.
- Travel Keys you allow stay on that phone or browser until their end date or until you remove them, locked with your travel password.
- Request history stays on the device, and guest mode keeps none.
- Your recovery phrase stays in the desktop app unless you choose to import it from your phone or browser. Then the app sends it to the desktop app over your encrypted link and doesn't keep it.
What we never collect
- Your name, email, phone number or a password. There are no accounts.
- Your recovery phrase or your keys. The only keys that ever reach our server are Travel Keys you choose to share, locked with a travel password we never get.
- Location, contacts, photos, files, messages or health data.
- Analytics, crash reports, advertising IDs or ad tracking. No app contains an analytics, crash reporting or advertising kit.
We don't sell data, share it for advertising, or use it to make decisions about you.
How long we keep it
- Synced records and the link between your sync key and Pro stay on our server until you delete them.
- Delete synced data, in each app's sync settings, erases every record our server holds for your sync key and unlinks Pro from it. Your subscription itself is managed in the App Store, Google Play or the checkout emails; see how to cancel.
- Remove sync key only forgets the key on that one device. The encrypted copy stays on the server until you use Delete synced data.
- Reset sync key copies your records to a new key, then deletes the old key's records.
- Pro checks are cached for 15 minutes when Pro is on, and 60 seconds when it isn't.
- Price requests aren't kept.
- Purchase records are kept by RevenueCat and the stores under their own policies. Write to us to have your RevenueCat record deleted, and we'll help you find your Pro ID.
Your choices
- Use your own node. Add your own node for a network, and public node providers stop seeing your addresses.
- Use it without Pro. Without sync, none of your addresses go to our server.
- Delete your synced data at any time from the app. Step by step.
- Use guest mode on a phone to keep no request history.
Wherever you live, you can ask us what we hold and ask us to delete it, and we'll answer. Because there are no accounts, we can only find data linked to a sync key or Pro ID you give us, and the delete action in the app is the fastest way. If you are in the EU or the UK, we handle this data to provide the service you asked for, and you can complain to your local data protection authority.
This website
0xstealth.app sets no cookies and runs no analytics. Its fonts and code are served from this site. It remembers whether you paused the motion, in your own browser only. The Pro checkout page, opened from the browser extension, loads RevenueCat's and Stripe's payment code, which may set its own cookies to prevent fraud.
Children
0xStealth is a wallet for adults. It is not directed at children under 13, and we don't knowingly collect anything from them. If you believe a child has used our sync service, write to us and we'll help delete it.
Changes
When this policy changes, we'll post the new version here with a new effective date. If a change affects what an app sends, we'll also say so in that app's release notes.