Zamen | زامن
Comment: Differential privacy and data collection is still not clearly defined as opt-in on iOS 10
When Apple originally announced the use of differential privacy in iOS 10, it was not without a little controversy. Skeptics from all corners began wondering how private differential privacy could really be when used in a mass deployment in the way that iOS 10 was going to use it.
Apple clarified that the use of differential privacy to collect user data would be opt-in, meaning if a user didn't want to give into the system they didn't have to. What Apple never indicated was where this opt-in area would be and what would happen if you decided against it…
When iOS 10 was officially released to the public a few weeks back, I decided to start from scratch versus restoring from a backup. Not because of any lingering idea that something from past iOS backups would interfere with iOS 10, but just to see what a new user on iOS 10 would see. The one thing I was critically looking for was the indication of where I could opt-in to Apple's use of differential privacy, and that's where it all got hazy.
Being an amateur iOS developer, I've grown accustomed to configuring devices and always opting-in to sharing diagnostic and usage information. I understand the importance of receiving crash reports from users so that a developer can work quickly to resolve issues. What I neglected to do was find where the instated differential privacy options with iOS 10 came in. The situation was made even more evident to me by Aleksandra Korolova, an assistant professor working on privacy at the University of Southern California's Viterbi School of Engineering.