Privacy policy
Draft for counsel review. Not in force.
We log no wallet address, IP or request body. Worker logs and log export are off, and no analytics event carries an address.
Calls to a data vendor that need your address go through our Worker, so the vendor sees our IP and not yours. Most carry the address in the request body. Two carry it in the web address: the 0x quote, as the taker, and the list of your open Jupiter orders. Those two vendors can read it there.
Your history and results stay in your browser. Our server keeps no record per person. Clearing this site’s data removes them.
Besides your history, this device keeps only your theme, your language, your last chain tab, the quick buy size you pick, the alerts you set, the filters you apply on each chain tab, the Discover views you save, the referral handle of the link you came by, your own partner handle once you make a partner link, the tokens you star, the limit and stop loss orders you set, the receipt book of your trades, the smart account notices you have seen and your demo mode choice and its simulated wallet and your first trade review choice and the tokens you opened last and whether the ticket details are open and your slippage setting and your Solana send speed and your Snipe mode choice and buy presets and your key settings and your warning lines, rebound keys, text size and first visit notice choice and the days you visited this week and two flags and the day each of six steps was last counted and the name of the wallet you connected last, never its address (D-75, D-85). None of it leaves this device, except the referral handle, which goes with each sign in so our server can name the partner in your trades (D-83), and your own partner handle, which is checked against its public record on our server before a link you copy carries it (D-143). During a sign in that leaves this page and comes back, this tab also keeps a one time code for that sign in, sent once to finish it and removed when you return (D-86).
The notify list takes an email only, on a page that knows no wallet. It keeps the address, the day it arrived and the version of the list’s wording. It also keeps the partner code you joined by, if any, so the launch email can carry your discount. The list and every export of it are deleted 30 days after the launch email is sent.
Only aggregate counts leave your browser, with no address field.
Cloudflare runs our server and holds the notify list. It processes requests on its network in many countries. Every request to us passes through its network, your IP address and any wallet address in the request body included. It also runs the human check shown before sign in and a public DNS lookup our server uses.
Helius reads a wallet’s public history for us after you sign in with that wallet. Where it processes is not confirmed yet. Its policy says it keeps request details, such as IP addresses and method calls, for up to 20 weeks and uses them for analytics and to improve its product. The IP address it sees is our server’s, not yours. When you send a Solana transaction from this browser, the browser may send it to Helius directly, and then Helius sees your IP. With the Fast or Snipe send speed, the browser sends it to Helius Sender first, and then Helius Sender sees your IP too.
Mobula gives us token prices and token data. We ask it about tokens only, never about a wallet. Where it processes is not confirmed yet.
Jupiter, 0x, KyberSwap and 1inch give us quotes, swap builds and limit orders. Our server sends them the address you trade from, so they see our IP and not yours. They are asked only for the ticket or order you open. Where each one processes is not confirmed yet.
Public chain nodes answer our reads and simulations: PublicNode, dRPC, BNB Chain, Base, Robinhood Chain, Arc and ethpandaops, and the Solana Foundation as a Solana fallback. Our server sends them the address you trade from, so they see our IP and not yours. If the first Solana send endpoint fails, your browser may send your signed transaction to the Solana Foundation directly, and then it sees your IP. Where each one processes is not confirmed yet.
On XRPL, Ripple runs the public test nodes our server reads, and Xaman handles sign in when you pick it. Ripple sees our IP. Xaman sees your IP and your XRPL address, because your browser talks to it directly. Where each one processes is not confirmed yet.
Telegram carries our own alerts about our systems. They carry no wallet address and no request body. Where it processes is not confirmed yet.
To ask what we hold about you, or to have it corrected or deleted, write to the contact in the block below. We hold your email if you joined the notify list, and your handle and addresses if you made a partner link. If you came by a partner link, we keep a keyed hash of your wallet with the handle it first signed in with, never the address, so a wallet binds to one link.
Token images come from the host a token’s own metadata names. Our server fetches them, so that host sees our IP and not yours, and it is sent no wallet address. It can be any host on the internet, so we do not name it.
Jito publishes the tips that recent Solana transactions paid to land. Our server reads those figures and sends Jito nothing but the request, never a wallet address, so Jito sees our IP and not yours. Where it processes is not confirmed yet.
To count returning visitors, this device keeps the UTC days you opened the terminal this week and two flags, never an id. It sends at most two counts a week, each a bare request with no body, and none when Global Privacy Control or Do Not Track is on.
When you sign in, our server sets one cookie on this browser. It lasts 24 hours from your signature and is never extended. It only shows you as signed in with that wallet: it cannot sign, trade or move anything, as every trade is still your wallet’s own signature. It ends when you disconnect, switch account or sign out. For Sign out everywhere, our server keeps a keyed hash of your address with a number, never the address itself.
Who is accountable
The identification block is pending: the business name, the accountable role, the contact email and the mailing address are not published yet.