OOmnistu

Blog / Engineering Playbooks

Engineering Playbooks

Apple's Privacy Manifest, Explained: PrivacyInfo.xcprivacy and What It Must Declare

What the bundled privacy manifest records - collected data types, required-reason APIs, tracking declarations with network-level teeth - and how it differs from the App Store privacy label and Play's Data safety section.

OOmnistu
Reviewed 2026-11-19 · 3 min read

Apps and third-party SDKs can carry a privacy manifest - a bundled property list named PrivacyInfo.xcprivacy that tells the store, and your users, what data the code collects and which sensitive APIs it touches. It is not the App Store privacy label, and confusing the two is how teams end up with mismatched declarations and review delays.

What the manifest actually is

Apple's documentation defines the privacy manifest as a property list recording two things: the types of data your app or third-party SDK collects, which you must provide on all platforms, and the "required reasons" APIs it uses, which you must provide on iOS, iPadOS, tvOS, visionOS and watchOS. In Xcode you add it via File > New File, choosing the App Privacy file type; the required name is PrivacyInfo.xcprivacy, and it must be included in the target's resources for Xcode to fold it into the privacy report it can generate for your app. Four top-level keys carry the declaration: NSPrivacyTracking (whether you track as App Tracking Transparency defines it), NSPrivacyTrackingDomains (the tracking domains you contact - with teeth: if the user has not granted tracking permission, network requests to those domains fail), NSPrivacyCollectedDataTypes (what you collect), and NSPrivacyAccessedAPITypes (which required-reason API categories you use and why).

Third-party SDKs have their own obligations

If you ship an SDK - as an XCFramework, Swift package or Xcode project - Apple says you need to include a privacy manifest if your SDK is on Apple's list of SDKs that require a privacy manifest and signature, or if it uses a required-reason API, collects data about the app's users, enables the app to collect such data, or contacts tracking domains. There is a practical build detail buried in the guidance: SDKs distributed as static libraries should use Xcode 15's static-framework support so the manifest can be bundled as a resource. For app developers, this is the part that matters day to day: your manifest is only as honest as the SDKs you embed, and the privacy report Xcode generates is how you check what they declared before Apple does.

Manifest, label, and Data safety: three different artifacts

The privacy manifest lives inside the bundle and is read by tools. The App Store privacy label is the store-listing declaration you fill in App Store Connect - the public-facing summary on your product page. Google Play's parallel artifact is the Data safety section, declared in Play Console rather than bundled in the binary; Play has no bundled-manifest counterpart. They overlap in content but not in mechanism, which is why drift between them is the common failure: the manifest says what the code does, the label says what you told the store, and reviewers and automated checks can compare. Keeping them in sync is a release-process item, not a one-time form.

A short checklist

The honest summary

The privacy manifest moved privacy disclosure from a store form into the artifact itself: machine-readable, bundled, and - for domains declared in NSPrivacyTrackingDomains - enforced at the network layer: requests to those domains fail if the user has not granted App Tracking Transparency permission. The work it creates is inventory and reconciliation: know what your code and your SDKs collect, declare it in the manifest, and keep the store listings telling the same truth.

Sources

Prepared with AI assistance and reviewed before publication. Manifest keys, platform scope and SDK obligations are drawn from the Apple documentation page above, checked on 19 November 2026.