Parents Decide Act
- Sponsor
- Rep. Gottheimer, Josh [D-NJ-5]
- Committees
- Energy and Commerce Committee (primary)
- Last action
- Apr 13, 2026
Bottom line
The Parents Decide Act aims to empower parents by mandating age verification and control features at the operating system level, significantly impacting tech companies' data collection and privacy practices.
What it actually does
This bill mandates operating system (OS) providers to implement age verification for all users, requiring parental or legal guardian verification for users under 18. It also compels OS providers to create a system allowing app developers to access this age verification information. The Federal Trade Commission (FTC) is tasked with promulgating regulations to define how these requirements are met, including data protection standards and parental control over app access.
Proponents argue
Proponents argue that this bill is a crucial step in protecting children online by giving parents the necessary tools to monitor and control their children's digital interactions and access. They contend it creates a safer digital environment, addresses growing concerns about minors' exposure to inappropriate content, and holds tech companies accountable for user safety.
Opponents contend
Opponents may raise significant concerns about the privacy implications of mandating extensive age and parental identity verification, arguing it could lead to over-collection of sensitive personal data. They might also highlight the technical complexities and substantial compliance costs for operating system providers and app developers, which could stifle innovation or be passed on to consumers. Critics could also question the effectiveness of such a system in preventing minors from circumventing controls.
The bill is short and straightforward, allowing for quick comprehension of its core mandates within a typical legislative review period.
Section 2(a)(1)
Mandatory Age Verification for All Users
This provision requires all operating system providers to demand a user's date of birth when setting up an account or using the operating system. This establishes a foundational requirement for age-gating access to computing devices and their functionalities.
Supporters argue
Supporters argue that this is a necessary first step to ensure children are protected online by establishing a baseline age for all users, allowing for subsequent age-appropriate content filtering and parental controls.
Critics contend
Critics contend that mandating date of birth collection for all users, regardless of age, represents a significant privacy intrusion and could lead to large databases of sensitive personal information that are vulnerable to breaches.
Tradeoffs
This provision balances the desire for universal child protection mechanisms against concerns regarding broad data collection and user privacy for adults.
Section 2(a)(2)
Parental Verification for Minor Users
If an operating system user is identified as being under 18 years of age, their parent or legal guardian must verify the user's date of birth. This provision aims to ensure that age declarations for minors are accurate and have parental consent.
Section 2(a)(3)
App Developer Access to Age Information
Operating system providers are required to develop a system that allows app developers to access the age verification information collected by the OS. This aims to enable apps to implement their own age-appropriate content or access restrictions based on the OS-verified age.
Section 2(d)(1)
FTC Rulemaking Authority
This section grants the Federal Trade Commission (FTC) broad authority to promulgate regulations within 180 days of enactment. These regulations will detail how OS providers verify parental age, manage shared devices, implement data protection standards for collected age data, and ensure parents can control what minors access on a device.
Establishes a 'Safe Harbor' provision, stating that an operating system provider cannot be held liable for a violation of this Act or its regulations if the provider follows the requirements described in such provision or regulation.
Section 2(b)
Why it matters:This is standard legislative practice to encourage compliance by offering protection from liability for those who adhere to the law. It's not necessarily evasive but can be missed by those focusing only on the direct requirements.
Case for: Supporters argue that the safe harbor is crucial for encouraging OS providers to invest in and implement the required age verification systems without fear of excessive litigation, provided they make good faith efforts to comply with the law and regulations.
Case against: Critics might argue that a broad safe harbor could potentially reduce the incentive for OS providers to go beyond the minimum compliance, potentially leaving loopholes or less robust protections if the regulations themselves are not sufficiently stringent.
Estimated impact: Significantly limits the legal exposure of operating system providers who comply with the Act, potentially reducing the number of lawsuits they face related to age verification failures.
Requires the FTC to promulgate regulations establishing 'Data protection standards related to how an operating system provider shall ensure a date of birth collected... is collected in a secure manner to maintain the privacy of the user... and is not stolen or breached.'
Section 2(d)(1)(B)
Why it matters:This is standard legislative drafting for delegating technical specifics to an expert agency. It's not evasive, but its importance can be understated by its placement within a list of regulatory topics.
Case for: Proponents assert that strong data protection standards are paramount to prevent the misuse or exposure of sensitive age and parental verification data. They argue that FTC oversight ensures these systems are built with privacy and security by design.
Case against: Some critics might argue that while important, the specifics of these standards could be overly prescriptive, technically challenging, or costly for OS providers to implement, potentially leading to a 'lowest common denominator' approach if not carefully crafted.
Estimated impact: Crucially defines the security and privacy posture for all age verification data collected under the Act, impacting the trust users place in the system and the vulnerability of sensitive personal information.