/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

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

Google has been clamping down on Android apps that abuse permissions, and that appears to have had a very tangible effect on the Play Store.

Engadget Jon Fingas

Context & Ripple Effects

In October 2018, Google stopped letting ordinary Play Store apps request call log and SMS permissions at all — from that day, only an app serving as the default Phone, SMS, or Assistant app could qualify. That policy was itself an escalation: earlier in 2018 Google had already reported removing 700,000+ policy-violating apps in a year, up 70% YoY, crediting new machine-learning screening.

The 98% figure is the first hard outcome measurement of that gate, arriving alongside news that rejected submissions rose 55%+ YoY in 2018 as automated protections rolled out. It matters because it turns Google's enforcement story from takedown counts into a measurable change in what kinds of apps can touch sensitive user data.

First-order effects

  • Developers whose apps legitimately needed SMS or call logs but weren't default handlers lost access overnight, forcing them to rebuild around alternatives or abandon the functionality.
  • Google gains a quantifiable win to point to: a 98% reduction in apps touching SMS/call log data within roughly a year of the policy taking effect.

Second-order effects

  • The permission-gate model becomes the template for Google's broader enforcement posture — rejection volumes keep climbing across subsequent years, with 2.28M apps and ~333K developer accounts rejected in 2023 alone.
  • App categories adjacent to messaging (contact managers, backup tools, automation utilities) face the same tightening logic, pushing them toward APIs and delegated flows instead of raw data access.

Third-order effects

  • If the pattern holds, platform owners rather than users become the effective arbiters of sensitive-data access on mobile — permission requests shift from a user-consent checkbox to a pre-approved developer category, a structure regulators scrutinizing app-store gatekeeping will increasingly weigh.

The trend: Mobile app stores are shifting from reactive takedowns to preemptive policy gates on sensitive permissions, with enforcement volume becoming the metric of platform trust.

Discussion

  • @stshank Stephen Shankland on x
    Android apps that used SMS & call logs dropped 98% last year after Google barred apps from accessing that unless it was a core function. Nice those were banned, scary so many sought that access. https://security.googleblog.com/ ...