FWIW just a couple weeks ago we got through the whole SNAP-R process a lot faster, in about 2 hours. It was a strange experience though. It felt like if anythi

FWIW just a couple weeks ago we got through the whole SNAP-R process a lot faster, in about 2 hours. It was a strange experience though. It felt like if anything Apple was trying to dissuade us from using encryption by presenting this vague legal hoop with very minimal guidance or concrete examples on what to do. The few other iOS devs I asked didn't remember much about it, the impression I got is that everyone not working for a big company with a legal or compliance team pretty much just checks "No" whether or not they're using https. Some people likely don't even realize using https counts as encryption, it wasn't explicitly called out anywhere on the form (though it does say something about "even if the encryption is built in to libraries provided by Apple", but of course no list of which libraries might include encryption). It feels odd and a bit lazy that Apple hasn't made this process any easier, when they clearly think a lot about encryption if they're going so far as to start requiring it. Maybe the legal requirements force them to keep the explanation generic and not do anything to improve the user experience around it.