Google Play Developer Program Policy Update

Please review Google Play Developer policy updates. View as webpage DEVELOPER UPDATE Hello Google Play Developer, As part of our commitment to maintaining security and transparency on Google Play, we're sharing our latest round of policy updates. How does this affect my apps? This is a mandatory service announcement sent to all Google Play developers. To save you time we've provided the executive summary below. You only need to click through to the full policies if your app uses these specific features. To view a log of your recent updates and monitor each app's submission activity, please check the submission activity in your Google Play Console. If applicable, you have at least 30 days from today to update your app. See our Policy Deadlines for specific timelines. Summary of changes: New policies 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. 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. Updated policy Subscriptions with ongoing eligibility-based discounts: 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. Clarifications (Our enforcement standards and practices remain the same) Permissions and APIs that Access Sensitive Information Location permission: As a reminder, this policy was announced last April and will become mandatory on January 27, 2027. To help you be prepared, we've clarified and added helpful information to the upcoming policy. Apps must use the minimum location scope necessary for its core functionality. For apps targeting Android 17 (API 37+), this includes mandatory use of the Android location button for one-time or infrequent location requests. Apps using ACCESS_FINE_LOCATION must complete a Play Console declaration to justify why coarse location or the location button is insufficient. All Files Access Permission: We've reiterated minimum scope principles to support developer comprehension of the use of the MANAGE_EXTERNAL_STORAGE permission. AccessibilityAPI: Clarified the policy summary on the isAccessibilityTool flag usage and disclosure requirements based on app designation. Deceptive Behavior: Clarified that developers and apps cannot engage in behaviors that manipulate the app review process. Families Self-Certified Ads SDK Program: New applicants can now join this program. Review the list of participating SDKs and self-certified versions in the Help Center and in SDK index. Cryptocurrency: Expanded Hong Kong licensing requirements to include the Virtual Asset Trading Platform license, and introduced an "Additional Options" section for apps qualifying for local regulatory exemptions. Use of SMS or Call Log permission groups Added an exception allowing Government or Authorized Mobile Network Operator apps to use the READ_CALL_LOG permission for Quality of Service reporting and clarified that apps utilizing the backup and restore exception must demonstrate the ability to restore data back to the device’s default handler. Added the SMS User Consent API as a privacy-preserving alternative for account verification. As a reminder, on January 27, 2027, account verification via phone call will no longer be a permitted use case for the READ_CALL_LOG permission and you must use an alternative API instead. Payments: We're providing additional guidance on how our Payments policy applies to Google Play apps that facilitate digital purchases through AI or agentic experiences. Reminders and additional information We're launching Play Age Signals, a new privacy-friendly, age-appropriate experience for families that will be available globally to all developers. Use The Play Age Signals API to tailor features, content, and safety settings to your audience. If you sell into or out of Japan, you must complete authorization by December 1st, 2026, or your payments will be held globally. Find out if this requirement applies to you and learn how to complete the authorization form. Starting in November 2026, you must declare your trader status in Play Console in accordance with new Console requirements. As recently announced, the games category has graduated from beta to general availability. All developers who want to build games for cars can now publish to the open testing and production tracks on Google Play for these form factors. We recently announced a February 2027 compliance deadline for new app quality requirements regarding memory and code optimization thresholds. Please review these requirements to maintain your app's visibility and publishing capabilities on Google Play. We have updated our Android XR app quality guidelines for Immersive and Augmented experiences. Please review these guidelines if you are building apps for XR headsets, Wired XR Glasses, or Audio & Display Glasses. To learn more about complying with these changes, read our full Policy Center announcement, watch our PolicyBytes video, or submit your questions in advance to our Policy Webinar. REVIEW UPDATES Thank you, The Google Play team Connect with us © 2026 Google LLC 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA You have received this mandatory email service announcement to update you about important changes to your Google Play Developer account.