Google Play FLAG_SECURE requirements policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Screen capture, recording, sharing, and accessibility apps.
If another app marks its screen with FLAG_SECURE, your app must respect that protection. Google prohibits features that bypass it to capture or expose protected content.
What to check
Test capture and sharing against a screen that uses FLAG_SECURE. Check recording libraries, overlays, remote assistance, and any instructions your app gives users for bypassing capture restrictions.
An accessibility permission alone doesn’t create an exception. Google’s exception applies to qualifying accessibility tools, and protected content must not be transmitted, saved, or cached for access outside the user’s device.
How to address the rejection
Remove bypass techniques and explain unavailable capture in the UI without offering a workaround. If you’re relying on the accessibility-tool exception, verify both eligibility and the complete data path.
Inspect temporary files, uploads, logs, and remote support sessions as well as the final recording. Include the protected-screen test in your review notes so the reviewer can confirm that your app respects the flag.
Messages this guide can help with
FLAG_SECURE requirements; FLAG_SECURE requirements policy violation; FLAG_SECURE requirements rejection; FLAG_SECURE requirements denied
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Google Play: FLAG_SECURE requirements Checked 22 September 2026