Privacy
Last updated 12 November 2026
What is recorded, what is sent where, and what this cannot protect you from. Every claim below can be checked against the source.
Who sees what
Your browser
Holds the key. Signs locally.
This site
Quotes, creates, records the fee.
Providers
Run the exchange itself.
The chain
Keeps it forever.
- yoursYour browser
- Sees
- Everything: the private key, the recovery phrase, your address labels, and the exchange in progress. The key is in memory only and the tab's session storage never holds it, so a reload needs the wallet reconnected.
- Never sees
- Nothing is hidden from it — which is the warning. An extension can read what is on this page, including a key typed into it, and a compromised device defeats every other row here.
- requiredThis site
- Sees
- Amount, currency pair, payout address, transaction hash, fee, and the country your connection appears to come from. Plus your IP address, user-agent and language header, kept at least a year because exchange providers require partners to retain and produce them.
- Never sees
- Your private key or recovery phrase. They appear in no server route, and the sanctions check runs here against a list downloaded from the US Treasury rather than by sending your address to anyone.
- requiredThe exchange provider
- Sees
- Your payout address, the amount, the pair, and the timing of the leg it runs. An exchange cannot be quoted or created without them. SideShift also receives your IP, because it asks integrations to forward the payer's address.
- Never sees
- The other legs, when a transfer is split across providers — and on a two-hop route, whichever end it was not handed.
- requiredExplorers and price feeds
- Sees
- blockstream.info and mempool.space see which Bitcoin address was asked about, and the public tickers of Binance, KuCoin, Gate and MEXC are read for dollar figures. Only Bitcoin payout addresses are looked up at all.
- Never sees
- Who asked. These calls are made by this server rather than by your browser, so they see the server's connection and not yours. That hides the asker, not the address.
- chosenGoogle Analytics
- Sees
- Which pages you viewed, roughly where you are, what brought you here, and a cookie telling one visit from the next. One click event is sent, carrying which page a button was pressed on and nothing else.
- Never sees
- Any address, amount, exchange id or transaction hash. None is ever passed to it — which is a line worth keeping, because a wallet address pushed into analytics is exactly what an identity-resolution business consumes.
- inherentRender and Cloudflare
- Sees
- Every request to this site, including IP addresses, because that is what hosting a site on someone else's machines means. Separate from the record this site keeps itself: both exist.
- Never sees
- Anything this site does not send them, which is the same traffic any visitor generates.
- inherentThe blockchain
- Sees
- Every transaction, permanently, by design: amounts, addresses, timing. Splitting a transfer raises the cost of putting it back together. A Monero leg removes the entry rather than obscuring it.
- Never sees
- Nothing, on a transparent chain. This is the one row nothing on this site can change, and it is the reason for every other decision here.
The tags are the argument. Three of these parties see what they see because an exchange cannot happen otherwise, and two because anything hosted on the internet and written to a public ledger works that way. One is a decision, and it is marked as one rather than filed among the others.
Nothing here is a claim about what the providers or Google do with what they receive. That is theirs, and this page can only be accurate about what leaves.
Never sent anywhere
Your private key. It is held in the browser tab, derives your address, and signs transactions locally. It appears in no server route. It is kept in memory only and cleared when you disconnect or close the tab.
Recovery phrases for wallets generated here. Same: created in your browser, never uploaded, no copy kept.
Address labels and the observer lists attached to them, which live in your browser's own storage.
A wallet extension, if you use one. Connecting TronLink or a Bitcoin wallet leaves the key in that extension: it gives this page an address, and approves every payment in its own window. Nothing is stored here, and this site never sees the key.
One exception to the lookups below. When TronLink signs, it talks to its own Tron nodes from your connection rather than through this server, so those nodes see your address and your IP. Pasting a key keeps every chain call behind this server instead; signing in the extension trades that for never handing the key over. Paying a deposit address yourself avoids both.
Your destination address, for sanctions screening. A Bitcoin payout address is checked against the US Treasury's published sanctions list, and that check runs here: the list is downloaded to this server and the comparison is made locally. The address is never sent to Treasury, and never to a screening company — this site buys no such service and subscribes to no such service.
An exchange in progress. Its amounts, addresses, exchange id and plan are kept in this tab's session storage, so reloading the page returns to the same step and stage. That storage belongs to the one tab and is cleared when it closes. The private key is never written to it: after a reload the wallet has to be connected again.
What this site records
Each exchange is written down for fee accounting. A record holds:
time · amount · currencies · payout chain · provider · fee rate and amount · payout address · transaction hash · a random browser handle
The handle is a random value generated in your browser so repeat exchanges can be grouped. It is not derived from anything about you and resets when you clear this site's data.
Country: each exchange also records the country your connection appears to come from, as a two-letter code supplied by the network in front of this site. It is approximate — a VPN or Tor changes it — and the IP address it is worked out from is not stored.
Recorded with every exchange: your IP address, your browser's user-agent and its language header. FixedFloat requires partners to retain this and to produce it on request, and exchanges here are created through such providers, so it is kept for at least a year and can be disclosed to them. This is personal data and it is not anonymous.
Google Analytics runs on every page. It is a script from Google that loads in your browser, sets cookies to tell one visit from the next, and reports to Google which pages you viewed, roughly where you are, and what brought you here. It runs on the exchange page too. One event beyond page views is sent: pressing an “exchange this pair” button reports which page it was pressed on, and nothing else. No address, amount, exchange id or transaction hash is ever passed to Analytics. This site used to promise no tracking script of any kind and no longer can: that sentence was true until analytics was added, and leaving it there would have been the easiest lie on the site to catch. A content blocker stops it, and nothing here breaks when it is blocked.
Still not recorded by this site: no account, no email, no browser fingerprint. Demo runs are recorded, flagged as rehearsals: a demo writes the same row a real exchange does — amounts, fee, payout address, country, browser handle — without the IP address, user-agent or language header, and it is never counted as earnings. This page said demo runs created no record at all, which was wrong, and a page promising that every claim can be checked against the source is the worst place to leave one that cannot.
What necessarily reaches other people
The exchange provider receives your payout address, the amount and the currency pair. An exchange cannot be quoted or created without them, and the provider sees the timing of the leg it handles. SideShift also receives your IP address: it asks integrations to forward the payer's address so its own checks see you rather than this server, and exchanges made through it do so.
Block explorers and price data. Balance lookups, transaction broadcasts and price checks are made by this server rather than by your browser, so those services see the server rather than you. The explorers are blockstream.info and mempool.space; dollar figures come from the public ticker endpoints of Binance, KuCoin, Gate and MEXC, which are read without any account or key and are sent nothing about you.
A Bitcoin destination address is looked up. When the payout is in Bitcoin, the address you entered is sent to a block explorer to read its public history for the linkability read-out shown beneath it. That request is made by this server, which hides who is asking — it does not hide which address was asked about, and an explorer still learns that somebody looked. No other payout chain is looked up at all.
Importing from a recovery phrase checks a few hundred addresses in one go, which tells the lookup service that those addresses were asked about together — again from this server, not from your connection. The phrase never leaves your browser; only the addresses derived from it are looked up.
A webhook, only if you paste one. Exchange status, amounts and payout address are relayed to whatever address you chose.
What this cannot protect you from
The blockchain is public. Every transaction made through this site is permanently visible to anyone. Splitting a transfer makes it harder to reassemble; it does not make it invisible.
Providers keep their own records. What they log, and for how long, is theirs — not something this site controls or can promise anything about.
The hosting platform sees requests. Render, and Cloudflare in front of it, handle traffic to this site and log requests, including IP addresses. That is inherent to being hosted, and it is separate from the record this site now keeps itself: both exist, and neither is invisible.
Your own machine. Browser extensions can read what is on a page, including a private key you have typed into it. A compromised device defeats everything described above.
This is not an anonymity service, and anyone selling you one is worth distrusting. What it does is avoid adding to what already leaks.
Retention
Exchange records are held for fee accounting and for the retention the exchange providers require of partners: at least one year for the IP address, user-agent and language header attached to each exchange. Ask and they will be deleted, unless a provider has an open request for them. Browser storage — labels, your handle, notification settings — lives on your device and is removed whenever you clear this site's data. The copy of an exchange in progress lives in the tab's session storage and goes when the tab closes.
Messages sent through Contact us are kept until they are pushed out. There is no expiry: the five thousand most recent are held and the oldest drops off beyond that, which on current volume is indefinitely. Each one stores what you wrote, its kind and status, anything written back to you, the two-letter country, the random handle your browser carries, and the page you sent it from. It does not store your IP address. A way to reply is optional and never required — a complaint about privacy should not cost you an address to make. Ask, quoting your reference, and the message and its replies will be deleted.
Cookies
Google Analytics sets cookies — the _ga pair, which distinguishes one visitor from another and one visit from the next. They are read by Google, not by this site, and they are what makes the visit counts on the other side of them possible. Blocking them costs you nothing here.
There are no advertising cookies, and nothing is sold or passed to an ad network. The only cookies this site sets itself are for the administrator area, and only when someone signs into it: a session cookie, and a flag that stops Analytics loading in that browser so the owner is not counted as a visitor.
No account, no sign-up, and nothing is held here — your browser pays each provider directly.
Questions about any of this? The source is the authority — everything described here can be checked against it.