How Developers (Don't) Think about Gender Privacy
summary
Study analyzes 900 posts with ~10,000 comments from Reddit plus code snippets and conducts 15 interviews (two-thirds recruited via Upwork, others via Twitter). Finds most implementations use a binary male/female only field and that gender is usually collected for audience demographics/advertising. Developers often don’t know privacy risks; some prefer free-text or tag-based identity, and platforms need clear purposes, standards for change over time, opt-out/unknown options, and elimination of unnecessary collection.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:22Overview
- 0:51Gender and Computing
- 2:21An illustrative example
- 3:26How do developers approach gender?
- 4:50Reddit Data Collection
- 5:57Reddit: the good
- 6:20Reddit: and the bad
- 7:07The Interview Study
- 7:46Interview Results
- 9:17Takeaways for Privacy Engineers
related talks
08mPrivacy Is the Price: Player Views and Technical Evaluation of Data Practices in Online Games
10mEvaluating Privacy Perceptions, Experience, and Behavior of Software Development Teams
53mCoding Like a Girl
01h 13mFeminist perspectives on privacy and data protection.
27mGender Recognition or Gender Reductionism? The Social Implications of Automatic Gender ...
45mPrivacy is not Binary: A discussion of data systems, ethics, and human rights
05mDeciding on Personalized Ads: Nudging Developers About User Privacy
33mDesigning and Building With Privacy In Mind