Re: [proposals] Why would notice and consent not be adequate? (Notice and consent debate) (#5)

I wonder if the entire debate around consent might be a red-herring. As this debate suggests, the current consent model is broken. Somewhere between the 1st and 100th pop-up, [most consumers](https://www2.deloitte.com/uk/en/pages/technology-media-and-telecommunications/articles/digital-consumer-trends-data-privacy.html) seem to just slip into a routine of clicking to close, and moving on. And I am not sure any design, language, or interpretation makes much difference. [The regulators are coming after](https://www.cpomagazine.com/data-protection/iab-europe-gdpr-violations-for-consent-management-may-force-major-changes-to-real-time-bidding-systems/) the entire consent model, as you well know.

It seems that for the existing ad tech stack to work, you might need the broadest possible consent. How do you get that from consumers when their experience is so poor? 

What if, rather than seeking to improve the consent process, you focus more on control? Consumers probably don't mind sharing information, especially with trusted brands, but [it is the lack of control that niggles more](https://www.techrepublic.com/article/data-privacy-is-a-growing-concern-for-more-consumers/). I appreciate the relationship between consent and control but surely the latter matters more? And if you get control right should the consent hurdle fall? If you build the right architecture around control then will it not be easy for consumers to reverse any and all consent? I suspect what worries most consumers is not the act of consent but the implications of the unfettered spread, use and abuse of their personal data. Build the right protocols around how their data is used and shared, provide them with transparency and control, and you might find them far more willing to consent.


-- 
GitHub Notification of comment by nlongcn
Please view or discuss this issue at https://github.com/patcg/proposals/issues/5#issuecomment-1048556025 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 23 February 2022 08:44:47 UTC