Incident #CBCC0E · 30 OCT 2026minor
Google Play tightens developer rules on location, contacts, storage, local network and accessibility permissions
Google Play's developer-facing policy text now lists dated requirements: location button and a declaration for precise location, restricted contacts access, new declarations for manage-contacts and local network permissions, and a rule on AppFunctions not deceiving AI agents. Storage and accessibility API wording was rewritten, with an explicit ban on using the Accessibility API to bypass security, record call audio or power autonomous agents. Attempts to mislead Play reviewers are now expressly prohibited.
Won back
- Apps must use the location button or justify precise location with a declaration, limiting location collection by apps
- Broad contacts access restricted to apps whose core function needs it, otherwise a contact picker is required
- Accessibility API barred from bypassing security controls, recording remote call audio or powering autonomous agents
- AppFunctions must not deceive or manipulate AI agents or bypass security controls
- New declaration requirements for manage-contacts and local network permissions
Evidence · 4 of 4 quotes matched in source
To use `ACCESS_FINE_LOCATION`, you must submit a Play Console declaration justifying why coarse location or the location button is insufficient.+ inserted · ✓ matched in source
The Accessibility API is prohibited from being used to bypass Android security and privacy controls, record remote call audio or power autonomous decision-making agents.+ inserted · ✓ matched in source
Developers must ensure that their AppFunctions do not deceive or manipulate AI agents, bypass security controls or interfere with other applications.+ inserted · ✓ matched in source
Attempts to manipulate Play review processes, including misleading reviewers as to the purpose and functionality of your apps, are strictly prohibited.+ inserted · ✓ matched in source
Archived version ↗ · 1,306 words changed