Before erasing your old phone, don't just check that a backup exists; assess whether you can restore it too.
What protection does a cloud backup have?
If your conversation is end-to-end encrypted but a separate backup is stored in the cloud without suitable encryption, your old messages may not have the same protection as your live conversation. To assess the security of an end-to-end encrypted chat backup, examine its storage location, backup encryption and recovery access separately from the security of messages in transit.
Key points
- End-to-end encryption of messages alone does not guarantee that the cloud backup has the same protection.
- To assess a secure messaging service's cloud backups, ask where the data is stored, who holds the key and whether encryption takes place on the device.
- If the cloud storage provider can decrypt the backup, its protection is not the same as a copy whose key is held only by the user.
- According to Livara's documentation, direct chats and compatible private groups with E2EE active are end-to-end encrypted; an incompatible older group may explicitly be outside E2EE. Channels are public and server-readable, and routing metadata is stored.
Why doesn't message encryption guarantee backup security?
Encrypting the conversation itself does not, on its own, guarantee the security of its backup. End-to-end encryption protects the conversation's content, but a backup is a separate copy and may have different storage and access rules.
If the app sends your history to the cloud, ask how the copy is encrypted before upload and who holds its key. Encryption of the original communication and encryption of the stored file are two separate layers; the presence of one does not establish the presence of the other.
To understand the general boundaries of this concept, read the guide to what end-to-end encryption protects and what it doesn't. Ask about the stored copy itself, not just whether “messages are encrypted.”
Where do old messages remain after a backup?
Old messages may remain on the device, in the cloud backup or in both places; the exact location depends on the app's settings and backup method. A backup is useful for recovery after replacing or losing a phone, but it creates another copy of the data that needs separate assessment.
To find those copies, don't look only inside the messaging app: also list the selected cloud account, the old device, linked devices and exported files. The existence of a backup file does not mean it can be restored; the required password or key and the recovery method must be accessible.
What should a secure messaging service's cloud backup make clear?
A secure messaging service's cloud backup should make clear what data is copied, where it is kept and who can decrypt it. The word “encryption” alone is not enough: you need to know whether the user holds the key or the service provider also has access to it.
With end-to-end encrypted backups, the copy is encrypted on the device before it is sent, and the decryption key remains with the user or their trusted devices. If the storage service has access to the key, this differs from a model in which the service cannot decrypt the backup. Check the service's technical explanation, not just the feature's marketing name.
Also check whether backups are enabled by default or need to be turned on, what data they include and how to stop or delete them. Turning backups off does not necessarily delete earlier copies; check the service's own controls for that.
Are WhatsApp backups encrypted?
WhatsApp offers end-to-end encrypted backups, but you need to check their status in your own account. In the app, go to Settings → Chats → Chat backup → End-to-end encrypted backup; menu names vary by language and version. WhatsApp's official guide explains the recovery conditions.
In October 2025, Meta introduced a passkey-based backup encryption option. Check the options available in your own version; do not assume every account has exactly the same recovery method. Before erasing your old phone, make sure you have access to the authentication method, password or key actually required.
An encrypted backup reduces the risk of the storage provider accessing the plaintext, but someone who gains access to your unlocked device, the required accounts or your recovery secret can still pose a threat.
How can I assess access to a backup?
To assess access, examine the chain of accounts and devices that lead to the backup:
- Check which cloud account is selected for backups and which devices have access to that account.
- Establish whether the provider can decrypt the backup's content.
- Check who can restore the copy if you forget your password or lose your device.
- Find out how to stop backups and delete stored copies.
- To understand ancillary data such as sending time and message destination, read the guide to what messaging metadata reveals; encrypting content does not necessarily hide this information.
These checks alone do not establish that an account has been hacked or a backup exposed; the aim is to understand protection boundaries and access paths.
How does Livara distinguish old messages from backups?
In Livara's security documentation, cryptographic identity backups are distinguished from chat-history backups: v7 is described as recovering identity and keys, not automatically restoring history. Take this difference seriously when changing phones; successful account login alone does not establish that old messages will return.
This explanation describes the product's declared architecture; it is not an independent recovery test. Before deleting the only existing copy, test the supported method with non-sensitive data and keep your recovery phrase somewhere safe. Public-channel content should not be treated like a private conversation either.
What should I do before enabling backups?
Before enabling backups, decide how much recovering old messages matters to you and what data you are entrusting to another storage location in return. Check the service's actual settings, the connected cloud account, authorized devices and options for stopping or deleting backups. If you cannot find a clear explanation of the encryption key or provider access, do not make assumptions about them.
If you need a backup to move to a new phone, make sure the recovery method is documented and accessible before erasing your old phone. If retaining history is not a priority, turning off cloud backups can prevent further copies from being created; messages may nevertheless remain on other devices or in other accounts.
Frequently asked questions
If messages are end-to-end encrypted, is the backup automatically encrypted too?
Not necessarily. Message encryption and backup encryption are separate features. Check the backup setting and the service's explanation of who holds the decryption key.
If a backup is in Google Drive or iCloud, who can read it?
The storage location alone does not answer that question. Access to the content depends on the type of backup encryption, where the key is held and the active settings; check these in the service's documentation.
Does turning off cloud backups delete every copy of the messages?
Not necessarily. Turning backups off may prevent subsequent copies, but it does not establish that earlier copies have been deleted from the cloud or other devices. Check the controls for managing and deleting copies.
Are Livara's public channels end-to-end encrypted too?
No. Livara channels are public, server-readable and not end-to-end encrypted; their content should not be considered private or hidden from the public. According to the provider's documentation, direct chats and compatible private groups with E2EE active are end-to-end encrypted; incompatible older groups fall outside this coverage. Check the status of the particular conversation.
