Privacy
What we keep, why, and how to have it changed or removed. Short, because we keep little.
Updated Nov 14, 2026
Visitors
Reading the site needs no account and sets no cookie. We run no analytics, ad or tracking scripts. We count how many times each token page is opened per day, as a number per token, with nothing about who opened it. To limit abuse, a request without a key is counted per minute and per day against a one-way hash of its IP address; those counts are deleted as their windows pass.
Your theme choice (light or dark) stays in your own browser’s storage and is never sent to us.
Accounts
An account keeps: a display name; if you sign in with GitHub, your GitHub id, login and the email GitHub shares; the public keys of your passkeys; your API keys as hashes, with their names and use counts; your watchlist; and your webhook address and secret if you set one. A signed-in session sets one cookie that is needed for the session to work, and nothing else.
We use this to run your account and API access, and to tell your webhook about tokens you watch. We don’t sell it or share it with anyone, and send you no marketing.
Logs
Each data API call is logged with the key’s public id, the path, the status and the time it took, to spot abuse and fix faults. Server logs are rotated and kept for a short time.
Addresses on the blockchain
Blockchain addresses and their balances are public. We show the largest holders of top tokens, the addresses public sources label as exchanges, market makers, funds or exploiters, and large holders nobody has labelled. We never try to find out who is behind an unlabelled address, never join it with anything off-chain, and keep pages of unlabelled addresses out of search engines.
If an address is yours and you object to it being shown, ask on the corrections page or write to us: we hide it from the site, the API and MCP, and keep only a note that it is hidden.
Who processes it
Our servers keep the data above. GitHub handles a GitHub sign-in. Telegram carries the alerts we send ourselves about the service, which hold no visitor data.
Your rights
You can delete your account yourself on the account page; that removes its keys, passkeys, watchlist and webhook. To ask what we keep about you or have it corrected, write to [email protected] from the email or GitHub account your account is tied to. Where data protection law gives you more rights, such as objecting or complaining to a regulator, you have them.
Changes
If what we keep changes, this page changes first, with its date.