Privacy nutrition label

The privacy nutrition label is the App Privacy section shown on your App Store product page, generated from a questionnaire you complete in App Store Connect and required before you can submit.

You declare it per data type, across categories like contact info, health, location, identifiers, usage data and diagnostics. For each one you say what it is used for, whether it is linked to the user's identity, and whether it is used to track them across other companies' apps and sites. Those last two produce the three headings users see: Data Used to Track You, Data Linked to You, and Data Not Linked to You.

The part that catches people is that you declare what your app does, including your dependencies. An analytics SDK, an ads SDK, a crash reporter or an attribution library collecting identifiers is your disclosure to make. "I did not write that code" is not a defence, and reviewers do compare declared behaviour against observed network traffic.

It is separate from the label but easy to confuse: the privacy manifest, a PrivacyInfo.xcprivacy file inside the app or SDK bundle that declares required-reason API usage and tracking domains. The label is what users read. The manifest is what tooling reads.

Keep the label, your privacy policy and your actual code saying the same thing. Contradictions between the three are a routine rejection.

See also: purpose string, Data safety, metadata rejection.