http://tigelane.blogspot.com/2011/01/apple-itunes-export-restrictions-on.html

...or other crypto functions.

Questions: (that's a great resource by the way)

1. Is using HTTPS considered using encryption? It seems to me you're accessing a URL and its the iOS API's that are actually being used or is that a Corona feature?

2. I'm gathering using the Corona SDK's crypto API will require going through this process. Are they considered published international standards?

3. What about something like UUENCODE or Base64 encoding? Not really encryption but its modifying text to keep it from being read, so I could see it being considered encryption. Certainly those qualify as published international standards but do they require you to say you're using encryption?

Apple's iTunes Connect > Frequently Asked Questions > World Wide Trade Compliance for the App Store goes into this in detail. But I'd say 1) It is. And 2) Should be. Even using encryption built into iOS or Mac OS qualifies.

Not sure about UUENCODE but sounds like Uncle Sam wants to hear about everything, so probably so if you like to play it safe.

http://stackoverflow.com/questions/2128927/using-ssl-in-an-iphone-app-export-compliance