European alternatives to WhatsApp

WhatsApp is the default messaging app for most of Europe. It is also owned by Meta Platforms, Inc. (US-incorporated), which places the parent group under US CLOUD Act jurisdiction. WhatsApp encrypts message content end-to-end, so the practical concern is not that messages are readable; it is the ownership structure and the metadata layer: contact graphs, who-messages-whom, timing, and the contact-discovery-by-phone-number mechanism that ties your identity to your SIM. For a privacy-conscious individual, a journalist or legal practitioner with a threat model, or a European organisation writing a data-sovereignty assessment, that profile is what prompts a look at the five alternatives below, weighed on who legally owns the company, where the servers sit, whether metadata is protected as well as content, and whether the app can run inside your own perimeter.

All five options below are end-to-end encrypted by default, so what actually separates them is where your conversations and metadata end up, and under whose jurisdiction. Threema is the easiest consumer-ready switch (Switzerland, Pfäffikon, EU-owned, all-Swiss hosting, CLOUD Act exposure: None, hosted with an ISO 27001-certified colocation partner, no phone number required), Olvid is the government-grade French option and the only one here that end-to-end encrypts metadata as well as content (France, Paris, EU-owned, ANSSI CSPN-certified, mandated for French government ministers), and Element/Matrix is the open, federated, self-hostable choice for organisations (United Kingdom, open-source Matrix protocol, used across European public sectors).

Which of your day-to-day habits actually survive a move away from WhatsApp?

• End-to-end encrypted one-to-one and group chats (every alternative here encrypts content by default).
• Voice and video calls (Threema, Wire, Element/Matrix and SimpleX all support encrypted calls; Olvid supports calls, with outbound calls on paid tiers).
• File, photo and document sharing.
• Group chats and, on most, broadcast/channel features.
• Multi-device use (Wire, Element/Matrix and SimpleX are multi-device by design; Threema and Olvid support it on current versions).
• Cross-platform clients for iOS, Android and desktop.

The honest list of trade-offs, so nothing surprises you later:

• Network effect. WhatsApp's value is that everyone is already on it. Every alternative requires the people you talk to to install it too. This is the single biggest real-world cost of switching and no feature comparison changes it.
• Chat history. WhatsApp chats cannot be migrated into another messenger as live conversations. You re-establish contacts and start fresh. Plan to keep WhatsApp installed read-only during a transition.
• Contact discovery by phone number. Threema, Olvid and SimpleX deliberately do not tie identity to your phone number. This is better for privacy, but it means you exchange a QR code or link rather than "finding" people automatically.
• WhatsApp Business / Click-to-Chat. Businesses relying on the WhatsApp Business API will not find a drop-in equivalent; the European messengers target secure team and organisational comms rather than customer-facing commerce chat.
• Status / Channels. Most alternatives offer a subset; SimpleX and Element/Matrix have channels, but the consumer "Status" feature is not a universal one-to-one match.

Leaving WhatsApp comes down to two things: getting your contacts onto the same app, and accepting that chat history stays behind. Here is a working sequence.

1. Pick the alternative your closest contacts will actually install. The hard constraint is the network effect, not the feature list. For a family or friend group, Threema or SimpleX install in minutes with no account setup. For a workplace or organisation, standardise on one (Element/Matrix, Wire or Olvid) so everyone lands in the same place.
2. Do not try to migrate chat history; plan to reference it instead. WhatsApp's end-to-end-encrypted backups cannot be imported by another app as live conversations. Keep WhatsApp installed but treat it as read-only archive during the transition. If you need a personal record of specific threads, use WhatsApp's own "Export chat" to email yourself a text/zip archive before you stop using it.
3. Seed the new app with your real contacts first. Spend the first day adding the 10–20 people you actually message daily. Exchange QR codes in person where you can (Threema, Olvid, SimpleX support this), or send invitation links. Once your core circle is reachable, the rest follows.
4. Decide on phone-number vs no-identifier up front. If avoiding phone-number-linked identity is a goal, choose Threema, Olvid or SimpleX and set them up without a number. If you prefer the familiar phone-number model for easier contact discovery, that is a trade-off to make consciously, not by default.
5. For organisations, decide hosted vs self-hosted before rollout. Element/Matrix, Wire and SimpleX can all run on infrastructure inside your own EU perimeter, the option that removes server-side CLOUD Act exposure entirely. If you self-host, provision the homeserver/relays on EU hosting (Hetzner, OVHcloud, Scaleway or your own data centre) before onboarding users.
6. Run both apps in parallel for 60 days. WhatsApp is still how some of your contacts will reach you at first, so do not delete it on day one. Keep it for the stragglers and the occasional inbound message, and revisit after two months once the new messenger has become the default for your active conversations.

Match your situation to a starting pick:

• You are a privacy-conscious individual or family switching from WhatsApp and want the easiest setup. Start with Threema (Switzerland, Pfäffikon, EU-owned, all-Swiss hosting, CLOUD Act exposure: None, hosted with an ISO 27001-certified colocation partner rather than holding the certificate itself). One-off purchase, no subscription, no phone number required, consumer-grade UX closest to WhatsApp. Best all-round pragmatic switch for non-technical contacts.
• Your threat model includes metadata and you want maximum privacy. Start with Olvid (France, Paris, EU-owned, ANSSI CSPN-certified) or SimpleX (United Kingdom, no user identifiers of any kind, twice audited by Trail of Bits). Olvid is the government-certified option that encrypts metadata as well as content; SimpleX is the architecture-first option with no account or identifier at all and self-hostable relays. Both are the right starting point for journalists, legal practitioners, and anyone whose concern is who-talks-to-whom, not just message content.
• You are a European government body, public-sector organisation or regulated enterprise. Start with Olvid, Element/Matrix or Wire. Olvid carries ANSSI CSPN and a French-government mandate. Element (open Matrix protocol) underpins sovereign deployments including the German BwMessenger and France's Tchap, and is fully self-hostable. Wire offers a self-hostable, open-source stack on the modern MLS encryption standard. All three keep the server inside your own security perimeter.
• You want a free, open-source messenger you can self-host yourself. Start with SimpleX (free, AGPLv3, self-hostable SMP/XFTP relays) or Element/Matrix (free, open-source, self-hostable Matrix homeserver). Both let you run the entire stack on EU infrastructure, removing server-side CLOUD Act exposure by construction. SimpleX is the privacy-maximalist choice; Element/Matrix is the more feature-complete team-collaboration platform.

Which of these fits comes down to whether your binding constraint is the network effect (who will actually install it), metadata privacy, government certification, or self-hosting control, and the comparison table above lets you sort by ownership, hosting region and CLOUD Act exposure to check your pick against it.