Skip to content
Browse documentation

Know the boundary of privacy.

A shielded pool protects payment details, but it does not make every interaction invisible.

Public and private data

Deposits expose the depositing wallet, asset, and amount. Private notes conceal individual balances and transfer values behind commitments and proofs. Cash outs expose the destination, asset, and amount. Transaction timing and pool interactions remain observable.

What stays on your device

Note secrets and receive keys are stored encrypted in the browser. Opening the store uses a wallet signature locally. Proofs are generated on your device; the relay receives transaction data to submit rather than the secret note keys.

What the relay changes

A relay can submit a private operation without your wallet submitting that transaction directly. That reduces one direct on-chain link. The relay and network providers may still observe connection metadata such as IP addresses and request timing.

Correlation and shared identifiers

Matching deposit and withdrawal amounts, close timing, a small pool, reused public destinations, and publishing your account number can weaken privacy. Sharing a claim link also shares the authority to claim its payment.

What Mirk cannot protect

A compromised browser, malicious extension, infected device, or someone with access to an unlocked store can expose private data. Encryption at rest does not protect secrets while malicious code can read the open app. See Security and limitations for the broader threat model.