Apple Privacy Manifest Guard for React Native

It reads a source file or a PrivacyInfo.xcprivacy and flags every line Apple treats as a required-reason API call. For each hit it names the category, such as NSPrivacyAccessedAPICategoryUserDefaults, and lists the reason codes Apple accepts there. It carries 36 rules covering all 5 categories and all 14 approved reason codes.

React Native, Flutter and Capacitor developers who ship iOS builds. They are the ones who get caught, because they never type the native symbol: shared_preferences and getFreeDiskStorage look like plain Dart and JavaScript, but on iOS they reach NSUserDefaults and the disk-space APIs, and Apple wants both declared.

Xcode does not check this at build time, so nothing warns you until App Store Connect emails ITMS-91053 after the upload. Chatbots confidently invent reason codes: there are exactly 14 approved codes and 5 categories, and a plausible-looking code such as C56D.9 is rejected as ITMS-91055.

Checking a file is free and always will be: open a file, run the check, get every finding with its category and legal reason codes. A licence adds scale and evidence, not answers. It scans the whole repository, writes the findings to a CSV, JSON or HTML report, and emits CI JSON so a build can fail on a missing declaration.

Mid-level freelance iOS developers bill $85 to $145 an hour in the 2026 US market, and the usual path is discovering the problem after the upload, then paying for a diagnosis and a resubmission. The extension is $29 once, one licence key per person or team seat, with a 7-day full refund.