Repository navigation
|
My app was flagged or rejected on App Store and Google Play for this. Missing store age-signal integration for US state ASAA duties. Which guideline is this, how do I find it in my project, and how do I fix it before I resubmit? |
Replies: 1 comment
|
Guideline. US state App Store Accountability Acts (Utah SB 142, Texas SB 2420, and successor state acts). See docs/GLOBAL-REGULATORY-2026.md section 2.2 (App Store and Google Play) Severity in the playbook. high What triggers it. Heuristic, not a certification. An app with accounts or age-gated features shows no integration with the store age signal surfaces (Declared Age Range on iOS, Play Age Signals API on Android) and no verifiable parental consent handling for minor accounts. Store-side duties began 6 May 2026 (Utah) and are documented with primary sources in docs/GLOBAL-REGULATORY-2026.md section 2.2. What to search your code for. How to fix it. Integrate the store age signal APIs, confirm verifiable parental consent for minor accounts before use, re-request consent on significant changes, and delete raw age verification data after verification. The guard reports this as This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
Guideline. US state App Store Accountability Acts (Utah SB 142, Texas SB 2420, and successor state acts). See docs/GLOBAL-REGULATORY-2026.md section 2.2 (App Store and Google Play)
Severity in the playbook. high
What triggers it. Heuristic, not a certification. An app with accounts or age-gated features shows no integration with the store age signal surfaces (Declared Age Range on iOS, Play Age Signals API on Android) and no verifiable parental consent handling for minor accounts. Store-side duties began 6 May 2026 (Utah) and are documented with primary sources in docs/GLOBAL-REGULATORY-2026.md section 2.2.
What to search your code for.
ageCategory,minorUser,parentalConsent,DeclaredAge…