Almost nothing reaches us.
The short version: the pages do their work in your browser, one route accepts a hash, and nothing is stored on our side. The long version is below, and every claim in it can be checked with the developer tools you already have.
What never reaches us
Anything you type into the home page, the sealer or the verifier stays in your browser. Those pages hash and check locally, and the result of that work is a string on your screen, not a request to a server.
You can check that instead of believing it. Open the network panel, type into the box on the home page, and read the requests: the page polls a block height off the public RPC and sends nothing else. Your keystrokes appear in no request body.
What the notary receives
If you press the notary button, your browser sends a SHA-256 digest, a byte count, an optional label you wrote, and the head of your previous receipt. It signs those and answers. The content behind the digest is not in the request and cannot be recovered from it.
The route holds nothing. There is no database on this deployment, so the request is answered and forgotten.
What your browser keeps
Your ledger lives in this browser's local storage, under one key. Clearing site data erases it and no copy survives anywhere else, including with us. Two smaller keys sit beside it: the wallet you last connected, so a reload does not make you pick again, and anything you typed into the box on the home page before pressing Seal it, so the sealer opens with it already there. All three are read and written by this tab and are never sent anywhere.
Wallets
Connecting a wallet exposes your address to this page, the same as any site you connect to. Signing a receipt is an EIP-191 message signature: it is never broadcast, spends no gas and moves nothing.
Your address appears inside the receipt you signed, because a receipt naming no signer would be worthless. That receipt only goes where you send it.
The chain
Live block numbers come from the public RPC for chain 4663, requested by your browser. That endpoint is operated by someone else and sees your IP address, the same as any site you visit. Signet does not proxy those requests, so we never see them either.
Analytics and third parties
There is no analytics script, no tag manager, no session recorder, no advertising pixel and no cookie set by this site. Fonts are served from the same origin by the framework, so no font CDN is contacted on your behalf.
Hosting produces its own request logs, which sit with the host and not with us. The hashing and the signature check still happen on your machine either way, so those logs record that you loaded a page and never what you put in it. See the trust page for the rest of the limits.
Last changed 15 September 2026