privacy-ux

A privacy manifest is a PrivacyInfo.xcprivacy file that declares data collection and API usage in your iOS app. Create it in Xcode 15+ by adding NSPrivacyCollectedDataTypes and NSPrivacyAccessedAPITypes to specify what data you collect and which Required Reason APIs you access, then submit it to App Store Connect alongside your Privacy Nutrition Label.

App Tracking Transparency (ATT) is a user permission prompt for tracking consent on iOS 14.5+, while privacy manifests declare all data collection and API usage regardless of tracking status. Both are required: ATT gates ad tracking, manifests provide complete transparency about data handling in your Privacy Nutrition Label.

Just-in-time permission UX shows permission requests only when users actually need a feature, not at app launch. Implement it by triggering permission prompts immediately before accessing the camera, pair it with ATT integration for iOS 14.5+, and document the access reason in your privacy manifest's NSPrivacyAccessedAPITypes.

iOS 17+ automatically blocks tracking domains declared in your privacy manifest, so you must list all third-party domains that track user activity. Declare them in NSPrivacyTracking within your PrivacyInfo.xcprivacy file; this prevents your app from being rejected during App Store review.

Required Reason APIs are system functions like file access or calendar queries that iOS restricts and requires you to declare a legitimate business reason for using. List them in NSPrivacyAccessedAPITypes within your privacy manifest; without declaring reasons, your app will be rejected during review.

Yes, privacy manifests feed directly into your Privacy Nutrition Label on App Store Connect. The NSPrivacyCollectedDataTypes and NSPrivacyAccessedAPITypes declarations you make in your PrivacyInfo.xcprivacy file automatically populate and validate your disclosure, ensuring consistency between your manifest and public label.