Repository navigation
|
How can a team catch Missing store age-signal integration for US state ASAA duties automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rnE 'ageCategory|minorUser|parentalConsent|DeclaredAgeRange|age-signals' . && ! grep -rqE 'verifyParentalConsent|handleAgeCategorySignal|rescindConsent|deleteAgeVerificationData' .Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. 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. The fix. 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. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
BOTH-US-ASAA-AGE-SIGNALS-MISSINGwith a coverage line and a proper exit code.What the hit means. Heuristic, not a certification. An app with accounts or age-gated features shows no integration with the st…