Google Play’s 2025 safety numbers: 1.75M blocked apps, 80k banned dev accounts, and ‘policy-by-default’ tooling

Original source: Help Net Security - “Google cleans house, bans 80,000 developer accounts from the Play Store” (Feb 20, 2026)

• https://www.helpnetsecurity.com/2026/02/20/google-strengthens-android-safe-app-ecosystem/

(Primary link referenced in the piece: Google Security Blog - https://security.googleblog.com/2026/02/keeping-google-play-android-app-ecosystem-safe-2025.html)

Why this matters for marketers (not just security people)

This is one of those platform updates that quietly changes the day-to-day:

• Listing hygiene and policy compliance are now a shipping constraint, not a “review-time surprise”.
• Trust signals (reviews, data safety disclosures, integrity checks) are being treated as part of the ecosystem’s core product.

If you are scaling paid spend on Android, anything that affects publication stability, review fraud, or permission disclosures can hit growth.

The headline numbers

Help Net Security cites Google’s 2025 enforcement metrics:

• 1.75M+ policy-violating apps prevented from being published
• 80,000+ developer accounts banned for attempting to publish harmful apps
• 255,000+ apps prevented from gaining “excessive access” to sensitive user data
• 160M fake/manipulated ratings and reviews blocked

The shift: “policy insights” moving earlier in the workflow

The practical changes called out are all about pushing checks left:

• Play Policy Insights in Android Studio: feedback while you code (especially around sensitive permissions/APIs)
• Expanded pre-review checks in Play Console: flags common issues before submission (privacy policy links, credential usage, etc.)
• Developer verification rolling out more broadly, with account types (including students/hobbyists)

In plain terms: you should expect “platform compliance” to behave more like build tooling and less like a checklist.

Tiny win to steal this afternoon

Do a 30-minute “release-risk scan” on your next Android build:

1. list the SDKs that touch sensitive data (analytics, attribution, payments, identity)
2. confirm your Play Console privacy policy URL is correct and stable
3. sanity-check your declared permissions vs what the SDKs actually request
4. make one decision: what permission or data collection can you remove without harming your north-star metric

That’s the fastest way to reduce the chance your growth plan gets interrupted by a platform friction moment.

Read the original: https://www.helpnetsecurity.com/2026/02/20/google-strengthens-android-safe-app-ecosystem/