Soheil is built to need as little data as possible. Trading needs no account and no name, and there are no analytics scripts and no tracking cookies (an account exists only for developers who want an API key); an email address is kept only if you ask for alerts by email. Everything below is the complete list.
What we process, and why
- Wallet addresses you connect or type in (for example a NEAR account or a refund address), to show balances and positions and to prepare, send and verify transactions. Addresses and transactions are public on their blockchains.
- Trade records: transaction hashes, networks, tokens, USD values, the route partner used and the wallet that made the trade, for swaps, bridges and Earn deposits made through Soheil, and whether the page was opened from our Telegram bot. We keep them to confirm trades on-chain, award XP and show verified totals. The public trust page shows hashes and amounts, never wallet addresses.
- Wallet connections: when you connect a wallet, its address, the first and last day it was connected and whether the site was opened from our Telegram bot, so we can count how many people use the site. Not linked to IP addresses. If you arrived through one of our campaign links (a short code in the address), that code is kept in your browser and noted with the wallet you first connect, so we can tell which links bring people who trade.
- Referral links: when you arrive through an invite link, the inviting wallet is stored with yours so the inviter earns a share of your XP.
- Quote statistics: which pairs, networks and amounts are requested, without any wallet address or other identifier. Detailed quote records are kept for 90 days, then reduced to daily totals.
- IP addresses are used in memory to limit abusive request rates and are written to our web server's standard access log, which rotates after 14 days. They are never linked to wallet addresses or trades.
Stored in your browser
Your theme, which wallets you connected, your portfolio watchlist, a short-lived copy of the balances last shown (so pages open instantly), an invite code if you arrived through one, the bot's chat tag if you opened the site from our Telegram bot, and which connected wallets were already reported today are saved in your browser's local storage, on your device only. You can clear them at any time in your browser settings. We set no cookies for visitors; only signing in sets one (the developer dashboard on api.soheil.fi, and our own admin panel for the operator).
Services that receive data
Soheil has no exchange or bridge of its own. To find routes, build transactions, read balances and track transfers, it sends wallet addresses, tokens and amounts to the services below, which process that data under their own privacy terms. Your private keys and seed phrase never leave your wallet; nothing here can move your funds without your signature.
Swap and bridge routes
Your request (networks, tokens, amount, your wallet address and the receiving address) goes to the route partners that serve those networks: LI.FI, Relay, Soheil Router, Layerswap, Symbiosis, NEAR Intents, Rango, Skip:Go, Across, KyberSwap, deBridge, Mayan, THORChain, USDT0, Velora, Chainflip, Garden, Uniswap, Cetus, Hyperlane, Jupiter, Liquidswap, STON.fi Omniston, SunSwap. Each partner's contracts are listed on the trust page.
Earn, Lend and Borrow
Wallet address (to read positions), asset and amount (to build a deposit, withdrawal, supply, borrow or repayment).
Aave · Kamino · Jupiter Lend · NAVI · Yield.xyz · LI.FI (Earn routes)
Limit orders, alerts and recurring reminders
EVM limit orders: wallet address and the order (tokens, amounts, price, expiry), sent from your browser straight to CoW Protocol's order book, which is public; our server then follows the order's status there. Take-profit / stop-loss, Solana price alerts and recurring buys: the token, the price levels or schedule and the swap, kept on our server with your Telegram chat or email address so we can tell you.
CoW Protocol (api.cow.fi)
Email alerts (only if you ask for them)
Your email address, the language, and what you asked to be told about: a wallet's loan health, a token's price levels or a recurring buy. We email a confirmation link first and send nothing else until it is opened; every email has a link that stops it.
Resend (email delivery)
Telegram notifications (only if you start our bot)
Your Telegram chat id, @username and first name, the invite or ad link you started the bot with, and the wallet addresses you link, so the bot can tell you when a trade completes, a limit order fills or a loan gets risky, and so we can count how people use it. The bot's links to this site carry a random tag for your chat: a wallet you connect or a trade you make after opening such a link is noted with your chat. Telegram sees the messages it delivers.
Telegram
Bot wallet (only if you make one in the Telegram bot)
Your Telegram user id and the wallet made for you, kept at Privy, the wallet provider it runs on. Our server keeps the wallet's address, your limits, your main wallet (where withdrawals go) and the transactions the bots send, so it can trade within your limits and tell you what it did.
Privy (wallet infrastructure)
Trading assistant (only if you write to it)
What you write, the replies, and what our tools looked up for the answer (balances of your connected or linked wallets, prices, routes, vaults) go to the AI model that writes the replies, through Venice's API (we use a model Venice marks as private; Venice's own privacy policy covers how it handles requests). Our server keeps the conversation (your messages, the replies and the offers made) for 30 days, so we can check the assistant's answers and look into misuse, then deletes it; it also counts how many messages each wallet, chat or address sends a day, for the daily limits.
Venice (AI model API)
Contact form (only if you write to us)
The topic, your message and the email address or Telegram name you give for our answer. Our server keeps them for a year so we can answer and follow up, then deletes them, and emails the message to our support address so we can reply; the ops chat is told only that a message arrived. No IP address or wallet is stored with it.
Resend (email delivery)
Soheil Router and the developer API (only if you use them)
A developer account keeps your email address, your password (hashed, never readable) and, if you turn it on, your authenticator app's secret (encrypted). Codes we email you are kept only as a hash and expire. Signing in to the dashboard sets one cookie on api.soheil.fi (HttpOnly, 14 days at most), used only to keep you signed in. For each API key we keep its name, fee settings and daily request counts. For each quote the router builds we keep the key, networks, tokens and amount, and for trades from Solana or Bitcoin the sending and receiving addresses, so the trade can be matched and paid out. The trades our contract records on-chain are kept like the other trade records. The request goes to the partners a trade may use, listed on the trust page.
The router's partners (trust page) · Resend (email delivery)
Balances and portfolio
Wallet address, to read token balances and DeFi positions on each network.
Zerion · Alchemy · Helius · TonAPI · TronGrid · mempool.space and Blockstream (Bitcoin) · Hyperliquid API · public RPC endpoints (Solana, Sui, Bittensor)
Transaction tracking
Transaction hashes, to confirm that a swap, bridge or deposit completed.
Block explorers and RPC endpoints of the networks involved · the route partner that built the route
Wallet connection
A connection session between the site and your wallet app; the wallet provider sees your address and this site's domain.
WalletConnect (Reown) · Coinbase Wallet · TON Connect · the browser extension or app you connect with
Read directly from your browser
Some data is fetched by your browser, not our server: your IP address is then seen by that service.
Sui RPC (fullnode.mainnet.sui.io) and NAVI (open-api.naviprotocol.io) for Sui transactions · Pyth (hermes.pyth.network) for NAVI oracle prices · TonAPI for TON transactions · wallet providers' verification endpoints
How long we keep data
- Trade records and XP: for as long as the site runs, so your level and verified history stay correct. Deleted on request.
- Quote statistics: 90 days in detail, daily totals after that.
- Telegram name and linked wallets: until you send /stop to the bot. After /stop we keep only the chat id, the dates it used the bot and the link it came through, for our user counts. EVM limit orders placed here (order id, wallet, tokens): kept with the order's outcome, to tell you when it fills.
- Wallet connection records: for as long as the site runs. Deleted on request.
- Developer accounts and API keys: until you delete the account or key. Deleted on request.
- Quotes built by Soheil Router: kept with the trade records, so our contract's trades stay verifiable.
- Contact form messages: one year.
- Web server access logs (IP addresses): 14 days.
- Nothing is stored about visitors who only read the site.
What we never do
We do not sell or rent data, show ads, run analytics or advertising scripts, profile visitors, or ask for your seed phrase or private keys. We do not send marketing email: an address given for alerts is used only for those alerts. The Telegram bot may send occasional announcements to people who started it; /stop ends them.
Where data is processed
Our server runs in the European Union. The services listed above run where their operators run them, which may be outside the EU; each one processes only what is needed for the request you make.
Your rights and how to reach us
You can ask what we hold about a wallet address, ask for trade and XP records to be corrected or deleted, and object to processing. Sign a message from the wallet in question when you ask, so nobody else can delete your records. Write to support [at] soheil.fi or message our official X, Telegram or GitHub account. If you are in the EU, you can also complain to your national data protection authority.
This page describes what the site does today. When we add a service that receives data, we add it here and update the date above.