SafeX
Wallet
Back to the wallet

SafeX Wallet

Privacy policy

Last updated: 30 Sep 2026. Effective date: 30 Sep 2026. Applies to the SafeX Wallet website, the Android app, and the Chrome extension. Official sites: safexwallet.cloud and safexwallet.org. Terms: safexwallet.cloud/terms and safexwallet.org/terms. Contact: support@safexwallet.org.

SafeX Wallet is a non-custodial cryptocurrency wallet. This policy explains what the apps handle, where it is stored, what gets sent over the internet and why, and the choices you have. The short version: the wallet apps do not collect a name, email, or phone number, and they contain no third-party analytics. Your keys stay on your device and never leave it. Swap quotes, activity lookups, and a directory report of public addresses are sent to the official site you opened, safexwallet.cloud or safexwallet.org, only as described below. SafeX cannot recover a lost recovery phrase.

1. Summary

  • We don't run user accounts, and we don't ask for your name, email address, phone number, or any other personal information.
  • Your recovery phrase, private keys, and wallet password are encrypted and stored only on your device. They are never sent to us or to anyone else.
  • The website, Android app, and extension contain no third-party analytics, advertising, or crash-reporting SDK.
  • When you open the wallet, create or import one, send, swap, open Buy, or receive an in-app notification, the app sends a random device id, the platform, the app version, your public addresses, and the transaction hash, notification title, or Buy asset, network, and fiat amount to safexwallet.cloud. That report is shown in the operator console. It never includes a recovery phrase, private key, password, keystore, or biometric data.
  • The Android app does not use Expo over-the-air updates.
  • To show balances and send transactions, the apps send your public wallet addresses and transactions you have signed and approved to the public networks listed below. Buy, Sell, and Swap quotes go through safexwallet.cloud or safexwallet.org, which forwards them to 0x or Jupiter. The device signs the result.
  • We don't sell, rent, or share user data, and we don't use it for advertising or credit decisions.

2. Information stored locally on your device

The extension saves the following in this browser's private storage for the extension, on your computer:

DataPurposeProtection
Recovery phrase and private keys, whether created in the extension or importedNeeded to sign transactions and control your walletEncrypted with a key derived from your password before storage. Never transmitted.
Your wallet passwordNot stored in readable form. It is only used on your device to encrypt and decrypt your keys.Never transmitted
Public wallet addressesShow your addresses and balances, and generate receive QR codesStored locally. Also included in the directory report described above.
Preferences: enabled coins, hide zero balances, selected network, and the auto-lock timerRemember your settingsStored locally

Recovery phrases, private keys, and passwords stay in your browser profile until you remove them (see Section 7). The operator console does not receive them.

While the wallet is unlocked, decrypted keys are kept in memory only as long as needed. They're cleared when the wallet locks, either manually or through auto-lock.

3. Information sent to blockchain networks and quote services

A wallet has to talk to blockchain networks to work. Balance, fee, and send calls go directly from the device to the public networks below. Buy, Sell, and Swap quotes, the website activity list, and price charts go through safexwallet.cloud or safexwallet.org, which then asks the network or quote service. The Android app and the extension call safexwallet.cloud for those routes. None of these calls include a recovery phrase, private key, or password.

  • BNB Chain, Ethereum, Polygon, Arbitrum, Base, and Optimism: *.publicnode.com, with BNB Chain also falling back to bsc-dataseed.bnbchain.org.
  • Tron: api.trongrid.io (Shasta uses api.shasta.trongrid.io).
  • Bitcoin: blockstream.info. Bitcoin send is supported. The transaction is signed on the device and then sent to the network. It is not display-only.
  • Solana: api.mainnet-beta.solana.com (devnet when test networks are on).
  • USD portfolio prices: api.coingecko.com, using public asset ids and no wallet address. USDT uses the id tether. Tron USDT is the public contract TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on CoinGecko's tron platform. The website asks through safexwallet.cloud/api/prices. The extension and Android app call CoinGecko directly, and may ask Binance public tickers when that quote is missing.
  • Price charts, when you open a coin: GET safexwallet.cloud/api/market with a public market id (for example ethereum) and a range (1D, 1W, 1M, 1Y, or All). No wallet address is sent. The server asks api.coingecko.com first. If that chart is missing, it asks api.binance.com for public klines using the market symbol and range only (for example BNBUSDT and 1D). If that host refuses, it asks data-api.binance.vision with the same symbol and range. The chart is kept in server memory by asset and range, not by address, and is not written to a database.
  • NFT lists, when a network has a Blockscout API: *.blockscout.com, using the public address.
  • Ethereum-style transfer history on the Android app: api.rabby.io, with the public address and network, for mainnet. If that list is unavailable, the app reads recent transfers from the public network. The website and the extension send the public address, chain, and network, plus an optional page and token list, to safexwallet.cloud/api/history. The extension asks for at most three networks at a time. For Ethereum, Polygon, BNB Chain, Arbitrum, Base, and Optimism mainnet, that server asks api.rabby.io first. If that list does not answer, it asks the public explorer for that network (eth.blockscout.com, polygon.blockscout.com, arbitrum.blockscout.com, base.blockscout.com, or explorer.optimism.io), and the matching testnet explorer when test networks are on. It asks api.etherscan.io only when those free lists do not answer and a server key is set. Tron uses api.trongrid.io. Bitcoin uses blockstream.info, then mempool.space. Solana uses api.mainnet-beta.solana.com and solana-rpc.publicnode.com. The history route keeps that response in server memory for about 30 seconds, and a one-minute request count by IP in the same memory. It does not write history to a database. Those values disappear when the server process ends.
  • Buy, Sell, and Swap, only when you request a quote: the website, Android app, and extension ask safexwallet.cloud/api/swap/0x, safexwallet.cloud/api/swap/jupiter, and safexwallet.cloud/api/swap/jupiter/tx. They do not call 0x or Jupiter directly. The 0x request includes your public address, the token pair, the sell amount, the network, and slippage. The Jupiter quote includes the token pair and amount. The Jupiter transaction request includes that quote and the Solana public address. The server forwards the 0x request to api.0x.org and the Jupiter requests to lite-api.jup.ag, then returns the quote or unsigned transaction. Signing stays on the device. The route code does not write the body to a database and does not log the address, token pair, or amount. It is not stored beyond the host's ordinary request logs, which record the time, path, and status.
  • Buy with a card, only when you press Continue to Transak: the website asks safexwallet.cloud/api/onramp with the selected network and your public address. The server returns a link to Transak, and the page opens it. Transak receives that public address, the asset, and the network so the crypto can be sent to you. The same moment, the directory report records the asset, network, fiat amount if you entered one, and public address. If Transak sends the order status back, that status is recorded too. SafeX does not receive your card number, identity documents, or the payment. Transak's own privacy policy covers the information you give them. Recovery shares and the recovery phrase are not included.
  • Price alerts stay on the device. The website and extension ask for public USD prices the same way the portfolio does. They do not send the alert level or your address with that request. A browser or Android notification, if you allow it, is shown by the device. It is not sent to SafeX.
  • WalletConnect, when pairing is available on this site: the WalletConnect relay. It receives pairing data, not keys. If pairing is turned off, the relay is not used.
  • The in-wallet browser on the website: the address you type is sent to this website so it can check whether that site allows itself to be shown inside SafeX Wallet. The page itself is not fetched or stored. The Android app checks the same thing from the phone.

In short, the apps send only:

  • Your public wallet addresses, to look up balances, token holdings, fee estimates, and transaction status;
  • Signed transactions that you've reviewed and confirmed, so they can be sent to the relevant blockchain network; and
  • The quote, history, and chart fields described above, which contain a public address only where the network needs one, or a market id and range with no address.

None of these calls include a recovery phrase, private key, or password.

  • Blockchains are public. Addresses, balances, and transactions recorded on a blockchain are permanently and publicly visible to anyone. This is how blockchain networks work, and neither we nor anyone else can change or delete on-chain data.
  • Network logs. Like any website, a network you contact may automatically receive technical information such as an IP address and the time of the request. When the app talks to a network directly, that network can associate the request with the addresses you look up. When the request goes through safexwallet.cloud or safexwallet.org, this website receives the fields described above and the network sees the server's onward request. Those fields are not saved as a user profile. Vercel, which hosts the site, keeps ordinary request logs of the time, path, and status. The route code does not add the wallet address or quote body to those logs. All connections use encrypted HTTPS. Each network's own privacy policy governs what it keeps.

4. Information we do not collect

We don't collect a user profile, and we don't keep:

  • Names, email addresses, phone numbers, postal addresses, or other identifiers (unless you choose to email us; see Section 5)
  • Recovery phrases, private keys, or passwords
  • A database of wallet balances or transaction history. Public chain activity may sit in server memory for about 30 seconds, as described in Section 3, and then it is gone.
  • Browsing history, web page content, or activity on other websites
  • Location data
  • Analytics, crash reports, usage statistics, or advertising identifiers. The wallet apps do not ship an analytics or crash-reporting SDK.

The extension doesn't read or modify the web pages you visit.

5. When you contact us

If you email us at support@safexwallet.org, we receive your email address and whatever you choose to include in your message. We use it only to respond to you, and we delete support correspondence when it's no longer needed. Never send us your recovery phrase, private key, or password. We will never ask for them. Anyone who asks for them is trying to steal your funds.

6. How information is used and shared

The data handled by the extension is used only to provide its single purpose: letting you create or import a wallet and view, send, and receive your crypto assets.

We don't sell user data, transfer it to data brokers, use it for personalised or interest-based advertising, or use it to determine creditworthiness or for lending purposes. The apps share data only as described in Section 3: public addresses and signed transactions with blockchain networks, and the quote, history, and chart fields with safexwallet.cloud or safexwallet.org so that site can forward them. That sharing is necessary for the wallet to function.

Chrome Web Store Limited Use disclosure

The use of information received through SafeX Wallet complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

  • User data is used only to provide and improve the extension's single purpose and user-facing features.
  • User data is transferred only as necessary to provide that single purpose (sending and reading blockchain data), to comply with applicable law, or for security purposes.
  • User data is never used or transferred to serve personalised, re-targeted, or interest-based advertising.
  • No human reads these requests as part of the product. The SafeX server does receive the swap, history, and chart requests described in Section 3 so it can forward them. It does not keep a user profile, and it does not receive a recovery phrase or private key.

7. Your control, retention, and deletion

  • Retention: the encrypted wallet stays on your device until you delete it. We hold no copy of your keys. Swap bodies are not saved. A history or chart response may remain in server memory only for the short time described in Section 3.
  • Deletion: you can delete all wallet data by removing the wallet in the extension (if available) or by uninstalling SafeX Wallet from chrome://extensions. Uninstalling permanently erases the encrypted vault and preferences from your browser.
  • Before deleting: make sure you have your recovery phrase written down safely. Because SafeX is non-custodial, we can't recover your wallet, recovery phrase, private keys, or password. Without your recovery phrase, deleted wallets and the funds in them can't be restored.
  • Access and correction: because we don't hold personal data about you, there's nothing for us to access, correct, or delete on our side. If you believe we hold any of your information (for example support emails), contact us and we'll delete it.

8. Security

  • Keys are created on the device as a recovery phrase and encrypted before they are saved. On the website and in the extension, the password encrypts the phrase and only that encrypted copy is stored. On Android the same encrypted copy is stored in the phone's secure storage. Android backup is off. iOS keychain items are stored for this device only. Backup and reveal screens block screenshots.
  • The website, extension, and phone clear the clipboard about 60 seconds after you copy a Secret Recovery Phrase, private key, or keystore.
  • The wallet can lock automatically after a period of inactivity (auto-lock).
  • Every transaction requires your review and confirmation before it is sent.
  • Network requests are made over HTTPS.
  • The extension doesn't load or run remotely hosted code.

No system is perfectly secure. Your wallet's security also depends on keeping your device, browser, password, and recovery phrase safe. Choose a strong password, keep your recovery phrase offline, and only install SafeX Wallet from its official Chrome Web Store listing.

9. Children

SafeX Wallet isn't directed at children under 13 (or the minimum age required in your country), and we don't knowingly collect information from children.

10. International users

SafeX Wallet stores the wallet itself only on your own device. Requests to safexwallet.cloud or safexwallet.org are handled by that site's host and may be processed in another country. The blockchain networks listed above may also operate servers in different countries. Their own privacy policies govern how they process technical request data.

11. Changes to this policy

We may update this policy from time to time, for example if the extension's features change. We'll post the updated policy at safexwallet.cloud/privacy and safexwallet.org/privacy with a new effective date. If a change affects how the extension handles your data, we'll also tell you inside the extension or in the Chrome Web Store listing before the change takes effect.

12. Risk

Transactions cannot be reversed. You are responsible for the recovery phrase and for checking every address and amount. This is not financial advice. SafeX Wallet does not provide insurance, and it does not promise that funds are safe from a lost phrase, a phishing site, or a compromised device. See the terms.

13. Contact

Questions about this policy or your privacy:

Email: support@safexwallet.org

Websites: safexwallet.cloud and safexwallet.org