Export compliance (ECCN/EAR) answered correctly

The ITSAppUsesNonExemptEncryption key in Info.plist is required by the US Bureau of Industry and Security (BIS) under the Export Administration Regulations (EAR). Apple enforces this during upload to App Store Connect — if the key is missing, the submission process stops and requires manual resolution in App Store Connect's compliance section. Declaring true incorrectly (claiming non-exempt encryption when only standard HTTPS is used) can trigger BIS filing requirements that the developer is not equipped to fulfill, creating ongoing regulatory exposure. Most apps qualify for the exemption under EAR §740.17(b)(1) and should declare false.

For apps using only standard HTTPS (the vast majority), set the key to NO in ios/[AppName]/Info.plist:

<key>ITSAppUsesNonExemptEncryption</key>
<false/>

For Expo, configure this in app.json:

"ios": {
  "config": {
    "usesNonExemptEncryption": false
  }
}

If your app implements custom encryption beyond standard TLS — for example, end-to-end encrypted messaging with a custom cipher — set true and consult the BIS Annual Self-Classification Report process. Do not set true as a conservative default; the exemption for standard TLS is explicit and well-established.