S. 1586 (119th)Bill Overview

App Store Accountability Act

Commerce|Commerce
Sponsor
Cosponsors
Support
Republican
Introduced
May 1, 2025
Discussions
Bill Text
Current stageCommittee

Read twice and referred to the Committee on Commerce, Science, and Transportation.

Introduced
Committee
Floor
President
Law
Congressional Activities
01 · The brief
Plain-English summaryWhat this bill actually does

Requires large app stores (over 5,000,000 U.S. users) to verify user age at account creation, create verified parental accounts for minors, and obtain verifiable parental consent before minors download or purchase apps. App stores must share a real-time age-category signal with developers, prominently display age ratings, and protect age-verification data.

Why people may split

Privacy vs verification: acceptable methods for proving age

Watch point

Relative to its intended legislative type, this bill is a substantive policy change that is generally well-structured: it defines terms, assigns duties to covered app stores and developers, and establishes enforcement and certification mechanisms, but it leaves important technical and resourcing specifics to subsequent guidance or industry standards.

Requires large app stores (over 5,000,000 U.S. users) to verify user age at account creation, create verified parental accounts for minors, and obtain verifiable parental consent before minors download or purchase apps.

App stores must share a real-time age-category signal with developers, prominently display age ratings, and protect age-verification data.

App developers must rely on store signals, limit sharing of age-category data, notify stores of significant changes, and obtain consent when required.

Passage40/100

Technically detailed, moderate-cost child-protection bill with bipartisan potential but faces strong industry lobbying, implementation complexity, and elevated Senate difficulty.

CredibilityPartially aligned

Relative to its intended legislative type, this bill is a substantive policy change that is generally well-structured: it defines terms, assigns duties to covered app stores and developers, and establishes enforcement and certification mechanisms, but it leaves important technical and resourcing specifics to subsequent guidance or industry standards.

Contention58/100

Privacy vs verification: acceptable methods for proving age

02 · What it does

Who stands to gain, and who may push back.

Likely benefits vs burdens50% / 50%
DevelopersDevelopers

These are examples from the analysis, not a ranked list of the most-affected groups.

Likely helped
  • Potential benefitIncreases parental control by requiring verifiable parental consent for minors' app downloads and purchases.
  • Potential benefitImproves transparency by mandating clear age ratings and parental consent disclosures about data practices.
  • DevelopersCreates a uniform federal standard, reducing multistate regulatory variation for app stores and developers.
Likely burdened
  • DevelopersIncreases compliance and operational costs for covered app stores and for developers integrating verification signals.
  • Potential burdenCentralizes age-verification processes and related personal data, raising breach and privacy risk concerns.
  • Potential burdenMay reduce minors' access to apps absent parental accounts or prompt reduced in-app purchases, lowering revenues.
03 · Why people split

Why the argument around this bill splits.

Privacy vs verification: acceptable methods for proving age
Progressive75%

Likely supportive of the bill’s child-safety and parental-consent goals, seeing benefits for protecting minors’ privacy and limiting targeted monetization.

Concerns would focus on how age verification is implemented, potential collection of sensitive identity data, and the bill’s federal preemption which might block stronger state protections.

Support is conditional on strong privacy limits and minimization of intrusive verification methods.

Leans supportive
Centrist60%

Generally favorable to the goals of protecting minors and clarifying parental consent while noting trade-offs.

Wants clear implementation guidance, cost estimates, and technical standards to avoid heavy compliance burdens or unintended privacy harms.

Would favor measured rules, FTC guidance, and the built-in safe harbor, but seek clarity on age-verification methods and effects on small developers.

Split reaction
Conservative30%

May appreciate stronger parental authority and child-safety intent but is inclined to oppose new federal regulatory mandates on platforms and app ecosystems.

Key objections include federal overreach, administrative burdens, preemption of state laws, and potential harms to market competition and innovation.

Likely to prefer less intrusive, state-led, or market-based solutions and narrower federal intervention.

Likely resistant
04 · Can it pass?

The path through Congress.

Introduced

Reached or meaningfully advanced

Committee

Reached or meaningfully advanced

Floor

Still ahead

President

Still ahead

Law

Still ahead

Passage likelihood40/100

Technically detailed, moderate-cost child-protection bill with bipartisan potential but faces strong industry lobbying, implementation complexity, and elevated Senate difficulty.

Scope and complexity
52%
Scopemoderate
52%
Complexitymedium
Why this could stall
  • Absence of cost estimates for industry and enforcement
  • Technical feasibility and privacy risks of proposed age verification
05 · Recent votes

Recent votes on the bill.

No vote history yet

The bill has not accumulated any surfaced votes yet.

06 · Go deeper

Go deeper than the headline read.

Included on this page

Privacy vs verification: acceptable methods for proving age

Technically detailed, moderate-cost child-protection bill with bipartisan potential but faces strong industry lobbying, implementation comp…

Unlocked analysis

Relative to its intended legislative type, this bill is a substantive policy change that is generally well-structured: it defines terms, assigns duties to covered app stores and developers, and establishes enforcement a…

Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.

Perspective breakdownsPassage barriersLegislative design reviewStakeholder impact map
Open full analysis