THE PRIVACY MODEL
Know the boundaries.
Privacy-maximizing. Metadata-minimizing. Never a promise of absolute anonymity.
Use Tor. Start fresh.
zkAPI hides the link between payment and usage. It does not provide network anonymity. The inference endpoint can see your IP on a direct connection and may correlate sessions by timing.
Use Tor Browser and the operator’s verified onion address. Start a fresh circuit for each session using Tor Browser’s circuit controls. A new identity also closes tabs and clears browser state. No onion address has been configured for this preview. This app does not detect or certify your Tor connection.
Two separate paths
| Party | Learns | Designed not to learn |
|---|---|---|
| Money / auth service | Valid payment and session spend | Prompt content or which deposit paid |
| Inference edge | Prompts and responses in memory | Billing identity |
| Ethereum | Deposits, closes, withdrawals | What a private balance paid for |
This separation depends on runtime-key mode and the deployment’s operational controls. Proxy mode would expose content to the payment relay and is not used here.
What this browser keeps
Conversations and runtime keys live in React state. Refreshing the page clears them. No prompts go into localStorage, IndexedDB, cookies, URLs, or analytics. Standalone mode sends only your current message to the edge.
The zkAPI SDK separately persists private wallet material for recovery. It does not receive conversation content. Clearing chat is not a guarantee of secure erasure from browser memory or the operating system.
Gated access has trade-offs
Standard wallet verification (SIWE) links an address to access. Anonymous Semaphore proofs avoid disclosing the holder address, but snapshots can become stale. Neither method removes funding links created by an exchange or timing correlation. Holder verification is not active in this preview.
Before you fund a wallet
zkAPI is experimental and the specified circuit uses a single-party Groth16 setup. Proof artifacts must match the vault’s immutable verifier. Deposits and withdrawals are public transactions. A configured deployment must preserve on-chain close, withdrawal, and escape paths even if its operator disappears.
> open terminal