How ENCLAVE Works:
From Genesis to Obliteration
Discover the precise architectural journey that separates ENCLAVE from traditional permanent chat platforms. Seven distinct phases guarantee absolute confidentiality from inception to destruction.
CREATE
The creator initiates an ephemeral room. The room salt and initial state are generated client-side using cryptographic entropy.
SHARE
The room link and access pass are generated as two distinct factors and must be sent through separate communication channels.
JOIN
A participant opens the room link and enters the access pass provided out-of-band.
ESTABLISH
The client verifies the Auth Commitment with the relay and unwraps the Room Master Secret locally in memory.
TALK
Messages are encrypted before leaving the device. The server routes opaque binary frames blindly.
LEAVE
When a user departs, key material is zeroized in memory and departure packets notify remaining sockets.
DESTROY
When the final participant disconnects or leaves, the room is permanently retired and cannot be revived.
A link isn't enough.
Conventional chat applications bundle access directly into a single URL. If that link is stored in browser history, scraped by preview crawlers, or intercepted on a clipboard, the conversation is exposed.
Every ENCLAVE room requires an independent access pass.
The pass is never included in the URL. This requires two independent pieces of information sent across two separate communication mediums.
The access pass is never included in query parameters (?pass=...), URL paths, or server access logs.
Both independent factors are required to derive session keys on the client.
Every room has an ending.
When the final participant leaves, the room enters its definitive dissolution sequence. Key handles are wiped and the chamber ceases to exist.
ACTIVE
Participants present. End-to-end encrypted session active in RAM.
ENDING
First participant leaves. Departure protocol armed.
DESTROYING
Final participant leaves. Zeroization protocol triggers.
DESTROYED
Room obliterated. Non-recoverable tombstone status.
When the final participant leaves, the room URL becomes inactive. No administrator or participant can revive, reconstruct, or view past ciphertexts.
ENCLAVE treats human conversation like spoken dialogue: temporary, contextual, and gone once the conversation concludes.
Experience it yourself
Create a room, share the pass, and observe the ephemeral destruction lifecycle in real time.