When publishing to the App Store, you must declare if your application uses encryption in order to comply with U.S. export regulations.
To make a declaration, you must add the ITSAppUsesNonExemptEncryption key in your applications Information Property List file. If your application doesn’t use encryption, or uses encryption that’s exempt from U.S. export compliance, set ITSAppUsesNonExemptEncryption to false.
The Unity core platform doesn’t use non-exempt encryption. If you’re using the core Unity platform with the iOS module, you can set ITSAppUsesNonExemptEncryption to false. However, it’s your responsibility to check that any third-party components and plug-insA set of code created outside of Unity that creates functionality in Unity. There are two kinds of plug-ins you can use in Unity: Managed plug-ins (managed .NET assemblies created with tools like Visual Studio) and Native plug-ins (platform-specific native code libraries). More info
See in Glossary included in your Unity project comply with encryption export regulations.
For more information, refer to Complying with Encryption Export Regulations.
Note: UnityWebRequest uses NSURLSession which is exempt from export compliance.
The Unity Mobile Notifications package is built on top of Apple’s notification API. Any networking for notifications is handled by the operating system, not the application, and is therefore exempt.