Google rejected 1.75 million apps from Google Play in 2025 for violating its developer policies, a 26% drop from the 2.36 million it blocked in 2024, according to Google’s own annual security report published in February 2026. That decline came alongside deeper checks: more than 10,000 safety tests per app and 266 million blocked install attempts across 2.8 billion devices. The numbers below cover why apps actually get rejected, how the rate has moved since 2023, and what a new developer verification requirement means for 2026 submissions.
How many apps does Google reject each year?
Google has published a specific pre-publication rejection count in its own annual security report for three years running: 2.28 million apps blocked in 2023, 2.36 million in 2024, and 1.75 million in 2025. The 2025 figure is the lowest of the three, a 26% drop from the 2024 peak, even though Google says its review process now runs more automated checks than in either prior year.
Figure 1: Apps Google blocked from publishing before they ever reached the Play Store. Source: Google’s annual security reports, 2023 to 2025 editions.
Google frames the drop as a sign that stronger pre-submission requirements, including expanded developer verification, are stopping bad actors earlier in the pipeline rather than catching them after they submit an app. Fewer apps reaching the review queue in a rejectable state is the more likely reading, not a lighter review process.
Why do apps get rejected from Google Play?
Data protection and privacy violations caused 44% of Google Play app removals in 2025, the largest single category. Content, goods, and services ineligible for distribution followed at 35%, then consumer information infringements at 13%, and scams or fraud at 5%.
Figure 2: Share of Google Play app removals by violation category, 2025. Source: Google Play’s annual transparency report, as analyzed by DigitalInformationWorld.
Warning
We could not locate a Google-authored page that states these exact category percentages in Google’s own words. The 44/35/13/5 split and the 8% and 10% rejection rates cited later in this article come from outlets that analyzed Google Play’s transparency report data (DigitalInformationWorld and Surfshark), not from a direct Google blog quote. The percentages as reported add to 97%, not 100%, most likely due to rounding or an undisclosed minor category. Treat these figures as directional rather than exact.
In 2024, the reported category mix looked different: data protection and privacy violations at 55%, content and goods ineligibility at 16%, data defects at 15%, and scams or fraud at 9%. Privacy stayed the top reason in both years, but its share of total removals fell as content-eligibility violations grew.
What actually happens during a Google Play review?
Every submitted app passes through automated and human checks before Google decides whether to publish it. The published removal categories above map closely to specific gates in that process: a Data Safety form that has to match the permissions an app actually requests, a content and goods eligibility check, and a review of whether the store listing tells shoppers the truth.
Figure 3: The core checks behind most Google Play rejections, modeled on Google’s published 2025 removal-reason categories.
None of those checks happen against a blank slate. Google is checking your app’s data collection and terms against what you have already disclosed, which means the underlying legal document has to exist and match reality before the technical review even matters. A Google Play EULA generator that spells out data collection, in-app purchases, and permitted use in plain language gives reviewers, and your own users, the same disclosures the Data Safety form is checking against. Apple runs a comparably structured process on iOS, where 90% of App Store reviews finish within 24 hours according to Apple’s own review-time data; see our App Store review time breakdown for that side of the comparison.
A rejection at any single gate sends the whole submission back, so the fastest path through review is making sure the declared permissions, the listed content category, and the store description all agree with each other before you submit.
Is Google Play’s rejection rate rising or falling?
Roughly 8% of app submissions were rejected in 2025, down from about 10% in 2024, according to Surfshark’s analysis of Google Play’s transparency report data. That means about 9 out of 10 submissions cleared review on their first pass, even as the raw rejection count fell alongside it.
Figure 4: Share of submitted apps rejected before publishing. Source: Surfshark analysis of Google Play’s transparency report data, 2024 to 2025.
A falling rejection rate alongside a falling raw rejection count points toward developers submitting cleaner apps, not Google loosening its standards. Google’s parallel enforcement numbers, more safety checks per app and more risky installs blocked, run in the opposite direction, which argues against a lighter review bar.
What happens to developer accounts that violate policy?
Google banned 80,000 developer accounts in 2025 for attempting to publish harmful apps, down sharply from 158,000 in 2024. At the same time, Google reinstated more than 12,500 developer accounts in 2025, up from just 1,500 in 2024, an eightfold increase, per Google Play’s transparency reporting as summarized by DigitalInformationWorld.
That combination, fewer bans and more reinstatements, suggests Google’s appeal process is resolving more disputed cases in developers’ favor than it did the year before. It does not necessarily mean enforcement got softer; it can equally mean fewer accounts were wrongly caught by earlier, blunter detection rules that a growing appeals volume was correcting.
If your app touches payments, subscriptions, or app store commission questions at all, the platform-level economics differ from Apple’s: 88% of EU App Developers Pay Apple No Commission in 2026 covers how commission tiers compare on the other major mobile storefront.
How does 2025 compare to prior years?
Three years of Google’s own reporting line up into a clear year-over-year table, with the headline 2025 rejection figure repeated below for reference.
| Year | Apps rejected pre-publication | Developer accounts banned | Rejection rate |
|---|---|---|---|
| 2023 | 2.28M | Not disclosed | Not disclosed |
| 2024 | 2.36M | 158,000 | 10% |
| 2025 | 1.75M | 80,000 | 8% |
Source: Google’s annual security reports (2023-2025 editions); rejection rate figures via Surfshark’s analysis of Google Play transparency data.
Every column in that table moved down between 2024 and 2025. That is unusual enough, across three separate metrics at once, that it is worth treating as a real shift in Google’s pipeline rather than noise in a single year’s numbers.
What’s changing for Google Play developers in 2026?
Google began rolling out mandatory developer verification in 2026, a requirement that developers confirm their real-world identity before an app can be installed or updated on certified Android devices. Enforcement starts September 30, 2026 in Brazil, Indonesia, Singapore, and Thailand, with a global rollout to follow in 2027.
Figure 5: Key Google Play safety enforcement and developer verification milestones. Sources: Google’s annual security reports; Android Developers Blog, 2026.
Google has said the verification step confirms developer identity rather than reviewing app content, and reports that more than 99% of apps were already registered to a verified developer ahead of the September 2026 enforcement date. That scale of an app economy is worth keeping in mind against the wider market: our App Store 2026 downloads and spending data covers how large the broader mobile app economy has grown across both major platforms.
The Bottom Line
The headline number is 1.75 million, the count of apps Google rejected from Google Play in 2025, down 26% from 2.36 million the year before. That decline shows up across every enforcement metric Google publishes at once: fewer developer account bans, a lower rejection rate, and more reinstated accounts, while the number of safety checks per app and blocked install attempts both grew. For a developer, the practical read is that Google’s review is getting more automated and more consistent, not more lenient, and the fastest way through it is making sure your app’s declared data use, content category, and public disclosures already agree with each other before you submit.
Frequently Asked Questions
How many apps does Google reject from the Play Store? Google rejected 1.75 million apps in 2025 for policy violations, down 26% from 2.36 million in 2024, according to Google’s own annual security report.
What is the most common reason a Google Play app gets rejected? Data protection and privacy violations were the leading cause of Google Play removals in 2025, accounting for 44% of cases. Content and goods ineligible for distribution made up another 35%.
What is Google Play’s app rejection rate? About 8% of app submissions were rejected in 2025, down from 10% in 2024, meaning roughly 9 out of 10 submissions were approved, per Surfshark’s analysis of Google Play’s transparency data.
How many Google Play developer accounts get banned? Google banned 80,000 developer accounts in 2025 for attempting to publish harmful apps, down from 158,000 in 2024. Reinstated accounts jumped eightfold, from 1,500 to over 12,500.
Sources and References
- Google Online Security Blog. (2026). “Keeping Google Play & Android app ecosystems safe in 2025.” Official 2025 annual security report.
- Google Online Security Blog. (2025). “How We Kept Google Play and Android App Ecosystem Safe in 2024.” Official 2024 annual security report.
- Google Online Security Blog. (2024). “How we fought bad apps and bad actors in 2023.” Official 2023 annual security report.
- Surfshark Research. “Google and Apple Removed Apps.” Analysis of Google Play and App Store transparency report data.
- DigitalInformationWorld. (2026). “Google and Apple removed millions of apps in 2025, citing fraud, privacy, and policy violations.” Analysis of Google Play’s annual transparency report.
- Android Developers Blog. (2026). “Android developer verification: Rolling out to all developers on Play Console and Android Developer Console.”
- Android Developers Blog. (2026). “Android developer verification: Building a safer ecosystem together.”
Note: All figures verified as of August 2026. Google publishes its Play Store enforcement numbers in a new annual security report each year, so headline figures here are refreshed at least twice a year to match.
