TY - GEN
T1 - User comfort with android background resource accesses in different contexts
AU - Votipka, Daniel
AU - Rabin, Seth M.
AU - Micinski, Kristopher
AU - Gilray, Thomas
AU - Mazurek, Michelle M.
AU - Foster, Jeffrey S.
N1 - Funding Information:
We thank the anonymous reviewers for their helpful feedback. This research was supported in part by a UMIACS contract under the partnership between the University of Maryland and DoD, and by a Google Research Award.
PY - 2019
Y1 - 2019
N2 - Android apps ask users to allow or deny access to sensitive resources the first time the app needs them. Prior work has shown that users decide whether to grant these requests based on the context. In this work, we investigate user comfort level with resource accesses that happen in a background context, meaning they occur when there is no visual indication of a resource use. For example, accessing the device location after a related button click would be considered an interactive access, and accessing location whenever it changes would be considered a background access. We conducted a 2,198-participant fractional-factorial vignette study, showing each participant a resource-access scenario in one of two mock apps, varying what event triggers the access (when) and how the collected data is used (why). Our results show that both when and why a resource is accessed are important to users' comfort. In particular, we identify multiple meaningfully different classes of accesses for each these factors, showing that not all background accesses are regarded equally. Based on these results, we make recommendations for how designers of mobile-privacy systems can take these nuanced distinctions into account.
AB - Android apps ask users to allow or deny access to sensitive resources the first time the app needs them. Prior work has shown that users decide whether to grant these requests based on the context. In this work, we investigate user comfort level with resource accesses that happen in a background context, meaning they occur when there is no visual indication of a resource use. For example, accessing the device location after a related button click would be considered an interactive access, and accessing location whenever it changes would be considered a background access. We conducted a 2,198-participant fractional-factorial vignette study, showing each participant a resource-access scenario in one of two mock apps, varying what event triggers the access (when) and how the collected data is used (why). Our results show that both when and why a resource is accessed are important to users' comfort. In particular, we identify multiple meaningfully different classes of accesses for each these factors, showing that not all background accesses are regarded equally. Based on these results, we make recommendations for how designers of mobile-privacy systems can take these nuanced distinctions into account.
UR - http://www.scopus.com/inward/record.url?scp=85075924443&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=85075924443&partnerID=8YFLogxK
M3 - Conference contribution
AN - SCOPUS:85075924443
T3 - Proceedings of the 14th Symposium on Usable Privacy and Security, SOUPS 2018
SP - 235
EP - 250
BT - Proceedings of the 14th Symposium on Usable Privacy and Security, SOUPS 2018
PB - USENIX Association
T2 - 14th Symposium on Usable Privacy and Security, SOUPS 2018
Y2 - 12 August 2018 through 14 August 2018
ER -