W3C home > Mailing lists > Public > public-tracking@w3.org > November 2012

tracking-ISSUE-189 (EUConsent): Explicit informed consent mechanism needed [Global Considerations]

From: Tracking Protection Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Thu, 22 Nov 2012 01:48:38 +0000
Message-Id: <E1TbLuA-0004aD-Fw@tibor.w3.org>
To: public-tracking@w3.org
tracking-ISSUE-189 (EUConsent): Explicit informed consent mechanism needed [Global Considerations]


Raised by: Mike O'Neill
On product: Global Considerations

There is a fundamental inconsistency between the current understanding of the DNT signal and a consent signal that would meet the European legal requirement for explicit informed consent (EIC). EIC must have been given before action is taken to identify users so if DNT is unset European servers would either need another mechanism or assume consent was absent, which does not correspond to the current TPC. It is also unlikely that the interpretation of DNT by receiving servers as specified in the TPC will be the same as the interpretation required for receiving Data Controllers & Processors for presence or absence of an EIC signal.
The Working Group is the natural place to design an EIC mechanism as all the expertise and focus on the issue is already here.
It would be very useful to have a technical mechanism for signalling EIC. The advantage the DNT mechanism had in this context was that the header is also sent to third-parties (in the HTTP sense), and the UGE API gives first-party sites the ability to control it for third-parties. It should also be possible to also do this for an EIC signal.
The GC group should define what an EIC should mean (e.g.  “action can be taken to identify this user for legal purposes”) and suggest a technical way it could be set and signalled. We should then ask the Working Group to ensure that normative text to describe the mechanism is put into the TPE alongside the DNT UGE mechanism.

Received on Thursday, 22 November 2012 01:48:39 UTC

This archive was generated by hypermail 2.3.1 : Friday, 3 November 2017 21:45:00 UTC