/
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
Handles
Browse by social media handle
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

How 30+ popular tech companies, from social networks to dating apps, responded to requests for personal data; how they interpret that data remains opaque

Here's what they gave us — and what they didn't.  —  The average American, one study tell us, touches their phone 2,600 times per day.

Engadget Chris Ip

Context & Ripple Effects

This Engadget exercise is the consumer-facing version of a question reporters have been circling for years: earlier coverage mapped what companies can collect in an ordinary evening — a pizza-and-movie-night data breakdown built from privacy policies — while Ars Technica's app surveys showed email and location flowing to Apple, Google, and other third parties as far back as 2015.

What distinguishes this piece is method: instead of reading policies or instrumenting apps, it exercised the access rights themselves, asking 30+ companies directly. That follows the GDPR-era template set when a reporter's Right of Access request returned 138GB of raw data from Apple, Amazon, Facebook, and Google — proof that getting your data is not the same as understanding it.

First-order effects

  • Users who file access requests with these 30+ social networks and dating apps receive disclosures of uneven completeness, and the companies' own interpretation of that data stays hidden behind the response.

Second-order effects

  • When first-party answers are opaque, scrutiny shifts to the plumbing: the related finding that apps leak sensitive signals like heart rate and pregnancy intent through Facebook's analytics SDK shows third parties holding data the user never requested from anyone.

Third-order effects

  • If access-request journalism keeps outpacing policy-based reporting, categories that escaped the social-media spotlight — like the opaque data practices in mobile games — become the next targets, pressuring regulators toward standardized, machine-readable disclosure formats rather than raw dumps.

The trend: Data access rights are shifting from legal formality to a reporting tool, exposing the widening gap between how much companies collect and how little they explain about what they do with it.