Almost nothing 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 itself polls a block height off the public RPC. If sign-in has been loaded — you are signed in, or you reached for the Sign in button — Privy's own requests appear beside it. Your keystrokes appear in no request body, ours or theirs.

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.

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. Those three are Signet's own, are read and written by this tab and are never sent anywhere. Sign-in and wallet connections keep storage of their own when you use them, described under Sign-in below.

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.

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.

Sign in is run by Privy, a third party. Its code is not loaded until something asks for it: opening the seal page, pointing at, tabbing to or pressing the Sign in button, or a Privy session already stored in this browser. Once loaded it stays for the rest of the visit.

Whatever you sign in with goes to Privy, not to us. With an email address, Privy receives the address. With a wallet, it receives the wallet address and a signed sign-in message, and opens an account against that address. Privy keeps your session in this browser's storage under keys that start with privy:, and reports its own usage events to its own servers.

If you choose a wallet in Privy's window, your browser fetches the wallet list from WalletConnect, and connecting a phone wallet or Coinbase Wallet goes through their relays and keeps their session data in this browser. Those services see your IP address, the same as any site you visit. None of it carries the content you seal.

Signet adds no analytics script, no tag manager, no session recorder, no advertising pixel and no cookie of its own. The only third party code the site loads is sign-in, above, and only when it is asked for. Fonts are served from the same origin by the framework, so no font CDN is contacted on your behalf.