Google Play stalkerware and monitoring apps policy: fixes and checks

By The Draftbit team · Updated
Sources checked

This guide is for Apps that transmit another person's device data for monitoring.

Google narrowly limits acceptable monitoring apps. The policy permits qualifying parental and enterprise employee-monitoring uses that meet its requirements; it doesn’t allow spouse tracking simply because someone says they consented.

What to check

Review your audience, marketing, notifications, icon, data collection, and distribution links. An app marketed as secret surveillance conflicts with the policy. So does a store listing that links to a hidden-monitoring APK elsewhere.

Qualifying monitoring apps need the appropriate isMonitoringTool manifest metadata, prominent disclosure and consent, a distinct identifying icon, and a persistent notification while running. They must also meet applicable legal requirements.

How to address the rejection

Remove prohibited monitoring use cases and covert functionality. If the product genuinely qualifies, make monitoring visible throughout operation and accurately describe it in the listing.

Test notification persistence, startup, background operation, and the collected data path. Provide reviewer access that demonstrates the qualifying use. A disclaimer or a permission prompt alone doesn’t turn an otherwise prohibited surveillance product into an acceptable monitoring app.

Messages this guide can help with

Stalkerware and monitoring apps; Stalkerware and monitoring apps policy violation; Stalkerware and monitoring apps rejection; Stalkerware and monitoring apps 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.

Your next stepSubmit a Google Play release with working review access