Android phones have always worked in the background. Google’s new Play terms make that quiet behavior much harder to ignore.
The updated Google Play Terms of Service take effect July 29, 2026, and spell out that system services on certified Android devices can use network connectivity, including cellular data, while the user isn’t actively using the phone. That includes moments when the screen is locked.
The timing adds weight. The revised terms follow Google’s $135 million settlement over allegations that Android devices sent cellular data to Google while idle without users knowing. Google isn’t saying every Android phone is secretly torching data plans, but it’s putting clearer language around behavior users usually notice only after something annoying happens.
Why Google is spelling this out now
The old assumption was simple. If a phone is locked and sitting on a table, most people expect it to be mostly still.
Google’s new wording makes that assumption harder to keep. System services include Google Play services, the Play Store, and Android operating system updates. These pieces can require network access to keep certified Android devices running properly.
Some of that activity can happen while the phone is idle. That helps explain why mobile data can move even when the user hasn’t opened an app or touched the screen.
What Android can still do quietly
The practical effect is clearer language with real consequences. A phone can keep handling system-level work through Google Play services, the Play Store, and Android updates in the background.
If that activity uses cellular data, the carrier bill still belongs to the user. That may be a shrug on unlimited plans, but it hits differently on prepaid service, roaming, or a tight monthly cap.
The terms don’t say every Android device will suddenly chew through data overnight, but they do confirm that background cellular data use is part of how these services can operate.
Where user control gets fuzzy
The update language is the more uncomfortable piece. Users may be able to manage some updates in Google Play settings, but certain updates can still happen if they fix a critical security issue, address a serious operability problem, or prevent abuse.
That tradeoff makes sense, and it’s still frustrating. Automatic updates protect people from real risks, but a bad rollout can change how a phone behaves after a reboot.
Anyone who has delayed updates after a broken release will recognize the tension. Android gives users plenty of switches, yet some system-level decisions still sit above those switches. If you’re on limited data or careful about updates, treat Android system services as active by default, not silent by default.
