App Stores Would Need Parental Consent

Summary#

HB 757, the proposed App Store Accountability Act, would add a new chapter to the Code of Virginia; it does not amend a named existing Act. Its stated goal is to create age-category and parental-consent rules for app stores and developers. It is introduced and is not law; if enacted, it would take effect July 1, 2027.

  • App store providers would have to ask for and verify users’ age categories, and set up a minor account linked to a parent account when they determine a user is under 18. Existing accounts would have to be addressed by July 1, 2028.
  • Before a minor downloads or buys an app, or makes an in-app purchase, the store would have to obtain the parent account holder’s affirmative consent after showing information about the app’s rating, content, and data practices.
  • Developers would have to assign age ratings and content descriptions, share required disclosures with app stores, and use age-category and consent information for age-related restrictions, safety features, or defaults.
  • App stores and developers would have to notify users or stores about significant app changes; stores would need renewed parental consent before giving a minor access to the changed version.
  • The Attorney General could seek injunctions and civil penalties of up to $7,500 per violation. A minor or parent who suffers harm could sue for actual damages or $1,000 per violation, whichever is greater, and could seek punitive damages for an egregious violation.

What it means for you#

  • Minors and parents: A minor identified by an app store would need a linked parent account. The parent would have to choose whether to consent before the minor downloads or buys an app or makes an in-app purchase. A parent could later withdraw consent.
  • App store providers: Providers doing business in Virginia would have to verify age categories using a commercially available method reasonably designed for accuracy. They would have to limit and protect age-verification data, and could not enforce a contract against a minor account holder without parental consent.
  • App developers: Developers doing business in Virginia would have to verify users’ age categories and, for minors, whether consent was obtained. They could request age data at specified times and in limited additional circumstances. They could not enforce a contract against a minor without verified parental consent.
  • People using pre-installed apps: Developers could request age-category information and reasonable help from app stores to obtain consent for pre-installed apps. The bill does not generally require blocking access to apps already installed before its effective date. Exceptions include withdrawn parental consent or a significant app change.
  • Emergency-service apps: The bill exempts qualifying apps that provide direct emergency access, meet stated data limits, do not require an account or unnecessary personal information, and are run by or partnered with a government entity, nonprofit, or authorized emergency provider.
  • General public: The bill does not create a new agency or require app stores to block all apps that lack a particular age rating.

Money#

No cost information is in the available material.

  • App stores and developers would have to carry out age verification, consent, data-protection, and notification duties, but the bill gives no cost or staffing estimate.
  • The state could incur enforcement costs; the Attorney General could seek to recover reasonable investigation and case-preparation expenses, including attorney fees.
  • Collected civil penalties and specified expenses and fees would go to a state trust fund. Successful private plaintiffs could recover attorney fees, expert witness fees, and court costs.

What is unclear#

  • The supplied material does not include current Virginia law on these issues, so it is not possible to verify how the bill would change existing duties or overlap with current rules.
  • The bill does not explain what counts as a “reasonable time frame” for developers to report a significant change, or how disputed age ratings, consent decisions, or age categories would be handled.
  • It does not set a process, timeline, or appeal for age verification or consent. It also does not specify how much information app stores must provide when developers request age-category data.
  • One cross-reference appears unclear: the store’s duty to respond to a developer’s request points to a developer duty about using age data, rather than the separate provision that describes when developers may request it.
  • The bill does not define how “harm” or an “egregious” violation would be assessed for private lawsuits, or how “each violation” would be counted for penalties and damages.

Case for#

  • The bill appears intended to give parents a choice before minors download or buy apps or make in-app purchases, and again after certain significant changes.
  • Requiring age ratings, content descriptions, and information about data practices could give parents more information when deciding whether to consent.
  • Having app stores verify age categories could give developers a common source of information, while the bill limits how often developers may request additional age checks.
  • The bill restricts collection and sharing of age data and provides safe harbors for good-faith reliance on commercially reasonable age checks and industry standards.

Case against#

  • Age verification and consent duties could require substantial work by app stores and developers, but the bill gives no cost estimate or detailed compliance process.
  • Age categories and consent status would be shared between stores and developers. The bill limits that sharing, but the required system still creates privacy and data-security responsibilities.
  • The bill does not spell out how to resolve errors or disputes in age verification, ratings, or consent, which could affect whether minors can use apps or whether businesses face liability.
  • Civil penalties and private lawsuits could create significant exposure. The bill does not explain how individual violations would be counted or how “harm” and “egregious” conduct would be judged.