Docs

US App Store Accountability Acts: Age Signal Data to Track

Texas, Utah, Louisiana and California now require apps to consume age-category signals from app stores — the events you need to log to prove compliance.

Analytics

Four US states — Texas, Utah, Louisiana, and California — have enacted App Store Accountability Acts that push age verification up the stack from individual apps to the app stores themselves. Texas’s law took effect January 1, 2026 and is already the subject of legal challenge; the others phase in through 2026 and 2027. The mechanism is the same across states: Apple and Google verify a user’s age band once at the device or account level, then expose that as a signal — an age category and, where relevant, parental consent status — that developers are required to request and act on. For any app with a US user base, this converts age handling from a one-time onboarding screen into an ongoing data pipeline with a real compliance paper trail attached.

The practical risk isn’t the initial integration — Apple’s and Google’s SDKs for reading these signals are reasonably well documented — it’s staying current. Parental consent isn’t a permanent state: a parent can revoke consent for a minor at any point, and once revoked, the law expects the app to detect that change and restrict access accordingly, generally by polling or subscribing to a revocation feed rather than checking once at install. An app that reads the age signal at first launch and never checks again is compliant on day one and silently non-compliant the moment a parent changes their mind.

Data Points to Track

  • Age signal request and response events, logged at the point your app calls the platform API, including which category was returned (not just a pass/fail boolean), so you can audit what the app actually received versus what it acted on
  • Consent status changes, captured whenever a poll or webhook indicates a parental consent revocation, with a timestamp for how long the app took to act on it
  • Feature or content gating decisions, logged alongside the age category that triggered them, creating the audit trail regulators and app stores will expect if a compliance question ever arises
  • Signal request failures or timeouts, since a failed age-check call needs a defined fallback behaviour (fail closed, not open) and that fallback path needs its own logging
  • State-of-user drift, comparing the age category or consent status your app last acted on against the platform’s current value on a recurring check, to catch any case where a background sync silently stopped working

Setup Steps

  1. Confirm which state laws apply to your user base and their respective effective dates, since Texas is already live while other states phase in through 2027 — don’t build to a single compliance date.
  2. Integrate the relevant platform API — Apple’s age signal APIs on iOS, the Play Age Signals API on Android — following each platform’s current documentation rather than a generic pattern, since the exact request/response shape differs.
  3. Build a recurring consent-status check, not just an install-time read, using whichever mechanism the platform provides (polling schedule or push notification) for revocation events.
  4. Define and log the fail-closed fallback for when an age signal request errors or times out, so a platform outage doesn’t silently leave restricted content accessible.
  5. Retain the audit log (signal requests, responses, and resulting gating decisions) for the retention period your legal team specifies, since this is the evidence an app would need to produce if a state regulator investigates.

Actionable Insights

The event to watch most closely in the first months is consent-revocation lag — the gap between a platform reporting a revoked consent and your app acting on it. A long or growing lag is both a compliance exposure and usually a sign the polling or webhook integration is degrading rather than working as designed. Signal request failure rate is the second metric worth a standing dashboard: a spike often means a platform-side API change your integration hasn’t kept pace with, and catching that within days rather than at the next compliance review is the difference between a quick patch and a regulator’s attention.

Expert help

Need help tracking this in your app?

Our team sets up analytics pipelines for mobile and web teams every day. Talk to us and get your first events flowing in under an hour.

Talk to an expert