Android developer verification for private Android apps

Android developer verification started to take effect on September 30 2026. To help our community prepare, here is a quick overview of what this means for your organisation: 

Private Android apps on unmanaged Google Play Protect certified Android devices must be registered to a verified developer identity to remain installable and receive updates. Apps deployed on fully managed devices or within an Android Work Profile are exempt from these requirements.

This change is designed to make it significantly harder for bad actors to distribute harmful apps, while giving organisations confidence that internal apps come from legitimate, verified sources. 

Does this apply to your organisation?

Applicability depends on your device management status:

• Managed devices (Exempt): If your devices are enrolled in Android Enterprise (either fully managed or using a Work Profile via EMM or MDM), your private apps do not require developer registration.
• Unmanaged devices (Action required): If you distribute private apps to unenrolled or personal devices, those apps must be registered under a verified developer account to remain installable and receive updates. 

Choosing your registration path

Depending on your architecture, Google provides different paths forward, including registering your organisation and app package names via the Android Developer Console, or exempting your devices entirely by enrolling them in Android Enterprise management.

For the complete overview of registration options, requirements and step-by-step instructions:

 📖 Review the Help Centre guide: Android Developer Verification for Private Apps

 🎥 Watch the step-by-step walkthrough video

Have a specific question about your deployment setup or registration path? Drop a comment below and we'll help point you in the right direction.