The world's most used messenger.
The US House of Representatives just banned it from all official devices.

WhatsApp is owned by Meta, a US company. Under the CLOUD Act (18 U.S.C. § 2713), all messages, backups, and metadata are subject to US government disclosure. In June 2025, the US House banned WhatsApp on official devices. A 2025 lawsuit alleges Meta can read messages despite claiming otherwise.

Switch to sovereign → See the comparison
2025–2026 alerts
US House of Representatives ban (June 2025): Office of Cybersecurity deemed WhatsApp "high risk due to lack of transparency in how it protects user data, absence of stored data encryption"
Federal lawsuit (Bloomberg Law, 2025): International plaintiffs allege Meta makes false E2EE claims. Lawsuit claims Meta CAN see WhatsApp messages in breach of privacy promises.
CLOUD Act: Meta Platforms, Inc. is a US company. Every WhatsApp message, metadata record, and cloud backup is subject to US government compelled disclosure, regardless of where users are located.
Saudi PDPL Art. 29: Meta's data transfer practices structurally conflict with KSA data sovereignty requirements. No US–KSA executive agreement exists.
SAMA Circular (March 2025): Saudi Central Bank issued a binding prohibition on WhatsApp for all financial institution customer communications, citing "unreliable channels, security concerns," and required PDPL-compliant alternatives in-app.
3.5B
WhatsApp users globally. Every conversation flows through Meta's US-jurisdiction infrastructure, fully accessible under the CLOUD Act. The world's most used messenger is owned by the world's largest surveillance advertising company.
€225M
GDPR fine from Ireland's Data Protection Commission against WhatsApp in 2021, for unlawful data processing and lack of transparency about how user data was shared with Meta. The largest GDPR fine in Ireland's history at the time.
0
GDPR Article 48 mechanisms that permit lawful CLOUD Act compliance for WhatsApp users. The conflict between EU data protection law and US compelled disclosure has no fix inside WhatsApp's architecture.
June 2025
Month the US House of Representatives banned WhatsApp on all official devices. The US government's own security office ruled it too risky. That's the finding, not a campaign.
Feature comparison

WhatsApp vs SCOVR: every feature, every exposure

The same messaging, voice, and video capabilities, with one critical difference: who has legal access to the data, and whose business model depends on it.

Feature WhatsApp Personal $0 WhatsApp Business $0 WhatsApp Business Platform WhatsApp Enterprise API SCOVR · Matrix Sovereign
Messaging
End-to-end encryption ✓ ✓ Partial (business can read) Partial ✓ E2EE by default
Group messaging ✓ ✓ ✓ ✓ ✓
Voice & video calls ✓ ✓ ✗ ✗ ✓
File sharing ✓ ✓ ✓ ✓ ✓
Max group size 1,024 1,024 Unlimited Unlimited Unlimited
Disappearing messages ✓ ✓ Platform dependent Platform dependent ✓
Data & Privacy
Cloud backup E2EE Opt-in only Opt-in only No No On-prem storage
Backup jurisdiction iCloud/Google (US) iCloud/Google (US) Meta servers Meta servers Your infrastructure
Metadata shared with Meta YES, all YES, all YES, all YES, all ✓ Not applicable
Phone number required YES YES YES YES ✓ No, username-based
Sovereignty
Data jurisdiction Meta / USA Meta / USA Meta / USA Meta / USA Your jurisdiction
CLOUD Act exposure YES YES YES YES NO
GDPR Art. 48 conflict YES YES YES YES None
PDPL (Saudi Arabia) conflict YES YES YES YES None
Self-hostable ✗ ✗ ✗ ✗ ✓
Air-gapped deployment ✗ ✗ ✗ ✗ ✓
Cryptographic key ownership Meta Meta Meta + Business Meta + Business ✓ You
Gag order risk (§ 2705(b)) YES YES YES YES Not applicable
Gov't intelligence pipeline CLOUD Act → Palantir CLOUD Act → Palantir CLOUD Act → Palantir CLOUD Act → Palantir Not applicable
SAMA compliant (KSA fin. sector) Prohibited Prohibited Prohibited Prohibited Compliant
Openness
Open standard protocol Proprietary Proprietary Proprietary Proprietary Matrix (open)
Interoperable federation ✗ ✗ ✗ ✗ ✓ Cross-org
Vendor lock-in Meta Meta Meta Meta None
Business messages E2EE ✓ ✓ ✗ Business can read ✗ Business can read ✓ Full E2EE
NIS2 supply-chain compliance Cannot satisfy Cannot satisfy Cannot satisfy Cannot satisfy Full documentation
The WhatsApp exposure

What WhatsApp exposes, and what Meta does with it

Meta Platforms is not a communications company. It is the world's largest surveillance advertising business. WhatsApp is its infrastructure for reaching 3.5 billion people, and the metadata those people generate is operationally valuable for Meta's core business, regardless of whether the message content is encrypted.

Critical

Meta's business model is surveillance advertising, and WhatsApp feeds it

WhatsApp's end-to-end encryption protects message content. It does not protect metadata. Meta collects and shares across its platforms: who you communicate with and how often, your contact list, your IP address and approximate location, your device identifiers, your usage patterns, timestamps, and behavioural signals. This metadata flows directly into Meta's advertising intelligence infrastructure: Facebook, Instagram, and Meta's broader advertising network. When a US CLOUD Act order compels Meta to produce data on a target, Meta holds extensive records of their communication patterns, social graph, device footprint, and behavioural profile. Message content is encrypted. The intelligence picture around it is not.

Structural

US House of Representatives ban: formal government cybersecurity finding

In June 2025, the US House of Representatives Chief Administrative Officer banned WhatsApp from all official House devices. The formal memo to all House staff cited: "lack of transparency in how it protects user data, absence of stored data encryption, and potential security risks." The US government's own legislators won't use it. If that's not enough to settle the question for every ministry and regulated institution outside the US, nothing is.

US House CAO Memo, June 2025 · Formal cybersecurity determination, WhatsApp is high risk for official use
High Risk

Federal lawsuit: Meta allegedly CAN see WhatsApp messages

In 2025, an international group of plaintiffs filed a federal lawsuit alleging that Meta has made false claims about the privacy and security of WhatsApp. The lawsuit challenges WhatsApp's core E2EE claim: the in-app assertion that "only people in this chat can read, listen to, or share" messages. The plaintiffs allege that Meta can access message content in breach of its privacy promises. The suit reflects a broader pattern: WhatsApp's architecture allows Meta to update, modify, and control what happens to message data at the infrastructure level. E2EE is only as strong as the trust placed in the company controlling the encryption key infrastructure.

Bloomberg Law, 2025 · International plaintiffs allege Meta's E2EE claims are false, federal lawsuit pending
Structural

Cloud backup: the gap that empties the promise

WhatsApp's E2EE applies to messages in transit. It does not automatically protect backups. When users back up WhatsApp to iCloud (Apple) or Google Drive (Google), which the vast majority do, those backups are stored on servers controlled by US companies. Both Apple and Google are subject to the CLOUD Act. A government order to Apple or Google can retrieve an unencrypted WhatsApp backup containing the complete message history of a target, bypassing WhatsApp's E2EE entirely. WhatsApp added opt-in E2EE backup in October 2021, but it is opt-in, disabled by default, and requires users to actively enable it. Most users have never heard of it.

CLOUD Act § 2713 (Apple/Google) · Backups to iCloud/Google Drive accessible under US law, opt-in E2EE backup disabled by default
Structural

GDPR fine: €225M for data practices Meta couldn't defend

In September 2021, Ireland's Data Protection Commission fined Meta €225 million for WhatsApp GDPR violations, the largest GDPR fine in Ireland's history at the time. The finding: WhatsApp failed to be transparent about how it shared user data with Meta and other Meta Group companies. The fine was increased from €50M to €225M after the European Data Protection Board (EDPB) intervened. The DPC had proposed a lower figure, but EDPB determined the violations were more serious than initially assessed. The fine is evidence, from a European data protection regulator not a competitor, that WhatsApp's data practices do not meet EU standards.

GDPR Arts. 12–14 + EDPB Art. 65 Decision · Ireland DPC fine, September 2021, €225M for GDPR transparency violations
Structural

Saudi PDPL conflict: WhatsApp's data practices violate KSA law

Saudi Arabia's Personal Data Protection Law (PDPL, Royal Decree M/19) restricts the cross-border transfer of personal data outside the Kingdom without NDMO authorisation. Meta's data processing, including WhatsApp metadata, contact data, and user behaviour, flows to US servers under Meta's global data architecture. There is no US–Saudi Arabia bilateral CLOUD Act executive agreement. There is no PDPL-compliant mechanism for the Meta data transfers that occur automatically when any Saudi user sends a WhatsApp message. Saudi government entities, financial institutions, healthcare organisations, and enterprises handling sensitive citizen data face an unresolvable conflict: using WhatsApp means violating PDPL.

PDPL Art. 29 (KSA) + CLOUD Act § 2713 · Cross-border transfer of user data without NDMO authorisation, structurally non-compliant
Regulatory Ban

SAMA March 2025: Saudi Central Bank bans WhatsApp for all financial institution communications

Saudi Arabia's Central Bank (SAMA) issued a binding circular in March 2025 prohibiting WhatsApp as a customer communication channel across all supervised financial institutions: banks, insurance companies, finance companies, and payment providers. The circular cited "unreliable channels" and "security concerns," requiring replacement with secure, PDPL-compliant alternatives: Live Chat or ChatBot systems embedded within official bank applications, compliant with national data protection law. It is not guidance. Any Saudi financial institution still routing customer communications through WhatsApp is already in breach of a binding central bank requirement. A US-owned, US-jurisdiction application cannot serve as compliant infrastructure for KSA financial sector communications, SAMA said so officially.

SAMA Circular, March 2025 · Binding prohibition on WhatsApp for all KSA financial institution customer communications, PDPL-compliant alternatives required
Critical

The Palantir pipeline: how WhatsApp metadata becomes a government intelligence dossier

WhatsApp metadata, including contact graphs, IP-based location, device identifiers, and behavioural timestamps, is legally compellable from Meta under the CLOUD Act. US government agencies submit orders; Meta produces records. Palantir Gotham, deployed by US intelligence and law enforcement, ingests subpoenaed social media data including location history, phone metadata, bank records, and travel data, correlating them into surveillance dossiers scored by confidence level. The ImmigrationOS contract (Palantir, $30M, 2025) sweeps in "GPS-based location information, telecommunications metadata, and travel records" to produce near-real-time location targets. The institutional ties go further: Palantir co-founder Peter Thiel sat on Meta's board from 2004 to 2022. Cambridge Analytica whistleblower Christopher Wylie testified to the UK Parliament that senior Palantir employees worked on the Facebook data project that became the Cambridge Analytica scandal. In H1 2025 alone, Meta received 374,516 government data requests globally: 81,064 from the US, 77.3% with non-disclosure orders preventing Meta from notifying users. Using WhatsApp means your metadata flows through the US company that is the primary data source for the world's leading government surveillance intelligence platform.

CLOUD Act § 2713 + Palantir Gotham / ImmigrationOS (2025) · Meta CLOUD Act disclosure → government agency ingestion → Palantir correlation with GPS, phone metadata, travel records and biometrics
The open standard advantage

Matrix: the sovereign backbone that replaces WhatsApp, without Meta

The Matrix open standard delivers everything WhatsApp offers, including messaging, voice, video, file sharing, and group chats, on an open protocol with no single owner, where your organisation controls its own server, its own data, and its own encryption keys. No Meta, no US jurisdiction, no surveillance advertising, no CLOUD Act applicability at any layer.

WhatsApp was the world's default messenger because it was simple and free. But simple and free was never the same as sovereign. WhatsApp's architecture requires your communications, and your organisation's metadata, to flow through Meta's infrastructure for every message, every call, every contact sync, making CLOUD Act exposure and metadata harvesting structural facts, not manageable risks.

SCOVR runs on Element Server Suite (ESS Pro), the enterprise build of the Matrix standard. For EU organisations subject to GDPR and NIS2, and for organisations in Saudi Arabia subject to PDPL, Matrix is the only option that resolves it at the root: a communications platform where Meta has no role, CLOUD Act compelled disclosure is a structural impossibility, and the advertising surveillance machine that owns WhatsApp has no foothold.

Read the Matrix specification →
No Meta. No US jurisdiction at any layer. CLOUD Act inapplicable.
Matrix servers deploy in your own data centre, a sovereign EU cloud, or a KSA-resident facility. No Meta, no US infrastructure at any point. CLOUD Act compelled disclosure doesn't apply. There's no US company to serve an order to.
End-to-end encryption by default. No Meta key access.
Matrix encrypts messages E2EE with keys generated on your devices. WhatsApp's E2EE is genuine for content, but Meta controls the encryption key infrastructure, the backup path, and the metadata. With Matrix, nobody, including AMVLET, can decrypt your communications.
No metadata harvesting. No advertising business model.
Meta's revenue depends on the data it collects from WhatsApp users. Matrix has no advertising model. Your communication patterns, social graph, usage behaviour, and device data are not collected, not shared, not monetised.
GDPR and PDPL compliance by architecture
When no US company is in the data path, the GDPR Article 48 conflict and the Saudi PDPL Article 29 conflict cease to exist. Compliance is an architectural fact, not a contractual assurance from a company that has already been fined €225M by European regulators for failing to comply.
Bridge to WhatsApp contacts
The open-source mautrix-whatsapp bridge lets Matrix users send and receive messages with WhatsApp contacts directly, running on your sovereign infrastructure. Your organisation moves to Matrix. Your external contacts stay on WhatsApp. The bridge handles the translation.
The platform choice

What you accept when you choose WhatsApp vs. what you control with Matrix

WhatsApp: what you accept

Meta holds your conversations. US law reaches every one of them.

  • Meta Platforms Inc. is a US company. CLOUD Act compelled disclosure applies to all 3.5 billion users' data regardless of where they are located.
  • WhatsApp metadata, including who you talk to, how often, your contacts, device data, and location signals, is shared across Meta's advertising infrastructure and legally compellable.
  • Cloud backups to iCloud and Google Drive (both US companies) bypass WhatsApp's E2EE. A government order to Apple or Google retrieves your complete message history.
  • The US House of Representatives formally determined WhatsApp is "high risk" for official use. If the US government's own legislators avoid it, that's your answer.
  • Federal lawsuit alleges Meta CAN see message content in breach of E2EE promises. The legal challenge to WhatsApp's core privacy claim is now before US federal courts.
  • Ireland's DPC fined Meta €225M for GDPR violations in WhatsApp data practices. A European regulator confirmed it. That's not a competitor talking.
  • Saudi PDPL Art. 29 is violated by Meta's automatic cross-border data transfers. No NDMO-compliant path exists for Saudi users.
  • SAMA formally banned WhatsApp for KSA financial institution communications in March 2025. The central bank called it incompatible with supervised financial use and banned it.
  • CLOUD Act-compelled Meta metadata flows into government systems ingested by Palantir Gotham. Your contact graph, location signals, and device identifiers can be correlated with GPS data, phone records, and travel history into a full surveillance dossier.
VS
SCOVR · Matrix: what you control

Your infrastructure. No Meta. No advertising. No exposure.

  • No US company in the data path. CLOUD Act applicability is structurally eliminated, not contractually managed.
  • No metadata harvesting. Matrix has no advertising business model; your communication patterns are not a product.
  • No cloud backup gap. Data stays on your sovereign infrastructure; there is no iCloud or Google Drive in the path.
  • GDPR and PDPL compliance by architecture: data stays in the jurisdiction where it is governed. The €225M in GDPR fines are evidence of the alternative.
  • mautrix-whatsapp bridge: reach WhatsApp contacts directly from your sovereign Matrix homeserver, without either party changing their app.
  • No vendor lock-in. Matrix is an open standard; your data, your deployment, your jurisdiction, permanently.
  • Cryptographic keys generated and held on your infrastructure. SCOVR cannot decrypt your content.
Common questions

Switching from WhatsApp: what organisations ask

WhatsApp says its messages are end-to-end encrypted. Doesn't that protect me from the CLOUD Act?+
No. E2EE protects message content in transit. It does not protect the metadata Meta holds (who you talk to, when, how often, your contact list, device identifiers, IP addresses). All of this is legally compellable under the CLOUD Act. Additionally, most users back up WhatsApp to iCloud or Google Drive, both US companies subject to CLOUD Act, where the backups are not E2EE by default. A government order to Apple or Google retrieves your complete WhatsApp history unencrypted. The E2EE claim holds for message content in transit. It says nothing about the metadata Meta holds, contact graphs, timestamps, device IDs, IP location, all of which law enforcement can reach.
Why did the US House of Representatives ban WhatsApp?+
The House Chief Administrative Officer issued a memo in June 2025 banning WhatsApp on all official House devices. The formal finding: WhatsApp is "high risk due to lack of transparency in how it protects user data, absence of stored data encryption, and potential security risks." This is the cybersecurity determination of the legislative branch of the US government, about a product made by a US company. The recommended alternatives were Teams, Wickr, Signal, iMessage, and FaceTime. The US government's own cybersecurity office made the call about a US company's product.
What does the federal lawsuit against Meta claim about WhatsApp?+
In 2025, an international group of plaintiffs filed a federal lawsuit alleging that Meta has made false claims about WhatsApp's privacy and security. The lawsuit challenges WhatsApp's stated E2EE guarantee: the in-app assertion that "only people in this chat can read, listen to, or share" messages. If the allegation is proven, the claim is legally false. The case is pending. The concern underneath it is real regardless: Meta controls the encryption key infrastructure, can update the app, and profits from user data. The architecture creates the possibility; the lawsuit alleges the actuality.
Does WhatsApp's CLOUD Act exposure create a conflict with Saudi Arabia's PDPL?+
Yes, and there's no fix inside WhatsApp's architecture. Saudi Arabia's Personal Data Protection Law (PDPL) restricts cross-border transfer of personal data outside the Kingdom without NDMO authorisation. Meta's data processing architecture automatically transfers WhatsApp user data, including phone numbers, metadata, contact lists, and device identifiers, to US servers. There is no US–Saudi Arabia bilateral executive agreement. There is no PDPL-compliant transfer mechanism for what Meta does as a matter of routine. Saudi government entities, regulated financial institutions, healthcare organisations, and enterprises handling sensitive citizen data face an unresolvable legal conflict: using WhatsApp as an institutional tool means being in ongoing violation of national data sovereignty law.
Can Matrix/Element really replace WhatsApp for organisations?+
Yes. The Matrix standard covers the full communication stack WhatsApp provides: encrypted messaging, voice and video calling, file sharing, group chats, and disappearing messages, all on an open, self-hosted protocol. The mautrix-whatsapp bridge allows Matrix users to send and receive messages with WhatsApp contacts directly, without either party changing their app. What Matrix cannot offer is the 3.5 billion user network, but for institutional deployments, the question is not consumer reach, it is sovereign security. Matrix cuts out everything WhatsApp can't fix: Meta's metadata harvesting, CLOUD Act exposure, the iCloud/Google backup gap, the €225M GDPR finding, and the June 2025 House ban. Sovereignty is not on WhatsApp's roadmap.
Why did Saudi Arabia's Central Bank ban WhatsApp, and what must financial institutions do?+
SAMA (Saudi Central Bank) issued a binding circular in March 2025 prohibiting WhatsApp as a customer communication channel for all supervised financial institutions: banks, insurance companies, finance companies, and payment service providers. The circular cited two grounds: "unreliable channels" and "security concerns." The required replacements are secure Live Chat or ChatBot systems embedded within official bank applications, explicitly compliant with Saudi PDPL requirements. The regulatory logic is clear: PDPL Art. 29 prohibits cross-border transfer of personal data outside the Kingdom without NDMO authorisation. Every WhatsApp message from a Saudi customer to a Saudi bank generates metadata, including phone numbers, contact lists, device identifiers, IP-based location, and timestamps, that Meta automatically transfers to US servers. There is no US–Saudi Arabia bilateral executive agreement that could make this lawful under PDPL. SAMA's circular says it plainly: a US-owned, US-jurisdiction application cannot serve as compliant infrastructure for regulated financial communications in Saudi Arabia. Financial institutions that have not migrated customer service communications off WhatsApp are in breach of a binding central bank requirement.
Does Palantir have access to WhatsApp data? How does the intelligence pipeline work?+
Palantir does not receive WhatsApp data directly, but the pipeline from WhatsApp to Palantir intelligence analysis is well-documented. The mechanism: WhatsApp and Meta collect metadata on all users (contact graphs, IP location, device identifiers, usage patterns). US government agencies submit legal orders to Meta under the CLOUD Act (§ 2713), compelling Meta to produce these records. In H1 2025, Meta received 374,516 government data requests globally; in the US alone, 81,064 requests were submitted, 77.3% accompanied by gag orders that prevented Meta from notifying users. The produced data flows into government agency systems. Palantir Gotham, used by multiple US intelligence and law enforcement agencies, ingests subpoenaed social media data including location history, phone metadata, bank records, and travel data, and correlates them into scored surveillance dossiers. The 2025 ImmigrationOS contract ($30M, Palantir/ICE) specifically sweeps in "GPS-based location information, telecommunications metadata, and travel records" to provide "near real-time visibility" of targets. The governance connection: Palantir co-founder Peter Thiel served on Meta's board from 2004 to 2022. Cambridge Analytica whistleblower Christopher Wylie testified to the UK Parliament that senior Palantir employees worked on the Facebook data project that became the Cambridge Analytica scandal. The chain from WhatsApp use to government intelligence analysis is legal, documented, and structurally inherent to WhatsApp's US-jurisdiction architecture.

The same messaging. None of WhatsApp's exposure to Meta.

Switch from WhatsApp to a sovereign communications platform that gives your organisation every messaging feature, without putting your conversations, metadata, and contact data inside Meta's surveillance advertising infrastructure, or within reach of US government compelled disclosure.

Book a migration briefing → Explore Enterprise