We're expanding our Families Policy Requirements policy to prohibit developers of anonymous chat apps from targeting children.

We're expanding our Age-Restricted Content and Functionality policy to apply to anonymous chat and random chat apps.

We're expanding our Child Safety Standards policy to apply to anonymous chat and random chat apps.

Android developer verification goes into effect. Apps from participating stores in Brazil, Indonesia, Singapore, and Thailand must be registered by a verified developer to be installed on certified Android devices.

We're also updating Play Console requirements to meet Android developer verification requirements. While 99% of apps on Play have been registered automatically, you should check your Play Console Home page to register any remaining apps to avoid global removal from Google Play and ensure a seamless user installation experience.

We're removing geofencing as an approved foreground services use case. Developers can instead use the Geofence API for this use case.

We're introducing the Contacts Permission policy to govern broad access of users' contacts. Apps that don't need broad access must use the Android Contact Picker, a more secure, easy-to-integrate alternative that minimizes data collection and improves user safety.

We're updating the Location Permissions policy. To meet our minimum scope requirements, apps targeting Android 17 (API 37+) must now implement the Android location button for one-time or infrequent precise location requests. If your app's core functionality requires broader ACCESS_FINE_LOCATION access, you must submit a Play Console declaration justifying why the location button or coarse location is insufficient.

Our SMS and Call Log Permissions policy will no longer permit account verification via phone call as a use case for the READ_CALL_LOG permission. To securely verify accounts without requiring sensitive app permissions, use the Digital Credentials API instead, either directly or through a verification provider built upon it, or the SMS Retriever API. Please refer to this page for additional alternative APIs.

Subscriptions with ongoing eligibility-based discounts, such as student plans, must clearly disclose eligibility criteria, the verification process, and post-eligibility pricing and benefit changes.

AppFunctions API: Developers building AppFunctions must comply with all existing Google Play policies. AppFunctions are strictly prohibited from deceiving or manipulating AI agents, bypassing security controls, or interfering with other applications.

Local Network Permission: This permission is restricted to apps that need it for core functionality when device pickers are insufficient. Apps targeting Android 17 or higher (API 37+) must submit a Play Console declaration to use this permission.

Manage Contacts Permission: This permission is restricted to apps that need it for core functionality when system pickers are insufficient and apps must submit a Play Console declaration to use it. All other apps must use narrowly scoped platform intents.