Repository navigation
|
How can a team catch Missing Privacy Nutrition Labels data type declarations automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rn 'email\|phoneNumber\|userName\|location\|coordinates' --include='*.swift' . && ! grep -rn 'NSPrivacyCollectedDataTypes\|privacyNutritionLabels\|privacy-nutrition-labels' .Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. Collecting sensitive user data (e.g. email, phone, name, coordinates) but missing the privacyNutritionLabels declaration or proper nutrition disclosure references. The fix. Update the app privacy manifest (PrivacyInfo.xcprivacy) with NSPrivacyCollectedDataTypes and complete corresponding Nutrition Labels in App Store Connect. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
APPLE-PRIVACY-NUTRITION-LABELSwith a coverage line and a proper exit code.What the hit means. Collecting sensitive user data (e.g. email, phone, name, coordinates) but missing the privacyNutritionLabels declar…