Privacy
Policy.

1. This website

The marketing pages set no cookies, run no analytics and load no third-party trackers. The fonts are served from this domain, so no other company sees that you visited. If you email us, we keep the email to reply to you and for no other purpose.

If you reserve a handle, we store the name you asked for, the X username you gave us and, if you filled it in, the wallet address that will claim it. The name appears on the public board; the X username and the wallet do not.

2. What the app stores on our servers

The app at signetpay.xyz/app is not a static page and this section is the honest account of what it keeps. Signing in sets one cookie, signetpay_session: it holds your wallet address, is signed so it cannot be edited, is not readable by scripts and expires after seven days. There is no other cookie and no analytics in the app either.

Your account record holds your wallet address, your handle, the stealth meta-address you publish so people can pay you, the display name, bio and link you choose to fill in, and when you first and last signed in.

If you join a product waitlist, we store the wallet that joined, which product and when. Nothing else — there is no email and no name unless you have filled one into your profile.

Payment requests are stored as you write them: both wallets and handles, the amount, the memo and whether the request is open, paid, declined or cancelled. A request has two sides, so it cannot be encrypted to one of them; it is readable by us. It is not on the chain, which is what keeps it off a block explorer, but it is not encrypted the way your balances are.

Your payroll roster is not in that list. The names, recipients and amounts you enter, and the record of each run, are encrypted in your browser and stored as a blob we cannot open — which is why the payroll page asks for your keys before it shows you anyone.

Your balances, positions, cost basis and memos are a different matter: they live in a blob encrypted in your browser with a key derived from your wallet signature. We store the blob and cannot open it.

The app reads the chain through our own proxy, so a public node sees our server's address rather than yours.

3. What the product is built never to see

Balances, positions, cost basis and transaction memos are encrypted notes. They are decrypted in your browser with your own key. Our servers never hold your positions, your portfolio dashboard or your tax export in plain text.

Signetpay performs no identity checks, and no fiat ramp or card is connected to it. If one is added, those checks will be performed by the licensed partner, and we still will not store the link between a KYC record and on-chain activity.

4. What we do process

Screening results for shield and unshield transactions, so the pool stays clean and we can meet legal obligations. Operational data needed to run relayers, paymasters and the API, such as request logs and error reports. Business account details for companies that buy seats.

5. Disclosure you control

A viewing key you issue lets its holder recognise every payment you receive, and never spend one. It is not limited to a date range and it does not expire: giving one away is a disclosure you cannot take back from that holder, so share it only with someone you would trust with the whole picture. Scoping and expiry are planned. We never issue viewing keys on your behalf and hold no master key.

6. Legal requests

We comply with valid legal process. Because notes are encrypted client-side, what we can produce is limited to what sections 2 and 4 describe.

7. Changes and contact

We may update this policy. The version on this page applies. Privacy questions go to hello@signetpay.xyz.