The news
Google Play announced new policy changes on 29 October 2026 and gave developers at least 30 days to comply, with the exact dates on its Policy Deadlines page. Two new rules cover permissions. An app that targets Android 17 (API level 37) and uses the local network permission, which lets it find and connect to other devices on the same network, must submit a declaration in Play Console. Apps that need the permission to manage contacts must also submit a declaration, and other apps must use narrower system options. The deadline for both is 25 August 2027.
Google also restated the location rules it announced in April, which become mandatory on 27 January 2027. Apps must ask for the least location they need. Apps that target Android 17 must use Android's location button for one-time or occasional requests, and apps that use precise location (ACCESS_FINE_LOCATION) must complete a Play Console declaration explaining why approximate location or the button is not enough. On the same date, apps that do not need the whole contact list must use the Android Contact Picker.
Two items concern the developer account. Starting in November 2026, every active account must declare in Play Console whether it is a trader under EEA and UK law, even if it does not publish there. Existing accounts have until 1 February 2027, and Google says a missing declaration may lead to blocked updates and removal from Google Play worldwide. Separately, developers who sell into or out of Japan must complete a payments authorisation by 1 December 2026, or Google holds their earnings in all regions.
What it means for you
- If your app asks for precise location, for deliveries, a store finder or staff check-in, Google will want a written reason from 27 January 2027 for why approximate location or a one-time tap is not enough.
- Apps that find printers, card terminals or other devices on the office network will need a declaration once they target Android 17, and so will apps that need to manage contacts. Google's date for both is 25 August 2027.
- The trader declaration is for every developer account, not only apps sold in Europe. If it is missing on 1 February 2027, updates can be blocked and the app removed everywhere.
- Only the account that publishes the app can file these forms. If your agency published it under their own account, they have to do it for you.
What to do now
- Put these dates in the calendar: 1 December 2026 (Japan payments, only if you sell into or out of Japan), 27 January 2027 (location and contacts), 1 February 2027 (trader status) and 25 August 2027 (local network and managing contacts).
- Ask your developer for a list of the permissions your Android app requests today, and which ones it really needs.
- Ask whether approximate location or the one-time location button would work for your app, and whether picking contacts one by one could replace reading the full list.
- In Play Console, open Account details and declare your trader status. Google says an account that does not distribute in the EEA or UK can declare as a non-trader.
- Ask who will submit the Play Console declarations and by when, so the work is done before your next app update.
How Didset can help
We build Android apps, and we can review your app's permissions, change it to the smaller ones Google prefers and prepare the Play Console declarations.
Talk to us about it


