/
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

Twitter says it may have shared users' data with its ad partners without user consent due to two ad targeting-related bugs that it says were fixed on August 5

Twitter has disclosed more bugs related to how it uses personal data for ad targeting that means it may have shared users data …

TechCrunch Natasha Lomas

Context & Ripple Effects

This disclosure extends a pattern: Twitter's 2018 admission that a bug had routed users' direct messages with business accounts to third-party developers since May 2017, followed in May by word that it shared some iOS users' location data with an ad partner — again without naming the partner or the duration.

What makes the August 5 ad-targeting bugs consequential is where the pattern led: two months later Twitter disclosed it had used email addresses and phone numbers submitted for account security for ad targeting, a practice that by 2020 had the FTC weighing a fine of $150M–$250M. The recurring shape — security and consent data flowing into the ad engine — is what regulators and advertisers will read into each new disclosure.

First-order effects

  • Users whose data flowed to ad partners through the two bugs now learn of the exposure only after the fact, since Twitter fixed the bugs on August 5 before naming affected users, partners, or data types.
  • Twitter's ad partners received targeting data without a documented consent basis, leaving both sides of those relationships exposed to questions about what was shared and under what terms.

Second-order effects

  • Each disclosure raises the compliance bar for Twitter's ad business: the FTC's eventual $150M–$250M fine over the security-data-for-targeting practice shows these bugs convert directly into regulatory liability, and the same scrutiny now attaches to this one.
  • Advertisers buying Twitter targeting must weigh the risk that audience data rests on shaky consent foundations, pressuring Twitter to prove provenance for its targeting segments or accept discounted inventory.

Third-order effects

  • If the pattern holds — security inputs, location, and now ad-targeting data all crossing the line regulators later penalized — platform ad systems will face structural requirements for consent auditing and data-lineage records, not just post-hoc bug fixes and disclosures.
  • Repeated self-disclosures without partner names or affected-user counts may push regulators toward mandating standardized breach-notification formats, ending the era of vague 'may have shared' statements.

The trend: Ad-targeting systems at major platforms are becoming a recurring source of privacy enforcement, as data collected for one purpose (security, consent flows) leaks into advertising pipelines and turns engineering bugs into FTC-scale liabilities.

Discussion

  • Twitter Help Center Twitter Help Center on x
    An issue with your settings choices related to ads on Twitter
  • @lukolejnik Lukasz Olejnik on x
    Twitter may have /accidentally/ shared data on users to ads partners even for those who opted out from personalised ads. That would be a violation of user settings and expectations, which #GDPR makes a quasi-contract. https://www.reuters.com/...
  • @frank_rieger Frank Rieger on x
    A textbook example of corporate weasel-wording, trying to obscure what really happened as much as possible https://help.twitter.com/...
  • @zackwhittaker Zack Whittaker on x
    Welp. Another Twitter data leak (via @riptari) — potentially as far back as May 2018. https://techcrunch.com/...
  • @jedisct1 Frank Denis on x
    Twitter has disclosed more bugs related to how it uses personal data for ad targeting that means it may have shared users data with advertising partners even when a user had expressly told it not to. https://techcrunch.com/...