Skip to content

California AB 1709: Meta, Google and TikTok sue over teen feeds

Filip LuchianencoUpdated 6 min read

Last updated: 2026-11-17

Meta, Google and TikTok each sued California Attorney General Rob Bonta on November 4, 2026 over Assembly Bill 1709 (Lowenthal, Chapter 183 of 2026). AB 1709 adds Business and Professions Code §§ 22682–22686. From January 1, 2027, a covered platform "shall not provide an addictive feature to a user who is under 16 years of age" (§ 22683(a)(1)), and "Before providing an addictive feature to a user, a covered platform shall verify the age of a user pursuant to the Digital Age Assurance Act" (§ 22684(a)(1)). The Digital Age Assurance Act is California's app store age signal law, covered in the post on app store age signal laws.

What does California AB 1709 require?

An "addictive feature" is an addictive feed, autoplay, or a feature the Attorney General adds by regulation (§ 22682(a)). A "covered platform" offers an addictive feature "as a significant part of the service" (§ 22682(c)(1)); services whose user interactions are limited to commercial transactions or consumer reviews, and feeds operated mainly for cloud storage, are excluded (§ 22682(c)(2)). A "user" is a California resident (§ 22682(f)).

A platform may keep accounts for users under 16 if it provides them no addictive feature (§ 22683(a)(2)). Otherwise it must "delete the account of a user under 16 years of age and any personal information associated with the user of the account" (§ 22684(b)(1)).

The age check has two steps. Step one is the Digital Age Assurance Act signal. Step two applies "If a covered platform is unable to verify the age of the user pursuant to paragraph (1)": the platform "shall instead rely on the age determination" under Health and Safety Code § 27001(a)(1)(B) (§ 22684(a)(2)). That provision comes from SB 976, California's 2024 addictive feeds law. Under it, from January 1, 2027, an operator may provide an addictive feed without parental consent where it "has reasonably determined that the user is not a minor".

Only the Attorney General or a local public prosecutor can enforce AB 1709 (§ 22686(a)). Civil penalties are "Up to fifty thousand dollars ($50,000) per affected minor for a knowing violation" and "Up to twenty-five thousand dollars ($25,000) per affected minor for a negligent violation" (§ 22686(b)). The Attorney General may adopt regulations and may alter the scope of "covered platform" (§ 22685). According to footnote 65 of the Meta complaint, no such regulations had been adopted as of its filing.

Who sued, and which sections do the suits challenge?

All three suits challenge the feed and autoplay ban and the deletion duty. Each claim is brought as applied to the plaintiff's own services.

Meta Platforms v. Bonta Google and YouTube v. Bonta TikTok v. Bonta
Court and number N.D. Cal., 3:26-cv-13201 N.D. Cal., 5:26-cv-13204 C.D. Cal., 2:26-cv-12965
Counsel Covington & Burling Cooley Gibson, Dunn & Crutcher
Services Facebook, Instagram, Threads YouTube TikTok
Sections challenged §§ 22682(a)(1)–(2), 22682(c), 22683, 22684(b) §§ 22683(a)(1), 22683(b), 22684(b)(1) §§ 22682(a), (b), (f), 22683, 22684, 22685, 22686
Claims First Amendment; Section 230 Section 230; First Amendment (personalized feeds); equitable and declaratory relief First Amendment (feeds, autoplay, compelled choice); no scienter; Section 230; vagueness; Commerce Clause
Preliminary injunction Docket entry 6, filed November 5, is listed as a preliminary injunction document Motion filed November 5; hearing set on November 9 for April 8, 2027 Sought in the prayer; motion status not established

The complaints are public: Meta (49 pages), Google (28 pages) and TikTok (60 pages).

Meta opens its complaint with the First Amendment protection of "editorial judgments" and continues in ¶1: "California Assembly Bill 1709 ... is California's latest attempt to flout that fundamental principle and appoint the State as the editor, curator, and controller of online speech." Meta states in ¶8 that it "will soon default minors to a cumulative two-hour time limit on Facebook and Instagram that only parents or guardians can override". Google states in ¶6 of its complaint: "Autoplay is off by default for every user under 18".

TikTok's suit is the broadest. In its prayer, TikTok asks for a declaration that §§ 22682(a), 22682(b), 22682(f), 22683, 22684, 22685 and 22686 are unconstitutional as applied or preempted. In Count IV, TikTok argues the penalties apply without scienter, and in ¶186 that the unit of a "violation" is undefined. Count VII is a Commerce Clause and extraterritoriality claim.

Does any suit challenge the age signal check?

Meta and Google leave § 22684(a) out of their claims. Meta's counts are directed at § 22684(b), the deletion duty, and Google's at § 22684(b)(1). The age verification step in § 22684(a)(1), which relies on the app store signal, is outside both suits.

TikTok's prayer covers § 22684 as a whole. Its specific challenge to the verification step is Count VI, a vagueness claim against the fallback. From ¶102 of the TikTok complaint: "The Act does not explain when a platform is 'unable to verify' a user's age." From ¶194, TikTok seeks a declaration that "A.B. 1709's age-verification requirement in § 22684(a)(2) is void for vagueness". Under § 22682(b)(3), a feed selected only on "device communications or signals concerning whether the user is a minor" is outside the definition of an addictive feed. TikTok argues in ¶91 that this information "might not allow TikTok to distinguish one minor from another", and in ¶101: "The Act therefore conditions every Californian's access to TikTok's personalized feed on age verification."

The signal's brackets include a break at 16, the age line in AB 1709. As amended by AB 1856, the Digital Age Assurance Act sets four brackets: under 13, 13 to under 16, 16 to under 18, and 18 or over. A developer that receives the signal "shall be deemed to have actual knowledge of the age range of the user ... even if the developer willfully disregards the signal" (Civil Code § 1798.501(d)(2)(A)), and the developer shall not "Share the signal with a third party for a purpose not required by this title" (§ 1798.501(d)(4)(B)). The Android and iOS interfaces for the signal are covered in the Play Age Signals post and the Declared Age Range post.

The fallback standard was still in rulemaking on November 17, 2026. The Attorney General published proposed SB 976 regulations on May 15, 2026; written comments closed on June 30, 2026, and the status on the page is "The Department is reviewing public comments". From proposed § 560(a): "If an operator has actual knowledge that the user is a minor, including via a signal pursuant to the Digital Age Assurance Act, the operator must not provide covered features unless it obtains verifiable parental consent." Under proposed § 561(a)(2), one age assurance method is "verified information other than age, such as behavioral patterns, data collected about the user, digital interactions, and metadata".

When is the AB 1709 hearing, and what happened with SB 976?

AB 1709 takes effect January 1, 2027 (Meta complaint ¶64). On the Google docket, Google moved for a preliminary injunction on November 5, 2026. The case was reassigned to Judge Beth Labson Freeman on November 6, and on November 9 the hearing was set for April 8, 2027 at 9:00 AM in San Jose, after the effective date. On November 10, the Attorney General filed a stipulated motion "to modify briefing and hearing schedule, permit a consolidated opposition brief, and extend page limits" for the plaintiffs' preliminary injunction motions (docket entry 25). The court entered an order on that stipulation on November 13 (docket entry 26). The text of the order was absent from the public docket copy on November 17, so whether the April 8, 2027 hearing date still stands is not established; the order itself, from PACER, would establish it.

The same three companies sued over SB 976 in 2025. Judge Edward J. Davila denied their preliminary injunction motions on August 5, 2026. Meta's appeal is Ninth Circuit No. 26-5120 (Meta complaint ¶63) and TikTok's is No. 26-5121 (TikTok complaint ¶4). On July 24, 2026, the Fifth Circuit ruled on Texas's minors' online law, including its age-verification duties (the Texas SCOPE Act post). New York's feed rules start January 25, 2027 (the New York SAFE for Kids Act post).

As reported by Courthouse News, a Meta spokesperson said: "Under the law, we would be forced to either remove features that keep teens' experiences age-appropriate, or cut thousands of California teens off from family, friends and their communities." In the same report, the Attorney General's office is quoted as "committed to defending California's commonsense laws to protect kids online".

What can an app scan show about AB 1709?

When I scan an app, I record whether the build contains Google's Play Age Signals library or links Apple's DeclaredAgeRange framework, and whether either is present beside an ad or attribution SDK. Presence means the code is in the build. Whether the app calls the API is established by a device test. Whether an age bracket or an advertising ID from an account set to age 13 to 15 is sent to an ad or analytics host is established by comparing a captured session on that minor account with one on an adult account.

Autoplay and feed contents are on-screen behavior, outside a static scan; whether autoplay starts, and what the feed contains, is visible in a recorded session on a test account. Whether an app is a "covered platform", how its feed is ranked, and whether the operator acted on a signal it received are facts in the operator's records, outside any capture. What a scan checks and the limits of a scan are on the methodology page.

I run these investigations for lawyers and for researchers working with lawyers, on one app or a list of apps in bulk. Sign up for a CanITrustThat account to run your own research, let us run an investigation for you, or read the app teardowns.

App privacy law, applied to real apps.

Posts on new laws, fines and studies, and teardowns of the apps those laws apply to.

How we use your address: privacy notice. Prefer a feed reader? Use the RSS feed.