The Parents Over Platforms Act requires application distribution platforms and app developers to implement age‑assurance measures across connected devices, provide parents with controls to block or limit minors’ access, and prohibit personalized advertising to minors. It defines an interoperable "Age Signal" that distributors must make callable by developers (with parental consent), and it sets out data‑minimization rules and limits on how age information may be used or shared.
The bill matters because it pushes responsibility for age verification and parental controls onto both app stores and app makers, creates an FTC enforcement pathway (treating violations as unfair or deceptive acts), and preempts state laws on the same topic. The Act also grants liability protections to distributors and operating system providers that make good faith compliance efforts, while imposing compliance and operational requirements on developers of apps that provide different experiences by age.
At a Glance
What It Does
Establishes a federated Age Signal framework: app distribution providers must collect or estimate users’ Age Categories and expose a callable Age Signal to developers when the account holder or a parent agrees. Developers of Covered Applications must use commercially reasonable methods to determine age, block or gate Adult‑only features from minors, and may not deliver personalized advertising to minors.
Who It Affects
Application distribution providers and operating system owners (who must implement age collection and parental controls), developers of mobile/tablet/VR/gaming apps that offer different experiences by age, advertisers who rely on cross‑site behavioral targeting, and parents seeking centralized controls over app acquisition.
Why It Matters
The Act centralizes age assurance at the platform/distributor level while imposing direct duties on developers and banning personalized advertising to minors—shifting implementation costs and compliance risk, creating new data‑handling limits, and giving the FTC primary enforcement authority with federal preemption of state regulation.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill builds an "Age Signal" framework around the mobile application ecosystem. Application distribution providers must ask users to declare age, use commercially reasonable methods to estimate age, give parents tools to block or prevent non‑adult accounts from acquiring apps, and provide a technical mechanism developers can call to receive an Age Signal when the user or parent permits sharing.
App distributors must also host or display developers’ parental‑control information on centralized product pages.
Developers that offer different experiences for Adults and Minors ("Covered Applications") must report that status to the distributor, use commercially reasonable methods to determine age, block minors from Adult‑only features or content, obtain consent before permitting minors to access content the developer marks as unsuitable without parental supervision, and refrain from delivering personalized advertising to minors. Developers may rely on an Age Signal from the distributor to meet their obligations, but they must limit the information requested, not willfully ignore available age information, not use age data to reconstruct date of birth, and not share Age Signal data except with necessary service providers or as required by law.Liability is allocated: distributors and operating system providers get a safety‑net if they make good faith efforts to comply—no liability for erroneous Age Signals, outages, or for developers’ misuse of Age Signals.
Developers retain primary responsibility for identifying whether their apps are "Covered Applications" and remain liable for correctly implementing age gating. Enforcement is through the Federal Trade Commission treating violations as unfair or deceptive acts; the bill also preempts state laws on the subject.
Finally, the Act becomes effective no later than 24 months after enactment, giving covered entities a limited transition window.
The Five Things You Need to Know
The Act defines an "Age Signal" that distributors must expose to developers when a user or the user’s parent agrees to share age category information.
Application distribution providers must give parents the ability to block non‑adult accounts from acquiring or using specific Covered Applications via centralized controls.
Developers of Covered Applications must not deliver personalized advertising to account holders who are Minors and must obtain parental consent before allowing minors access to Adult‑designated content.
The FTC enforces the Act by treating violations as unfair or deceptive acts under the Federal Trade Commission Act and gains full investigatory and remedial authority; the law also preempts any state or local laws on the same topic.
The Act shields distributors and operating system providers from liability for erroneous Age Signals or outages if they made good faith compliance efforts, while placing the onus on developers to identify Covered Applications and implement age‑gating correctly.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Definitions that set the scope (Age Signal, Covered Application, Minor, Adult)
This section establishes the vocabulary that determines who counts as a Minor versus an Adult, what constitutes a Covered Application (apps that provide different experiences by age or are intended only for adults), and what an Age Signal is (a shareable indicator of age category agreed to by the account holder or parent). Practically, those definitions decide whether an app must implement age gates and whether the Age Signal mechanism applies to a given product; they also exclude browsers, online search engines, and browser extensions from the bill’s coverage.
Platform duties: collect age, estimate when needed, and provide Age Signals
Application distribution providers must prompt for age at account creation, may use commercially reasonable methods to estimate Age Category, and must expose a callable Age Signal to developers when sharing is authorized. They must also offer parents tools to obtain and correct Age Category information. The provision permits multiple estimation methods and allows distributors to rely on a parent’s input for minors, which institutionalizes platforms as central age‑assurance points for the app ecosystem.
App store functions: parental controls, developer product pages, and anti‑preference rule
Distributors must provide parents an interface to block non‑adult accounts from acquiring apps and must let developers present parental control information on centralized product pages. Importantly, distributors are barred from using data collected from third‑party apps while complying with these duties to favor their own apps or act anticompetitively—an explicit attempt to prevent app stores from converting age‑assurance data into marketplace leverage.
Developer obligations: age verification, gating, consent, and advertising ban
Developers of Covered Applications must report status to the distributor, use commercially reasonable efforts to determine age, block minors from Adult‑only features, obtain consent before allowing minors into certain content, and may not serve personalized ads to minors. When relying on the Age Signal, developers must minimize data requested, avoid willful blindness to other age information, restrict sharing to necessary service providers, and not repurpose age data to reconstruct birthdates.
Liability limits, FTC enforcement, preemption, and effective date
The bill limits distributor and OS provider liability for erroneous Age Signals or outages if they made good faith efforts to comply, while holding developers accountable for correctly classifying Covered Applications and reasonably using Age Signals. Enforcement is delegated to the FTC under its unfair/deceptive acts authority, with penalties and remedies available under the FTC Act. The statute preempts state law on the same subject, and it takes effect no later than 24 months after enactment.
This bill is one of many.
Codify tracks hundreds of bills on Privacy across all five countries.
Explore Privacy in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Parents — gain centralized controls at the app store level to block or restrict non‑adult accounts from acquiring apps and to view developers’ parental‑control information, making parental supervision more scalable.
- Minors (privacy/protection) — receive explicit protections: Adult‑only features and personalized advertising are to be blocked or prohibited, reducing exposure to age‑inappropriate content and cross‑site behavioral targeting.
- Application distribution and operating system providers — get clarity on responsibilities and a statutory liability shield for good‑faith compliance, plus control over the technical Age Signal interface.
- Developers that build age‑aware experiences responsibly — obtain an interoperable Age Signal to simplify compliance and can rely on distributor signals (with limits), reducing the need to build fragmented age systems for each platform.
Who Bears the Cost
- Small and independent developers — face implementation costs to assess, report, and gate content, and to modify data practices to avoid personalized advertising to minors.
- Advertisers and ad tech firms — lose the ability to use cross‑site behavioral targeting for minors, forcing shifts to contextual or first‑party strategies and possible revenue decline for apps with significant minor audiences.
- Application distribution providers and OS vendors — must implement age‑estimation mechanisms, parental control UIs, Age Signal APIs, and compliance processes; those operational and engineering costs come alongside legal and policy work to interpret "commercially reasonable" methods.
- State and local regulators — are preempted from enforcing their own age‑assurance regimes, which shifts regulatory oversight and any localized policy goals to the federal level (FTC).
Key Issues
The Core Tension
The central dilemma is balancing effective, centralized parental control and child protection against the privacy and market‑concentration risks of routing age data through a few platform operators: the bill solves fragmentation and parental burden by placing authority and responsibility on distributors, but doing so concentrates sensitive data and leaves open how to define acceptable methods, enforce data‑use limits, and prevent platform market‑power from translating into competitive advantage.
The bill pushes complex technical and policy choices into a short list of terms: "commercially reasonable" methods, "Age Signal" mechanics, and what counts as a Covered Application. Those are implementation choke points. "Commercially reasonable" is intentionally vague: it gives platforms and developers flexibility but creates uncertainty about testing standards, acceptable accuracy rates, and what methods (biometrics, identity documents, AI estimation, payment data) are permitted.
That uncertainty will matter when the FTC evaluates good‑faith compliance or when developers decide whether an Age Signal alone suffices for legally mandated age restrictions.
Centralizing age assurance at distributors simplifies parental control for many families but concentrates sensitive age metadata with a few platform owners. The bill tries to limit secondary uses—prohibiting distributors from using third‑party app data to favor themselves and forbidding developers from using Age Signals to reconstruct birthdates—but enforcement depends on internal platform transparency and FTC investigatory power.
The prohibition on personalized ads to minors also creates measurement and monetization tensions: apps that monetize through targeted ads must rework business models or implement robust age gating, which could incentivize platforms to default to less privacy‑protective age estimation approaches or to favor first‑party data models.
Operationally, the bill excludes browsers and search engines from coverage while allowing Covered Websites to reuse Age Signals, which raises cross‑platform interoperability questions (e.g., how an age signal issued by an app store authenticates on the open web). The 24‑month compliance window reduces immediate pressure but does not resolve international data flows, COPPA overlap, or how to treat minors who lie about age or share accounts.
Finally, the liability shield for distributors depends on the FTC’s interpretation of "good faith" efforts and available technology—an interpretive contest that will determine whether the shield operates broadly or narrowly in practice.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.