Privacy

Last updated 9 September 2026

What we see

When you scan, the address you enter is sent to our read-only chain proxy and the tickers it holds are sent to our price endpoint. Public blockchain addresses are already public; we do not link them to any identity.

When you clear a position, nothing about it is sent anywhere by us. The price comes from the liquidity pool through the same read-only proxy, the amount you will accept is worked out in your browser, and the transaction goes from your wallet straight to the network. Until 9 September 2026 this step sent your address and your amounts to a third-party swap aggregator, because the sale went through one. It no longer does.

What we keep

No accounts, and nothing at all is written to your device: no cookies, no local storage, no identifier of any kind. That is also why there is no cookie banner. There is nothing to consent to.

We do count how far people get, because otherwise we cannot tell which part of this page is failing them. The counting happens on our own servers, not through anybody else's analytics script, and the entire record is one number per day for each of these: the page was opened, a scan finished, a scan found nothing, a scan was run again, a wallet was connected, the clear button was pressed, a position cleared, the price feed was asked again.

Each of those is counted at most once per visit, so the numbers say how many visits reached a step rather than how many times a button was pressed. The list of what has already happened in this visit lives in the page's memory and is gone when the tab closes; nothing is written to your device, which is also why this site has no cookie banner. There is nothing to consent to.

A scan also records which of five bands the stranded total fell into (nothing, under $5, $5 to $20, $20 to $100, over $100). That is how we tell whether the people arriving are holding anything this tool can help with. The exact figure is never sent; a band is far too coarse to say anything about one wallet.

Two more numbers come with a page view, both grouped so that neither can become a record of a person: which country our hosting provider says the request came from, and which of a fixed handful of places you arrived from (a link on X, Telegram, Reddit, Google, Discord, GitHub, somewhere else, or no referrer at all). The address of the page you came from is turned into one of those words in your browser and never sent to us.

If you arrived through a link carrying a partner code (?ref= in the address), that code is counted with the page view, and again if a position clears, so we can tell whether a partner sends people this tool can help. Only codes we have configured in advance are counted; anything else is ignored. The code says something about the link, not about you.

If you hand out an invite link, the address in that link is stored when somebody clears a position through it, along with what they were charged, because that is the record of what we owe you. It is an address you chose to publish in order to be paid, and it is the only address this site keeps. The address of the person who cleared is not stored, and nothing connects the two. Nobody who simply opens an invite link is recorded at all; only a clear writes anything down.

What we do not have: the wallet address you scanned or cleared from, your IP address, your browser or device details, and any way to tell two visitors apart or to connect one visitor's two visits. Testnet visits are not counted at all.

The daily totals are kept indefinitely, because a figure from last month is what makes this month readable. There is nothing in them to delete on request: they are counts of visits, and no row of them describes a person.

Our hosting provider records ordinary server logs (request paths, timestamps, IP addresses) for a limited period as part of running the service. If any of this changes, this page changes first.

Third parties

• Robinhood Chain public RPC nodes and Blockscout, for balances, pool prices and network data. Requests reach them through our proxy, so they see our server rather than you.
• Robinhood's public price API, for the official price of the tickers you hold.
• Cloudflare, which hosts this site and serves every request to it.
• Public spot price endpoints (Coinbase, CoinGecko), for the ether price used to estimate the network fee. They are asked for one number and are told nothing about you.

A third-party swap aggregator was on this list until 9 September 2026. The sale no longer goes through one, so it is no longer asked anything.

Typefaces are served from this site. No font, script, or analytics request goes to any other company, and the page's security policy blocks any attempt to load one. This is not only a privacy position: a page that asks you to sign transactions should not be running code fetched from somebody else's server.

Each has its own privacy terms. Your wallet software has its own as well; we never see your keys or your seed phrase, and we never ask for them.

Your rights

Data protection law gives you rights over personal data held about you. We hold almost none: no account, no identifier, no IP, and nothing on your device. The single exception is a payout address you published yourself by handing out an invite link, which we keep so that we can pay you and will remove on request. Otherwise there is nothing here to hand over, correct or erase, and we could not find your visit among the daily totals if you asked us to. If you want your server-log entries handled, that is a request for Cloudflare, whose logs those are.

Contact

Anything about this page, or about privacy generally, goes to the contact in security.txt.