1 Reply
      Latest reply on Jul 10, 2019 12:22 PM by KMT
      mariiasaveleva Level 1 Level 1 (0 points)

        Hello,

         

        I'm working on demo application which uses HTTPS to communicate with server and Google's open-source authorization cocoapod (https://github.com/google/auth-library-swift.git) to authorize to Google's service account. This cocoapods has CryptoSwift as a dependency (https://github.com/krzyzanowskim/CryptoSwift).

        I'm going to distribute it for beta testing for external testers via TestFlight.

         

        According to documentation (https://help.apple.com/app-store-connect/#/devc3f64248f), looks like in my case the encryption is used for authentication and qualifies for exemptions provided under category 5 part 2, of the BIS Export Administration Regulation.

         

        As I understand, I DON'T need to:

        - Send any additional documents to Appstore connect

        - Submit a Self Classification Report to the U.S. Bureau of Industry and Security (BIS) directly.

         

        Is it correct?

        Also, is the process different for TestFlight open beta release (for external testers with public link) and Appstore release?

         

         

        Thank you!

        • Re: Export compliance documentation for encryption
          KMT Level 9 Level 9 (14,355 points)

          Seen this discussion from last year?

           

          h ttps://github.com/krzyzanowskim/CryptoSwift/issues/76

           

          My opinion is the same as yours...don't need to do anything.

           

               >...is the process different for TestFlight open beta release (for external testers with public link) and Appstore release?

           

          I would expect them to be one and the same, at least in your example. Review is review...