Resources / App Review Rejections
App Review Rejections for launch-blocking compliance issues
Explore rejection guides across Apple App Store, Google Play, and China Android app stores for Privacy Policy, Data Safety, SDK disclosure, permissions, and other launch-blocking compliance problems.
These guides connect to AI-enhanced analysis with rule-backed checks when you need help diagnosing the next fix.
App Store
App Store rejection guides
App Store privacy policy rejected
Apple rejected the app because the privacy policy URL is missing, inaccessible, too generic, or does not match the app's actual data handling.
App Store App Privacy mismatch
Apple found that App Privacy answers do not match the app binary, policy text, permission usage, or third-party SDK behavior.
App Store Guideline 5.1.1 rejection
Guideline 5.1.1 usually means Apple sees a user privacy or consent problem around data collection, transparency, or permission handling.
App Store Guideline 5.1.2 rejection
Guideline 5.1.2 commonly points to how the app uses collected data, shares it, or gives users control after collection.
App Store tracking transparency rejected
Apple rejected the app because ATT behavior, tracking disclosure, or related policy and App Privacy answers do not match.
App Store SDK disclosure rejected
Apple found that embedded SDKs or their data practices are not disclosed clearly enough in store-facing privacy materials.
App Store permission usage description problem
Apple rejected the app because permission usage descriptions are vague, misleading, or unsupported by the actual feature flow.
App Store user-generated content policy issue
Apple rejected the app because UGC moderation, reporting, blocking, or legal policy requirements are missing or unclear.
App Store login required rejected
Apple rejected the app because reviewers could not access the app or required features due to login, paywall, or incomplete demo access.
App Store metadata mismatch
Apple rejected the app because store metadata, screenshots, privacy claims, or listed features do not match the actual app experience.
Google Play
Google Play rejection guides
Google Play privacy policy rejected
Google Play rejected the app because the privacy policy URL is missing, inaccessible, too generic, or inconsistent with the app's user data practices.
Google Play Data Safety rejected
Google rejected the app because the Data Safety section is incomplete, inaccurate, or no longer matches the release build.
Google Play Data Safety mismatch
Google Play flagged a mismatch between Data Safety answers and actual app behavior, SDK collection, or privacy policy wording.
Google Play sensitive permissions rejected
Google rejected the app because sensitive permissions are overbroad, poorly justified, or not supported by prominent disclosure and store forms.
Google Play health permissions rejected
Google rejected the app because health-related permissions, data declarations, or user-benefit explanations are incomplete or unsupported.
Google Play SMS and call log rejected
Google rejected the app because SMS or call log access is restricted and the declared use case or disclosure package is not sufficient.
Google Play SDK disclosure rejected
Google rejected the app because third-party SDK-driven data collection or sharing is not reflected accurately in Data Safety and policy disclosures.
Google Play user data policy issue
Google flagged the app under the User Data policy because collection, sharing, disclosure, or user-control expectations are not met.
Google Play deceptive behavior issue
Google sees a mismatch between what the app claims, what users expect, and what the app actually does in onboarding, permissions, billing, or data handling.
Google Play App Content form issue
Google rejected or blocked the app because App Content declarations are incomplete, inconsistent, or unsupported by the app and listing.
China Android app stores
China Android app stores rejection guides
SDK disclosure missing in China Android app stores
China Android app stores rejected the app because the third-party SDK disclosure list is missing, incomplete, or inconsistent with the shipped app and policy.
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.
Permission disclosure issue in China Android app stores
China Android app stores flagged the app because requested permissions are not disclosed clearly enough in policy, prompts, or submission materials.
Third-party SDK list requirement in China Android app stores
The store requires a third-party SDK list with vendor-level detail, and the app's current submission pack does not meet that requirement.
Account deletion required in China Android app stores
The store requires a visible account deletion or account cancellation path, and the app's current UX or policy does not meet that expectation.
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.
ICP filing guide for China Android app stores
The launch is blocked because the app or supporting web surfaces need ICP-related documentation or clearer operational readiness for China distribution.
Minor protection rules in China Android app stores
The app faces scrutiny under minor-protection or youth-safety rules, and current policy, age gating, or feature controls are not sufficient.
Content compliance issue in China Android app stores
The app was flagged for content-compliance readiness, including moderation, prohibited categories, community controls, or store-facing explanations.
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.