Free export compliance check
Check ITSAppUsesNonExemptEncryption, encryption scope, third-party SDK review, and the next technical detail to verify in App Store Connect.
Answer four questions about the planned iOS build. The check identifies contradictions and the next evidence to collect, but it does not make a legal export classification.
{
"expo": {
"ios": {
"infoPlist": {
"ITSAppUsesNonExemptEncryption": false
}
}
}
}Free tool
This Boolean Info.plist key tells Apple whether the app uses non-exempt encryption. If it is absent, App Store Connect asks export-compliance questions during uploads. The correct value depends on the cryptography actually shipped.
HTTPS, secure storage, authentication, VPN, messaging, and bundled SDKs can use encryption. Separate Apple operating-system services from cryptography included by your app or a library.
The inventory must describe the production build. Copying a value from a tutorial or another app is not defensible evidence.
False can fit apps that use no encryption or only exempt encryption. True signals non-exempt encryption and may lead to document and compliance-code requirements.
Exempt standard cryptography can still carry reporting duties or a French declaration. Current Apple material and App Store Connect remain the procedural authority.
Expo can set the key through ios.infoPlist. Config plugins and native changes may alter the resolved value, so inspect the production configuration and final Info.plist together.
The free checker evaluates four answers. A complete LaunchLint scan can find configuration, SDK signals, and contradictions, but cannot provide legal advice.