- From: Nataliia Bielova <nataliia.bielova@inria.fr>
- Date: Tue, 13 Jun 2017 17:09:07 +0200
- To: public-tracking@w3.org
- Message-Id: <762D59E8-AFCB-4D78-BD21-E9810189FC52@inria.fr>
Objection to Option B By not having an “other-party” property, the publisher doesn’t have an easy way to communicate the list of embedded third parties to the user agent, therefore reducing its possibility to provide privacy-friendly implementation of the publisher’s server. I agree with EFF and CDD that “the ‘other parties’ field offers publishers a compliance framework for the consent requirements under EU law whilst reducing the opportunities for malware and the leakage of user data.” Moreover, even though GDPR and ePR are EU laws (that are nevertheless applied to all the countries that provide services to persons who are physically located in the EU), I would like to remind that the main motivations for the chapter’s extension was to “help web-sites to achieve privacy compliance in the EU “. Best, Nataliia --- Nataliia Bielova Researcher at Inria http://www-sop.inria.fr/members/Nataliia.Bielova/ <http://www-sop.inria.fr/members/Nataliia.Bielova/> https://extensions.inrialpes.fr/ <https://extensions.inrialpes.fr/>
Received on Tuesday, 13 June 2017 15:10:35 UTC