What "encrypted calls" actually means

"Encrypted" appears on almost every communications product. Here is what it means for GT Connect, in plain language, including the parts it does not cover.

How a browser call travels

GT Connect uses WebRTC, the calling technology built into modern browsers. When you call a colleague, the two browsers first exchange a small amount of setup information through our signalling service. Then the audio and video travel directly between the two devices whenever the network allows it.

What DTLS-SRTP does

WebRTC requires media to be encrypted. The browsers agree on keys using DTLS (a cousin of the TLS that protects websites) and then encrypt the audio and video with SRTP. Someone who intercepts the traffic on the network sees scrambled data.

What about relays?

On strict networks, calls may pass through a relay server (TURN). The relay forwards encrypted packets; it does not have the keys to decrypt the media.

What encryption does not cover

• Your devices. If a phone or computer is compromised, encryption in transit cannot help. Keep devices updated and locked.
• Who is on the call. Encryption protects the content, not the fact that a call happened. Call history on your device records that.
• Group calls today. Each participant connects to each other participant, and each of those connections is encrypted in the same way.

What we do not claim

We do not currently hold security certifications such as SOC 2 or ISO 27001, and we do not claim end-to-end encryption for features that are not built yet, such as server-side recording. When those features arrive, we will explain clearly how they work. See our Trust center for the current details.