SECURITY SPECIFICATION

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.

AES-256-GCM Authenticated Encryption·Argon2id (m=32MB, t=3, p=1)·Constant-Time Verification
07 / ARCHITECTURE

Security is an architecture, not a badge.

We enforce mathematical boundaries across six independent layers. Click any layer to inspect its formal specifications.

LAYER 01 SPECIFICATIONIDENTITY

Local Client Entropy

Entropy is drawn from device hardware random number generators to create unique cryptographic salts and nonces.

Cryptographic Primitive / Standard
CSPRNG + WebCrypto SubtleCrypto
Security Guarantee
Zero entropy predictability across room sessions.
VERIFIED PROTOCOLAUDITED MODEL
08 / TECHNICAL HONESTY

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.

Boundary 01

Physical Photography & Display Recording

An external optical camera aimed at a physical display cannot be prevented mathematically.

Boundary 02

Operating System Screenshots

If a user captures their OS window buffer before room dissolution, cryptography cannot retroactively wipe that file.

Boundary 03

Manual Transcription & Copying

An authorized participant in the conversation can intentionally copy or transcribe text prior to departing.

Boundary 04

Malicious Extensions & Endpoint Malware

If a device is infected with browser extension keyloggers or OS trojans, encryption secures the network, not the compromised machine.

Privacy is strongest when endpoints are trustworthy.
Cryptographic tools defend the wire and the courier. Human discretion safeguards the room.
FORMAL THREAT BOUNDARY

Ready to initialize a private chamber?

Zero logs. Out-of-band pass separation. Instant dissolution.