What it does not do
None of the following appears in this application’s source or its dependencies. This is a statement about code in a repository, and you can grep it.
- No analytics and no telemetry. There is no analytics package, no product-metrics SDK and no error-reporting service here.
- No cookies, and no browser storage. No page you can reach writes a cookie, and nothing reads or writes local or session storage.
- No account, no profile and no sign-in. There is nothing to register and nothing that identifies you between one page and the next. Your launches are found by asking the chain what your wallet created, which is a question anybody can ask.
- No middleware. Nothing intercepts a request before a page renders it.
- No fonts fetched at page load. The typefaces are downloaded when the site is built and served from this origin, so opening a page does not call a font host.
What it does do
Rendering a page reads from a few places, all server-side, and none of them receives anything about you beyond what the request needs:
- The chain, for what exists: every market on this launchpad is read from the registry contract, which is public and which anybody can read the same way.
- The indexer, over HTTP, for what a market has done — its price history, its volume and its trades. It is asked about markets, never about readers.
- The projects table, for the pages vetted teams have written about themselves. Read here and written only by the desk.
There is exactly one thing you can ask this site to store, and it is the one you type yourself: a report filed on Support. That writes a ticket — what you wrote, anything you attached, the page you were on, your browser’s user agent, and an email or handle only if you chose to give one. Nothing else records anything you did, and no page files one on your behalf.
On a page where you can trade, your browser also talks to the chain’s RPC endpoint and to whatever wallet you connect — both directly, not through this site. A wallet sees what you approve in its own dialog, and the RPC endpoint sees what any node sees.
What is enforced rather than promised
These are assertions in a test that runs on every change and fails the build. They are not policies that could quietly lapse:
- This application constructs no signer of its own, so it holds no key that could move anything of yours.
- It reads no private key, mnemonic or secret out of its environment.
- It hardcodes no address, hash, ticker or figure. Everything it shows is read at request time from the chain or the indexer, which is also why a figure it cannot read is shown as missing rather than as zero.
What this page cannot tell you
The repository records no operating entity and no jurisdiction, so this page names neither. There is an address to write to on Support, which tells you where a message goes and not who receives it.
Nor can it speak for whoever hosts the deployment you are reading. A host serves the request before this code sees it, and may keep logs of its own — addresses, times, user agents — under its own terms. That is outside this repository and outside anything described here.
What can go wrong with a market, and what nobody here is able to undo, is on Terms.