Apple asks about your app's privacy in three separate places, and it is easy to assume one replaces another. It doesn't. Here is what each one is, and how they fit together.
The three, side by side
| Privacy manifest | App Privacy label | Privacy policy | |
|---|---|---|---|
| What it is | PrivacyInfo.xcprivacy file in your Xcode project | Answers in App Store Connect | A web page you host |
| Who reads it | Apple's upload checks, and Xcode's privacy report | Users, on your App Store page | Users, App Review |
| Written by | You, plus each SDK's own manifest | You | You |
| Changes need | A new build | No new build | No new build |
The privacy manifest (PrivacyInfo.xcprivacy)
A property list inside your app bundle that describes:
- the data types your code collects,
- whether the app tracks users, and the domains used for tracking,
- the required-reason APIs you call (such as
UserDefaultsor file timestamp APIs) and the approved reason for each.
Since May 1, 2024, App Store Connect requires approved reasons for required-reason APIs in new uploads. Commonly used third-party SDKs must ship their own manifest (and a signature when you add them as binaries). When you build an archive, Xcode combines all manifests into a privacy report you can use to check your label.
The App Privacy label
The "privacy nutrition label" on your App Store page. You fill it in under App Privacy in App Store Connect: which data types are collected, for which purposes, whether they are linked to the user's identity, and whether they are used for tracking. It must include what your third-party SDKs collect. You can update it at any time without submitting a new build.
Walkthrough: filling in the App Privacy label without guessing.
The privacy policy
A page at a public URL, linked in App Store Connect and inside your app. Guideline 5.1.1(i) asks that it explains what you collect and why, how third parties protect that data, how long you keep it, and how people can ask for deletion. Details: what your privacy policy must say.
Keeping them consistent
Reviewers and users notice when the three disagree. A simple routine:
- Start from your SDK list. Each SDK's documentation describes its data collection; its manifest covers the API reasons.
- Generate Xcode's privacy report from an archive and compare it with your label answers.
- Write the policy from the same answers, so every data type in the label is explained in the policy.
- Revisit all three when you add or remove an SDK.
AppSubmitKit covers the second and third parts: one questionnaire with presets for SDKs like Firebase, AdMob, RevenueCat and Sentry gives you the App Privacy answers and a hosted privacy policy that match. The manifest still lives in your Xcode project.