Privacy

What this software does with a request. Read what it is not before you read the rest.

This is not a legal privacy policy. It does not name a data controller, give a contact address, or state a governing law, because none of those exists in the repository this site is built from. It describes the behaviour of the code, which you can check.

What it does not do

None of the following appears in this application's source or its dependencies. This is a statement about the code in the 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 in this application.
  • No cookies, and no browser storage. Nothing here 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.
  • No middleware. Nothing intercepts a request before a page renders it.
  • No fonts fetched at page load. The two typefaces are downloaded when the site is built and served from the same origin, so opening a page does not call a font host.

What it does do

Rendering a page reads from two places, both server-side, and neither receives anything about you beyond what the request needs:

  • The program registry, a database this deployment is configured with. It is read and never written; the write functions its client library offers are not imported here.
  • The indexer, over HTTP, asked about a specific market by its token address when a market page needs to check that market against the chain.

On a page where you can trade, your browser also talks to the chain's public RPC endpoint and to whatever wallet you choose to 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

Four of 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.
  • It reads no private key, mnemonic or secret out of its environment.
  • It exposes no route that writes and declares no server action, so there is no path by which it acts on your behalf or records anything you did.
  • It hardcodes no address, hash, ticker or figure. Everything it shows is read at request time from the registry or the indexer.

What this page cannot tell you

The repository records no operating entity, no contact address and no jurisdiction, so this page names none of them.

Nor can it speak for whoever is hosting 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.