Google Play
Google Play enforces contacts, location, geofencing and subscription rules Jan 27, 2027
69 days left — Jan 27, 2027
- What stops working
- From January 27, 2027 Google Play enforces new rules on apps that read contacts, request precise location, run foreground services for geofencing, or sell eligibility-based subscription discounts. Account verification by phone call is no longer an accepted reason for the READ_CALL_LOG permission. Apps that do not comply can be rejected at review or removed from the store.
- Who is affected
- Android app developers and publishers whose apps use contacts, precise location, foreground services for geofencing, call-log permissions, or discounted subscriptions.
- Official migration path
- Switch to the Android Contact Picker, use the location button for one-time precise location (Android 17 targets), move geofencing to the Geofence API, file Play Console declarations where broad access is still needed, and update subscription disclosures.
- What the official path does not cover
- Google provides policy text and APIs but not the code changes, permission-flow redesign, Play Console declarations or store-listing rewrites each app needs; agencies with many client apps repeat this per app and push a new release through review.
- Source
- Google Play Console Help: Policy Deadlines table (read Nov 18, 2026; October 2026 policy updates) · announced 2026-10-29 · verified 2026-11-18
Need this done before Jan 27, 2027?
Fixed price, fixed scope, fixed date. From $2,500 for a single integration or workflow; you get the working replacement, the code, and a before/after check. Quote within one business day.
One short form (company, email, what runs on this, needed-by). Reply within one business day.
Not ready yet? Get an email when Google Play deadlines approach · Firms: get listed for Google Play work.
Spotted a wrong date? Report it — corrected with the source within one business day.