Parents Over Platforms Act
- Sponsor
- Sen. Moran, Jerry [R-KS]
- Committees
- Commerce, Science, and Transportation Committee (primary)
- Last action
- Apr 20, 2026
Bottom line
The Parents Over Platforms Act aims to enhance online safety and privacy for minors by requiring age verification and restricting data practices within the mobile app ecosystem, while centralizing enforcement under the Federal Trade Commission.
What it actually does
This bill mandates that application distribution providers (like app stores) implement age assurance mechanisms, including asking users to declare their age and providing age signals to app developers. It requires developers of 'covered applications' (apps with different experiences for adults and minors, or adult-only apps) to use commercially reasonable efforts to determine user age, prevent minors from accessing adult-only content, obtain parental consent for age-gated content, and prohibits personalized advertising to minors. It also preempts state and local laws related to these provisions.
Proponents argue
Supporters argue that this bill is a crucial step to protect children from harmful online content and exploitative data practices, such as personalized advertising, by empowering parents with greater control over their children's digital experiences. They contend that establishing a clear federal standard for age assurance will create a safer online environment for minors and hold technology companies accountable for their impact on youth.
Opponents contend
Critics may contend that the bill's age verification requirements could lead to increased data collection on all users, raising privacy concerns for adults and potentially creating new vulnerabilities for data breaches. They might also argue that the mandates impose significant technical and financial burdens on app developers, particularly smaller entities, potentially stifling innovation and limiting access to online services, while the preemption clause could undermine more robust state-level protections.
The bill is relatively short and clearly structured, making it accessible for an informed reader to understand its core provisions and implications within a reasonable timeframe.
Sec. 101(a)
Application Distribution Provider Age Assurance Responsibilities
This section requires application distribution providers (ADPs), such as app stores, to ask account holders for their age when creating an account. ADPs must use commercially reasonable efforts to determine an account holder's age category and provide a mechanism for users to update their age if incorrect. Crucially, ADPs must also offer developers of covered applications the technical ability to access an 'age signal' if the account holder or their parent agrees to share it.
Supporters argue
Proponents argue that these requirements are fundamental to creating a safer online environment for minors, as they establish a baseline for age verification at the point of entry into the mobile ecosystem. They contend that providing age signals to developers is essential for enabling apps to tailor experiences appropriately for different age groups.
Critics contend
Opponents may raise concerns that mandating age declaration and verification could lead to increased collection of personal data, potentially infringing on user privacy and creating larger targets for data breaches. They might also argue about the technical feasibility and accuracy of 'commercially reasonable efforts' to determine age.
Tradeoffs
This provision balances the desire for enhanced child protection through age verification against potential privacy concerns arising from increased data collection and the technical challenges of accurate age estimation.
Sec. 102(a)
Application Distribution Provider Parental Control and Data Use Obligations
This section requires ADPs to provide parents with the ability to prevent their minor children from acquiring or using specific covered applications. ADPs must also offer developers a centralized way to provide information about their app's parental controls. Importantly, ADPs are prohibited from using data collected from third-party covered applications for anti-competitive purposes, such as favoring their own applications.
Sec. 102(b)(1)(F)
Prohibition on Personalized Advertising to Minors
This specific clause prohibits developers of covered applications from delivering personalized advertising to minors. Personalized advertising is defined as ads selected based on personal data obtained from an account holder's activities over time and across non-affiliated websites or online applications to predict preferences or interests. It explicitly excludes contextual advertising or advertising based on activities within the developer's own applications.
Sec. 102(b)(1)(G) and (H)
Restrictions on Age Data Use by Developers
These subsections impose strict limitations on how developers of covered applications can use age information, whether obtained via an age signal from an ADP or through their own methods. Developers must request the minimum amount of information needed for compliance, cannot willfully disregard available age information, and are severely restricted in sharing age data with third parties (only for safety/privacy measures or legal requirements). They are explicitly prohibited from using age data for any purpose beyond the Act's intent, including attempting to obtain a user's date of birth.
Sec. 203
Federal Preemption of State and Local Laws
This section establishes that no state or political subdivision can maintain, enforce, prescribe, or continue in effect any law, rule, regulation, requirement, standard, or other provision that has the force and effect of law, if it is related to the provisions of this Act. This means the federal law would override any existing or future state or local laws on age assurance practices within the mobile ecosystem covered by this Act.
The definitions of 'covered application' and 'covered website' are critical, as they determine the scope of entities subject to the bill's most stringent requirements. A 'covered application' is one where a developer provides a 'different experience for adults than for minors' or an 'experience that is intended only for adults.' This includes different account types, content, features, advertising, or data practices based on age. 'Covered website' extends these requirements to URL-accessible versions of covered applications.
Sec. 2(9) and Sec. 2(10)
Why it matters:Defining scope in the definitions section is standard legislative practice. However, the breadth of 'covered application' means many apps not typically considered 'adult-only' could fall under its purview, which might be overlooked.
Case for: Supporters would argue that these broad definitions are necessary to ensure comprehensive protection for minors across a wide range of digital experiences, preventing developers from creating age-differentiated content without adhering to safety standards.
Case against: Critics might argue that the definitions are overly broad and could inadvertently capture applications that pose minimal risk to minors, imposing unnecessary compliance burdens on a vast number of developers. This could lead to a chilling effect on age-appropriate content development.
Estimated impact: Significantly expands the number of applications and websites subject to age assurance, parental control, and advertising restrictions, impacting a large segment of the mobile and web ecosystem.
This subsection specifies an important exception to the 'commercially reasonable effort' standard for age determination. For applications 'intended only for adults and required by law to restrict access to adults,' an age signal indicating a user is an adult is *not* sufficient by itself to satisfy the age determination requirement for purposes of other laws. However, an age signal indicating a user is a minor *is* sufficient to block access.
Sec. 102(b)(2)(B)
Why it matters:This is a technical clarification to ensure the bill's age signal mechanism doesn't inadvertently undermine existing, stricter age verification requirements for certain adult content (e.g., gambling, alcohol, pornography), which is standard legislative drafting to avoid conflicts.
Case for: Proponents would argue this ensures the bill complements, rather than weakens, existing laws that mandate robust age verification for specific adult-only content, thereby maintaining high standards for protecting minors from truly harmful material.
Case against: Critics might argue that this creates a two-tiered system of age verification, adding complexity for developers of legally age-restricted content who must still implement additional, potentially redundant, verification methods beyond the age signal.
Estimated impact: Clarifies that developers of legally age-restricted content cannot solely rely on the age signal for adult users, requiring them to maintain or develop additional, more robust age verification processes for those specific applications.