Google Play Policy Updates: What Every Developer Must Know
Google has tightened its policies significantly. Here is a complete breakdown of the most impactful changes and exactly what you need to do to stay compliant.
Google Play has removed over 2.3 million non-compliant apps in recent enforcement cycles. Unlike Apple's pre-submission review, Google often approves apps and removes them later when policies are violated: which means your app can lose visibility or be delisted with little warning. Here are the changes you need to act on now.
Data Safety Section is mandatory and enforced
CriticalGoogle Play now actively cross-references your Data Safety Section declarations against your app binary. If you declare that you do not collect location data, but your APK contains an SDK that accesses location, your app will be removed or rejected. Inaccurate declarations can result in account suspension.
Action required
Audit every SDK in your app. Use tools like Exodus Privacy or AppTester's Health Check to identify SDKs collecting data you may not be aware of. Update your Data Safety form to accurately reflect all data collection.
Precise location requires stronger justification
CriticalGoogle has tightened the requirements for apps requesting ACCESS_FINE_LOCATION. Apps must demonstrate a core use case that genuinely requires precise location. Background location (ACCESS_BACKGROUND_LOCATION) now requires a special declaration and policy review.
Action required
Switch to ACCESS_COARSE_LOCATION wherever possible. If you truly need precise location, ensure your app description clearly explains why and that the feature is prominently used in the user flow.
Target API level requirements updated
HighNew apps must target Android 14 (API level 34) or higher. Existing apps must meet this requirement to receive updates. Apps targeting older API levels will be hidden from devices running newer Android versions.
Action required
Update your targetSdkVersion to 34 in your app/build.gradle. Test thoroughly on Android 14: several behaviour changes around permissions, intents, and broadcast receivers may require code updates.
Health, fitness, and financial app policies
HighApps in health, fitness, and personal finance categories face stricter requirements around data handling, consent, and what they can claim about their capabilities. Medical claims require regulatory documentation. Financial apps may require licences depending on the jurisdiction.
Action required
If your app offers health tracking, ensure you comply with HIPAA (US) or equivalent frameworks. For financial apps, clearly state that the app is not a regulated financial service unless it is. Remove any claims that could be interpreted as medical advice.
Photo and media permissions scoped
HighREAD_EXTERNAL_STORAGE is no longer sufficient for accessing photos on Android 13+. Apps must now request READ_MEDIA_IMAGES, READ_MEDIA_VIDEO, or READ_MEDIA_AUDIO as appropriate. Apps still using READ_EXTERNAL_STORAGE will fail on modern Android versions.
Action required
Update your permission requests to use the granular media permissions. Test on Android 13 and 14 devices to confirm your media access works correctly with the new permission model.
User-generated content moderation
MediumApps with user-generated content (comments, posts, chat, reviews) must demonstrate moderation capabilities. Google requires that UGC apps have a reporting mechanism, and that reported content is actioned. Apps without any moderation are at risk of removal.
Action required
Implement a report/flag mechanism for any UGC feature. Document your moderation policy and include it in your store listing description or a linked policy page.
Check compliance before Google does
Our App Health Check scans your APK for policy violations, dangerous permissions, and SDK compliance issues: in seconds, for free.