Table of contents
- Quick nav
China Store Privacy Policy Screenshots: Popup + In-App Entry Capture Guide
Reviewers want proof of the UX, not only a URL
When a China Android store asks for 隐私政策截图, they usually want evidence that the app shows consent UI and a revisit path—not another marketing screenshot. Behavioral rules are covered in the privacy compliance checklist. This article is the capture playbook.
The standard pair
| Asset | Must be readable in the frame | Common fails |
|---|---|---|
| ① First-launch privacy dialog | Policy link or text; clear Agree and Disagree / Not now actions | No dialog; only “Got it”; pre-ticked consent |
| ② Permanent entry | Settings / Me / About opens the policy again | Buried deeper than ~4 taps; 404 |
Many consoles also require the full policy text or a public URL, identical to what ships in the binary.
Capturing the dialog (①)
- Fresh install or clear data so first-launch logic runs.
- Frame the whole dialog: title, summary or “View privacy policy”, both buttons.
- If the policy opens in a WebView, add a second shot of scrollable readable content (some stores reject “download only”).
- Prefer explicit consent wording over a single dismissive “OK”.
- Do not collect personal information before consent—the screenshot cannot prove code, but mistimed dialogs fail automated checks.
Use a phone-like canvas (for example 1080×1920) and compress to each store’s size cap.
Capturing the permanent entry (②)
- Walk from home to Settings → Privacy policy (or equivalent).
- Final screen must show the full policy or a stable H5; entity name and contact must match developer registration.
- If you have accounts, the policy should describe deletion/注销; the screenshot at least proves the entry exists—keep a short screen recording for tougher reviews.
Do not mix materials
| Material | Purpose |
|---|---|
| Feature screenshots | Listing conversion — China size hub |
| Beian / ICP proof shots | Filing proof |
| Privacy popup + entry | Notice-and-choice proof |
Platform notes (always re-read the live console docs)
| Store | Typical emphasis |
|---|---|
| Xiaomi | First-launch dialog, no collection before consent, consistent texts, standalone policy |
| MyApp (应用宝) and peers | Dialog + entry images + text/URL; shallow navigation |
| Huawei / OPPO / vivo / Honor | Same themes; field labels vary (“privacy proof”, “agreement screenshots”, …) |
If labels are ambiguous, upload ① and ② as separate files plus one combined strip.
Checklist
- Dialog reproducible on clean install
- Deny / exit path is real
- Entry reachable in roughly four taps
- In-app text matches store URL/attachment
- Entity matches copyright / business license
- Text in the image is sharp
Fix SDK and copy issues with the compliance checklist; screenshots only prove what users can see. Capture on device or simulator, then compress for each store.