A video call is secure when the audio and video are end-to-end encrypted — encoded on your device, decoded only on the devices of the people you’re calling, and unreadable to every server in between. That’s the headline. But calls have a wrinkle that messages don’t: they’re live streams that have to be routed somewhere in real time, and how that routing works determines both who could listen and what else you reveal by making the call at all.

This guide covers what “secure” means for a call specifically, the three ways your call can travel, the IP address question nobody mentions, and the things encryption still doesn’t hide.

What “secure” means for a call

Four properties, and they’re not all the same thing:

  1. The media is end-to-end encrypted. Your camera and microphone data are sealed on your device. The provider’s servers move packets they cannot decode. (The plain-English version of how that works.)
  2. It’s on by default, for every call — not a special “secure meeting” mode you have to remember to enable, and not just for one-to-one while group calls fall back to something weaker.
  3. Only the intended people can join. A call to a person is different from a room with a link; more on that below.
  4. Nothing is being transcribed or recorded server-side. If something on a server is turning your conversation into text, the conversation is not end-to-end encrypted. This one has become the most common way the property quietly disappears.

Worth saying plainly: “encrypted” on its own means very little for calls. Essentially all video calling encrypts traffic in transit — that’s table stakes, and it protects you from someone on the same café Wi-Fi. It says nothing about whether the provider can see your call. The video-calling industry has a track record of using “end-to-end encryption” loosely, so the phrase deserves the same scepticism you’d apply to any app’s security claims.

The three ways your call can travel

This is the part that’s genuinely specific to calls, and it’s worth understanding because it’s the difference between marketing and architecture.

Peer-to-peer. Your device connects directly to the other person’s, and the media never touches a server at all. Cryptographically this is the cleanest arrangement — there’s no middle to compromise. It has two real costs: it exposes your IP address to the person you’re calling, and it doesn’t scale, because every participant must send their video to every other participant. Fine for two people; it collapses somewhere around four.

Relayed. When a direct connection can’t be established — which is common behind home routers and mobile networks — the call is bounced through a relay server. The relay forwards encrypted packets without being able to open them, so end-to-end encryption survives. It also means neither party learns the other’s IP address, which is a privacy gain. Most calls in the real world end up here.

Forwarded through a media server. Group calls typically use a server that receives each participant’s stream and forwards it to the others, so your phone uploads once instead of five times. Historically this required the server to decrypt everything, which is precisely why so many group calls were never truly end-to-end encrypted. Modern techniques — an extra layer of encryption applied to the media frames themselves, with group keys managed between the participants — let such a server route streams it cannot read. It’s a solved problem now, but it is harder, which is why group calling is where “end-to-end encrypted” claims most often quietly weaken.

You don’t need to interrogate an app about its topology. You do need to know that “we use encryption” and “our servers cannot hear your call” are different sentences.

The IP address question

Here’s a leak that’s unique to calling and almost never discussed.

In a genuine peer-to-peer call, the two devices connect directly — which means each side learns the other’s IP address. An IP address is not a home address, but it does typically reveal your approximate location (usually city-level) and your internet provider. For a call with your sister, irrelevant. For a call with someone you’ve met online, a stranger, or a person you have reason to be cautious about, it’s a real disclosure.

Relaying the call through a server removes that exposure: each side only ever talks to the relay, so neither learns the other’s address. This is the interesting case where routing your call through a server is better for privacy — as long as the relay is forwarding sealed packets it can’t open.

The practical upshot: an app that always relays, or that lets you force relaying, is doing something meaningful for you. It’s a good question to ask of any app you’d use to call someone you don’t fully trust.

What encrypted calls still don’t hide

End-to-end encryption protects the contents of the conversation. It does not, on its own, protect:

  • That the call happened. Who you called, when, and for how long is metadata, and most providers retain some form of it. Sealed content, visible pattern.
  • Recording by either participant. Nothing can stop the other side pressing record, or pointing a second phone at the screen. Encryption is not a promise about the person you’re talking to.
  • AI transcription and summaries. The modern version of the problem. If a notetaker, assistant, or meeting summary feature is processing your call on a server, then the server can hear your call — by definition, whatever the marketing says elsewhere in the product. These features can be genuinely useful, but they are a trade, and it should be an explicit, opt-in one.
  • Whatever is behind you. A camera shows your home’s interior, what’s on the wall, who walks past, and often enough to identify where you live. Blur, a virtual background, or just a considered angle does more for real-world privacy than most settings.
  • Your notifications. Screen sharing while messages pop up has ended more privacy than any cryptographic weakness.

None of this argues against encrypted calls. It argues that a call is a situation, not just a data stream.

Most business video tools are built around a meeting link: a URL that creates a room, and broadly, anyone who has the URL can turn up. That model exists because meetings involve people from different organizations who need a low-friction way in. It also created an entire genre of uninvited-guest incidents.

For a family, that’s the wrong shape. You’re not convening a meeting; you’re calling your mother. Calling a person in a defined circle — rather than opening a room and distributing an address — removes the whole category of problem: there’s no link to leak, forward, or guess, and there’s no lobby to police.

It matters for a second reason too. A link-based call typically identifies participants by whatever name they typed in. A circle-based call knows who people actually are, because they were already in your circle.

Choosing a private video call app

  1. End-to-end encrypted media, on by default — for group calls as well as one-to-one, not as a special mode.
  2. A clear answer on server access. Look for “our servers can’t hear your calls,” not “encrypted.” Vagueness is informative.
  3. No server-side transcription or AI summarisation unless you explicitly turn it on, with the trade spelled out.
  4. Relay available, so you’re not forced to expose your IP address to the other party.
  5. Person-to-person calling, not open meeting links, for anything family-related.
  6. Cross-platform. A call is the one feature where a single missing platform means the call simply doesn’t happen.
  7. Minimal metadata retention, and a stated policy on what call records are kept and for how long.
  8. Simple enough for the least technical person you call. The most private app in the world is useless if a grandparent can’t answer it.

FAQ

What makes a video call app secure? End-to-end encrypted audio and video that’s on by default for every call including group calls, servers that can’t decode the media, no server-side recording or transcription, and control over who can join. Encryption “in transit” alone is not the same thing.

Are video calls encrypted by default? Almost all video calls are encrypted in transit, meaning protected between you and the provider’s servers. Far fewer are end-to-end encrypted, meaning the provider itself cannot access the media. The distinction is the entire question, and product pages often blur it.

Can my video call be recorded without me knowing? By the provider, not if it’s genuinely end-to-end encrypted — there’d be nothing readable to record. By the other participant, yes: screen recording, a recording feature, or another phone. Encryption protects the channel, not the people on it.

Does a video call reveal my IP address? It can. In a direct peer-to-peer call each side sees the other’s IP, which typically reveals approximate location and internet provider. Calls routed through a relay server don’t have this exposure — one of the few cases where using a server is the more private option.

Are group video calls less secure than one-to-one? They’re harder to secure, because group calls usually route through a media server. That server can be built to forward streams it can’t decrypt, but it’s more complex — which is why weaker end-to-end encryption claims cluster around group calling. Check that the guarantee covers groups.

Do AI meeting notes break encryption? Effectively, yes, if the processing happens on a server: something with access to your conversation is turning it into text. On-device processing is a different matter. Either way, it should be opt-in and clearly explained rather than quietly enabled.

A call is the most intimate thing most apps carry: your voice, your face, your home behind you, and whoever else is in the room. It deserves better than a claim of “encryption” that stops at the company’s front door. Sodal treats calls the way it treats everything else — end-to-end encrypted, made to people in your circle rather than to a link, with nothing readable left on anyone’s server when you hang up.