- From: Don Marti via GitHub <sysbot+gh@w3.org>
- Date: Fri, 11 Mar 2022 16:46:25 +0000
- To: public-patcg@w3.org
@kirangopinath71 This is a good example of whether or not to choose to ask for consent at all. When designing a system, we have to take into account the user research literature and what we can be reasonably expected to understand, as human web developers, about human web users. The number of situations in which any human being would want to share with anyone else that they were browsing a web page about a pregnancy test kit is vanishingly low, so asking for consent is going to produce far more errors than true consent. Asking for consent would not only waste the time of everyone who answered the consent prompt correctly, but also result in inappropriate processing of the information of everyone who failed to get it right. This specific case is a good example of where consent is not a good fit. (Users who really want to share this info can do it on their own) We have to do a better job of looking at the user research to determine not just when to ask for consent (and how to do it, and when to skip it), but how to apply a "consent yes" setting to real-world data processing decisions. [About 36% of users are more likely to engage with personalized ads](https://yougov.co.uk/topics/consumer/articles-reports/2018/03/26/targeting-personalised-ads-right-audience) but that probably doesn't mean that they want all their pharmacy shopping habits shared. -- GitHub Notification of comment by dmarti Please view or discuss this issue at https://github.com/patcg/proposals/issues/5#issuecomment-1065292646 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 11 March 2022 16:46:26 UTC