Google Play Policy Changes: A Checklist for App Owners

Google Play updates its Developer Program Policies several times a year, and every update comes with a date after which non-compliant apps can be blocked or removed. Google's Policy Deadlines page is the official list. The entries below were read on 3 November 2026. Each is marked as in force (the date has passed) or upcoming, so you know what to fix now and what to schedule.

Already in force

• Anonymous and random chat apps (26 August 2026). Three policies were widened: such apps may not target children, must follow the Child Safety Standards policy, and fall under the age-restricted content policy. Only relevant if you build chat or social features.
• Register your apps for developer verification (30 September 2026). Play asks developers to check the Console home page and register anything missing, to avoid removal. Our post on developer verification explains it.
• Target API 36 for new apps and updates (31 August 2026). Covered in the target API post. The extension to 1 November has now ended.
• Financial features declaration (from 30 October 2025). Google said every app on an account must complete it, even with no financial features, before updates can be made. If an old account still shows it pending, finish it first.
• 180-day appeal window. From the same October 2025 announcement: account terminations can be appealed for 180 days.

Upcoming: 27 January 2027

• Contacts. Apps that do not need broad access to a user's contacts must use the Android Contact Picker instead.
• Precise location. Apps targeting Android 17 (API 37) or higher must use the Android location button for one-time or infrequent precise location. If core functionality needs broader fine-location access, a Play Console declaration is needed.
• Call log permission. Account verification by phone call will no longer be an allowed use of the call-log permission. Google points to the Digital Credentials API or SMS Retriever instead.
• Geofencing. It is removed as an approved reason to run a foreground service. Use the Geofence API.
• Subscriptions with ongoing eligibility-based discounts, such as student plans, must clearly disclose who qualifies, how it is checked and what happens to price and benefits afterwards.

Upcoming: April and August 2027

• 14 April 2027: developers building AppFunctions must follow all Play policies and may not deceive or manipulate AI agents.
• 25 August 2027: the local network permission is restricted to apps that need it for core functionality when device pickers are not enough, and apps targeting API 37 or higher must file a declaration. The manage-contacts permission gets a similar declaration rule.

Account rules worth knowing

Personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in continuously for 14 days before applying for production access. Google says review usually takes seven days or less, and that this page does not cover organisation accounts. For a business, a registered organisation account is often the better long-term choice, and it avoids tying the app to one person. Our Play Store launch guide walks through it.

Why these changes matter to a business owner

Most of the 2027 rules share one idea: ask for less. Google wants apps to use a system picker, which shows the user a screen, instead of holding standing access to the whole address book or a continuous location trail. For a shop, clinic or school app, that is usually good news. A picker needs less justification, creates less personal data for you to protect under India's data-protection law, and avoids the review delays that come with sensitive permissions.

The cost falls on apps that were built years ago with broad permissions out of habit. A delivery app that tracks a rider in the background still has a valid reason. A loyalty app that reads the full contact list to find friends probably does not, and it is better to change that before a rejected update forces the issue. If you are not sure which group you are in, the permission list in the manifest file will tell your developer within minutes.

A compliance checklist

1. Open the Policy status page in Play Console and clear any warning.
2. Confirm that the financial features declaration and the data safety form are complete and accurate.
3. List every permission in your manifest, and write down the business reason for contacts, location, SMS, call log and local network.
4. Replace broad permissions with system pickers where possible, which also removes a privacy risk.
5. If you sell subscriptions with discounts, rewrite the offer screen to disclose eligibility and what happens after.
6. Keep a dated note of each policy you reviewed, so the next audit is quick.

Dates on the Policy Deadlines page can change, so re-read it before each release. VS Tech Builders reviews permissions and declarations as part of every Play Store publishing job; if your app is already live and you are unsure, ask us to review it.

Sources

Checked on 3 November 2026. Technology changes quickly; always confirm details with the official source before you act on them.

• Policy Deadlines — Play Console Help
• Upcoming Android and Google Play deadlines — Android Developers
• Policy announcement: October 30, 2025 — Play Console Help
• App testing requirements for new personal developer accounts — Play Console Help

Frequently asked questions

Where can I see Google Play policy deadlines?

Google lists them on the Policy Deadlines page in the Play Console Help Center, with the announcement date for each change. Android Developers also keeps an Upcoming Android and Google Play deadlines page. Your own Policy status page in Play Console shows warnings that apply to your specific apps, so check all three before a release.

What happens if my app does not meet a new Play policy?

Google gives a deadline for each change, generally at least 30 days after announcement and often much longer. After that date, updates can be rejected or the app can be limited or removed, depending on the policy. Play Console warnings usually arrive before enforcement, so fixing them early keeps your updates unblocked.

Do the 2027 contacts and location rules apply to all apps?

The contacts rule applies to apps that do not need broad access to contacts. The location button requirement applies to apps targeting Android 17 (API 37) or higher, with a declaration route if broader access is essential. Both are dated 27 January 2027. Apps that need neither permission are not affected.

Do I need 12 testers before publishing my first app?

Only for personal developer accounts created after 13 November 2023. Google requires at least 12 testers opted in to a closed test for 14 continuous days before you can apply for production access. The help page I read does not address organisation accounts, so check Play Console for the rules shown on yours.