When to Appeal
Not every rejection needs an appeal. Before you start the process, determine whether the rejection is:
- Valid - Your app genuinely violates a guideline. Fix the issue and resubmit.
- Unclear - You do not understand what the reviewer is referring to. Ask for clarification first.
- Incorrect - You believe the reviewer made a mistake or misunderstood your app. This is when you appeal.
Most rejections fall into the first category. Honest assessment saves time.
Apple App Store Appeals
Step 1: Resolution Center (First Response)
Every rejection comes with a message in the Resolution Center within App Store Connect. Your first action should always be to reply there:
- Be polite and professional
- Reference the specific guideline cited in the rejection
- Explain clearly why you believe your app complies
- Include screenshots or videos if the reviewer may have missed functionality
- Provide step-by-step instructions to reproduce the feature in question
Response time is typically 24-48 hours.
Step 2: Request a Phone Call
If the Resolution Center exchange is not resolving the issue, you can request a call with the review team. This is especially useful for complex situations where written communication is not enough.
Step 3: App Review Board Appeal
If you have exhausted the Resolution Center and phone call options, Apple provides a formal appeal process:
- Go to the Apple Developer website
- Navigate to "Contact Us" and select "App Review"
- Submit a formal appeal explaining your case
- The App Review Board (a senior team separate from the original reviewer) evaluates your appeal
- You receive a final decision, typically within 5-7 business days
The App Review Board decision is considered final, though developers have occasionally succeeded by resubmitting with modifications after a final rejection.
Google Play Appeals
Step 1: Policy Support Form
When Google removes or rejects your app, you receive an email with the specific policy violation. To appeal:
- Go to the Google Play Console
- Find the "Policy status" section
- Click "Submit appeal" or use the appeal link from the notification email
- Provide a detailed explanation of why you believe the decision was incorrect
- Include any changes you have made to address the concern
Step 2: Detailed Appeal Form
If the initial appeal is denied, you can submit a more detailed appeal through Google's support form. Include:
- Specific policy sections you believe apply (or do not apply)
- Evidence that your app complies
- Details about any changes you have made
- Comparison with similar apps that are approved (use cautiously)
Step 3: Escalation
Google does not have a formal equivalent to Apple's App Review Board, but persistent, well-documented appeals do get escalated internally. If your developer account is at risk of termination, consider getting legal representation familiar with Google Play policies.
Appeal Best Practices
Do
- Stay calm and professional - Emotional appeals never help
- Be specific - Reference exact guideline numbers and explain point by point
- Provide evidence - Screenshots, videos, links to documentation
- Offer solutions - "We can modify X to comply. Would this approach be acceptable?"
- Acknowledge the concern - Show you understand why the flag was raised, even if you disagree
Do Not
- Threaten legal action - This shuts down productive dialogue
- Copy-paste the same message - Each response should address the reviewer's specific feedback
- Rush the process - Take time to build a solid case
- Insult the reviewer - They are doing their job
- Submit multiple appeals simultaneously - This creates confusion and delays
Timelines
| Platform | First Response | Appeal Decision | Final Escalation |
|---|---|---|---|
| Apple | 24-48 hours | 3-5 business days | 5-7 business days |
| 3-7 business days | 7-14 business days | Varies |
Prevention Is Better Than Appeal
The best appeal strategy is avoiding rejections in the first place:
- Use a pre-submission checklist
- Stay current on guideline updates
- Test thoroughly before submission
- Provide clear reviewer notes and demo accounts
- When in doubt, ask Apple or Google before building the feature