Privacy manifests (PrivacyInfo.xcprivacy)
A file in each app and listed SDK that states what data it collects and why, checked by Apple at upload.
In one line
Can list what the app and its add on tools collect, in a file Apple checks
A file in each app and listed SDK that states what data it collects and why, checked by Apple at upload.
Apple turned self-declared privacy into machine-readable files. Xcode merges them into a privacy report, and tracking domains get blocked for ATT-denied users.
What it can and can't do
What the user does: Nothing. It is checked when the developer uploads the app, and shown in a privacy report
It can
- Show what data each tool says it collects and why
- Block tracking sites for people who said no to tracking
- Flag missing reasons so Apple can reject the upload
It cannot
- Prove the file is complete without Apple's checks
- Apply on Android; Google uses the Data safety form and SDK Index
- Skip warnings: rejection for missing reasons began 1 May 2024
How it differs between platforms: Only iPhone (iOS 17 and later) has these files. Android has no such file.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Not supported | Supported |
| First version | Not available | iOS 17.0 |
| Permission or entitlement | Not listed | Not listed |
| Protection level | none | none |
| How access is granted | not-exposed | none |
| What the user sees | Not listed | Not listed |
| How long it lasts | Not listed | Not listed |
| How to take it back | Not listed | Not listed |
| Store policy | None listed | Required in new submissions that use listed SDKs or required reason APIs since 1 May 2024; signed SDK requirement for listed third party SDKs |
| API | Not listed | PrivacyInfo.xcprivacy: NSPrivacyTracking, NSPrivacyTrackingDomains, NSPrivacyCollectedDataTypes, NSPrivacyAccessedAPITypes |
| Notes | No manifest file. Play uses the Data safety form and the SDK Index instead. | Upload warnings started March 2024; rejection for missing reasons started 1 May 2024. Domains in NSPrivacyTrackingDomains are blocked when ATT is denied. |
Data you get
What comes back: Plist of declarations
Shape: object
How often: static per build
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
NSPrivacyTracking | boolean | None | Not listed | Not listed |
NSPrivacyTrackingDomains | list | None | Not listed | Not listed |
Technical limits
- iOS only
- Self declared; Apple spot checks
- Apps with unlisted reasons get rejected
The story
What it is
A file inside each iOS app that states what data it collects and why, checked by Apple.
For you
You never read it, but it helps. Xcode can merge the files into a privacy report, and tracking domains can be blocked for people who said no to tracking.
For makers
It turns promises into a file Apple can check at upload. Makers must keep a manifest for the app and each popular SDK, and update it whenever an SDK changes what it collects.
Where you see it
| Type | Example | Apps |
|---|---|---|
| ads | An ad SDK ships a manifest that lists its tracking domains, so iOS can block them if the user said no. | Google AdMob, AppLovin |
| games | A game studio adds manifests for four SDKs before upload, or App Store Connect rejects the build. | Supercell |
| analytics | An analytics tool states that it collects device IDs for analytics only, not ads. | Firebase, Amplitude |
| social | A social app generates a privacy report to compare with its nutrition label. | Snapchat |
| security | Researchers read manifests to find SDKs that quietly collect more than the app says. | None named |
| developer | A developer explains in the manifest that a file timestamp API is only used to show file dates. | None named |
Risks
- Self declared
- Can lag behind code
Android and iPhone in short
- Android: Android has no matching file. Google uses the Data safety form and the SDK Index.
- iPhone: Required for new apps and listed SDKs from spring 2024.
What the platform says
- Apple: Privacy manifest files. Apps and SDKs describe the data they collect and the reasons they use certain APIs.
Good uses and abuse
Legitimate uses
- Auditable data use
Known abuse
- Wrong or empty declarations
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 1 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2023-06, iPhone WWDC23: Privacy manifests announced
- 2024-03, iPhone Xcode 15.3: App Store Connect begins emailing warnings
- 2024-05, iPhone App Store: Required reason API declarations enforced from 1 May 2024
Related capabilities
Related
- Required reason APIs. Can't use fingerprint prone phone details on iPhone without an approved reason
- App Store privacy nutrition labels. Can tell you what the app says it collects, on its App Store page
- Third-party SDK data sharing. Can share anything the app can see with its add on tools, who send it on
Sources
How well checked: Based on official documentation.