Legal documents: Meta paid Bright Data to scrape data from other websites for years while publicly condemning the practice and suing companies over scraping
Facebook owner Meta Platforms Inc. for years paid a contractor to scrape data from other websites while publicly condemning …
Context & Ripple Effects
The documents land in the middle of a long pattern: Meta has spent years litigating against the same practices its own procurement funded. Its own suit against Bright Data went nowhere, and later a federal judge likewise dismissed X's attempt to sue Bright Data over scraping — leaving Bright Data with a winning record against two of the loudest anti-scraping voices in tech.
That failure matters because Meta's public posture on third-party data access has repeatedly collided with court records: it settled for $725M over the Cambridge Analytica-era class action, and separately paid $90M on a decade-old cookie privacy suit. The Bloomberg report adds a procurement-side counterpoint to that legal history.
First-order effects
- Meta's credibility as an enforcer of terms-of-service data boundaries takes a direct hit — any future argument it makes in court that scraping harms users now runs against documented evidence it paid for exactly that.
- Bright Data emerges with unusual leverage: it has survived both Meta's and X's litigation attempts, strengthening its position to sell scraping services to other large buyers.
Second-order effects
- Rival platforms suing scrapers face a harder courtroom path — the combined Meta-and-X dismissals give defendants a ready-made 'industry standard practice' argument, raising the cost of litigation as an enforcement tool.
- Meta's own data-access controversies, from the $725M settlement to later internal-doc revelations about fending off regulator scrutiny, become recurring ammunition for plaintiffs and regulators framing the company as inconsistent on data ethics.
Third-order effects
- If courts keep siding against scraping lawsuits, enforcement migrates from litigation to technical walls — login requirements, rate limits, and paid API tiers — which is precisely the 'public-data permission boundary' fight that defines who can reuse web content at scale.
The trend: Platform litigation against scrapers is collapsing while commercial scraping becomes normalized procurement, pushing the real battle over public-data permissions into product design rather than courtrooms.