Security for Slack huddles (2024)

Supplemental Slack info for you and your team.

Security for Slack huddles

Looking for details about the security of Slack huddles? You’re in the right place.

Huddles security

We use the WebRTC standard for real-time communications with the latest recommended security techniques. Here's how we protect huddle integrity and confidentiality:

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.

Huddles fall under the same security programme as the rest of Slack. For more information, visit our Trust Centre.

Information stored from huddles

We store certain information about huddles to help us improve the experience and troubleshoot issues:

Stored huddle metadata includes where the huddle was started (in a channel or in a direct message), who started it and participated, when members joined or left, the topic (if one was added) and the time that 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 huddle.

Note: It’s not possible to record huddles, and transcriptions are not stored by Slack or Amazon Web Services (AWS).

Nice one!

Thanks a lot for your feedback!

If you’d like a member of our support team to respond to you, please send a message to feedback@slack.com.

Got it!

If you’d like a member of our support team to respond to you, please send a message to feedback@slack.com.

Whoops! We’re having some problems. Please try again later.

Security for Slack huddles (2024)

Huddles security

Information stored from huddles

IN THIS ARTICLE