Can I trust WhatsApp Messenger?
This app did not meet one of the trust checks that applied to it, with no red flags.
- Best for
- Everyday messaging with content kept away from third parties
- What it means for you
- Messages and calls are protected by end-to-end encryption, meaning Meta cannot read message content. No third-party analytics or advertising services are named in code as destinations for data; the telemetry code addresses only Meta's own infrastructure. The build includes code to send contacts only to Meta-owned systems, and the code reads no advertising identifier.
- Main concern
- MetaAI conversations bypass WhatsApp E2EE, exposing content to Meta servers
- The developer's description
- Messaging app offering end-to-end encrypted messages, calls, and video chats with contact discovery and photo/video sharing features.
- Third-party services
- 1
- Findings rated low or higher
- 3
Open on the App StoreOpens the app's listing on the App Store in a new tab.
Full findings
Open this scan in your dashboardThe account that ran this scan sees every finding and the Rescan button there.
Trust checks
Secure by Design
StrongStrong security foundation
Why this result
This check looks for security issues at high severity or above in the code of this build, and none were recorded. Its scope covers stored credentials, how the app protects data on the device, and how it protects data in transit.
App Transport Security is disabled across all four bundle components of WhatsApp, removing the operating system's built-in requirement that connections use HTTPS. WhatsApp's own messaging, media, and API traffic is protected by custom certificate verification and remains secure. Secondary content such as link previews, media loaded through third-party delivery networks, and content shown in the in-app browser can potentially be intercepted or modified by an attacker on the same Wi-Fi network. Additionally, a deprecated keychain storage setting remains in active use, and app files default to a protection level that allows forensic imaging tools to access them after the device has been unlocked at least once since boot. These gaps sit alongside strong fundamentals: end-to-end encryption via the Signal Protocol for all messages, biometric-bound keys stored in the device's secure hardware chip, custom certificate verification on core communications, and HTTPS for every identified production endpoint.
Data Minimization
StrongTracking done right
Why this result
The check looks at analytics and attribution code for companies other than the developer: the data it reads, the companies named in code as recipients, and whether a consent step runs before that code. In this build, either no such code was recorded, or a consent step runs before it and the app's own disclosures describe the collection.
The app's own privacy declaration, bundled in every component of WhatsApp, simultaneously states the app does not track users across other companies' apps and websites for advertising, while listing user identifiers, advertising data, coarse location, and product interaction history as data types collected and linked to the user's identity specifically for third-party advertising purposes. This internal contradiction makes it impossible to confirm whether the consent framing presented to users accurately reflects what is collected and why. On the positive side, WhatsApp contains no third-party analytics or advertising SDKs, does not access the device's Advertising Identifier, and uses Apple's own privacy-preserving attribution methods that do not link installs to individual identities.
Manifest Mismatch
One criterion not metDisclosure incomplete or contradicted
Why this result
The check compares the app's privacy disclosures against what the code does, and at least one claim did not match in this build. Mismatches of this kind include a data category collected but not disclosed, a recipient the disclosure omits, and an identifier attached to data the disclosure describes as anonymous.
User Control
StrongNo lock-in
Why this result
The check looks for a way to export the data an account has accumulated and a way to delete the account itself. In this build, either both were found, or the app has no account of its own and keeps its data on the device. For an app without an account, the developer has no server-side copy to export or delete, and deleting the app removes the data in its own storage.
Chat backups stored in iCloud use a proprietary encryption format specific to WhatsApp's own backup system, meaning backup data cannot be imported by other messaging applications. The account is bound to a phone number and managed through Meta's servers. These characteristics create partial lock-in. No confirmed evidence of artificial barriers to account deletion or data export was found, which limits the certainty of this assessment in either direction.
Strengths
- Messages are end-to-end encrypted using Signal Protocol; Meta cannot read message content
- iCloud backups are encrypted with hardware-bound Passkey keys, inaccessible to Apple or anyone without the user's device
- No third-party analytics or advertising SDKs are present; the telemetry code names only Meta's own infrastructure as its destination
- No advertising identifier (IDFA) is collected; attribution uses Apple's privacy-preserving SKAdNetwork only — no cross-app tracking
- Chat Lock is protected by Secure Enclave biometric-bound keys that cannot be extracted from the device
- All Keychain credentials are device-locked and cannot migrate to another device through backups
- All production API traffic uses HTTPS; certificate pinning applied at messaging, media upload, and media download layers
- The app includes code to pass contacts only to WhatsApp/Meta-owned infrastructure, not third-party vendors
What the app contains
1 service
Third-party services the scan names in the build:
- Ipification (SIM-based phone number verification)
Libraries
| Library | Version | Advisory |
|---|---|---|
| PsiphonTunnel | 1.0 | none confirmed |
| SharedModules | 1.0 | none confirmed |
| not recorded | none confirmed |
Changes since the previous scan
- Version 26.31.74 (Build 1035496826 / FBAppVersion 2.26.31.74), score 83.
- Score 47 before, 83 after.
- Version 26.10.74 (Build 912595971) before, 26.31.74 (Build 1035496826 / FBAppVersion 2.26.31.74) after.
- Score change since version 26.10.74 (Build 912595971): +36 points.
- Since the previous scan: 13 findings added, 8 removed.
- Version 26.10.74 (Build 912595971), score 47.
- First public scan of this app.
Method and limits
Static analysis: the decompiled code, manifest and resources of this build, read file by file. Network traffic at run time is established by a capture of the running app.
- Files decompiled
- 3,400
- Scan date
- 13 August 2026
Corrections
No correction is published for this app.
Developer response
No response is published for this app.
Report an error Opens an email to [email protected] that names this app and this scan.