Alabama committee hears hours of testimony on bill to require app‑store age verification and parental consent

A House committee on HB317 heard more than a dozen witnesses on a bill that would require app stores to verify a user’s age and obtain parental approval before a minor downloads an app.

The bill’s sponsor, Representative Johnny Sells, told the committee HB317 is “part of a package” intended to protect children in digital spaces, saying legislators already take safety steps for kids in other contexts. “We do different things to protect our children,” Sells said as he introduced the measure.

Why it matters: Supporters told legislators the measure would give parents a single point of control over app downloads and reduce privacy risks from sharing sensitive data with many separate app developers. Opponents warned the bill could raise First Amendment and privacy issues, be legally vulnerable in court and impose burdens on small developers that do not operate social platforms.

Supporters’ case Nicole Lopez, safety policy director for youth at Meta, said parents are overwhelmed by the number of apps teens use and urged app‑store verification as the most practical, privacy‑protective option. “We believe the easiest, most accurate, and most privacy‑protective solution is to require app stores to verify ages and to get parental approval anytime a teen under 16 wants to download an app,” Lopez testified. She said app stores already collect birthdate information when parents set up family accounts and could route a single approval to multiple apps.

Christie Horn and Malia Stevens, who identified themselves as affiliated with child‑safety advocacy, stressed that apps can expose children to privacy risks and exploitation and said layered protections — age verification, accurate ratings and parental control — are needed. “This bill finally gives parents the ability to protect their children,” Horn said.

The Digital Childhood Alliance’s John Reed, a former Department of Justice attorney who said he spent years working on app‑store issues, framed the bill as contract‑focused and content‑neutral. Reed said the measure prevents minors from binding themselves to terms of service without a parent’s consent: “When your kid signs that term of service on the app, they're committed to a contract with legal obligations,” he said.

Opposition and concerns Representatives of trade groups and developers warned the committee the draft is overbroad. Caleb Williamson, state public policy counsel at the App Association, said many app developers are small businesses that produce educational or single‑purpose apps and are not social platforms. “Our members are building apps that aren't necessarily fostering an environment where people can communicate with one another,” Williamson said, arguing the bill’s mechanisms could impose unnecessary burdens on those developers.

Justin Hill of NetChoice said parental education and engagement are necessary and warned lawmakers not to expect the bill to fix all harms. “Parents are gonna get a false sense of security if you pass legislation like this,” Hill said, adding that courts have struck down other state age‑verification laws.

A commenter who identified himself as Knox Argo urged caution, saying several states had considered similar measures and some had not passed them. “This bill really doesn't take care of all the problems that people said they want to take care of,” Argo said.

Committee action and next steps Committee members asked detailed questions about how the bill would identify a parent or guardian, whether grandparents or other caregivers could act, whether consent would need to be renewed after app updates, and how the App Store would share limited age information with developers. Sponsor Sells and other supporters said the bill uses an app‑store signal to convey minimal age/consent information and that renewal would be required for substantive app updates.

The committee did not vote on HB317. Chair Sells told members the committee will continue studying the bill and indicated amendments would be considered at a later date; several members urged drafting changes to address constitutional and small‑developer concerns. The chair also provided a comparison of similar bills in other states and said staff would circulate that summary to committee members.

Ending note The hearing featured testimony from technology companies, child‑safety advocates, developer representatives and private citizens. Witnesses repeatedly urged the committee to balance parental authority, privacy protections and the potential legal risks of the proposal as it is revised.