Google says it saw a 98% drop in the number of Play Store apps accessing SMS/call log data in 2019 since cracking down on apps abusing permissions in Oct. 2018
Context & Ripple Effects
In October 2018, Google required Play Store apps to be the default Phone, SMS, or Assistant handler before touching call logs or SMS data (a policy that made sensitive permissions conditional on core function). That rule arrived on top of a broader enforcement ramp — Google had already credited new machine learning for a 70% YoY jump in removals the year before (700,000+ apps pulled in 2017) and reported rejections up 55%+ in 2018 (as automated protections rolled out).
The 98% drop in apps accessing SMS and call log data is Google's first measured outcome of the permission rule, and it foreshadows the enforcement scale the Play Store later settled into — millions of rejections and hundreds of thousands of blocked developer accounts a year (2.28M apps rejected in 2023 alone).
First-order effects
- Developers of SMS- and call-log-dependent apps must either qualify as the default Phone/SMS/Assistant app or lose access to that data — the 98% decline shows most chose to drop the permission rather than re-architect.
- Users see fewer third-party apps with access to their messages and call histories, shrinking the attack surface for abusive permission use Google cited when it announced the crackdown.
Second-order effects
- The success of a function-gated permission model gives Google a template for tightening other sensitive Android permissions, shifting the burden onto developers to justify data access rather than on Google to detect misuse.
- App review volume scales with policy strictness — the rising rejection and removal counts across 2017-2023 suggest automated enforcement became the operating cost of the Play Store's curation posture.
Third-order effects
- If the pattern holds, mobile platform gatekeeping consolidates around policy-plus-automation: app stores act as de facto data-access regulators, with developers designing around default-handler requirements and periodic policy audits as a structural condition of distribution.
The trend: App stores are evolving from passive distribution channels into active data-governance layers, with Google using permission restrictions and automated review to police sensitive data at scale.