- From: Stefan Haase via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Feb 2022 10:20:51 +0000
- To: public-patcg@w3.org
What role do regulatory requirements such as GDPR / ePrivacy in Europe play in the solution discovery & design from your perspective? That is one aspect I rarely read about in these proposals, yet I believe that this should be an integral part of the problem definition and solution design. Looking at IPA specifically for example, I believe that data protection authorities might categorize the match key as personal data (https://gdpr.eu/eu-gdpr-personal-data/) and storing it on the users device would therefore require user consent. Would you just accept that as a given, or could solutions be more tailored towards regulatory requirements (in a sense: try to discover solutions do not require user consent to not end up modeling 30% of conversions that are lost due to tracking opt-outs). -- GitHub Notification of comment by sthaase Please view or discuss this issue at https://github.com/patcg/proposals/issues/2#issuecomment-1041332373 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 February 2022 10:20:53 UTC