# Security for Slack huddles

Looking for details about the security of [Slack huddles](https://slack.com/help/articles/4402059015315-Use-huddles-in-Slack)? 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 signaling communication with our media server.

**Note:** Huddles fall under the same security program as the rest of Slack. For more information, visit our [Trust Center](https://slack.com/trust).

## 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 and participated, when members joined or left, the topic (if one was added), 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 huddle.

**Awesome!**

Thanks so much for your feedback!

If you’d like a member of our support team to respond to you, please send a note to [feedback@slack.com](mailto:feedback@slack.com).