Google Play's October 2026 Policy Update: A Developer Checklist

Google Play's 29 October policy update brings trader status, a Japan payments deadline and January 2027 location and call-log rules. Dates, code for the location button, and a checklist.

Aditya BansalAditya BansalAuthor14 November 20264 min read 21 views
Google Play's October 2026 Policy Update: A Developer Checklist
In this article▾
  1. The deadlines, in order
  2. Location: what changes and why
  3. Adding the location button
  4. Manifest
  5. Compose
  6. Call log, contacts and local network
  7. Phone call verification
  8. Manage Contacts permission
  9. Local Network permission
  10. The smaller items worth a skim
  11. A checklist for this sprint

Google Play published a large policy announcement on 29 October 2026. Some items are clarifications you can skim, but a few come with dates: a trader status declaration this month, a Japan payments deadline on 1 December, and location and call-log changes that become mandatory on 27 January 2027. If you maintain an Android app, here is what matters, sorted by deadline, with the code you'll need for the location button.

The deadlines, in order

From the Play Console policy announcement of 29 October 2026, which gives developers at least 30 days to update for new and changed policies:

  • November 2026: trader status. Declare your trader status in Play Console under the new requirements.

  • 1 December 2026: Japan authorisation. If you sell into or out of Japan, complete the authorisation form, or your payments may be held globally.

  • 27 January 2027: location permissions. Use the minimum location scope your core features need; on Android 17 (API 37+), use the location button for one-time precise location; and file a Play Console declaration if you request ACCESS_FINE_LOCATION.

  • 27 January 2027: phone call verification. Stop using READ_CALL_LOG to verify accounts by phone call and move to an alternative.

  • February 2027: app quality. New memory and code optimisation thresholds to stay visible and publishable.

If you only do one thing this week, put the two January items in your sprint planning. They are the ones that touch code.

Location: what changes and why

The policy is called "Minimum Scope". Play's help article on foreground location splits use cases into two kinds:

  • Transactional: one-time or infrequent precise location, such as finding nearby stores, sharing your location once, tagging a photo or autofilling a delivery address. For apps targeting Android 17, this should go through the location button.

  • Persistent: ongoing precise location that is core to the app, like active navigation or fitness tracking. This keeps the full permission but needs a declaration explaining why coarse location or the button isn't enough.

The help article says the precise location declaration becomes available in Play Console in November 2026, compliance is mandatory from 27 January 2027, and 30-day self-extensions will be available. It also says existing apps aren't exempt: updates that don't meet the standard may be rejected.

Adding the location button

The Android developer guide recommends the Jetpack library, which renders the system button on Android 17 and falls back to a normal permission prompt on Android 16 and lower. Note that it is marked experimental and subject to change.

Manifest

Declare the standard location permissions plus USE_LOCATION_BUTTON. If the button is your only route to precise location, add the onlyForLocationButton flag:

<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission
    android:name="android.permission.ACCESS_FINE_LOCATION"
    android:usesPermissionFlags="onlyForLocationButton" />
<uses-permission android:name="android.permission.USE_LOCATION_BUTTON" />

With that flag, users can only share precise location through the button, which is the whole point of the policy for transactional apps.

Compose

A minimal version of the guide's sample:

import androidx.compose.runtime.Composable
import androidx.core.locationbutton.compose.LocationButton
import androidx.core.locationbutton.compose.LocationButtonTextType

@Composable
fun NearMeButton(onGranted: () -> Unit, onDenied: () -> Unit) {
    LocationButton(
        onPermissionResult = { isGranted ->
            if (isGranted) onGranted() else onDenied()
        },
        textType = LocationButtonTextType.UsePreciseLocation
    )
}

You can change colours, corner radius and outline, and pick the label from a fixed list ("Use precise location", "Share precise location" and so on). The location icon itself can't be removed or restyled, and the font size follows the user's accessibility settings. Plan your layout around that.

Call log, contacts and local network

Phone call verification

If your sign-up flow reads the call log to confirm a missed-call verification, that has to go by 27 January. The announcement lists the SMS User Consent API as an alternative for account verification. If you are rethinking verification anyway, passkeys remove the phone step entirely; our guide to replacing SMS OTP with Credential Manager walks through it.

Manage Contacts permission

Now restricted to apps that need it for core functionality when system pickers aren't enough, with a declaration required. Everyone else should use narrowly scoped platform intents. If you read contacts only to let users pick one, we covered the Android 17 contact picker in October.

Local Network permission

Also restricted to apps that need it when device pickers can't do the job. Apps targeting API 37 must submit a Play Console declaration.

The smaller items worth a skim

  • Subscriptions with eligibility-based discounts, such as student plans, must clearly disclose who qualifies, how it is verified and what happens to the price when eligibility ends.

  • AppFunctions: apps exposing functions to AI agents must follow all existing policies and can't deceive or manipulate agents or bypass security controls.

  • Deceptive Behavior: now states explicitly that developers can't manipulate the app review process.

  • Payments: new guidance on how the Payments policy applies to digital purchases made through AI or agentic experiences.

A checklist for this sprint

  1. Complete the trader status declaration in Play Console.

  2. If you sell in Japan, submit the authorisation form before 1 December.

  3. Search your manifests for ACCESS_FINE_LOCATION, READ_CALL_LOG and the contacts permissions. List each feature that uses them.

  4. Classify location features as transactional or persistent, and prototype the location button for the transactional ones.

  5. Plan the Android 17 target bump alongside this. If you are still catching up from the last one, the target API 36 migration checklist covers the groundwork.

Dates here are from Google's announcement and help pages as of early November 2026. Google says some timelines may firm up as it gathers feedback, so check the Policy Deadlines page in Play Console before you ship.

Keep reading

More from Aditya Bansal

More from Aditya Bansal

More in Software Development

Have a story of your own?

Publisha is free to start. Write with AI that keeps your voice, and publish in a click.