Privacy Manifest

What is Privacy Manifest?

A Privacy Manifest is a property list file introduced by Apple at WWDC23 as part of iOS 17 privacy updates that documents the data types collected by an app or third-party SDK, the APIs used, and the justified reasons for each. Privacy Manifests are required for apps and SDKs submitted to the App Store, ensuring that data collection practices are declared explicitly and transparently. Xcode aggregates these manifest files from both the app and all included SDKs to generate a unified Privacy Report and accurate Privacy Nutrition Labels.

How it works

Privacy Manifests function as structured declarations embedded within an app bundle or SDK package. When a developer builds their app in Xcode, the tool automatically aggregates all privacy manifest files from the app itself and every third-party SDK included in the project.

Privacy Manifest File Structure

Each manifest file, named PrivacyInfo.xcprivacy, declares three core elements. First, the categories of data collected, such as contact information, location, or usage data. Second, the APIs accessed by the app or SDK, particularly those on Apple's list of required reason APIs. Third, the specific, Apple-approved reason for accessing each API, ensuring that usage aligns with legitimate user-facing functionality rather than fingerprinting or other privacy-invasive purposes.

Required Reason APIs

Required reason APIs are a specific subset of system APIs that Apple identified as having significant fingerprinting potential. An example is NSFileSystemFreeSize, which returns available disk space. Developers must declare an approved reason for using any required reason API in the Privacy Manifest. Apple maintains a categorized list of accepted reasons, and any undeclared or unjustified API usage can result in App Store rejection.

Privacy Nutrition Labels and Privacy Reports

Privacy Nutrition Labels are displayed on an app's App Store product page and summarize the app's data practices for end users. They are generated based on the information declared across all aggregated Privacy Manifests. Xcode compiles this information into a Privacy Report that developers can review before submission, allowing them to verify that all data collection is accurately represented. The Privacy Report mirrors the structure of Privacy Nutrition Labels, giving developers a preview of what users will see.

Third-Party SDK Accountability

Before Privacy Manifests, developers often had limited visibility into exactly what data third-party SDKs collected or which APIs they accessed. Privacy Manifests transfer accountability to SDK vendors, who must now ship their own manifest files with their SDKs. Apple has designated a list of commonly used third-party SDKs, called privacy-impacting SDKs, that require a manifest. Including an SDK without a valid manifest can block App Store approval.

Why it matters

Privacy Manifests represent a meaningful shift in how Apple enforces data transparency across the iOS ecosystem. For app developers, they reduce the risk of App Store rejection by providing a clear framework for declaring data practices before submission. For end users, Privacy Nutrition Labels generated from these manifests provide understandable, consistent information about how their data is used, which builds trust in the apps they install.

For mobile marketers and measurement partners like Airbridge, Privacy Manifests directly affect how SDKs are built and distributed. Airbridge's iOS SDK includes a Privacy Manifest that accurately documents the data it accesses and the reasons for each API call, ensuring that apps integrating Airbridge for attribution and analytics remain compliant with Apple's App Store requirements. Failure to maintain an up-to-date manifest can result in App Store review issues that delay or block app releases, making manifest compliance a critical part of SDK maintenance and integration workflows.

How to comply with Privacy Manifest requirements on iOS

Complying with Apple's Privacy Manifest requirements involves preparation at both the app level and the SDK level.

1. Audit your app's data collection. List every type of data your app collects directly, including user identifiers, usage data, and any diagnostics. Map each data type to Apple's defined categories used in Privacy Nutrition Labels.

2. Audit all third-party SDKs. Check that every SDK integrated into your app ships a PrivacyInfo.xcprivacy file. For SDKs on Apple's privacy-impacting SDK list, a manifest is mandatory. Contact SDK vendors that have not yet provided a manifest.

3. Document required reason API usage. Review your app's code for any APIs on Apple's required reason API list. For each one, select an approved reason from Apple's documentation and declare it in your app's PrivacyInfo.xcprivacy file.

4. Create or update your app's PrivacyInfo.xcprivacy file. Add this file to your Xcode project at the app target level. Declare all collected data types, accessed APIs, and their approved reasons using Apple's defined keys and values.

5. Generate a Privacy Report in Xcode. Before submitting to the App Store, use Xcode's Generate Privacy Report feature to aggregate all manifests from your app and SDKs. Review the output to ensure all declared data practices are accurate and complete.

6. Update your App Store Privacy Nutrition Labels. Use the Privacy Report as a reference when updating the privacy details on your App Store Connect listing. Ensure the labels reflect the actual data collection described in your manifests.

7. Establish an ongoing review process. As you update SDKs or add new data collection features, revisit your Privacy Manifest to keep it current. SDK updates may introduce new API usage that requires additional declarations.

Related concepts