Summary
The store flagged the app because personal-information collection, scope limitation, or disclosure detail does not meet China Android app stores review expectations.
China Android app stores App Review issue
Personal info collection rules in China Android app stores
The store flagged the app because personal-information collection, scope limitation, or disclosure detail does not meet China Android app stores review expectations.
china android personal info collection ruleschina app personal information rulesandroid china privacy collection
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.
What this means
Stores expect personal-information collection to be necessary, transparent, and limited to the declared purpose.
The policy and prompts should explain what is collected, why it is needed, and whether third parties receive it.
This is a core launch issue for most submissions to China Android app stores.
Common causes
- The app collects more fields than are obviously needed for the feature or explains them too vaguely.
- The privacy policy, permission prompts, and SDK disclosures describe different collection scopes.
- Retention, sharing, or user-rights explanations are missing or too generic.
Step-by-step fix
- Step 1
Map each personal-information field to a necessary feature-level purpose and remove unnecessary collection.
- Step 2
Rewrite policy, prompts, and store materials so the same collection scope appears everywhere.
- Step 3
Check vendor and SDK disclosures so third-party collection is not omitted.
What to update
- Chinese Privacy Policy
- Permission prompts
- Store disclosure materials
- SDK vendor list
How LogicSpring helps
- LogicSpring helps launch teams turn raw data inventory into clearer China-facing privacy and SDK disclosures.
- You can regenerate the policy and export materials from one structured project instead of separate manual docs.
- Precheck reduces the risk of fixing collection scope in one place but not another.
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.