Operational summary
The first enforcement milestone applies to participating stores in four countries. It is an operational deadline for affected distribution, followed by broader global expansion beginning in 2027.
Recommended sequence
- List every store that distributes each package in the four initial countries.
- Check registration and the production certificate before the release freeze.
- Assign an owner to unresolved packages and certificate mismatches.
- Plan for the 2027 expansion even if September does not affect current users.
Build a deadline matrix
September 30, 2026 is the first enforcement date for participating stores in Brazil, Indonesia, Singapore and Thailand. Android says broader global expansion begins in 2027 after rollout feedback.
A useful readiness matrix includes country, store, package, delivered certificate, console owner and remediation state. Headquarters location is irrelevant if users can install or update the app in an affected market.
- First phase: four countries and seven participating store organizations.
- Play Console also has a package-registration deadline with global Play consequences.
- Unregistered apps can still have separate ADB or advanced-flow paths.
Frequently asked questions
Is September 30 a universal sideloading ban?
No. Official Android guidance scopes the first phase to participating stores and selected countries, with ADB and advanced flow treated separately.
Should teams outside the four countries wait?
No. Android says global expansion begins in 2027, and package ownership or signing problems can take time to resolve.
Sources and review
PkgReady summarizes operational implications but does not replace an official console or Android documentation. Reviewed 2026-08-14.