What is export compliance? (ITSAppUsesNonExemptEncryption)

Apple asks because software that uses encryption falls under US export controls, and it points developers to the Export Administration Regulations. Apple says that if your app uses, accesses, contains, implements or incorporates encryption, you need to determine its export compliance requirements, and its examples include standard encryption algorithms and the cryptography built into Apple’s operating systems. Which answer is right for your app is your call: Apple says the responsibility, and the liability for a wrong exemption claim, is yours.

ITSAppUsesNonExemptEncryption is the Info.plist key that answers the question in the build itself. NO means the app, including the libraries it links, uses no encryption or only encryption that is exempt. YES means it uses non-exempt encryption; you then also set ITSEncryptionExportComplianceCode to the code Apple gives you after reviewing your documentation. Without the key, App Store Connect walks you through the questionnaire for every upload, and until it is answered the build shows Missing Compliance. The Missing Compliance guide shows how to set the key in a native or Expo project.

In VibeView. VibeView answers Apple for each build from the first of these that has an answer: your Info.plist key, then the answer saved for the app. The Submit dialog asks once (No or Yes) and saves it for every later build; change it in Builds → Stores → your app → Edit, or with vibeview testflight encryption --no-uses-encryption (CLI 0.56.0 or later). With Yes, the build waits until you upload your documents in App Store Connect; VibeView doesn’t upload them. See Export compliance.