Summary
The app faces scrutiny under minor-protection or youth-safety rules, and current policy, age gating, or feature controls are not sufficient.
China Android app stores App Review issue
The app faces scrutiny under minor-protection or youth-safety rules, and current policy, age gating, or feature controls are not sufficient.
Use LogicSpring to run a free precheck, regenerate the right policy or disclosure pack, and shorten the loop from rejection notice to resubmission.
The app faces scrutiny under minor-protection or youth-safety rules, and current policy, age gating, or feature controls are not sufficient.
Stores may expect stronger disclosure and user-protection measures when minors could access the app or its content.
This can affect content, social interaction, account settings, spending flows, and personal information handling.
The issue often spans privacy policy, Terms, age gating, and moderation controls.
Audit whether the app targets, permits, or could materially attract minors in the target category.
Add or clarify age gating, parental or guardian controls, and minor-data disclosure sections.
Update reviewer notes and policy documents to show how minor protection is implemented in practice.
Only for pure listing or form corrections. If the shipped build still requests the wrong permission, bundles the wrong SDK, or behaves inconsistently, resubmitting the same build is risky.
Prepare the updated public policy URL, the exact store fields you changed, screenshots for permission or disclosure flows where relevant, and a short reviewer note explaining what changed and why it now matches the app.
Yes. Review teams compare these surfaces together. If one says you collect or disclose something and another says you do not, the mismatch itself often becomes the next rejection.