Repository navigation
|
My app was flagged or rejected on Google Play for this. Random or anonymous chat app without minor blocking and child-safety standards. 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. Age-Restricted Content, Families, and Child Safety Standards policies (Play Console Help answers 17036597, 17122218, 14747720, effective 26 August 2026) (Google Play) Severity in the playbook. critical What triggers it. 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). What to search your code for. How to fix it. 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. 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. Age-Restricted Content, Families, and Child Safety Standards policies (Play Console Help answers 17036597, 17122218, 14747720, effective 26 August 2026) (Google Play)
Severity in the playbook. critical
What triggers it. 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).
What to search your code for.
random chat,anonymous chat,chat with strangers,Omegle,strangerHow to fix it. Enable the Play Conso…