Google Play Policy Changes 2026: What Indian App Owners Do

Google Play's policy update of 29 October 2026 gives app owners at least 30 days, so roughly until 28 November 2026, to meet new rules on local network access, contacts and AI agent functions. Two more dates are fixed: 27 January 2027 for location and call log rules, and February 2027 for app quality.

These Google Play policy changes 2026 affect many Indian apps, because OTP login, delivery, maps and invite features are common here. If your Android app asks for location, reads contacts or uses call logs to verify phone numbers, plan a review this month.

This post is for founders and business owners who already have an Android app, or are about to build one. After reading it, you will know which rules touch your app, which dates matter, and what to ask your developer.

Which Google Play policy changes 2026 matter to Indian app owners?

Google published the update on its Play Console Help page on 29 October 2026. We read the page in full. These are the changes that matter to most business apps:

• Local Network Permission (new): Allowed only for apps that need it for core functionality, when the standard device pickers are not enough. Apps targeting Android 17 (API level 37) or higher must submit a declaration in Play Console.

• Manage Contacts Permission (new): Also limited to apps that need it for core functionality. Other apps must use narrow platform intents (a built-in Android way to pick one contact without reading the whole list).

• AppFunctions API (new): Apps using it must follow all existing policies. They may not deceive or manipulate AI agents, bypass security controls or interfere with other apps.

• Subscriptions with ongoing discounts (updated): A student plan, for example, must disclose who is eligible, how eligibility is checked, and what price and benefits apply after eligibility ends.

• Location permission policy: Becomes mandatory on 27 January 2027. For apps targeting Android 17, one-time location needs should use the Android location button.

• Call log for phone verification: From 27 January 2027, READ_CALL_ LOG is no longer a permitted way to verify a phone number. Google earlier removed this use case in its 15 July 2026 update, and asks developers to switch to an alternative API.

• App quality: Memory and code optimisation requirements apply from February 2027.

• Trader status: Play Console starts asking developers to declare trader status from November 2026.

Google says developers have "at least 30 days" from 29 October 2026 to comply with the new and updated policies. That is why we use 28 November as the working date.

Sources: Policy announcement, 29 October 2026 and the Play Console announcements list, which shows the 15 July 2026 and 15 April 2026 updates.

Does my Android app need to change right now?

Probably not in the next week, but you should check this month. The local network declaration applies to apps that target Android 17 (API level 37) or higher. If your app still targets an older level, you have more time on that point. Target level is the Android version your app is built against.

The dates that apply to apps at any target level are different. The call log change on 27 January 2027 and the location policy on 27 January 2027 are fixed. A developer can check both in an afternoon by listing every permission your app requests.

The cost of waiting is real. An update that breaks a policy can be rejected at review, and a rejected update delays your own fixes and festival-season offers.

Which types of Indian apps are most affected?

The rules hit apps that handle phone numbers, places and contacts. Here is a plain mapping from app type to risk.

If your app is a basic catalogue or booking app that never asks for these permissions, most of this does not touch you. A short permission audit confirms that. Want a fixed number for your project? Send 3–4 lines on WhatsApp and get a written quote within 48 hours.

What should I do before 28 November and 27 January?

Treat this as a small, dated checklist. Most apps can finish it in one release cycle.

1. List every permission. Open your app's manifest file (the file that declares what the app may access) and write down each permission with the screen that uses it.

2. Remove what you do not need. Many apps carry permissions from old features or third-party libraries. If a library asks for contacts, ask whether you still need it.

3. Switch phone verification away from call logs. If you verify numbers through call log access, move to SMS or another supported method before 27 January 2027.

4. Prepare declarations. If you will target Android 17, draft the local network and location explanations now. Keep each reason short and tied to a core feature.

5. Check subscription screens. If you offer student or other eligibility-based discounts, add the eligibility and post-discount price text.

6. Test memory use on a mid-range Android phone, which is what many of your customers carry.

7. Release a build and check the Play Console messages for warnings before the deadline.

Your developer should also confirm that you, not the developer, own the Google Play account. We build every app so the client owns the code, store accounts and data from day one, and this is the kind of week when that matters. A Play developer account costs US$25 one time, and an Apple Developer account costs US$99 a year.

How much does a Play Store compliance update cost?

We do not have a standard published price for a compliance update. The work depends on how many permissions the app uses and how old the code is, so we quote it after a short review.

For context, a mobile app built from one codebase for Android and iOS starts from ₹14,999, and a complete app system runs ₹2.5–10 lakh. Other Indian cost guides quote ₹2– 25 lakh for apps overall, which shows how wide the range is. Our app development cost guide for India explains what moves the number.

A policy update is usually a small fraction of the original build, because it changes permissions and screens, not the whole app. Ask any developer for a written, fixed quote after they have seen your permission list, not before.

Who can handle this for my app?

If you built your app with us, send us the app name and we will check it against this announcement. If another developer built it, you can still bring the project to us. Because you own the code and the store account, there is no lock-in either way.

Our mobile app development team in Delhi reviews permissions, updates the app and handles the Play Console declarations. For apps built in Flutter (a Google toolkit that builds Android and iOS apps from one codebase), see our Flutter app development service. One person on WhatsApp stays on the project, and you get a working build every two weeks.

Keep one rule in mind from all of this. Google updates its Play policies several times a year, as the announcements list shows for January, April, July and October 2026. A yearly permission audit costs far less than an emergency fix after a rejected release.

Frequently asked questions

Do the Google Play policy changes in 2026 apply to my existing Android app?

They apply if your app uses the permissions or features the policies cover, such as location, contacts, call logs, the local network or student-style subscription discounts. Some points, like the local network declaration, apply only to apps targeting Android 17 (API level 37) or higher. A permission audit tells you which rules touch your app.

What is the deadline for the new Google Play policies?

Google gives developers at least 30 days from 29 October 2026 for the new and updated policies, so plan for about 28 November 2026. The location policy and the call log change take effect on 27 January 2027, and app quality requirements apply from February 2027.

Can I still use READ_CALL_LOG to verify phone numbers on Android?

No. Google lists phone-call verification as no longer permitted for READ_CALL_LOG, with the change effective on 27 January 2027. If your login verifies numbers through call logs, switch to SMS or another supported method before that date, and test the new flow on a mid-range phone.

What happens if my app does not follow a Google Play policy?

Google can reject an update, and for serious or repeated problems it can take further action on the app. The exact outcome depends on the policy. The safer approach is to check your permissions before each release and respond early to any warning in Play Console.

Who should own my Google Play developer account?

You should, not your developer. The account holds your app, your reviews and your payments. Registration is US$25 one time. At Ureka, the client owns the code, domain, store accounts and data from day one, so you can change developers without losing the app.