NewThe guide: 11 paywall examples

5 minutes

App Store checklist: avoid rejection and pass review on the first try

An App Store rejection most often comes from missing links, prices displayed poorly, and forgotten legal mentions. Apple cites the guideline that was violated, and the fix is limited to that point.

Clément Parot

App Store checklist: avoid rejection and pass review on the first try

Article summary

  • An App Store rejection most often comes from legal links, prices displayed poorly, and forgotten mentions, not from the code.
  • The privacy policy, terms of use, and support URL must be identical in the app, App Store Connect, and the site.
  • Each paywall option must display the exact price, the billing frequency, and the trial terms.
  • The Restore Purchases button must exist and work, and the cancellation instructions must be visible.
  • Apple cites the guideline that was violated: you fix only that point, then reply in App Store Connect if needed.

Summarize this article with

An App Store rejection does not only happen to other people. Most of the time the code is not the problem. Missing links, prices displayed poorly, and forgotten legal mentions are. firstapp walks you through everything to check before you submit.

Landing page before submission

This guide starts from one premise: your app works, your ASO is done, your build is ready. What follows covers what makes submissions fail after all of that: the legal details, the transparency signals, and the trust elements Apple checks every time.

The first thing to do before you submit is not technical. It is to create a landing page for your app.

This is not optional. A web page, even a minimal one, is where your legal links live. It lets reviewers check that you exist, and it makes you look like a real product rather than a side project. A page with the app name, a short description, the Privacy Policy, the Terms of Use, and a support email is enough.

Newsletter

Once a week.

Last issue

We opened 10 apps to see how they sell a subscription.

+534 people read us each week

The checklist, point by point

1. The legal links

Three URLs must be ready and live before submission: Privacy Policy, Terms of Use, and support URL. These three links must be placed in the same spot in App Store Connect, in the app (Settings screen), and on your website. The URLs must be identical in all three places. Apple compares them.

2. The support page

Your support page must show a visible contact email and state whether you are an individual developer or a company. Reviewers check this page. If no way to contact you can be found, the submission is rejected.

3. Legal access inside the app

In Settings or an "About" screen, users must be able to reach the Privacy Policy, the Terms of Use, and Support in a single tap. Do not hide them in submenus or in small print. Apple tests this accessibility during review.

4. The clarity of the paywall

Each offer on your paywall must clearly display the exact price, the billing frequency, and what the user gets. Whatever is vague gets rejected.

Correct

Monthly - €4.99/month
Annual - €39.99/year, billed annually

Rejected

Go Premium
Best offer

If you offer a free trial, the trial length and what happens at the end must be stated next to the button, not in the small print at the bottom.

5. The Restore Purchases button

A visible, working Restore Purchases button is mandatory for any app with in-app purchases. It must be reachable from the paywall or from Settings. Its absence is an almost automatic rejection reason. Test it before you submit.

6. The cancellation instructions

You do not need a cancellation flow inside the app, but you must tell the user how to cancel. Add a line such as:

Cancel anytime via Settings > Apple ID > Subscriptions

Place this instruction on the paywall or in the subscription settings.

7. No misleading UI

Apple reviewers are trained to spot dark patterns. Explicitly watched: counters that reset, misleading price anchors, and paywall close buttons that are intentionally hard to find. If the interface looks designed to trap the user, it will be rejected.

The simple rule: if you have to justify a design choice by telling yourself "technically it is not forbidden," do not do it.

8. Reviewer credentials

If part of your app requires a login, you must provide a working test account in the "App Review Notes" field in App Store Connect. This is not optional. If the reviewer cannot access your app, it is rejected automatically.

The final checklist before you click Submit

Go through every point before submission:

To check

- All legal links are live and identical in the app, App Store Connect, and the website

- The support page shows a visible contact email

- Privacy Policy and Terms of Use are reachable in one tap inside the app

- The EULAs are available

- Each paywall option displays the exact price and the billing frequency

- The free-trial terms are displayed next to the CTA

- The Restore Purchases button exists and works

- Cancellation instructions are visible on the paywall or in settings

- No dark pattern in the interface

- In-app purchases and subscriptions are in "Ready to Submit" status in App Store Connect

- A test account is provided in the App Review Notes if the app requires a login

Source: Apple - App Reviews

Responding to an App Store rejection

A rejection is not the end. Apple always cites the specific guideline that was violated in its rejection notice. Here is how to respond:

1. Read the rejection notice in full. Apple states the precise guideline that was violated. Fix only what is cited. Do not change anything else.

2. Use "Reply to App Review" in App Store Connect if the reason is not clear. That often produces concrete detail on exactly what is missing.

3. For clear mistakes by Apple, submit an appeal through the App Review Board. It is rare, but it works on clear cases.

Most App Store rejections are avoidable. They happen because these points are treated as details, while Apple treats them as fundamental trust signals. Prepare them before you code your last feature.

FAQ

What gets an app rejected most often?

Most often, it is not the code. It is missing links, prices displayed poorly, and forgotten legal mentions. A landing page, even a minimal one, must exist before submission: app name, short description, privacy policy, terms of use, and support email.

Which links must be identical everywhere?

Three URLs: privacy policy, terms of use, and support. They must be the same in App Store Connect, in the app (Settings or About, in one tap), and on the site. The support page must show a visible email, and state whether you are an individual developer or a company.

Is the Restore Purchases button mandatory?

Yes, for any app with in-app purchases. It must be visible and working from the paywall or from Settings. Its absence is an almost automatic rejection reason. Each offer must also display the exact price and the frequency, and a free trial must state its length next to the button.

How do you respond to a rejection?

Apple cites the guideline that was violated. You fix that point, and nothing else. If the reason is not clear, "Reply to App Review" in App Store Connect gets you the detail. An appeal to the App Review Board is reserved for clear mistakes by Apple. If part of the app requires a login, a test account must appear in the App Review Notes.

Newsletter

Once a week.

Last issue

We opened 10 apps to see how they sell a subscription.

+534 people read us each week