Fix the rejection.
Not just the reply.
Choose the exact policy or decision you are facing. Each guide separates product fixes from appeal arguments and shows the evidence a reviewer needs to verify your resubmission.
Or paste your rejection for a free diagnosis →Start with the policy named in your rejection
Apple App Store
Policy fixes, reviewer replies, appeal decisions, and expedited review.
App Store Guideline 4.3 Design Spam Rejection
A practical recovery plan for Apple Guideline 4.3 rejections involving template similarity, repeated apps, or insufficient product differentiation.
Open recovery guide →Guideline 2.1 — App CompletenessApp Store Guideline 2.1 App Completeness Rejection
Diagnose crashes, broken review paths, inaccessible accounts, and incomplete features behind Apple Guideline 2.1 rejections.
Open recovery guide →Guideline 2.3 — Accurate MetadataApp Store Guideline 2.3 Metadata Rejection
Align App Store screenshots, descriptions, claims, age rating, and review notes with the submitted build after a Guideline 2.3 rejection.
Open recovery guide →Guideline 3.1.1 — In-App PurchaseApp Store Guideline 3.1.1 In-App Purchase Rejection
Map digital entitlements, external payment paths, and purchase messaging after an Apple Guideline 3.1.1 rejection.
Open recovery guide →Guideline 5.1.1 — Data Collection and StorageApp Store Guideline 5.1.1 Privacy Rejection
Audit privacy policy, permissions, disclosures, data minimization, retention, and deletion after an Apple Guideline 5.1.1 rejection.
Open recovery guide →Guideline 1.4.1 — Medical AppsApp Store Guideline 1.4.1 Medical App Rejection
Separate unsupported health measurements from documented medical functionality, then prepare the methodology, safety, and regulatory evidence Apple can verify.
Open recovery guide →Guideline 1.1.6 — Trick or Joke FunctionalityApp Store Guideline 1.1.6 Trick or Joke Functionality Rejection
Diagnose whether a fictional chat, simulated phone, fake location, or prank feature can deceive users, then choose a product fix, clarification, or appeal.
Open recovery guide →Guideline 3.1.2(c) — Subscription InformationApp Store Guideline 3.1.2(c) Subscription Information Rejection
Correct unclear subscription value, title, duration, price, trial terms, Privacy Policy, and Terms of Use before resubmitting an iOS paywall.
Open recovery guide →Guideline 5.6 / 2.3.1 — Hidden FeaturesApp Store Guideline 5.6 Hidden Features Rejection
Audit release-only paths, test hooks, feature flags, remote configuration, and reviewer access after Apple says functionality appears intentionally hidden.
Open recovery guide →Guideline 1.3 — Kids CategoryApp Store Guideline 1.3 Kids Category SDK Rejection
Audit analytics, crash-reporting, subscription, advertising, and other third-party SDK data flows after an Apple Kids Category rejection.
Open recovery guide →Guideline 2.1 / 5.1.2 — App Tracking TransparencyApp Store ATT Permission Request Not Found Rejection
Fix an AppTrackingTransparency permission request that App Review cannot locate, or remove tracking and reconcile the submitted binary with App Privacy answers.
Open recovery guide →Guideline 2.5.4 — Background ModesApp Store Guideline 2.5.4 Background Modes Rejection
Remove an unused UIBackgroundModes declaration or prove the reviewer-visible audio, location, VoIP, accessory, or task-completion feature that requires it.
Open recovery guide →Guideline 2.1(b) — In-App Purchase ReviewApp Store Guideline 2.1(b) First In-App Purchase Rejection
Put a first In-App Purchase, subscription group, and app version into the same App Review submission after an Apple Guideline 2.1(b) rejection.
Open recovery guide →Guideline 4.8 — Login ServicesApp Store Guideline 4.8 Login Services Rejection
Resolve an Apple Guideline 4.8 rejection by adding a qualifying privacy-preserving login option or proving that a listed exception applies.
Open recovery guide →Guideline 4.2 — Minimum FunctionalityApp Store Guideline 4.2 Minimum Functionality Rejection
Turn a thin website wrapper, content-only app, or limited utility into a product that delivers durable app-like value under Apple Guideline 4.2.
Open recovery guide →Guideline 4.2.6 — Commercialized TemplatesApple Guideline 4.2.6 Template App Rejection
Resolve ownership, submission, and consolidation problems when Apple rejects an app created from a commercialized template or app-generation service.
Open recovery guide →Guideline 5.1.1(v) — Account DeletionApp Store Account Deletion Rejection
Implement an in-app account-deletion path, remove unnecessary friction, and explain legitimate retention after an Apple account-deletion rejection.
Open recovery guide →Guideline 5.2 — Intellectual PropertyApp Store Guideline 5.2 Intellectual Property Rejection
Prove rights or remove unauthorized brands, media, services, and misleading affiliations after an Apple Guideline 5.2 rejection.
Open recovery guide →Guideline 1.2 — User-Generated ContentApp Store Guideline 1.2 User-Generated Content Rejection
Add reporting, blocking, moderation, contact, and age-appropriate safeguards after an Apple user-generated-content rejection.
Open recovery guide →Appeal decisionApp Store Appeal vs. Resubmit: Which Path Should You Take?
Decide whether to fix, clarify in App Store Connect, or file a formal App Review Board appeal after an iOS rejection.
Open recovery guide →App Review responseApp Store Rejection Response Template: What Reviewers Need
Structure a concise App Store Connect reply that states verified changes, exact navigation, evidence, and a clear request without risky claims.
Open recovery guide →Expedited reviewHow to Request an Expedited App Store Review After Rejection
Prepare a factual expedited-review request for a critical bug or time-sensitive event without treating urgency as a substitute for compliance.
Open recovery guide →Google Play
Policy remediation, declarations, appeals, and evidence-based responses.
Google Play Repetitive Content Rejection
Differentiate low-value, templated, white-label, or duplicative Android apps after a Google Play Repetitive Content rejection.
Open recovery guide →Broken Functionality policyGoogle Play Broken Functionality Rejection
Reproduce crashes, frozen screens, dead controls, install failures, and review-environment defects behind Google Play rejection.
Open recovery guide →User Data policyGoogle Play User Data Policy Rejection
Reconcile privacy policy, prominent disclosure, consent, permissions, secure handling, and deletion after a Google Play User Data rejection.
Open recovery guide →Data safety requirementsGoogle Play Data Safety Form Rejection
Audit SDK collection and align Google Play Data safety declarations with actual app behavior and privacy documentation.
Open recovery guide →Metadata policyGoogle Play Metadata Policy Rejection
Correct misleading claims, spammy keywords, irrelevant text, screenshots, and store listing mismatches after Google Play rejection.
Open recovery guide →Limited Functionality and ContentGoogle Play Limited Functionality and Content Rejection
Increase stable utility and mobile value when Google Play rejects a static, text-only, single-purpose, or low-content app.
Open recovery guide →Account Deletion requirementGoogle Play Account Deletion Rejection
Provide both in-app and external account-deletion routes and reconcile Data safety disclosures after a Google Play rejection.
Open recovery guide →Sensitive Permissions and APIsGoogle Play Permissions Declaration Rejection
Remove unnecessary sensitive permissions or prove core-functionality eligibility with an accurate declaration and review video.
Open recovery guide →Photo and Video Permissions policyGoogle Play Photo and Video Permissions Rejection
Remove ineligible READ_MEDIA_IMAGES and READ_MEDIA_VIDEO access or prove why broad media access is indispensable to the app's core purpose.
Open recovery guide →Foreground Service permissionsGoogle Play Foreground Service Permission Rejection
Align Android 14+ foreground service types, manifest permissions, Play Console declarations, and reviewer evidence after an FGS rejection.
Open recovery guide →Exact Alarm PermissionGoogle Play USE_EXACT_ALARM Rejection
Remove an ineligible USE_EXACT_ALARM permission or prove that precise timing is indispensable to the app's core alarm, timer, or calendar experience.
Open recovery guide →VpnService policyGoogle Play VpnService Policy Rejection
Prove an eligible core VPN use case or remove VpnService from every active artifact, then align the listing, disclosure, consent, declaration, encryption, and review video.
Open recovery guide →Impersonation policyGoogle Play Impersonation Policy Rejection
Correct misleading identity, ownership, branding, icons, and affiliation claims after a Google Play Impersonation policy rejection.
Open recovery guide →Subscriptions policyGoogle Play Subscriptions Policy Rejection
Correct unclear pricing, recurring-value, cancellation, trial, and paywall disclosures after a Google Play subscriptions rejection.
Open recovery guide →Appeal decisionGoogle Play Appeal vs. Resubmit: How to Choose
Choose whether to fix a rejected release, submit a compliant update, or appeal a mistaken Google Play enforcement decision.
Open recovery guide →Enforcement Process — Repeated App RejectionsGoogle Play Suspension for Repeated App Rejections: Recovery Guide
Stop the rejection loop, preserve release evidence, and prepare a precise appeal after Google Play suspends an app for repeated rejections.
Open recovery guide →Policy appeal responseGoogle Play Policy Appeal Template: Build an Evidence-Based Case
Prepare a concise Google Play appeal that identifies the enforcement, addresses the cited policy, and proves compliance without unsupported promises.
Open recovery guide →