Guideline 3.1.2 subscription transparency rejection: how to fix it

What App Store Guideline 3.1.2 says

Guideline 3.1.2 states that apps may offer auto-renewable in-app purchase subscriptions, in any category, as long as they follow Apple's subscription rules.

Two parts matter most for a transparency rejection. Guideline 3.1.2(a), Permissible uses, says the subscription must provide ongoing value to the customer, must last at least seven days, and must be available across all of the user's devices. Guideline 3.1.2(c), Subscription Information, says that before asking a customer to subscribe you should clearly describe what the user gets for the price, and you must communicate the requirements set out in Schedule 2 of the Apple Developer Program License Agreement, which includes the subscription terms and the legal links. The official text lives on the App Store Review Guidelines page.

Why apps get rejected under 3.1.2

Common triggers:

• The subscribe screen does not show the price and billing period clearly before purchase.
• The screen does not state that the subscription auto-renews until the user cancels.
• There is no functional Terms of Use link, or the link is broken, or it only lives in app settings.
• The privacy policy is not linked where it needs to be.
• The subscription does not provide ongoing value, for example it unlocks a one-time feature with no continuing benefit.
• The displayed terms do not match the actual product configured in App Store Connect.

The thread is that the user cannot clearly see the full terms, or the legal links, at the moment they are asked to subscribe.

How to fix it

1. Show the full terms on the subscribe screen. Display the subscription name, the price, the billing period, and that it renews automatically until canceled, all before the purchase action.
2. Add functional legal links. Put a working Terms of Use, or EULA, link and your privacy policy link on the subscribe screen itself, not only in settings.
3. Describe the value plainly. State what the user gets for the price, following Guideline 3.1.2(c).
4. Confirm ongoing value. Make sure the subscription delivers continuing benefit and meets the seven-day minimum across devices, per Guideline 3.1.2(a).
5. Reconcile with App Store Connect. Check that the price, duration, and terms shown in the app match the product you configured, then resubmit.

Remember that submitted is not approved. A resubmission goes back through review, and Apple checks the subscribe screen and the links again.

How AppFlight helps

AppFlight can wire your subscriptions through an integration like RevenueCat or Superwall, and it builds the native paywall screen, so the price, billing period, renewal terms, and the Terms of Use and privacy policy links can be placed where Guideline 3.1.2 expects them. Because the paywall is generated to your description, you can ask for the full disclosures and functional legal links on the subscribe screen from the start. When Apple returns a 3.1.2 rejection, AppFlight reads the rejection reason, works on the paywall and the disclosures, and resubmits the build. AppFlight does not guarantee approval. The terms still have to be complete and match your product, and Apple reviews every app and every resubmission.