The lock icon is the start, not the finish. This guide explains the encryption, data collection, backups and account settings worth comparing before you commit to a messaging app.
Every messaging app looks private. The icon shows a lock, the store listing promises security, and a conversation feels like it belongs only to the people in it. Under the surface, though, these apps differ sharply in what they encrypt, what the company behind them can see, and where old messages end up. Before you trust one with conversations you want kept private, a short list of features and policies is worth comparing closely.
Why Not Every Messaging App Is Private by Default
In one widely cited evaluation, the Electronic Frontier Foundation scored 39 messaging products against seven security criteria, covering chat clients, texting apps, email services and voice and video calling tools. The criteria were designed to measure protection against government surveillance, criminal snooping and corporate data collection. Only six products passed every check. Several of the most widely used names, including Skype, Snapchat, Google Hangouts, Facebook chat and Yahoo Messenger, failed the best practices test, usually meeting just two of the seven criteria: encryption in transit and an audited codebase. Among mass-market options, Apple’s iMessage and FaceTime came closest, falling short on two requirements.
None of that makes a popular app dangerous by itself, but it shows that popularity and privacy are separate qualities. The EFF’s conclusion was blunt: convenience and security best practices rarely show up in the same app, and the genuinely secure options often demand extra work to install, set up and use correctly. A label reading “private” or “secure” is marketing until you confirm what sits behind it.
What End-to-End Encryption Does and Doesn’t Protect
End-to-end encryption means a message is scrambled on the sender’s device and unscrambled only on the recipient’s. The decryption key lives on the receiving device rather than on the servers in between, so the company running the app cannot read the content. Encryption in transit alone does not do this. It protects the message while it moves but leaves it readable wherever it lands in the middle, such as on the provider’s server.
Even genuine end-to-end encryption leaves gaps worth knowing about:
- Metadata. The EFF’s transit encryption standard ignored metadata entirely, so usernames and address details sat outside its test. Who you talk to, when, and how often can still be visible to the service even when the words themselves are not.
- The devices at each end. If someone gets hold of a phone that is already open, the encryption on the network does nothing to stop them reading the conversation on its screen.
- The other person in the chat. A recipient can screenshot, forward or copy a message once it is decrypted. Encryption restricts the company, not your contacts.
- Stolen keys. One EFF criterion asks whether past communications stay secure if keys are stolen, a property known as forward secrecy. Apps that earn this check use temporary keys for each session and delete them afterward, so a leaked long-term key cannot be used to decipher old messages.
The EFF noted that an app failing any of the first four criteria, which cover encryption and identity verification, can be considered insecure to some degree.
What the App Maker Collects Beyond Your Messages
Encrypted messages do not add up to a private company. The FTC’s enforcement record makes that clear. Flo Health, the maker of a period tracking app, settled FTC allegations that it shared users’ health information with outside data analytics providers after promising that such information would be kept private. In a separate case, the companies behind an app called Kuuhuub settled allegations that they broke a federal children’s privacy law: they gathered and shared personal details about children who used the app and never told the parents or asked for their consent.
Treat the privacy policy as part of the product, not the fine print around it. Before settling on a messaging app, read what it says about the data it collects, what it shares with analytics and advertising partners, and how long it keeps any of it. A policy that stays vague about sharing with “third parties” is telling you something. If the app’s business model is advertising, assume data collection is part of how it pays for itself, and look for settings that limit what is gathered.
Phone Numbers, Usernames and Account Setup Trade-Offs
How an account is created shapes how identifiable you are on the service. Apps built around phone numbers are convenient because existing contacts can find you, but they tie the account to a real-world identity and hand the company another piece of contact information to store and possibly share. Apps that allow registration with a username put more distance between the account and your identity, at the cost of making it harder for people to find you.
One scorecard criterion fits here: whether you can verify a contact’s identity independently. Encryption protects a message in transit, but it cannot tell you who is actually on the other end if an account has been taken over. Apps that support identity verification, such as comparing a short code with your contact through a different channel, make that check possible. Questions worth asking before you commit: Does signup require a phone number or an email address? Can other people find you by searching that identifier? Can you verify a contact inside the app? Can you delete the account when you are done, and what does deletion actually remove?
Backups: Where Your Message History Really Lives
A strong encryption design can be quietly undone by the backup. Security commentary on encrypted messaging has highlighted that the gains from end-to-end encryption are undercut where plaintext or recoverable ciphertext gets reintroduced through cloud backups and multi-party backup chains. Apple’s iMessage is the example most often cited: messages are encrypted on devices, but device backups that are not protected by Apple’s Advanced Data Protection can leave message history in a form the company can access. The chat was encrypted; the copy of the chat was not.
When comparing apps, ask three things about history: where it is stored, whether backups are encrypted, and who holds the key if they are. An app that encrypts messages end to end but stores unencrypted backups on its own servers has a gap you should know about before relying on it. The same distinction between ordinary and end-to-end-encrypted storage applies to cloud file storage, which we explain in our guide to end-to-end encryption in cloud storage.
Disappearing Messages and Other Privacy Controls
The EFF called out secure deletion as a feature many tools lacked, and it remains a fair test of any app you are considering. The exact controls vary by app, but the questions to ask are consistent. Does the app offer messages that disappear automatically after a set time, and does deletion apply on both sides of the conversation? Does a deleted message also come out of backups, or does the copy persist? Can you limit who finds you, who can add you to groups, and who can see your activity status?
Controls only help if they are on. Some privacy settings default to the permissive option and have to be switched manually, so walk through the settings screen after installing any app rather than assuming the defaults protect you.
Independent Audits, Open Code and Transparency Reports
Three of the EFF’s seven criteria had nothing to do with the encryption itself. They asked whether the code is open to independent review, whether the security design is properly documented, and whether the code has been audited by outsiders. Those checks matter because they are the main way an outsider can have confidence in a privacy claim.
| Scorecard criterion | What it means in plain terms |
|---|---|
| Encrypted in transit | Messages are scrambled while they move across the network. |
| Encrypted so the provider can’t read it | True end-to-end encryption, with keys held on devices rather than servers. |
| Can you verify contacts’ identities | Some way to confirm the person you message is who the app claims. |
| Past messages safe if keys are stolen | Forward secrecy, using temporary keys deleted after each session. |
| Code open to independent review | The source code is published so outside researchers can inspect it. |
| Security design documented | The encryption methods, key handling and limits are written up publicly. |
| Independent security audit | Outside experts have reviewed the implementation. |
The EFF was upfront about the limits of its own work: it did not run vulnerability assessments or analyze encryption implementations in depth. It judged products on principles and features. That still tells you something. An app that publishes its code, documents its cryptographic design and undergoes outside audits has opened itself to scrutiny; an app that asks for trust without any of that has not.
One further consideration is post-quantum readiness. Security commentary has noted uneven progress across messaging platforms, describing Signal and Apple as already offering post-quantum protections while Android messaging protocols had reportedly not received comparable upgrades. Standards bodies including NIST and CISA have shifted to urging faster migration, driven partly by “harvest now, decrypt later” collection, in which encrypted data is gathered today in hopes of decrypting it once sufficiently capable quantum computers exist. For household messaging this is a long-horizon concern rather than an urgent one, but it is one more item an app’s security documentation may address.
A Checklist Before You Switch
Run through these points before moving your conversations:
- End-to-end encryption is on by default for chats and calls, not an optional mode buried in settings.
- Backups are either end-to-end encrypted with keys you control, or the gap is clearly documented.
- The privacy policy states specifically what is collected and shared, with no advertising data practices you are unwilling to accept.
- You can verify a contact’s identity inside the app.
- The code is open or has been independently audited, and the security design is documented publicly.
- Disappearing messages and account deletion exist and work the way you expect.
- You have a plan for the accounts you are leaving behind, since an abandoned account on an old app is one more place your data sits.
Worth doing
Encryption and data collection are separate questions. An app can encrypt every message and still collect contacts, usage patterns and profile details, so check the privacy policy even after confirming the encryption.
Switching apps is also a good moment to shrink your overall exposure instead of carrying it along. Our guide to cleaning up old online accounts explains how to close the accounts you no longer use before they become a liability. And if you are unsure what your internet provider can see about your traffic in the first place, our honest look at whether you need a VPN covers what one hides and what it does not.
The essentials
- In one Electronic Frontier Foundation evaluation of 39 messaging products, only six passed all seven security criteria, and several popular apps met just two.
- End-to-end encryption protects message content, not metadata, not the devices at each end, and not copies stored in ordinary cloud backups.
- FTC cases against Flo Health and the makers of Kuuhuub show app companies sharing or collecting data after promising privacy, so read the policy, not the marketing.
- Check where message history is backed up and who holds the encryption keys, because a backup can undo the protections in the chat itself.
- Open code, documented security design and an independent audit are the main ways to verify a privacy claim before you rely on it.
Reader questions
Does encryption in transit mean my messages are private?
No. Transit encryption protects messages while they move but leaves them readable at servers in the middle, including the provider’s. End-to-end encryption, with keys held on your devices, is what keeps the company itself from reading them.
Can the app maker still see data if messages are end-to-end encrypted?
Often yes. Message content is protected, but metadata such as usernames and contact details, plus the usage data described in the privacy policy, may still be collected. The FTC has settled cases with app makers that shared user data after promising to keep it private.
Do disappearing messages guarantee deletion?
Not automatically. Check whether deletion applies on both sides of the conversation and whether backups retain copies afterward. The EFF has flagged secure deletion as a feature many messaging tools lacked.
Is a paid messaging app more private than a free one?
Price alone tells you little. What matters is the encryption design, the privacy policy, whether the code can be reviewed and whether the app has been independently audited, not the fee.
We describe how services generally work; features, settings and terms change often, and they differ between companies. This is general information, not legal advice. Check the provider’s current policies and official sources such as FTC.gov.