What Ends Up in Your Phone Backup

Whether your conversations with a companion app appear in your phone’s backup depends on two things you do not control: where the app stores its data, and which storage locations the app marked as backup-eligible. Both major mobile platforms let a developer flag directories to include or exclude, so two apps with identical features can behave completely differently when you restore a device.

The practical consequence is that a phone backup is an unreliable archive and an unreliable eraser. It may hold more of your chat history than you expected, or none of it.

Backups copy files, not accounts

A device backup is a copy of on-device state: app containers, settings, keychain items, photos, and system databases. It is not a copy of anything held on a company’s servers.

That distinction decides almost everything. If a companion app keeps conversation history server-side and the phone holds only a cache and a login token, your backup contains essentially nothing of your conversations — the history reappears after a restore because the app fetches it again, not because the backup preserved it. If the app keeps history in a local database and does not exclude it, your backup contains the conversations themselves.

You usually cannot tell which from the outside without testing, and the test is awkward: sign out, clear the app, restore, and see what returns. A softer signal is what the app does with no network connection, which is the subject of what airplane mode tells you about an app.

Cloud backup versus local backup

The two paths have different exposure profiles and it is worth knowing which you use.

A cloud device backup lives in your platform account and is protected by that account’s credentials and second factor. Some platforms encrypt backups so that only your device can read them; some hold a key that the provider can use, which is what makes provider-side recovery of a forgotten password possible at all. If your platform offers a stronger end-to-end option for backups, turning it on is one of the highest-value privacy settings on the whole device, and it protects far more than one app.

A local backup to a computer puts the archive on a disk you control. On some platforms an unencrypted local backup is readable with ordinary tools, which means anyone with access to that computer can browse app data without unlocking your phone. If you take local backups, encrypt them.

A synced folder is not a backup and a backup is not sync. Chat history that appears on two devices is being synced through the app’s servers, not through your backup, and it obeys the app’s rules rather than your platform’s.

Backups are why deletion does not always stick

This is the part people discover late. If you delete an account, clear an app, then restore your phone from a backup taken before the deletion, local remnants can come back. The account is gone; the files on the device are not, because the backup predates the cleanup.

Restoring an old backup rolls back your device state, including the parts you cleaned up. It can also restore a stale login token, a cached avatar, a keyboard dictionary that learned a persona’s name, and app settings you had changed. What survives a deliberate cleanup is covered in more detail in what account deletion leaves on your device, and the difference between removing an app and closing an account is covered in deleting the app is not deleting the account.

If you want a clean device, restore and then clean, in that order. Cleaning before a restore accomplishes nothing.

Excluding one app from a backup

Both platforms let you turn backup off per app, and it is a reasonable choice for a conversational app whose history you do not need to preserve locally.

The tradeoff is symmetrical and worth stating plainly. Excluding the app means a restored phone starts that app fresh: no local cache, no local settings, and no local history if history was local. If the app is server-backed, you will barely notice, because signing in restores everything. If the app is local-first, you will lose the conversations. There is no way to get selective exclusion — the switch is per app, not per file.

Check the per-app backup list once, after installing anything you would rather not archive. It is buried in the same settings area as your backup size breakdown, and that breakdown is itself informative: an app consuming a large amount of backup space is storing a lot locally.

Switching phones is a different operation

A restore and a migration are not the same event, even though both end with your apps on a new device. Direct device-to-device transfer moves more than a cloud restore does on some platforms, and app-store-based reinstallation moves less than either. Which one you use changes what carries over, and that is covered separately in what changes when you switch phones.

What this does not tell you

Backups are about your copy. They say nothing about the company’s copy, which is governed by a retention policy rather than by your settings, and which continues to exist whether or not your device holds anything.

They also cannot be audited from the outside with any confidence. You can see how much space an app occupies in a backup, and you can observe what returns after a restore, but you cannot enumerate the contents of a modern encrypted device backup file by inspection. Treat the space figure as a hint and the restore test as the only real evidence — and treat the whole subject as one input into privacy hygiene rather than the centre of it.