- From: Lukasz Olejnik via GitHub <sysbot+gh@w3.org>
- Date: Thu, 10 Feb 2022 12:34:59 +0000
- To: public-patcg@w3.org
By topic do you mean Topics API? In this case there's no question that personal data may be processed, and consent is needed. What I meant is actual privacy-preserving tech where no personal data is processed. I agree with ePrivacy take, though. But it would be tough to decide who should ask about the consent, and where (on a website browsing? Why, if conversion//fetches happen later?) in context of Turtledove. So I'd like to highlight that this will be a big headache (and I know what I'm talking about here), because in terms of "consent" it is necessary to establish _WHO_ should get the consent. My initial question was more generic, not aimed at any specific proposal. -- GitHub Notification of comment by lknik Please view or discuss this issue at https://github.com/patcg/proposals/issues/5#issuecomment-1034870786 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 10 February 2022 12:35:01 UTC