The Terms of Use (EULA) Apple asks subscription apps for

Guideline 3.1.2 in practice: where the standard EULA link goes, where a custom one goes instead, and the five things that have to be visible inside the app.

Apps with auto-renewable subscriptions must show functional links to a privacy policy and a Terms of Use (EULA) under guideline 3.1.2 — inside the app and in the metadata. Apple's standard EULA covers it: link it from the App Description. A custom EULA goes in the App Store Connect field instead.

Checked 19 September 2026. Store policies change, sometimes without notice. Everything below links to the official documentation, and that page — not this one — is the authority. If the two disagree, the store is right.

This is one of the most repeated rejections on the App Store, and one of the easiest to clear — once you know that “EULA” here does not mean “write a licence agreement”.

What guideline 3.1.2 asks for

For apps offering auto-renewable subscriptions, Apple requires functional links to your privacy policy and your Terms of Use (EULA). Both have to be reachable in two places:

in the app itself, wherever you present the subscription; and
in the app metadata — the Privacy Policy field in App Store Connect for the policy, and either the App Description or the EULA field for the Terms of Use.

Alongside those links, the subscription information inside the app must state the title of the auto-renewing subscription, its length, and its price — including price per unit where that makes sense.

You do not have to write the EULA

Apple publishes a standard one: the Licensed Application End User License Agreement, at apple.com/legal/internet-services/itunes/dev/stdeula/. It is the default licence that applies to your app unless you supply your own, and linking it satisfies the Terms of Use requirement.

Which means the decision is small:

If you use	Put the link	Put it in App Store Connect’s EULA field?
Apple’s standard EULA	The App Description, and in-app beside the subscription	No — the field is for custom agreements
Your own custom EULA	The EULA field in App Store Connect, and in-app beside the subscription	Yes

Most apps should use the standard EULA. A custom one is worth the effort only if you have terms the standard agreement does not cover, and it is then reviewed as part of your submission.

Where the rejections actually come from

The pattern in practice is not “no EULA” — it is “the reviewer could not find it”:

The links are in Settings, not on the paywall. They have to be where the subscription is offered, on the screen where someone decides to buy.
They are text, not links. A line saying “see our terms of use” with nothing to tap is not a functional link.
The metadata half is missing. The in-app links are there, but the App Description has no Terms of Use link and no custom EULA is uploaded.
The link opens something unrelated — a marketing page, a 404, or a policy for a different product.
The subscription facts are absent. Links present, but the paywall never says the length or the price per period.

If you have been rejected more than once on 3.1.2 with the links apparently in place, check the metadata side and the paywall side separately. They are two requirements, and satisfying one twice does not satisfy the other.

A checklist before you resubmit

Paywall shows subscription title, length and price (plus price per unit if relevant)
Paywall has a tappable Privacy Policy link that loads
Paywall has a tappable Terms of Use (EULA) link that loads
App Store Connect Privacy Policy URL is set and loads signed out
Standard EULA linked from the App Description, or a custom EULA uploaded to the EULA field
Every one of those URLs opens without a login

What about Google Play?

Play has no equivalent field. It requires a privacy policy link in Play Console and inside the app, and nothing about a EULA — see the terms of service guide for what that means for a cross-platform app. In practice you publish one set of terms and link it from both places.

What AppFoyer does here

When you tell us the app sells subscriptions on iOS, the generated privacy policy and terms both carry the Apple standard EULA link, and the compliance checklist flags the app until both pages have it — that item exists precisely because this is the rejection people hit twice.

The pages are hosted at fixed URLs you can paste into App Store Connect and into your paywall, and they keep working after you stop thinking about them. What we cannot do is the in-app half: the paywall links and the subscription facts are your app’s own UI.

Templates, not legal advice — and for the EULA specifically, verify the current wording of guideline 3.1.2 before you submit.

The authoritative sources

App Store Review Guidelines — Apple. Section 3.1.2 is the rule this page is about; it is the text that decides.
Licensed Application End User License Agreement — Apple’s standard EULA, the document you link.
App Store Connect — app information — Apple, for where the fields live.

Do this in a few minutes instead

AppFoyer hosts the pages this guide is about — privacy policy, terms, support, account deletion and app-ads.txt — on their own subdomain, with no domain or server of your own. One app is free, and nothing a store requires is ever behind a paywall.

Start free See a live example

Does your app need a terms of service?
What each store actually requires, why 'required' and 'a good idea' are different answers, and the five sections that do real work in an app's terms.
The support URL App Store Connect asks for
What belongs on a support page, why a link to your homepage is not enough, and how it differs from the marketing URL.
What a subscription paywall has to say
The facts both stores require before purchase, the links Apple wants on the paywall itself, and why these rejections are almost always about placement rather than wording.