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, keys are generated entirely in-memory on your local device using PBKDF2-SHA256 (100,000 iterations) with optional room secrets.

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

Files and chat payloads sent within the session are encrypted with AES-256-GCM. The signaling server routes ciphertext only and has no ability to decrypt payloads.