Privacy
There are no accounts on this site, so there is no profile to build. What follows is the complete list of what gets stored, taken from the code rather than from a template.
What we store when you claim a rank
A claim writes one row describing the listing and one row recording the terms you were shown. Between them they hold: the coin’s name, contract address and chain, the amount quoted, the season it was bought in and when that season closes, the browser user agent string, and a hash of your IP address.
The IP is stored as a SHA-256 hash truncated to 32 characters. The original address is never written to the database. The hash exists so a pattern of abuse can be recognised across claims, and it cannot be turned back into an address.
The record of what you were shown at the moment you accepted is kept because it is the evidence of what was agreed. If you later dispute a payment, that row is what says which price, which season and which terms were on screen.
What we store when you just look
Nothing, on our side. Reading the board or the race writes no row in our database.
We use Google Analytics to count visits and see which pages are read. It sets its own cookies in your browser and sends Google the page you are on, your browser and device type, and the request itself, which includes your IP address. We see those visits only as totals in Google’s reports. We run no advertising or tracking pixels. A browser setting or extension that blocks Google Analytics stops all of it, and the site works the same.
The race keeps two things in your own browser and never sends them anywhere: your sound and filter settings, and the live state of the current run so a reload does not reset what is on screen. Clearing site data removes both.
Payments
Payments are handled by a third party checkout. Card details, wallet addresses and everything else needed to move the money go to that processor and never reach this site. What comes back to us is a confirmation that an amount was paid against a listing, and that is what gets recorded.
Who else sees a request
- The hosting provider, which terminates the connection and keeps its own request logs.
- The database provider, which stores the rows described above.
- The payment processor, but only when you start a payment.
- Google, through Google Analytics, on every page you open.
- pump.fun, when a contract address is checked, and the public Solana or EVM node for that chain. This is how a listing is verified as a real token rather than trusted from a form.
- Public IPFS gateways, which serve coin artwork. Images are fetched by our server rather than by your browser, so those gateways do not see you.
How long it is kept
Listings, payments and the terms shown at purchase are kept indefinitely. Closed seasons are archived rather than deleted, which is the promise the board makes: a rank you paid for stays on the record permanently.
That permanence is the reason a claim is worth buying and it is also a real limit on deletion. A listing can be removed from view, and we will do that on request. The payment record behind it cannot be erased without falsifying the accounting that every rank on the site is computed from.
Your requests
You can ask what is stored against a listing, ask for a listing to be taken down, or ask for the user agent string on a disclosure row to be cleared. Reach us the same way you would to report a listing.