iOS privacy nutrition labels match actual data collection

Apple reviews nutrition label accuracy both during the review process and in response to user reports filed through the App Store. Mismatches like declaring analytics as 'Data Not Linked to You' while calling setUserId() expose you to enforcement and rejection on every subsequent update. Under Apple's App Privacy guidelines (external apple-app-privacy) and GDPR Art.13, users have a right to accurate disclosure of what data is collected and how it is linked to their identity. A mislabelled label is not a minor oversight — Apple has removed apps and forced resubmission for label inaccuracies.

Use Xcode's App Privacy Report on a real device (Settings → Privacy & Security → App Privacy Report) to see what data your app actually accesses at runtime. Cross-reference every third-party SDK's published nutrition label documentation — Google, Meta, and most major SDKs publish these.

For fastlane users, keep nutrition label declarations in fastlane/metadata/ios/ and audit them before every submission. Pay particular attention to analytics: if setUserId() or any equivalent identify() call exists in the codebase, analytics data is linked to the user and must be declared as 'Data Linked to You.'