End-to-end encryption
What is end-to-end encryption?
The service still carries the data, but it only ever handles content it cannot read.
On this page
How does end-to-end encryption work?
The encryption keys are created on the participants' devices and exchanged between those devices only. Each device encrypts audio, video or messages before they leave it, and only the other participants' devices can decrypt them. Servers in between still route the data, but they handle scrambled bytes.
In a group video call that runs through a media server, an SFU, end-to-end encryption needs a second layer. The normal encryption in transit protects each connection between a device and the server; on top of it, the app encrypts every video frame and audio packet with keys the server never sees. The server can still forward the packets, because it only needs their labels, not their content.
What does end-to-end encryption change in a meeting?
It protects the conversation from anyone who can reach the provider's servers: a compromised machine, a leaked database or an operator.
| Feature | Effect of end-to-end encryption |
|---|---|
| Cloud recording | Usually unavailable, because the server cannot see the picture or hear the audio. |
| Transcripts and AI summaries | Usually unavailable server-side, for the same reason. |
| Joining from older apps | Often blocked, because those apps cannot hold the keys. |
| Recovering a lost conversation | Not possible from the provider; only participants' devices ever had it. |
So the real question is not “encrypted or not” but which risk matters more for a given meeting: the provider having access, or losing recording, transcripts and easy joining.
How does Meeto protect calls?
Meeto calls are encrypted in transit (WebRTC, DTLS-SRTP) through Meeto's media servers in Europe and South-East Asia. Every call, one-to-one included, runs through those servers.
Recording and AI summaries are opt-in features for Pro and Team hosts: they start only when the host turns them on, and everyone in the call sees an indicator while they run. Meeting content is not used to train AI models. Chat is deleted when the meeting ends. Recorded media is kept for 90 days, and the owner can switch a shared link off. The security overview and the privacy checklist cover these controls.
Frequently asked questions
Is encryption in transit the same as end-to-end encryption?
No. Encryption in transit protects data on its way to a server, and the server can read it once it arrives. End-to-end encryption keeps the content unreadable to every server on the way, including the provider's. Many services that say calls are "encrypted" mean encryption in transit.
Can an end-to-end encrypted meeting be recorded?
A participant's own device can record what it shows, but a cloud recording, an automatic transcript or an AI summary made on the provider's servers needs readable media. That is why services that offer an end-to-end encrypted mode usually switch those features off while it is on.
How can I tell whether a service is really end-to-end encrypted?
Look for documentation that the keys are created and kept on participants' devices, that the provider cannot obtain them, and that features needing server access, such as cloud recording or AI summaries, are unavailable in that mode. Words like "secure" or "encrypted" alone do not tell you.
How does Meeto protect a call?
Meeto calls are encrypted in transit (WebRTC, DTLS-SRTP) through Meeto's media servers in Europe and South-East Asia. Recording and AI summary start only when a Pro or Team host turns them on, and everyone in the call sees an indicator while they run. Meeting content is not used to train AI models; the privacy policy describes processing and retention.
Put it to work
Open your Meeto account to set it up, or explore the working product first.