Comply with Google Play October 2026 Policy Updates

Google Play announced policy updates on October 29, 2026. Developers have at least 30 days from that date to update apps for the new rules. These changes restrict certain permissions, clarify AppFunctions usage, and update subscription disclosures.

This guide walks through the key updates and the exact steps to stay compliant in Play Console.

Key New Policies from October 29

The announcement introduces three new policies.

The Local Network permission is now restricted. Only apps that need it for core functionality may use it when device pickers are not enough. Apps targeting Android 17 (API 37+) must submit a Play Console declaration.

The Manage Contacts permission follows the same pattern. It is limited to apps that require broad contact access for core features. All other apps must switch to narrowly scoped platform intents. A Play Console declaration is required.

AppFunctions API users must follow all existing Google Play policies. AppFunctions cannot deceive or manipulate AI agents, bypass security controls, or interfere with other apps.

An updated policy covers subscriptions with ongoing eligibility-based discounts (for example student plans). You must clearly disclose eligibility criteria, the verification process, and what happens to pricing and benefits after eligibility ends.

Clarifications That Matter

Google also clarified several existing policies. Enforcement standards stay the same, but the wording is sharper.

Location permissions require the minimum scope needed. For apps targeting Android 17, one-time or infrequent precise location requests must use the Android location button. Apps requesting ACCESS_FINE_LOCATION need a Play Console declaration if coarser options are insufficient.

All Files Access (MANAGE_EXTERNAL_STORAGE) reminders restate the minimum-scope principle.

Accessibility API guidance clarifies the isAccessibilityTool flag and disclosure requirements.

Deceptive Behavior now explicitly covers manipulation of the app review process.

Families Self-Certified Ads SDK Program is open to new applicants. Check the current list of participating SDKs in the Help Center and SDK Index.

Cryptocurrency rules expand Hong Kong licensing requirements.

SMS and call log permissions add an exception for certain government or MNO apps for QoS reporting. The SMS User Consent API is listed as a preferred alternative. Phone-call account verification via READ_CALL_LOG ends on January 27, 2027.

Step-by-Step Compliance Actions

1. Review the full policy announcement in Play Console Help. Note the 30-day minimum window from October 29, 2026.

2. Audit your app for Local Network and Manage Contacts permissions. If you target API 37+ and still need the full permission, prepare a declaration. Otherwise migrate to system pickers or intents.

3. For contact access, prefer the Android Contact Picker where possible. See our earlier guide on Android 17 Contact Picker for implementation details.

4. If you ship AppFunctions, re-read the prohibitions. Do not use them to influence AI agents or other apps. Cross-check with our AppFunctions guide.

5. Update any student or eligibility-based subscription listings. Add clear text for eligibility rules, verification steps, and post-eligibility changes.

6. Complete the Play Console declarations for any restricted permissions you still request. Incomplete declarations can block submission.

7. Declare your trader status in Play Console if required. This becomes mandatory starting November 2026 for applicable developers.

Watch the Official PolicyBytes Video

Google published a short PolicyBytes episode covering these updates.

Additional Reminders and Deadlines

• Play Age Signals API is available for age-appropriate experiences.
• Japan payment authorization is due by December 1, 2026 for sellers into or out of Japan.
• New app quality requirements on memory and code optimization have a February 2027 compliance deadline.
• Games for cars are now generally available on open testing and production tracks.

Check the Policy Deadlines page for the latest effective dates.

Tips for a Smooth Submission

Test permission flows on a device running Android 17 or the latest emulator image. Confirm that pickers and the location button appear when expected.

Document why a restricted permission is required before you write the Play Console declaration. Vague answers are more likely to be rejected.

Keep a changelog of policy-related code and listing changes so you can respond quickly if a reviewer asks for clarification.

Conclusion

The October 29, 2026 updates tighten permission rules and add transparency requirements for subscriptions and AppFunctions. Most teams can meet them by switching to system pickers, adding declarations, and updating store listing text. Complete the Play Console steps before your next release to avoid submission delays.

Sources

• Policy announcement: October 29, 2026 — Play Console Help
• Google Play PolicyBytes - October 2026 policy updates (YouTube)
• Permissions and APIs that Access Sensitive Information policy pages
• Policy Deadlines page