China Android app stores App Review issue

Real-name requirement in China Android app stores

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 real name requirementchina app real name policyandroid china real-name registration

Fix China Android app stores review issues before the next submission

Use LogicSpring to run a free precheck, regenerate the right policy or disclosure pack, and shorten the loop from rejection notice to resubmission.

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.

What this means

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.

Common causes

  • The app category or feature set triggers identity-related scrutiny but the submission package treats it like a generic app.
  • Terms, privacy policy, or onboarding do not explain any identity or account requirements clearly enough.
  • The team has not documented which features are gated or region-specific.

Step-by-step fix

  1. Step 1

    Clarify whether the app actually falls under a real-name requirement and which features are affected.

  2. Step 2

    Update onboarding, policy, and reviewer notes to explain registration and identity handling accurately.

  3. Step 3

    Restrict or defer features if the current implementation cannot support the required compliance posture.

What to update

  • Onboarding and registration flow
  • Privacy Policy identity sections
  • Terms of Service
  • Reviewer notes

FAQ

Can I resubmit to China Android app stores without changing the binary?

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.

What evidence should I prepare before resubmitting?

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.

Should the privacy policy, store form, and in-app disclosure all match?

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.