How SRIFT Session Creation and End-to-End Encryption Works

Creating a session on SRIFT initiates a decentralized, peer-to-peer room where you act as the host. A unique 7-character session identifier is allocated on the signaling server, but encryption keys are never sent to the server. Instead, every participant's device generates its own keys (ECDH P-256 with HKDF-SHA256) and shares only the public half, so the server relays ciphertext it can never read.

Host Approval and Access Control

When peers request to join your session, you receive an instantaneous cryptographic handshake request. As the host, you have unilateral authority to approve (srift_approve_join), reject (srift_reject_join), or kick (srift_kick_user) participants.

Zero-Retention Security Proof

Chat and audio go directly between participants' browsers, and files take the fastest path available. Everything is end-to-end encrypted under keys generated on each device (WebRTC's DTLS on direct links, AES-256-GCM on anything the server relays), and the server stores no files, chat or audio.