Zero Source-Code Retention
OutSync does not store your code in permanent databases. All room edits are synchronized using ephemeral in-memory CRDT structures that vanish once the room session terminates.
Security Architecture
Built from the Ground Up for Privacy & Security
Understand how OutSync protects proprietary source code, encrypts voice streams, and maintains an ephemeral zero-log infrastructure.
Direct Peer-to-Peer Voice Mesh
Voice audio streams travel directly between collaborator browsers via WebRTC with DTLS-SRTP end-to-end encryption. No audio packets are recorded, stored, or processed on our servers.
Isolated Execution Sandboxes
Code execution requests run in isolated, disposable containerized environments with restricted network access, strictly enforced CPU/memory limits, and automatic timeout kills.
Zero Account & Zero Tracking Policy
No registration, user accounts, password hashes, or behavioral tracking cookies. OutSync operates with 100% anonymous, permission-free access.
Security & Architecture Facts
Is code stored on disk after I close the tab?
No. Room states exist strictly in ephemeral server memory to facilitate delta synchronization. Once all participants leave and the room expires, the memory state is permanently garbage collected.
Are WebRTC voice calls recorded?
No. Voice audio is transmitted peer-to-peer over DTLS-SRTP encrypted WebRTC media channels. Our servers only facilitate the initial SDP signaling handshake and STUN/TURN traversal.
How are room IDs generated?
Room IDs use cryptographically secure random identifiers or optional custom vanity tokens to prevent unauthorized room scanning.