Android Per-App Backup Controls Explained: What You Actually Give Up
Google is rolling out Android per-app backup controls to Pixel devices, letting users see exactly which apps are storing data to their Google Account and disable individual ones. 9to5Google spotted the feature two days ago; BGR confirmed it today. The rollout covers Pixel hardware running stable Android 16 and 17 with Google Play services version 26.24. Samsung devices checked at the same time did not show the feature, 9to5Google reported. Google has not published an announcement or confirmed any timeline for broader availability.
Android's Auto Backup system has been enrolling apps automatically since Android 6.0 with no mechanism for users to audit what was stored or opt out individual apps. That changes now, at least on Pixel.
How Android per-app backup controls work on Pixel
The new controls live at Settings → Accounts and backup → Google Backup → Other device data. Where the previous screen showed a single line reading "Apps & app data" with a count and combined storage figure, there's now a full "App data" section broken out by individual app, per 9to5Google and BGR.
The three apps using the most backup space appear at the top, each with a storage size and a toggle. Tapping "Show more" expands the complete list, including apps flagged as "No data backed up" at the bottom. Every app starts enabled.
Flip one off and Android surfaces an explicit warning: the app's existing backup data will be deleted from your Google Account, and no future backups from this device will be created for it, 9to5Google noted. The consequences are immediate and permanent. Android stores only the most recent backup per app, overwriting the previous one on each cycle, so once the deletion triggers there's no restore path, per Android Developers documentation.
One boundary worth knowing: these toggles apply to third-party app data only. SMS and MMS messages, call history, and device settings sit in a separate "Device data" section without individual controls, 9to5Google reported. If the "App data" section is absent from your Pixel's settings, the rollout hasn't reached your device yet. Non-Pixel Android users have no confirmed path to access it.
Why the old backup screen told users almost nothing
Auto Backup has enrolled every app targeting Android 6.0 or higher automatically, with no user opt-in required, per the Android Developers data backup overview. The system runs quietly once a day when the device is idle and on Wi-Fi, at least 24 hours after the previous cycle. Before this week, the only user-facing indicator was that single aggregate line: a count of participating apps and a combined storage figure. No breakdown, no participant list, no way to exclude any individual app.
Developers have always been able to restrict their own app's backup behavior using the android:allowBackup flag in the manifest, per Android Developers. A call made before the app ships, entirely invisible to users. The new controls give the user an equivalent lever for the first time.
Some coverage has framed these controls as a way to reclaim "precious cloud storage." That framing doesn't hold up. Backup data sits in a private partition of Google Drive, capped at 25 MB per app, and explicitly does not count against a user's personal Drive quota, per Android Developers. Disabling an app's backup doesn't free up a gigabyte of Drive space. The benefit is audit capability and selective control, not reclaimed storage.
Managing Google Backup per-app settings: what you actually give up
Before touching any toggle, the question worth asking is simple: does this app restore its own data through a login or account sync? If yes, the backup toggle is largely redundant. Sign back in on a new phone and the data comes back regardless of what Android's backup system did. If no, disabling backup means starting from scratch next time.
Restore happens automatically whenever an app is installed, whether during device setup, after a factory reset, or through a fresh Play Store install, per Android Developers. For a game that doesn't sync progress server-side, losing the backup means losing the save. For a password manager with its own encrypted cloud sync, or a productivity app tied to a Google or Microsoft account, it may not matter at all. The backup toggle only fills gaps the app itself doesn't cover.
The privacy case for disabling backup is narrower than it might seem. Auto Backup on Android 9 and higher is end-to-end encrypted using the device's PIN, pattern, or password, meaning the data is encrypted before it leaves the device and the remote storage provider cannot read it, per Android Developers. That's a meaningful protection. The EFF noted last year a separate concern: some apps run their own backup processes entirely outside of Android's system backup, and those may not carry the same encryption guarantees. A messaging app that independently backs up chat history to its own cloud servers operates under a different set of rules. The toggle in Google's settings screen doesn't govern that data at all.
A practical framework for deciding:
- Leave backup on for apps where saved state matters on a new device and there's no independent sync: productivity tools, games without server-side saves, apps whose data exists only locally.
- Consider disabling for apps with login-based restore that will come back whole through their own sync, apps with no meaningful state worth preserving, or apps where any cloud footprint is unwanted regardless of the encryption protections.
- The deciding question: If this app disappeared from your phone tonight and you reinstalled it fresh tomorrow, would Android's backup be the only way to recover its data? If yes, leave the toggle on.
The 25 MB per-app cap is also worth keeping in mind. Apps storing large amounts of data may already be hitting that ceiling, meaning the backup is partial by design, per Android Developers. What gets backed up is what the developer chose to include, not necessarily everything a user might expect to recover.
What this rollout means right now
The controls are live for Pixel owners on the right Play services version. For everyone else, they're not. Google hasn't said whether the feature will expand beyond Pixel or when, per BGR.
Auto Backup has been running silently on Android devices since 2015, accumulating snapshots of app state across potentially hundreds of installed apps, with users having no practical way to know which apps were participating or what was being stored. These controls don't change how backup works under the hood. They change what users can see and act on. Pixel owners can now audit that list and selectively opt apps out; everyone else still can't. Whether that gap closes, and how quickly, will say something about how seriously Google treats backup transparency as a platform-wide feature rather than a Pixel selling point.
Comments
Be the first, drop a comment!