Summary
The app falls into a category where real-name or stronger identity-related rules apply, and the current compliance package does not reflect that.
China Android app stores App Review issue
The app falls into a category where real-name or stronger identity-related rules apply, and the current compliance package does not reflect that.
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 falls into a category where real-name or stronger identity-related rules apply, and the current compliance package does not reflect that.
Some app categories in China face stronger identity verification, account registration, or traceability expectations.
Even if the app only partially touches those categories, stores may still ask for more explicit explanation.
This is especially relevant for social, community, fintech, and content-heavy apps.
Clarify whether the app actually falls under a real-name requirement and which features are affected.
Update onboarding, policy, and reviewer notes to explain registration and identity handling accurately.
Restrict or defer features if the current implementation cannot support the required compliance posture.
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.