One more thing... on encryption export compliance for iPhone apps
Let me add an important thing to the previous posts (see our first blog post to start from the beginning):
Let me add an important thing to the previous posts (see our first blog post to start from the beginning):
Thanks very much for the information. Looks like we are in the same boat as you. :(
On iTunes Connect, how do you go through the process of confirming to Apple you will go through with CCATS but start selling in US and Canada right away? Once it asks "Does your product contain encryption used for protection of data or information security purposes?" we are FORCED to enter a CCATS PDF.
Do you say your product doesn't contain encryption and then Apple will add the ruling later?
Do you have an appropriate contact at Apple we could ask about this?
Thanks very much!
Jeremy
we selected 'doesn't contain encryption' and then entered the process via e-mail with Apple. But I can't recommend that simply because we don't know yet if this means we have to resubmit our application data or if Apple can change these settings without affecting our existing application info and/or a binary that may already have been submitted in other cases. If you've got the time: it looks like you should only complete it when you've gone through the whole CCATS process.
What we did was sending an e-mail to itunesconnect[at]apple.com. They routed our request to an Export Compliance Specialist who took care of us and offered that 3-step-process. That was all by e-mail and not via iTunesConnect.
thank you for a nice article, as the rest of the compliance series. I am curious on how long the process did take.
There seems to be new rules regarding the export laws. Any comment on that? See link for more information.
http://www.bis.doc.gov/encryption/
Regards
Joham