By platform

EULA Generator for iOS Apps

Written for App Store review: privacy nutrition labels, ATT, required-reason APIs and the privacy manifest.

Apple applies its standard licensed application end user licence agreement unless you supply your own, and a custom EULA must meet or exceed Apple’s minimum terms. If your app has restrictions Apple’s default does not cover, you need your own.

Apple does not merely require a privacy policy URL - it requires the policy to be consistent with the App Privacy details you declare, and review rejects submissions where they diverge. The nutrition label, the manifest and the policy are three views of the same facts, and reviewers compare them.

App Tracking Transparency governs cross-app and cross-site tracking. Accessing the advertising identifier or linking user data with third-party data for advertising requires the ATT prompt, and the policy has to describe the same behaviour the prompt asks about.

Privacy manifests added another layer. SDKs must declare their data collection and their use of required-reason APIs, and apps must include the manifests of the third-party SDKs they bundle. The SDK list is therefore also a recipients list.

What a EULA for an iOS app has to cover

A licence grant at least as protective as Apple’s standard terms, with Apple as third-party beneficiary
Scope of use across the user’s devices consistent with Apple’s family-sharing model
Restrictions on reverse engineering, redistribution and commercial resale
Maintenance and support responsibility, which sits with you rather than Apple
Export control and government end-user provisions Apple requires you to pass through

How an iOS app actually moves personal data

Device and advertising identifiers

IDFA access requires ATT authorisation. IDFV, and vendor SDK identifiers, are separate and still personal data in most regimes.

Analytics and crash reporting SDKs

Firebase, Crashlytics, Amplitude and similar collect device, session and event data and transmit it to their own infrastructure.

Attribution and advertising SDKs

AppsFlyer, Adjust, Meta and Google SDKs perform exactly the cross-party linking ATT governs.

In-app purchases and subscriptions

Apple handles payment, but you receive transaction identifiers and subscription status, which are linked to the user.

Permissions-gated data

Location, contacts, photos, microphone, health and motion each require a purpose string that must match the policy.

Push tokens

Device tokens tied to installs, retained for as long as notifications are enabled, and a recipient relationship with your push provider.

Third parties the draft will ask you about

Apple · Firebase and Crashlytics · Amplitude or Mixpanel · AppsFlyer or Adjust · Sentry · RevenueCat · OneSignal · AWS or Google Cloud

The rules that apply

App Store Review Guideline 5.1

A publicly accessible privacy policy URL is mandatory, covering data collected, use, retention and third-party sharing, plus a way to revoke consent and request deletion.

App Privacy details (nutrition labels)

Declared per data type across data used to track, data linked to the user and data not linked. Must match the policy.

App Tracking Transparency

The ATT prompt is required before tracking, and the policy has to describe tracking consistently with it.

Account deletion requirement

Apps offering account creation must offer in-app account deletion, not merely a support email.

Privacy manifests and required-reason APIs

Apps and SDKs declare collected data and the approved reasons for using certain APIs, which surfaces third-party collection you may not have documented.

What the generated EULA contains

Licence grant and its boundaries
Non-exclusive, revocable, per-device or per-seat - and explicitly a licence, not a sale.
Restrictions
Reverse engineering, redistribution, resale, and running the software as a service for third parties.
Ownership and third-party components
That the IP stays yours, plus the open-source components whose own licences travel with the build.
Updates, telemetry and support
What updates are automatic, what data the client reports back, and what support the licence entitles someone to.
Termination and what happens to data
The events that end the licence, and whether local data survives.
Warranty, liability and export control
As-is warranties where permitted, a defensible cap, and the export restrictions distribution platforms require you to pass through.

Getting through App Store review

Inventory every SDK and what it collects
Including transitive dependencies. Privacy manifests make this list explicit.
Write the policy, then fill in the nutrition labels from it
Not the other way round - the policy is the document with room to be precise.
Host the policy at a stable public URL
Same URL in App Store Connect and inside the app’s settings screen.
Implement in-app account deletion
Reachable in a few taps, with a clear statement of what is deleted and what is retained by law.
Align ATT prompt copy with the policy
Both should describe the same tracking in the same terms.
Re-check on every SDK update
A new SDK version can change what is collected and what the manifest declares.

Where this usually goes wrong

Nutrition labels that do not match the policy

The most common privacy-related rejection. Reviewers read both.

Tracking without an ATT prompt

Or presenting the prompt after the SDK has already started collecting.

No in-app account deletion

An app that lets users register must let them delete in-app. A support email is not sufficient.

Undeclared third-party SDK collection

SDKs collect on their own account, and the privacy manifest requirement has made those flows visible to Apple.

Vague permission purpose strings

"To improve your experience" is rejected. The string has to explain the specific use.

A policy URL that 404s or sits behind a login

It must be publicly reachable, and reviewers check it.

Frequently asked questions

Does my iOS app need a privacy policy?

Yes. App Store Review Guideline 5.1.1 requires a publicly accessible privacy policy URL for every app, with no exception for free apps or apps that collect little data.

What happens if my nutrition labels do not match my policy?

Rejection is common, and inconsistency between declared collection and actual behaviour can also be a deceptive-practice issue with regulators independently of Apple.

Do I need an ATT prompt?

If you access the advertising identifier or link user data with third-party data for advertising or measurement, yes. Analytics used only for your own product typically does not require it, but SDK defaults often do more than expected.

Is in-app account deletion really mandatory?

Yes for apps that support account creation. It must be initiated inside the app rather than only through a website or support request.

What is the difference between a EULA and terms of service?

A EULA licenses software that runs on the user’s own device. Terms of service govern a service you host and operate. Desktop apps, mobile apps and downloadable tools need a EULA; a web app usually needs terms.

Does my mobile app need its own EULA?

Apple applies its standard licensed application end user licence agreement unless you supply your own, and if you do, you must meet or exceed its minimum terms. Google Play expects a licence too. If you have custom restrictions, supply your own.

Do I need to list open-source components?

If you ship them, yes. Most permissive licences require attribution in the distributed product, and copyleft licences impose conditions that your own EULA cannot override.