Play Protect blocking custom DPC app during 6-tap QR provisioning — Appeal submitted
Hello Android Enterprise Community Team,
We are developing an enterprise Device Policy Controller (DPC) application for managing company-owned devices via Android Enterprise dedicated device management.
Issue Summary:
- Our DPC app is hosted on our secure HTTPS enterprise server and provisioned via standard 6-tap QR code onboarding on factory-reset devices.
- During provisioning, Google Play Protect blocks the application with the message: "App blocked to protect your device".
- The DPC app is strictly used for enterprise device management (Device Owner mode, kiosk enforcement, remote lock/unlock, system restrictions) and does NOT harvest sensitive personal user data (contacts, call logs, SMS, and media are completely disabled).
Actions Taken:
1. We have verified our DPC APK package name, manifest provisioning activities, and public signing certificate SHA-256 checksums match the QR code bundle contract.
2. We have submitted the official Google Play Protect Appeal Form (under Android Enterprise DPC Allowlisting guidance - Article 16694822) with our APK, package name, signing certificate SHA-256, and enterprise use-case details.
Questions / Guidance Requested:
1. How long does the DPC allowlisting review process typically take once the Play Protect appeal form is submitted?
2. Is there any additional verification step or specific enterprise channel recommended for custom DPC allowlisting?
Any guidance or insights from the community and Google team would be greatly appreciated!
Thank you,
Chandan Vishwakarma
