Repository navigation
|
How can a team catch Random or anonymous chat app without minor blocking and child-safety standards 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 -rqi 'random chat\|anonymous chat\|chat with strangers\|Omegle' . && ! grep -rqi 'ageGate\|minorBlock\|csae' .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. Apps whose core function is randomly connecting users to strangers, or anonymous communication with hidden identities, must use Play Console functionality to block minors, may not target children, and are in scope of the Child Safety Standards policy (published CSAE standards, in-app reporting, CSAM removal, child-safety contact). The fix. Enable the Play Console minor-blocking tools, set the age rating and target audience to exclude children, publish CSAE standards, add in-app reporting, and designate a child-safety contact. 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
GOOGLE-ANON-CHAT-MINOR-BLOCKwith a coverage line and a proper exit code.What the hit means. Apps whose core function is randomly connecting users to strangers, or anonymous communication with hidden identities, must use Play Console functionality to block minors, may not ta…