Export Compliance Checker
Should ITSAppUsesNonExemptEncryption be YES or NO?
Answer once, add the key to Info.plist, and App Store Connect stops asking on every upload.
Include third-party libraries. HTTPS counts, so answer yes if your app talks to any server over https://.
For example HTTPS through URLSession, the Keychain, Data Protection, CryptoKit or CommonCrypto. Answer no if you bundle your own crypto library such as OpenSSL, libsodium or SQLCipher.
For example hashing passwords, verifying signatures or checksums, or DRM. Answer no if it keeps data confidential, such as encrypting files, databases or messages.
AES, RSA, ChaCha20, TLS and similar, usually through a well-known library. Answer no for custom or proprietary algorithms.
Quick answers
What does the key do?
Without ITSAppUsesNonExemptEncryption in your Info.plist, App Store Connect asks the export compliance questions every time you upload a build, and TestFlight builds sit on "Missing Compliance" until you answer.
Where do I set it in Xcode?
Either add the key to Info.plist, or set the build setting INFOPLIST_KEY_ITSAppUsesNonExemptEncryption ("App Uses Non-Exempt Encryption") if your target generates its Info.plist.
Is this legal advice?
No. It follows Apple's published guidance for the common cases. If you ship custom cryptography or aren't sure, read Apple's export compliance docs and check with someone qualified.
