Apple Schedule 2, Section 3.8(b): Subscription Disclosure Checklist
Apple's Paid Applications Agreement has been a common source of App Store rejections for apps with auto-renewing subscriptions. This guide separates the current, narrower disclosure list from the stricter placement lessons that emerged earlier, so you can check both what you say and where you say it before submitting.
Why this clause catches developers out
Apple began rejecting apps that did not meet Schedule 2, Section 3.8(b) of the Paid Applications Agreement, a long contract developers accept before submitting an app. The practical problem is easy to miss: a requirement can sit inside contract language rather than in the more visible App Store Guidelines, Human Interface Guidelines, or developer documentation. Check the agreement itself before a submission, not only the purchase-screen design.
The current disclosure list
The August 2024 update quotes the current requirement as a clear and conspicuous disclosure of three subscription facts: the title, which may match the in-app product name; the length of the subscription; and the price, with price per unit where appropriate. Links to the privacy policy and terms of use must also be accessible within the licensed application. Use the checklist below to verify each item on the actual purchase screen.
Placement matters as much as wording
Earlier reviewer feedback drew a sharp line between information shown only in the StoreKit modal alert and information shown inside the app. The modal alone was judged insufficient. The disclosure had to appear during the purchase flow itself, clearly and conspicuously, without asking the user to open a link or perform another action first. Treat that placement rule as a design constraint even when you reuse the standard Apple purchase sheet.
Below the fold versus behind a button
One accepted arrangement placed the details below the fold but used a leading arrow to draw attention to them. By contrast, putting the same details in a separate view reached through a button from the purchase flow did not qualify for another developer. The distinction is not simply whether the text exists somewhere in the app. It is whether a person moving through the purchase sees it in that flow without an extra detour.
A ready-to-adapt disclosure pattern
Start with your real price and period, then state when the charge is applied, including at the end of a trial or introductory period where relevant. Explain automatic renewal, the 24-hour cancellation deadline before the current period ends, and that cancellation is available through account settings. Add the free-trial forfeiture warning and links to the terms and privacy policy. Finally, place the finished text on the purchase-initiation screen, using a visible cue if it sits below the fold, and consider repeating it in the App Store description as a precaution.
Design the disclosure in from the start
The underlying complaint was that a legal exposure was converted into a late-stage engineering task. A standard iOS purchase sheet already covered most of the older details except the 24-hour renewal policy, yet developers were asked to build their own version. Whether or not that system-level gap remains, the submission lesson is unchanged: audit contract terms early, design the disclosure into the paywall from the start, and test the exact screen a reviewer will see.
| Check | Pass condition | Common failure |
|---|---|---|
| Subscription title | Shown clearly and conspicuously | Only a generic plan name with no product title |
| Subscription length | Stated on the purchase screen | Hidden in a linked page |
| Price | Stated, with price per unit where appropriate | Shown only after tapping through |
| Privacy policy and terms links | Accessible within the licensed app | Available only on a website or in settings |
| Placement | Inside the purchase flow without an extra user action | Only in the StoreKit modal alert |
| Below-fold layout | Uses a clear cue such as a leading arrow | Details buried with no pointer |
Based on the August 2024 quoted update and earlier reviewer feedback described in this guide; confirm against the current official agreement before submission.
Frequently asked questions
What must an auto-renewing subscription disclosure include now?
Show the subscription title, its length, and its price, including price per unit where appropriate. Make links to your privacy policy and terms of use accessible inside the licensed app. The August 2024 update quoted in this guide narrows the earlier, longer list to those items.
Is the StoreKit modal alert alone enough?
No. Earlier rejection feedback said adding the information only to the StoreKit modal alert was not sufficient. It also had to appear inside the app, clearly and conspicuously during the purchase flow, without requiring the user to open a link or take another step.
Where should the disclosure sit in the purchase flow?
Put the disclosure on the screen where the purchase is initiated. One reviewer accepted placement below the fold when a leading arrow pointed users to it. Another arrangement was rejected when the same information sat in a separate view reached by a button from the purchase flow.
What should a practical disclosure template cover?
Adapt the wording to your own price, period, trial or introductory terms, renewal deadline, cancellation route, and legal links. State that subscriptions renew automatically unless cancelled within 24 hours before the current period ends, explain how to cancel in account settings, and note that any unused free-trial portion is forfeited if you buy a subscription.
Should the disclosure also appear in the App Store description?
Readers reported it may also be required in the App Store description. Because that change is comparatively easy, adding the same disclosure there was recommended as a precaution.