- 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.
To require operating system providers to verify the age of any user of an operating system, and for other purposes.
Referred to the House Committee on Energy and Commerce.
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.
Popular policy goals offset by significant industry, privacy, and implementation objections and high Senate barriers.
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.
Child safety emphasis versus privacy and data-collection concerns
Who stands to gain, and who may push back.
- 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.
Why the argument around this bill splits.
Child safety emphasis versus privacy and data-collection concerns
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.
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.
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.
The path through Congress.
Reached or meaningfully advanced
Reached or meaningfully advanced
Still ahead
Still ahead
Still ahead
Popular policy goals offset by significant industry, privacy, and implementation objections and high Senate barriers.
- Specific verification methods FTC will permit or require
- Extent of opposition from major technology firms
Recent votes on the bill.
No vote history yet
The bill has not accumulated any surfaced votes yet.
Go deeper than the headline read.
Child safety emphasis versus privacy and data-collection concerns
Popular policy goals offset by significant industry, privacy, and implementation objections and high Senate barriers.
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.