Free HTML to Google published a large policy update on 29 October 2026. Most of it is aimed at apps with special permissions, but a few items reach almost everyone, including people who turn a website or an HTML project into an app. Here is what is in it, sorted by who it affects, with the dates you need.
Google gives developers at least 30 days from 29 October to comply with new policies unless a later date is stated. The exact dates for each item live on Google's Policy Deadlines page, so treat this article as a map, not the final word.
Affects every developer
Trader status declaration
Starting in November 2026, every account must declare in Play Console whether it is a trader or a non-trader under EU and UK consumer law. The deadline for existing accounts is 1 February 2027, and missing it can lead to blocked updates and app removal. Apps with ads or purchases almost always mean trader. We wrote a full step-by-step guide: Google Play trader status, explained.
Affects you if you earn money
Japan payments authorization: 1 December 2026
Developers who sell into or out of Japan must complete a payment collection authorization in Play Console by 1 December 2026. If it is missing, Google says your payouts will be held, and not only for Japan. If you sell anything (paid apps, in-app products or subscriptions), open the Payments profile in Play Console and look for the task.
Subscriptions with eligibility discounts
If you sell a subscription with a discount that depends on who the user is, such as a student plan, you must explain the eligibility rules, how you check them and what happens to the price when the user is no longer eligible. A simple subscription with one price is not affected.
Affects you if your app uses certain permissions
Location
The location policy that Google announced in April becomes mandatory on 27 January 2027. If your app asks for location, make sure it only does so when a feature clearly needs it, and that the reason is visible to the user at that moment. Website apps that never use location should simply leave it off. In the Free HTML to APK builder, phone features are off unless you turn them on, so most apps never ask.
Local network access
Access to devices on the user's Wi-Fi network (printers, smart plugs, a local server) is being limited to apps that need it for their core feature. Apps targeting the next Android version (API level 37) and higher will need a declaration in Play Console, and others are encouraged to use the system's device pickers. If your HTML app only loads your website over the internet, this does not touch you.
Managing contacts
A new policy covers apps that can change the user's contacts. Apps that need it must explain why it is core to the app. Apps that only occasionally add a contact should hand that job to the system contacts screen instead.
Call logs
The temporary use of call log access for phone-call verification ends on 27 January 2027. This only matters to apps that read call logs, which an ordinary HTML or website app never does.
Affects fewer apps
- AppFunctions: apps that expose actions to AI agents on the phone must follow all Play policies and must not trick agents or get around security controls.
- App quality: new expectations around memory use and code optimization, with dates in February 2027.
- Families, age signals, crypto in Hong Kong and XR apps: specific updates for those categories.
A simple to-do list
| When | What | Who |
|---|---|---|
| Now to 1 Dec 2026 | Japan payment collection authorization | Anyone selling on Play |
| Now to 1 Feb 2027 | Declare trader or non-trader | Every account |
| By 27 Jan 2027 | Check location requests follow the new policy | Apps that use location |
| Before you target API 37 | Local network declaration if you need it | Apps that talk to Wi-Fi devices |
| Any update | Explain eligibility rules for discounted plans | Apps with student or similar plans |
What this means for an HTML or website app
For a typical app built from a website or HTML files, the work is short: declare your trader status, set up the Japan task if you sell anything, and keep permissions to the ones you use. Nothing in this update forces you to rebuild your APK or AAB.
The target API rule is a separate yearly requirement and still applies to every update. If Play Console tells you your app must target Android 16, read how to fix the API level 36 error.
Read Google's own text in the 29 October 2026 policy announcement before you make changes. For the whole publishing process, see the Google Play guide.