Security
Built for private payments, checked in layers.
Kloak is designed around private settlement, selective disclosure, and clearer verification. This page explains the practical model rather than promising magic.
Owned by
Kloak security and product team
Last updated
April 10, 2026
What this page is for
Use this page to understand how Kloak handles verification, encrypted stored secrets, and what kinds of issues should be reported.
How verification works
Kloak now verifies shared proofs in layers: the proof package itself, public Aleo chain references, and Kloak record status when available. Public-chain checks are treated as the primary confidence signal.
How secrets are handled
Webhook secrets and stored proof payloads are encrypted at rest. Hidden payment facts needed for selective disclosure stay tied to wallet-held receipts rather than being treated as general backend data.
What to report
Please report bugs that expose payment history, bypass access checks, break proof revocation, or create mismatches between wallet-held receipts and Kloak records.