Privacy notice

01

Draft status

This notice describes what the site and its operator actually process today. The legal controller, privacy contact and a rights-request process are not yet published.

02

Your wallet and keys

The site asks your wallet for its address and one signature. Your shielded keys are derived from that signature in your browser and kept in memory only; they are never sent to the operator or stored on a server. The site never asks for a private key or seed phrase.

Your wallet address is public on chain whenever it sends a transaction, such as a deposit, a token withdrawal, a reclaim or a ragequit.

03

What the operator sees

Orders are sealed to the operator’s clearing key, so the operator can read each order’s side, size and limit before the call. Balances and fills are sealed to your own viewing key; the operator does not learn them from the chain.

When the relayer submits a transaction or order for you, it receives the proof and the transaction data, which become public on chain, and keeps a record of the transaction hash. RFQ messages pass through the operator’s mailbox sealed to the counterparty’s session key; the operator stores the ciphertext until it expires.

04

Sanctions screening

Depositor wallet addresses, which are public on chain, are checked against Chainalysis’s sanctions screening service. The operator keeps each result and re-checks it daily. A deposit that is not cleared is left out of the association set; its depositor can still take it back with a ragequit.

05

Browser storage

The site caches public pool data (the note tree and pool events) in IndexedDB so later visits load faster. It holds nothing secret. The luminary_language local storage preference remembers your language, and the sidebar_state cookie remembers navigation preferences for up to seven days. Clearing site data removes all of it.

06

Hosting and third parties

The site and its API are hosted on Vercel and its database on Supabase; they process technical connection information, such as IP addresses and request metadata, under their own policies. The site adds no advertising pixels or marketing analytics.

The hero loads a Sketchfab viewer and its JavaScript to display the animated Chinese dragon, which can expose technical information to Sketchfab. The embed requests Sketchfab’s do-not-track option; that setting is not a promise that no provider data processing occurs. You can block third-party content in your browser, although the scene may then be unavailable.

07

Disclosure to an auditor

If you choose to disclose your account, your viewing material (never your spending secret) is sealed to the auditor’s key and published on chain. The auditor can then read every note, order and result of your account; this cannot be undone.