How to answer Apple’s encryption question honestly.
Every iOS developer meets it on the first TestFlight upload: a build marked Missing Compliance and a question about whether the app uses encryption. The common advice is to add one line to Info.plist, set it to NO, and never see the question again. That advice is often right, but for a different reason than people think, and for a lot of apps the honest answer depends on something nobody mentions: whether you sell in France.
What the question is actually asking
Apple’s documentation explains why it asks at all. When you upload a build, it goes to a server in the United States, and if you distribute outside the U.S. or Canada, the app is subject to U.S. export law wherever your company is based. In Apple’s words, if your app “uses, accesses, contains, implements, or incorporates encryption,” that counts as an export of encryption software. You’re also subject to the import rules of the countries you sell in.
The Info.plist key is ITSAppUsesNonExemptEncryption, and the word that matters is non-exempt. Apple says to set it to NO if your app, “including any third-party libraries it links against,” either doesn’t use encryption or only uses forms of encryption that are exempt from export compliance documentation requirements. So NO doesn’t mean “my app has no encryption.” Almost every app that talks to a server has encryption. NO means “nothing in my app requires me to upload documents.” That’s a claim you can check, and the half of it people skip is the clause about third-party libraries.
Apple sorts every app into three cases
App Store Connect’s help has a short table that does most of the work. Paraphrasing its three rows:
- Encryption limited to what’s in Apple’s operating system. HTTPS through URLSession, CryptoKit, the system’s own TLS. No documentation required in App Store Connect.
- An industry-standard algorithm that isn’t provided by Apple’s operating system. Your own copy of TLS, AES or similar, bundled in the app. Upload a French encryption declaration, and a footnote says that’s only required if you distribute on the App Store in France.
- Proprietary algorithms not accepted by an international standards body such as the IEEE, IETF or ITU. Upload a CCATS, a formal classification from the U.S. Bureau of Industry and Security, plus the French declaration if you’re in France.
Very few indie apps are in the third row. Rolling your own cipher is a bad idea for reasons that have nothing to do with export law. The interesting line is between the first two rows, because it isn’t about what your code does. It’s about whose code does it.
Your dependencies probably bring their own TLS
If you write a native Swift app and make every network call through URLSession, you’re in the first row. Cross-platform apps and apps with large SDKs often aren’t, because those stacks ship their own cryptography instead of calling the system’s.
We checked our own Flutter app. The Flutter engine that ships inside every iOS release build, Flutter.framework, contains BoringSSL, Google’s fork of OpenSSL; its source paths are right there in the binary. Dart’s built-in HttpClient is socket-based rather than a wrapper around URLSession, which is why the Dart team publishes cupertino_http as a separate package for apps that want the system’s networking stack. Our Podfile.lock turned up a second copy: the Firestore iOS SDK talks to its backend over gRPC, and it pulls in a pod called BoringSSL-GRPC. Neither was a decision anyone on the team made. Both came in with a dependency.
That doesn’t make these libraries a problem. They implement standard, published algorithms, which puts an app that bundles them in Apple’s second row, not its third. What it changes is the answer you’re giving when you set the key to NO without looking.
A twenty-minute audit
You can find out which row you’re in without reading any law, by looking at what the build actually contains.
- Read the lock files. Search Podfile.lock, Package.resolved for the usual names: BoringSSL, OpenSSL, libsodium, SQLCipher, CryptoSwift. Anything that encrypts a local database or a file counts, not only networking.
- Search the binary itself. Build an archive, open the .app bundle and run strings over each framework in its Frameworks folder, grepping for boringssl or OPENSSL_. This catches static libraries that never show up as a named dependency.
- Write down what each one is for. TLS for API calls, an encrypted local store, a payment SDK’s own channel. You’ll need this for App Store Connect’s questions anyway, and it’s useful the day someone asks.
- Check your territories. In App Store Connect, look at which countries the app is available in. If France is on the list and anything you found is in the second row, Apple’s table says you need the French declaration.
What to do with the answer
If everything you found goes through Apple’s frameworks, set the key to NO and you’re done. If you bundle standard crypto and don’t distribute in France, Apple’s table says no documentation is required, which is the condition for NO. If you bundle standard crypto and do sell in France, the honest key value is YES: you upload the declaration in App Store Connect under App Information, and Apple’s help page says it expects to review complete submissions in about two business days. Once it’s approved you get a code, which goes in a second key, ITSEncryptionExportComplianceCode, so later builds stop asking.
France isn’t an arbitrary detail. Apple’s overview notes that the French government controls the import and export of encryption apps, with secure storage, secure communications and security anti-virus apps as the main items of control and banking and medical apps among the exemptions. It points to ANSSI, the French national cybersecurity agency, for the specifics. If you’re unsure whether your app needs a declaration, that’s the place to read, not a forum thread.
One more thing that trips people up. Apple’s developer article still warns that apps using exempt encryption might need to file an annual self-classification report with the U.S. government. In March 2021 the Bureau of Industry and Security removed that reporting requirement for most mass-market encryption products, according to law-firm summaries of the rule published at the time. It kept it for a narrow set of items, mostly chips, components and toolkits. If your app is an ordinary consumer app using standard TLS, check the current rule before you spend a weekend on a report you may not owe.
Who’s on the hook
Apple asks the questions, but the answers are yours. Its help page is blunt that reviewing the export regulations is your responsibility and that you’re liable for misinterpreting them or claiming an exemption inaccurately. This post isn’t legal advice, and an app that does anything unusual with cryptography should talk to someone who does this for a living.
For everyone else, the practical version is short. Know what crypto your build contains, know which of Apple’s three rows that puts you in, and know whether you sell in France. Then set the key to the value that matches, and re-run the audit whenever you add an SDK, because the next dependency can change the answer without changing a line of your own code. It’s the same lesson we took from reading every privacy manifest in our app: the declarations Apple asks for describe your whole bundle, and most of the bundle isn’t yours.