How it works
Built on mediasoup, a Selective Forwarding Unit. The server relays your audio and video to other people in the room — it does not record, inspect, or process your calls. All media is encrypted end-to-hop with SRTP and DTLS.
Make the privacy choices that are right for you. Learn how to manage and control your data on SomaTalk SFU.
Get answers to your privacy questions in plain language.
Built on mediasoup, a Selective Forwarding Unit. The server relays your audio and video to other people in the room — it does not record, inspect, or process your calls. All media is encrypted end-to-hop with SRTP and DTLS.
When you hit "Record", the file is created in your browser (as a Blob) and downloaded to your device. It is never uploaded to our servers. Server-side recording is disabled by default.
Everything is ephemeral. Display names, chat messages, and session data only exist while the room is active — once it ends, they're gone. We don't record calls, ask for payment info, or collect sensitive personal data.
We use Umami, a privacy-friendly analytics tool with no cookies and no PII. GDPR, CCPA, and PECR compliant. Small bits of data (display name, room prefs) may live in your browser — purely functional.
Server logs are streamed to the console and not stored on disk; only error-level logs are on by default. Chat and session data disappear when the room ends unless the host has set up persistence.
SRTP/DTLS for media, TLS/HTTPS for traffic, hardened infrastructure. No system is bulletproof — if you spot a vulnerability, please let us know.
SomaTalk may connect to RTMP endpoints, CDNs, or other APIs. Each has its own privacy policy — please review theirs. We're not responsible for how third parties handle data on their end.
Open-source — anyone can host their own instance; if you use someone else's, they are responsible for privacy. We may update this policy; the "Last updated" date will reflect changes.
By continuing you accept the policy above.