← Back to the feed

If Meta’s going down, it’s taking TikTok and YouTube with it

Developed over time first seen 2 months ago

The Verge ·

Meta has reached a proposed US child-safety settlement with 47 states and other jurisdictions, and is using it to urge TikTok, YouTube and Snap to adopt similar protections for teenagers. The arrangement matters because it could set a practical benchmark for future platform-safety negotiations while helping Meta avoid being placed at a competitive disadvantage by stricter rules.

Subject to court approval, Meta would pay at least $12 billion, with a further $5.3 billion conditional on all three named rivals introducing measures such as daily usage limits and default nighttime notification restrictions. TikTok and YouTube would also need comparable settlements with states; otherwise Meta could reduce its own payment by about $5 billion. The agreement additionally envisages Apple and Google sharing reliable age signals with Meta to support age verification.

  • Meta’s child-safety settlement could pressure rivals into matching restrictions.
  • At least $12 billion is due if the deal is approved.
  • Meta’s additional payment depends on TikTok, YouTube and Snap.

New here? Start with this

Meta is the US technology company behind Facebook, Instagram and WhatsApp. It has faced lawsuits from US states alleging that features of its social-media services can harm young users, while TikTok, YouTube and Snap face similar scrutiny over how children and teenagers use their platforms.

The proposed settlement would require Meta to make changes intended to protect younger users and would involve a large payment to states and other authorities. Its unusual feature is that the final cost could depend partly on whether rival platforms accept comparable restrictions and financial settlements.

This matters because agreements of this scale can influence how social-media companies design their services for young people. It could also increase pressure on Apple and Google, whose phone software and app stores may be able to provide age information used by the platforms.

Both sides, in good faith

The strongest fair case each way — we don't pick a winner.

The case for

Supporters could argue that child-safety obligations should apply consistently across the major platforms where young people spend time, rather than allowing one company to bear the cost while competitors continue with less demanding safeguards. They may see Meta’s proposal as a way to create a workable industry baseline, encourage reliable age assurance from app-store gatekeepers, and prevent regulation from distorting competition by imposing uneven rules. The conditional payment structure can be presented as an incentive for a coordinated settlement that delivers broader protection for children.

The case against

Critics could argue that a settlement intended to address Meta’s own alleged conduct should not make its financial liability depend on whether its commercial rivals accept comparable restrictions or payments. In their view, this risks turning child-safety enforcement into a competitive bargaining tool, pressuring other firms through public campaigns and potentially insulating Meta from accountability. They may also question whether linking the deal to Apple and Google’s age signals would concentrate too much influence over access to online services without sufficient independent scrutiny.

More coverage

Americas Business Markets Software Technology Trending Weird & Viral World

Read the full article at the source →

Cookie-free view counts · Privacy choices

We count page views to improve this website, including before you choose optional analytics. This counter keeps only a daily total: no visitor IDs, page addresses or browsing histories. It uses no tracking cookies and sends no data to Google or Microsoft. Optional analytics add richer reports if you accept them.

Your choice is remembered using a preference cookie. Rejecting analytics, Do Not Track and Global Privacy Control also stop this counter. Ordinary server access logs are separate.