What this rejection means
Auto-renewing subscriptions need specific details: the title, length and price of each plan in the app, and working links to the privacy policy and Terms of Use (EULA) in the app and the listing.
Why reviewers send it
Before someone starts an auto-renewing subscription, Apple wants them to see what they get, how long it lasts, what it costs, and the terms. Paywalls designed for the web often skip the Terms of Use link or the price per period.
The message App Review sends
Guideline 3.1.2 - Business - Payments - Subscriptions
We noticed that your app did not fully meet the terms and conditions for auto-renewable subscriptions: the app’s metadata is missing a functional link to the Terms of Use (EULA).The exact wording changes from one review to the next; the guideline number is what to look for.
How to fix it
- On the paywall, show each plan’s name, length and price per period, with links to the Terms of Use and the privacy policy.
- In App Store Connect, add a Terms of Use link to the description (or set a custom EULA) and the privacy policy URL.
- Resubmit with the new build and the subscriptions attached to the version.
Fix it with Lovable, Bolt or Cursor
If the app was built with an AI builder, paste this into it, then check the result on a phone:
On the paywall, show each plan’s title, duration and price per period, and add visible links to the Terms of Use (EULA) and the privacy policy.What to reply in App Store Connect
Replace the [brackets] with what you actually changed:
Guideline 3.1.2 — The paywall now shows the title, length and price of each subscription, with links to the Terms of Use and the privacy policy. We added the Terms of Use link to the App Store description.Got a different message?
Paste the whole rejection into the rejection explainer. It recognises this one and 26 others, in your browser — nothing is uploaded.
Other App Store rejections
- App Store Guideline 4.3 Spam rejection
- Guideline 4.2 Minimum Functionality rejection
- Guideline 2.1 App Completeness rejection
- Guideline 2.1 Information Needed: demo account
- Guideline 4.0 Design rejection: sign-in in Safari
- Guideline 2.3.3 Accurate Metadata: screenshots
- Guideline 2.3.10: Android mentioned in the app
- Guideline 2.3.8: app icon or name doesn’t match
- Guideline 4.8 Login Services: Sign in with Apple
- Guideline 5.1.1(v): account deletion required
- Guideline 5.1.1: permission purpose string
- Guideline 5.1.1: sign-up required to use the app
- Guideline 5.1.1(i): privacy policy link missing
- Guideline 5.1.2: App Tracking Transparency
- Guideline 3.1.1: digital goods without In-App Purchase
- Guideline 1.5: support URL doesn’t work