In plain terms: Google Play has updated its rules on personal data and several technical capabilities, and the Policy Deadlines page in Play Console lists January 27, 2027 for part of these changes. If your app touches contacts, precise location, the call log, geofences or discounted subscriptions, this concerns you. Below is each change, what it means in practice and where to start checking.

Three dates to put in your calendar

DateWhat changes
January 27, 2027Contacts, location, READ_CALL_LOG, geofencing in foreground services, subscriptions with ongoing eligibility-based discounts
April 14, 2027The AppFunctions API must comply with Google Play policies
August 25, 2027Local Network and Manage Contacts: restrictions and Play Console declarations

Dates come from the Play Console Help "Policy Deadlines" page. Check it before planning work, since Google may refine the timelines.

1. Contacts: Contact Picker instead of broad access

Apps that do not need broad access to contacts must use the Android Contact Picker. It is a system picker where the user chooses the contacts to share and the app receives only those. It is available from Android 17, needs no permission and collects less data.

A related platform change: apps that target the next Android release will no longer be able to write to contacts directly with WRITE_CONTACTS. Instead you use the ACTION_INSERT, ACTION_EDIT and ACTION_INSERT_OR_EDIT intents, which need no permission. For a small set of apps with broad needs (for example contact managers or background sync with an enterprise account) a special MANAGE_CONTACTS permission arrives, with a declaration in Play Console. This does not affect apps targeting older versions.

What to check: search your code for WRITE_CONTACTS, direct ContactsContract writes and applyBatch, replace user-initiated actions with intents, and decide whether you really need broad access.

2. Location: the location button as the minimum scope

The updated policy names the location button as the recommended minimum scope for precise location. In practice: if your app requests precise location, justify why it is needed continuously and consider a flow where location is requested at the moment of the user's action. We wrote about the consequences of background access in our article on location and background tasks.

3. READ_CALL_LOG: phone-call verification no longer fits

Account verification through a phone call is no longer a permitted use of READ_CALL_LOG. If your sign-in or number confirmation relies on reading the call log, you will need to replace that flow with a different verification method.

4. Geofencing in foreground services

Geofencing has been removed from the approved foreground service use cases. For these scenarios Google points to the Geofence API. If your app keeps a notification-bearing service running only to track geofences, its architecture needs a second look.

5. Subscriptions with eligibility-based discounts

Subscriptions with ongoing eligibility-based discounts (for example student or regional pricing) must clearly disclose the eligibility criteria, the verification process and the price after eligibility ends. Check your paywall, your Play Console listing and the subscription management screen: all of it should be clear before purchase. For monetization models, see also our piece on subscriptions versus one-time purchases.

What comes next: 2027

By April 14, 2027 the AppFunctions API must comply with Google Play policies: deceiving or manipulating AI agents, bypassing security controls or interfering with other apps is prohibited. By August 25, 2027 Local Network access is restricted to apps that need it for core functionality when system pickers are insufficient, and apps targeting Android 17 (API 37+) must submit a declaration in Play Console. The same logic applies to the Manage Contacts permission.

January checklist

  1. List every sensitive permission in your manifest: contacts, precise location, call log, foreground services.
  2. For each, write down which feature it enables and whether narrower access would do.
  3. Replace broad contact access with the Contact Picker and intents.
  4. Review discounted subscriptions: criteria, verification, price after the discount ends.
  5. Update Data safety and your privacy policy, as described in our article on privacy manifests, ATT and Data safety.
  6. Add these checks to your release checklist.

The rule across all of these changes is the same: request the minimum access, explain it to the user, and build sensitive capabilities on system components.

Sources: Play Console Help: Policy Deadlines; Play Console Help: Google Play Policy Update, April 15, 2026; Android Developers Blog: A more reliable way to add and edit contacts on Android.