Looking for details about the security of Slack's voice and video features? You’re in the right place! 

Tip: if you’re having connection, audio or video issues with Slack Calls, click here to begin troubleshooting.

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 signalling communication with our media server.

Additional information

Recordings or transcriptions of calls are not recorded or stored in Slack.

We do store some metadata from a call, including the name of a call, where a call was started (channel or direct message), who started and participated in a call, the time a call ends and when members join or leave a call.

General performance metrics, e.g. latency and jitter, are also stored to help us improve the voice and video call experience. 

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: Slack’s voice and video calls fall under the same security programme as the rest of Slack. For more information, visit our security policy.

Tip: If you have any questions about security or making calls in Slack, send us a message. We’d love to hear from you!