# Guideline 3.1.2: subscription information missing > Rejected under Guideline 3.1.2 for missing Terms of Use (EULA), prices or plan details on the paywall? Exactly what to show, in the app and the listing. **Guideline 3.1.2 — Subscriptions: required information is missing.** 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. - App Store · Guideline 3.1.2. Subscriptions: required information is missing. - Interactive page: https://capwr.app/free-tools/app-store-rejection-explainer/guideline-3-1-2-subscriptions - Rejection explainer: https://capwr.app/free-tools/app-store-rejection-explainer - Last updated: 2026-10-14 ## 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 1. On the paywall, show each plan’s name, length and price per period, with links to the Terms of Use and the privacy policy. 2. In App Store Connect, add a Terms of Use link to the description (or set a custom EULA) and the privacy policy URL. 3. 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](https://capwr.app/free-tools/app-store-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](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-3-spam) - [Guideline 4.2 Minimum Functionality rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-2-minimum-functionality) - [Guideline 2.1 App Completeness rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-1-app-completeness) - [Guideline 2.1 Information Needed: demo account](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-1-information-needed-demo-account) - [Guideline 4.0 Design rejection: sign-in in Safari](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-0-design) - [Guideline 2.3.3 Accurate Metadata: screenshots](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-3-screenshots) - [Guideline 2.3.10: Android mentioned in the app](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-10-other-platforms) - [Guideline 2.3.8: app icon or name doesn’t match](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-8-app-icon) - [Guideline 4.8 Login Services: Sign in with Apple](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-8-sign-in-with-apple) - [Guideline 5.1.1(v): account deletion required](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-v-account-deletion) - [Guideline 5.1.1: permission purpose string](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-purpose-string) - [Guideline 5.1.1: sign-up required to use the app](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-sign-up-required) - [Guideline 5.1.1(i): privacy policy link missing](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-i-privacy-policy) - [Guideline 5.1.2: App Tracking Transparency](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-2-app-tracking-transparency) - [Guideline 3.1.1: digital goods without In-App Purchase](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-3-1-1-in-app-purchase) - [Guideline 1.5: support URL doesn’t work](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-1-5-support-url) ## Fixed it? Send the build back to App Review CapWrapp builds the fixed commit on GitHub’s Mac machines, uploads it to TestFlight, and sends the build you pick to App Review from one page — no Xcode. [Get started free](https://capwr.app/login). ## About CapWrapp CapWrapp turns a web app on GitHub — built with Lovable, Bolt, Base44, Cursor or by hand — into iPhone and Android apps. It adds Capacitor if the repo needs it, signs the builds, and ships them to TestFlight and Google Play from GitHub Actions, with no Mac or Xcode on your side. [Get started free](https://capwr.app/login) · [Lovable to App Store guide](https://capwr.app/guides/lovable-to-app-store)