iOS Privacy Policy Generator: What Apple Checks Before Your App Ships
Published November 19, 2026 · Updated November 19, 2026
Every iOS app needs a privacy policy URL before it can be submitted to the App Store, even an app that collects nothing. Apple asks for it in App Store Connect under App Privacy > Privacy Policy, requires a link inside the app, and expects the text to agree with your App Privacy answers, your App Tracking Transparency (ATT) prompt and the data your SDKs send. A generic website policy that never mentions the app is the usual reason a submission comes back under Guideline 5.1.1.
To build one, open the free privacy policy generator, choose iOS - App Store as the platform, tick the SDKs in your build and, if you show the tracking prompt, select Apple ATT prompt under consent mechanisms. You get a hosted URL to paste into App Store Connect.
Where App Store Connect Asks for the URL, and What It Rejects
Apple's App Store Connect Help states that "a privacy policy URL is required for all apps." The field sits with your privacy answers, not in the general app metadata:
- In App Store Connect, open Apps and select your app.
- In the sidebar, select App Privacy.
- In the Privacy Policy section, click Edit.
- Enter the Privacy Policy URL. The User Privacy Choices URL (where users can access or delete their data) is optional. tvOS apps paste the text into Apple TV Privacy Policy instead.
- Click Save. URL changes go out with your next app version.
App Review reads the document against Guideline 5.1.1(i): what data the app collects, how, and every use of it; confirmation that third parties (analytics, ad networks, SDKs) give equal protection; retention and deletion policies; and how users revoke consent or request deletion. Submissions most often fail because:
- The URL returns a 404, opens a login wall, or lands on a homepage instead of the policy.
- The document never names the app or its SDKs, or there is no link to it inside the app.
- Users can create an account but cannot delete it in the app (Guideline 5.1.1(v)).
- Personal data goes to a third-party AI service without disclosure and permission. Apple's November 2025 update named third-party AI in Guideline 5.1.2(i).
Matching the Policy to Your App Privacy Answers
The App Privacy questionnaire produces the "privacy nutrition label" on your product page, split into Data Used to Track You, Data Linked to You and Data Not Linked to You. Apple counts data as "collected" when it leaves the device and you or a partner can access it for longer than it takes to serve the request in real time. On-device processing is not collection, which is worth saying in the policy too.
For each data type, Apple asks the same questions. The policy should answer each one in words:
| App Privacy question | Apple's options | What the policy must say |
|---|---|---|
| Data types collected | Contact Info, Health & Fitness, Financial Info, Location (Precise / Coarse), Sensitive Info, Contacts, User Content, Browsing History, Search History, Identifiers (User ID / Device ID), Purchases, Usage Data, Diagnostics, Surroundings, Body, Other Data | The same categories. If the label says Coarse Location and Crash Data, the policy names both. |
| Purposes | Third-Party Advertising, Developer's Advertising or Marketing, Analytics, Product Personalization, App Functionality, Other Purposes | Each purpose, attached to its data type. "To improve our services" covers none of them. |
| Linked to the user? | Yes / No | Whether data is tied to an account or device ID, or de-identified first. |
| Used for tracking? | Yes / No | Which partners and identifiers, and that it happens only after ATT permission. |
The label must include data your SDKs collect, not just your own code. You can skip a data type only if it meets every one of Apple's optional-disclosure criteria (no tracking or advertising, infrequent, optional, entered by the user each time). Data Apple's own services such as MapKit collect is not yours to declare. The App Store privacy requirements checker lists each store's forms side by side.
ATT and the IDFA: What Tracking Permission Changes
Since iOS 14.5, an app must get permission through the AppTrackingTransparency framework before it tracks a user or reads the advertising identifier (IDFA). Apple defines tracking as linking your app's data about a user or device with other companies' data for targeted advertising or ad measurement, or sharing it with a data broker. The mechanics:
- Add
NSUserTrackingUsageDescriptiontoInfo.plist. That string is the explanation shown in the system prompt. - Call
ATTrackingManager.requestTrackingAuthorization(completionHandler:)before any tracking starts. The status comes back as.authorized,.denied,.restrictedor.notDetermined. - Unless the status is
.authorized,ASIdentifierManager.shared().advertisingIdentifierreturns all zeros (00000000-0000-0000-0000-000000000000). - If your privacy manifest sets
NSPrivacyTrackingto true, list the tracking hosts inNSPrivacyTrackingDomains. iOS blocks requests to those domains until the user grants permission.
Turning tracking on adds four things to the policy: that you or named partners track, the identifiers involved (IDFA, often IDFV or hashed email), the partners who receive them, and how to withdraw permission in Settings > Privacy & Security > Tracking. Say what happens if the user declines, and keep the usage string, policy and "Used for tracking" answers consistent. SKAdNetwork attribution needs no ATT permission, so if that is all you use, do not claim you track.
SDKs That Create Obligations iOS Developers Miss
Apple holds you responsible for what your SDKs collect. Since May 2024, new apps and updates that add an SDK from Apple's list of commonly used SDKs must include that SDK's privacy manifest (PrivacyInfo.xcprivacy), and a signature when it ships as a binary. Manifests declare collected data in NSPrivacyCollectedDataTypes and "required reason" APIs in NSPrivacyAccessedAPITypes. In Xcode's Organizer, Generate Privacy Report on an archive collects every SDK's declarations in one PDF. Check each one against your policy:
| SDK | What it sends | Label rows and policy line |
|---|---|---|
| FirebaseCrashlytics | Stack traces, device model, OS version, an installation ID | Diagnostics (Crash Data), Identifiers. Name Google. |
| Firebase Analytics (GoogleAppMeasurement) | App instance ID, screen views, events, coarse location from IP; the IDFA once ATT is granted and AdSupport is linked | Usage Data, Identifiers, Coarse Location. If linked to Google Ads, it can count as tracking. |
| FirebaseAuth / GoogleSignIn | Email, name, profile photo, user ID | Contact Info, User ID, linked. Name the sign-in providers. |
| FirebaseMessaging / OneSignal | Push token, device and session data; OneSignal also email or SMS if you use those channels | Identifiers (Device ID), Usage Data. Name the push provider. |
| Google Mobile Ads (AdMob) | IDFA after ATT, ad interactions, IP-derived location | Advertising Data, Device ID, usually Data Used to Track You. |
| FBSDKCoreKit (Meta) | Install and session App Events logged automatically unless turned off | Usage Data, Identifiers. Name Meta and any ad measurement. |
| AppsFlyer / Adjust / Branch | IDFA or IDFV, install and attribution events | Usually tracking. Name the attribution partner. |
| RevenueCat | App user ID, purchase and subscription history | Purchases (Purchase History), User ID. |
| Sentry | Crash data, breadcrumbs; IP and user details if sendDefaultPii is on | Diagnostics; add Identifiers if PII is enabled. |
Cross-platform builds hide more: Flutter's shared_preferences and React Native storage libraries use UserDefaults, a required-reason API that needs a declared reason even when no data leaves the device. The SDK disclosure generator turns an SDK list into policy paragraphs.
Copy-Ready iOS Clauses
These clauses cover the iOS parts most policies leave out. Add them to a full app policy (see the guide to writing a privacy policy for a mobile app), replace the brackets and drop what does not apply.
Information collected by [App Name] on iOS
[App Name] collects [e.g. email address and user ID when you create an account; crash data; coarse location from your IP address] for [app functionality / analytics]. Data processed only on your device, such as [photos you edit], is never sent to us.
App Tracking Transparency
We ask permission through Apple's App Tracking Transparency prompt before we or our partners use your advertising identifier (IDFA) or link this app's data with other companies' data for advertising. If you allow tracking, [partner names] receive [IDFA, ad interactions] to [show personalized ads / measure ads]. If you decline, we do not access the IDFA. You can change your choice in Settings > Privacy & Security > Tracking.
Third-party SDKs
The app includes third-party software that collects data on our behalf: [Firebase Crashlytics (Google): crash reports; RevenueCat: purchase history; OneSignal: push token]. Each provider must protect this data to a standard equal to this policy.
Retention and deletion
We keep account data while your account is active and delete it within [30] days of account deletion. Delete your account in [Settings > Account > Delete Account] or email [privacy@example.com] to request deletion or withdraw consent.
Rather not edit a template? The generator on our homepage writes these sections from your answers.
Frequently Asked Questions
Does my iOS app need a privacy policy?
Yes. Apple requires a privacy policy URL for all apps, including apps that collect no data. That policy can be short, but it must load publicly and be linked inside the app.
What is App Tracking Transparency (ATT) and why is it required?
ATT is the framework behind the "Allow to track" prompt. Since iOS 14.5, apps need permission through it before tracking users across other companies' apps and websites or reading the IDFA.
Do I need to disclose all third-party SDKs and frameworks?
Disclose the data every SDK collects, in both the App Privacy answers and the policy. Naming providers (Google for Firebase, Meta for the Facebook SDK) shows who receives it.
What are Privacy Nutrition Labels and how do they relate to my privacy policy?
They are the App Privacy cards on your product page, built from your App Store Connect answers. Their data types, purposes and tracking answers must match the policy.
Can Apple reject my app if the privacy policy isn't iOS-specific enough?
Yes. A policy that does not name the app, omits SDK data, or skips retention and deletion can be rejected under Guideline 5.1.1(i).
How does Sign in with Apple affect my privacy policy?
Users can hide their email, so you may receive a relay address ending in privaterelay.appleid.com. Say that you receive a name and an email or relay address from Apple.
How often should I update my iOS app privacy policy?
Whenever you add an SDK, a permission or a new use of data, before submitting that version. Update the App Privacy answers in the same release.
This page summarizes Apple's requirements as of the date above; it is not legal advice. Sources: Manage app privacy (App Store Connect Help), App privacy details on the App Store, Third-party SDK requirements, App Review Guidelines.