Nothing is asked of you

No account, no email, no documents. Here is exactly what that covers and what it does not.

There is no sign-up, because there is nothing to sign up to. The note is generated in your browser, the deposit is a transaction you send yourself, and the withdrawal proof is built on your own machine. Nowhere in that sequence does the service need your identity, and there is no field to put it in if you offered.

What a request to this site contains

The useful question is not what we promise not to collect, but what physically leaves your machine. Loading a page sends an HTTP request — your IP address and a user agent, as with every website in existence. Fetching the leaf set asks for public chain data. Submitting a withdrawal sends a proof and a destination address. Your nullifier, your secret and your note are in none of it, and you can confirm that yourself in the browser's network tab.

The one request that does not go to this domain

Google Analytics is loaded on these pages. It is worth naming the price rather than tucking it into a policy: Google is sent your IP address and the time of your visit, and on a mixer, visit times sit close to deposit times. IP anonymisation is switched on, which truncates the address before Google stores it — that is a reduction, not a cure, because the request still reaches them. Nothing about your note, your amount, your pool or your destination is ever passed to it. If that trade is wrong for your threat model, Tor or a VPN is the answer, and it is a better answer than anything a website could promise you.

What is absent

• Accounts of any kind — no email, no username, no password, nothing to reset.
• Identity documents, at any stage, for any amount.
• A wallet connection to withdraw. The relayer submits, so the destination stays untouched until the SOL lands in it.
• Third-party fonts and CDNs. The analytics tag above is the only external script on the site, which is why it is named here instead of being left off the list.

What no amount of design can hide

Both your transactions are on a public ledger and will stay there. The claim is that they cannot be joined — not that they vanish. And the site runs on a server, which sees request IPs the way all servers do. If your threat model includes that, route through Tor or a VPN; it is not something a web page can fix on your behalf, and any mixer swearing it keeps no logs at all is asking you to believe something unfalsifiable.

What the operator sees, precisely

Deposits pause in a holding wallet before they enter a pool, so that a deposit can be refused and returned. During that window the operator sees the transfer and the address it came from. Once the deposit is in, the zero-knowledge withdrawal conceals which note belongs to whom from everybody, operator included. The residual exposure is a thin pool, and it is expressed as a number on the pool picker rather than as a reassurance.