Evaluating the Impact of Community Oversight for Managing Mobile Privacy and Security
summary
Built a mobile tool called CO-oPS app and deploys it in a four-week field study with 101 participants across 22 communities to test community-based oversight of app permissions. Quantitative logs show a majority change at least one permission — often permissions changed to deny — and about half hide apps; surveys report higher transparency, trust, and awareness but no change in belonging. Qualitative interviews flag expertise gaps, privacy concerns, and the lack of a control group as key limits.
AI-written summary · about
chapters (12)
- 0:00Community oversight introduction
- 1:14CodCops app design
- 2:18Field study methodology
- 3:44Survey constructs and data
- 4:49Transparency and privacy findings
- 5:32Awareness from app usage
- 6:15Trust in oversight communities
- 6:57Participation and decisions
- 7:39Privacy management efficacy
- 8:44Limitations and future work
- 10:48Key insights and features
- 11:49Conclusion
related talks
28mEmbracing innovation by building privacy friendly apps
13mSafetypedia: Crowdsourcing Privacy Inspections
37mHey, You, Get off My Private Data: Do Apps Respect Your Privacy as They Claim?
29mCOVID-19 Apps: Public Health or Hype?
08mComparing User Perceptions of Anti-Stalkerware Apps with the Technical Reality
14mTowards Understanding Privacy and Trust in Online Reporting of Sexual Assault
06mAppMoD: Helping Older Adults Manage Mobile Security with Online Social Help
05mA Fait Accompli? An Empirical Study into the Absence of Consent to Third-Party Tracking