Build a PrivacyInfo.xcprivacy file without digging through the docs.
Reason codes checked against Apple's documentation · September 2026
Start from
Most apps only touch UserDefaults. Start there, then add anything else you use.
Required reason APIs
Tick each API category your code calls, then every reason that applies. Third-party SDKs ship their own manifests, so only include your own code.
Tracking
Collected data
Tick data your app or its server collects. Leave empty if nothing leaves the device.
Contact info
Health & fitness
Financial
Location
Sensitive & contacts
User content
History
Identifiers
Usage data
Diagnostics
Body & surroundings
Other
PrivacyInfo.xcprivacy
In Xcode: File → New → File → App Privacy, or drop this file into your app target. Make sure it's included in the target's Copy Bundle Resources.
Quick answers
Do I need a privacy manifest?
Yes if your app calls any required reason API. Since May 2024 App Store Connect rejects uploads that use these APIs without declaring a reason, and nearly every app touches UserDefaults.
Does this replace the App Store privacy label?
No. You still fill in App Privacy in App Store Connect. Xcode can generate a privacy report from your manifests to help keep the two in sync.
What about my SDKs?
Each third-party SDK must include its own privacy manifest. Update to recent versions of Firebase, RevenueCat and so on, which ship them.
