Slack calls security and privacy policies
Looking for details about the security of Slack’s built-in calling feature? You’re in the right place.
Tip: If you’re having connection, audio, or video issues with Slack calls, learn more about how to troubleshoot.
Slack calls security
We use the WebRTC standard for real-time communications with the latest recommended security techniques. Here's how we protect the integrity and confidentiality of a call:
- All traffic is encrypted in transit.
- Media traffic is encrypted with SRTP using a DTLS-SRTP key exchange.
- Real-time data channel traffic is encrypted with DTLS.
- HTTPS or secure WebSockets using TLS 1.2 are used for signaling communication with our media server.
Slack's voice and video calls fall under the same security program as the rest of Slack. For more information, visit our Security policy.
Information stored from Slack calls
We store certain information from Slack calls to help us improve the calling experience and troubleshoot issues:
- Stored call metadata includes the name of a call, where it was started (in a channel or a direct message), who started and participated, when members joined or left, and the time it ended.
- Stored performance metrics include latency and jitter.
- To provide media connections with the lowest possible latency or lag, the public and private IP addresses of a device may be shared with other devices while on the same call.
Note: It's not possible to record or transcribe Slack calls.