The App Privacy section in App Store Connect produces the "privacy nutrition label" on your App Store page. You must complete it before you can submit a new app or an update, and you are responsible for what your third-party SDKs collect, not only your own code.
Most mistakes come from guessing. Here's how to answer it methodically.
Step 1: Does your app collect data?
In Apple's definition, "collect" means transmitting data off the device in a way that lets you or your third-party partners access it for longer than needed to handle the request in real time.
- Data that never leaves the device is not collected.
- Data sent to your server only to process a request and then discarded right away is generally not collected.
- Data sent to an analytics, crash reporting or advertising SDK is collected, even if you never look at it.
Apple also defines a narrow set of criteria for optional disclosure, such as an infrequent, clearly labeled, user-initiated feedback form that isn't used for tracking or advertising. Every criterion must apply. If you are not sure, disclose.
If nothing is collected, answer "No" and your label shows Data Not Collected. You still need a privacy policy.
Step 2: List data types, SDK by SDK
Start from your dependencies, not your memory. Open your Podfile, Package.swift or Xcode project and list every SDK. Then, for each one:
- Read the SDK's privacy documentation and its privacy manifest (
PrivacyInfo.xcprivacy). Apple requires privacy manifests for commonly used SDKs. - In Xcode, archive your app and choose Generate Privacy Report to see collected data types from all manifests in one place.
Map what you find to Apple's categories: Contact Info, Health & Fitness, Financial Info, Location, Sensitive Info, Contacts, User Content, Browsing History, Search History, Identifiers, Purchases, Usage Data, Diagnostics, Surroundings, Body and Other Data.
Step 3: Choose purposes for each data type
For each data type, select every purpose that applies:
- Third-Party Advertising: showing third-party ads in your app, or sharing data with parties who show ads.
- Developer's Advertising or Marketing: your own ads or marketing, such as promotional emails.
- Analytics: understanding user behavior and measuring features or audiences.
- Product Personalization: customizing what the user sees, such as recommendations.
- App Functionality: authentication, customer support, preventing fraud, crash prevention, and other features the app needs to work.
- Other Purposes: anything not covered above.
Crash logs are a common example of data with two purposes: App Functionality (fixing crashes) and Analytics (measuring stability across releases).
Step 4: Linked to the user?
Data is linked to the user when it's connected to their identity, through their account, their device or other details. Most data you store alongside a user ID or an email address is linked.
Data counts as not linked only if you take real steps to de-identify it: remove direct identifiers before collection, and don't try to re-link it later.
Step 5: Used for tracking?
Tracking has a specific meaning: linking data from your app about a user or device with data from other companies' apps, websites or offline sources for targeted advertising or advertising measurement, or sharing it with data brokers.
- If any data type is used for tracking, you must also request permission through App Tracking Transparency before tracking.
- Analytics you run only for yourself is usually not tracking.
- Ad SDKs that use the advertising identifier for attribution often are.
A worked example
Take a habit-tracking app with Sign in with Apple, an in-app purchase SDK, a crash reporter and a product analytics SDK. A typical label could look like this. Always confirm against each SDK's own documentation.
- Contact Info > Email Address: App Functionality. Linked. Not tracking.
- Identifiers > User ID: App Functionality. Linked. Not tracking.
- Purchases > Purchase History: App Functionality. Linked. Not tracking.
- Diagnostics > Crash Data: App Functionality, Analytics. Not linked. Not tracking.
- Usage Data > Product Interaction: Analytics. Not linked. Not tracking.
Step 6: Keep the label and the policy in sync
Your privacy policy and your App Privacy answers describe the same facts, so they should never disagree. When you add an SDK, update both. You can edit App Privacy answers in App Store Connect at any time, without submitting a new build.
How AppSubmitKit handles this
AppSubmitKit uses one questionnaire for both outputs. You pick your SDKs from a catalog that pre-fills their typical data types, confirm purposes, linking and tracking using Apple's categories, and get two things: a hosted privacy policy in each of your languages, and an App Privacy answer sheet in the order App Store Connect asks for it. Change an answer, and the policy is marked for republishing so the two never drift apart.
The generated policy is a starting point, not legal advice. If your app handles sensitive data, have it reviewed by a lawyer.