H.R. 8250 (119th)Bill Overview

To require operating system providers to verify the age of any user of an operating system, and for other purposes.

Commerce|Commerce
Cosponsors
Support
Bipartisan
Introduced
Apr 13, 2026
Discussions
Bill Text
Current stageCommittee

Referred to the House Committee on Energy and Commerce.

Introduced
Committee
Floor
President
Law
Congressional Activities
01 · The brief

Requires operating system providers to collect users' dates of birth, require parental verification for users under 18, and provide mechanisms for app developers to access age-verification information.

Directs the FTC to promulgate rules within 180 days, enforces violations under FTC authorities, mandates data-protection standards, provides a safe harbor for compliant providers, requires an FTC report in 18 months, and takes effect one year after enactment.

Passage35/100

Popular policy goals offset by significant industry, privacy, and implementation objections and high Senate barriers.

CredibilityPartially aligned

Relative to its intended legislative type, this bill establishes clear statutory obligations and an enforcement framework but relies heavily on delegated rulemaking for technical implementation and omits any discussion of costs or resource implications.

Contention65/100

Child safety emphasis versus privacy and data-collection concerns

02 · What it does

Who stands to gain, and who may push back.

Who this appears to help vs burden50% / 50%
DevelopersDevelopers
Likely helped
  • Targeted stakeholdersProvides parents tools to control minors' device access via verified parental consent.
  • Targeted stakeholdersReduces minors' access to age-restricted apps and potentially harmful content.
  • DevelopersCreates compliance, engineering, and legal work for operating system providers and developers.
Likely burdened
  • Targeted stakeholdersCentralized birthdate collection increases risk from data breaches compromising minors' personal information.
  • DevelopersCompliance costs and technical burdens may be significant for smaller OS providers and developers.
  • Targeted stakeholdersUsers lacking IDs or parental cooperation may be excluded from device use or services.
03 · Why people split

Why the argument around this bill splits.

Child safety emphasis versus privacy and data-collection concerns
Progressive75%

Generally supportive of stronger protections for minors online and parental control tools but wary of centralized personal data collection.

Will stress the need for robust privacy, data-minimization, and protections for marginalized youth.

Leans supportive
Centrist60%

Cautiously favorable toward protecting children and enabling parental controls, but focused on implementation, cost, and realistic verification methods.

Emphasizes need for clear FTC guidance and minimized burdens on consumers and developers.

Split reaction
Conservative25%

Skeptical about federal mandates on operating systems and data collection.

Values parental authority but opposes expansive federal regulation, potential privacy risks, and new burdens on businesses.

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 likelihood35/100

Popular policy goals offset by significant industry, privacy, and implementation objections and high Senate barriers.

Scope and complexity
52%
Scopemoderate
52%
Complexitymedium
Why this could stall
  • Specific verification methods FTC will permit or require
  • Extent of opposition from major technology firms
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

Child safety emphasis versus privacy and data-collection concerns

Popular policy goals offset by significant industry, privacy, and implementation objections and high Senate barriers.

Unlocked analysis

Relative to its intended legislative type, this bill establishes clear statutory obligations and an enforcement framework but relies heavily on delegated rulemaking for technical implementation and omits any discussion…

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