Google Will Exempt Sanctioned Countries From Android Verification Checks

Google plans to disable its coming Android developer verification checks on devices in countries subject to U.S. sanctions. The geographic exception will preserve ordinary app installation inside those places, but it will not give developers who live there a route to become verified. A Google spokesperson told Ars Technica that those developers will be unable to complete the process, narrowing their practical access to users in other markets.

The distinction between a device and a developer determines how the policy works. Google’s Android documentation says devices in sanctioned countries will be excluded from the checks. An unverified app can therefore continue to circulate within an exempt country. Google also warns that users there will not receive the program’s added security benefits. The same app will face the new verification barrier when a user tries to install it on a covered device in a market where enforcement is active.

Google’s current FAQ does not name every territory covered by the exception. Ars Technica listed Cuba, Iran and North Korea, along with Ukrainian territory under occupation, among the affected locations. That list can change, so the operative boundary will depend on where Google applies verification checks when each market enters the program.

The Device Exemption Does Not Verify Developers

Android developer verification is designed to apply beyond Google Play. Under the planned system, a developer who wants an app to install normally on certified Android devices must provide identity information to Google and register the app. That requirement reaches software distributed from a website or another store, not only software submitted to Google’s own marketplace.

For a developer in a sanctioned country, the exemption solves only the local installation problem. A company spokesperson told Ars Technica that residents of the affected countries cannot enroll in the verification program. Their apps can remain installable without the check on devices located in exempt markets, yet the developers cannot obtain the status needed for ordinary distribution to covered devices abroad.

Devices in sanctioned countries will be excluded from Android developer verification checks.

That wording, published in Google’s FAQ and last updated March 25, 2026, places the exception on devices rather than developer accounts. It also creates an uneven result. Users in the exempt locations keep the familiar freedom to install unverified apps, while local developers lose the straightforward path to reach users in markets where verification is enforced.

An Advanced Installation Route Will Remain

Unverified software will not become technically impossible to install everywhere else. Google has described an advanced flow for experienced users who deliberately choose to proceed. Ars Technica reported that the route includes multiple steps, prominent warnings and a 24-hour wait. Apps installed through Android Debug Bridge, a tool commonly used for development and testing, are also exempt from verification according to Google’s FAQ.

Those alternatives do not offer the same reach as a normal installation. A developer can tell technically confident users how to use the advanced flow, but the added delay and warnings make it unlikely to serve a broad consumer audience. The result is a practical divide between verified apps that install through the standard path and unverified apps that require a user to know about and complete an exception process.

Google says verification is intended to make it harder for malicious actors to distribute scam applications. The company also says Android remains open because developers may use different distribution channels. The sanctioned-country policy shows that distribution channel and installability are separate questions: an app may still be hosted outside Google Play, while the operating environment decides whether a user can install it normally.

Enforcement Starts in Four Markets

Brazil, Indonesia, Singapore and Thailand are first in line, with enforcement scheduled for September 30, 2026. The company expects a wider global expansion in 2027. Its FAQ says enforcement will cover certified devices running Android 7 or later and will be delivered through Google Play services.

Coverage is tied to Google-certified Android hardware, not every device built from the open-source Android code. Ars Technica reported that this makes the policy broadly applicable to nearly all Android phones outside Russia and China. Many phones used in places such as Cuba and Iran are imported models that retain Google certification. Without a location-based exception, those devices could receive enforcement through Play services even though local developers cannot verify. Google’s approach instead switches off the check for devices in the exempt locations.

The first launch markets are not the sanctioned locations addressed by the exception. They are where the new checks begin operating. Once enforcement is active, a developer’s verification status will affect whether an app follows the ordinary installation path on those devices. The country exemption works in the opposite direction by preventing the check from running on devices in covered sanctioned places.

This arrangement avoids blocking unverified apps inside markets where Google says it cannot verify local developers, but it does not preserve those developers’ previous international reach. The policy therefore creates two geographic boundaries: one determines where checks operate, and the other determines which developers can obtain the credential those checks require. The September rollout will show how clearly Android explains that split to users and developers before the program expands further.