Summary
The store requires a Chinese privacy policy or a more explicit privacy notice than the app currently provides.
China Android app stores App Review issue
Privacy policy required in China Android app stores
The store requires a Chinese privacy policy or a more explicit privacy notice than the app currently provides.
china android privacy policy requiredchina app store privacy policyandroid china store privacy policy
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
China Android app stores generally expect a Chinese-language privacy policy that matches local disclosure expectations.
A translated global policy is often not enough if it lacks SDK details, permission explanations, or local compliance structure.
The policy may also need to be linked from both the listing and the app itself.
Common causes
- No Chinese privacy policy exists or the linked version is not public.
- The policy is a direct translation of a generic global template and lacks China-specific disclosure detail.
- The policy does not match the SDK inventory, permissions, or account/deletion flows visible in the app.
What the rejection often looks like
- The store says a Chinese privacy policy is missing, not publicly accessible, or does not meet platform disclosure requirements.
- Reviewers note that the current policy is only in English or is a generic translation without enough detail about permissions, SDKs, and personal information handling.
- The app is blocked because in-app privacy links, listing links, and the actual hosted policy do not match.
Step-by-step fix
- Step 1
Publish a public Chinese privacy policy covering local disclosure expectations, SDKs, permissions, and user rights.
- Step 2
Align that policy with the app's current data collection and third-party integrations.
- Step 3
Update all listing and in-app links to point to the current Chinese policy.
What to update
- Chinese privacy policy document
- In-app privacy entry and footer links
- Store listing privacy URL
- SDK, permission, and personal information disclosure sections
How to avoid getting rejected again
- Maintain a China-ready privacy policy variant instead of translating the global policy at submission time.
- Check that the Chinese policy and SDK list are published together and linked consistently from store listing and in-app settings.
- Review account deletion, permission disclosure, and personal-information sections before every submission to China Android app stores because those often drift first.
How LogicSpring helps
- LogicSpring can generate English and Chinese policy variants from one structured project.
- The China workflow helps teams avoid shipping a thin translated policy that still gets rejected.
- This speeds up launches into China-focused Android ecosystems without rebuilding the compliance stack from scratch.
FAQ
Do China Android app stores require a Chinese-language privacy policy?
In practice, yes for most serious launches. A Chinese-language policy is often expected, and it usually needs more explicit local disclosure detail than a direct translation of a global template provides.
Why does a translated global privacy policy still get rejected in review for China Android app stores?
Because stores often expect local structure and concrete details around SDKs, permissions, personal-information collection, user rights, and account management. A literal translation can still be too thin for review.
Where should the Chinese privacy policy be linked?
It should usually be accessible from the store listing and from inside the app, and both links should point to the same current hosted policy so reviewers do not see conflicting versions.