Google to bring an Android 11 feature that auto-resets permissions granted to apps that haven't been used in months, to phones running Android 6 and above
Jon Porter / The Verge :
Context & Ripple Effects
Google’s permission controls have moved from an earlier à la carte permissions proposal toward Android 11’s temporary permissions and scoped-storage requirements. Extending an inactivity-based safeguard to older releases makes that privacy model relevant beyond the newest OS cohort.
The related coverage also shows Google later applying an unused-app policy to storage through auto-archiving, reinforcing a broader effort to make dormant software retain less access and less device footprint.
First-order effects
- Users of Android 6-and-later phones gain automatic removal of permissions from apps left unused for months, reducing the access those dormant apps retain.
- App developers with infrequently opened apps will need to request permissions again when users return, making permission recovery part of the reactivation flow.
Second-order effects
- Developers have greater incentive to minimize the permissions requested at relaunch, since unnecessary prompts create a direct point of friction for returning users.
- Google narrows the privacy difference between newer Android releases and the large installed base on older versions, reducing developers’ ability to treat legacy devices as a less-restricted permission environment.
Third-order effects
- If Google continues pairing temporary, inactivity-based, and storage-related controls, Android permissions become less of a one-time grant and more of an access state that must be continually justified by use.
- Platform-level management of dormant apps shifts privacy enforcement away from users remembering every old installation and toward operating-system defaults.
The trend: Android is moving toward lifecycle-based app privacy, where unused software progressively loses access rather than retaining it indefinitely.