Security Architecture &
Cryptographic Threat Model
ENCLAVE uses standard W3C Web Cryptography primitives to enforce a zero-knowledge, zero-persistence model. We publish our mathematical assumptions, cryptographic standards, and formal boundaries.
Security is an architecture, not a badge.
We enforce mathematical boundaries across six independent layers. Click any layer to inspect its formal specifications.
Local Client Entropy
Entropy is drawn from device hardware random number generators to create unique cryptographic salts and nonces.
Security has boundaries.
ENCLAVE protects communication in transit and while stored within the system according to its cryptographic design. We do not make impossible promises about physical endpoint security.
Physical Photography & Display Recording
An external optical camera aimed at a physical display cannot be prevented mathematically.
Operating System Screenshots
If a user captures their OS window buffer before room dissolution, cryptography cannot retroactively wipe that file.
Manual Transcription & Copying
An authorized participant in the conversation can intentionally copy or transcribe text prior to departing.
Malicious Extensions & Endpoint Malware
If a device is infected with browser extension keyloggers or OS trojans, encryption secures the network, not the compromised machine.
Ready to initialize a private chamber?
Zero logs. Out-of-band pass separation. Instant dissolution.