ACTION-157: Update logged-in consent proposal by April 24

Update logged-in consent proposal by April 24

State:
pending review
Person:
Shane Wiley
Due on:
April 24, 2012
Created on:
April 10, 2012
Associated Product:
Compliance Next
Related emails:
  1. action-195: Clarify action items needed for issue-65 (from aleecia@aleecia.com on 2012-05-30)
  2. Re: Action-157: Update logged-in consent proposal (from fielding@gbiv.com on 2012-05-09)
  3. Re: Action-157: Update logged-in consent proposal (from achapell@chapellassociates.com on 2012-05-09)
  4. Re: Action-157: Update logged-in consent proposal (from justin@cdt.org on 2012-05-09)
  5. Re: Action-157: Update logged-in consent proposal (from fielding@gbiv.com on 2012-05-08)
  6. RE: Action-157: Update logged-in consent proposal (from jccannon@microsoft.com on 2012-05-08)
  7. RE: Action-157: Update logged-in consent proposal (from wileys@yahoo-inc.com on 2012-05-07)
  8. Re: Action-157: Update logged-in consent proposal (from jbrookman@cdt.org on 2012-05-07)
  9. Re: Action-157: Update logged-in consent proposal (from fielding@gbiv.com on 2012-05-07)
  10. Re: Action-157: Update logged-in consent proposal (from tien@eff.org on 2012-05-07)
  11. RE: Action-157: Update logged-in consent proposal (from jbrookman@cdt.org on 2012-05-07)
  12. RE: Action-157: Update logged-in consent proposal (from wileys@yahoo-inc.com on 2012-05-07)
  13. Re: Action-157: Update logged-in consent proposal (from jmayer@stanford.edu on 2012-05-07)
  14. RE: Action-157: Update logged-in consent proposal (from wileys@yahoo-inc.com on 2012-05-07)
  15. Re: Action-157: Update logged-in consent proposal (from jmayer@stanford.edu on 2012-05-07)
  16. Re: Action-157: Update logged-in consent proposal (from justin@cdt.org on 2012-05-07)
  17. Re: Action-157: Update logged-in consent proposal (from singer@apple.com on 2012-05-07)
  18. RE: Action-157: Update logged-in consent proposal (from jccannon@microsoft.com on 2012-05-06)
  19. Re: Action-157: Update logged-in consent proposal (from npdoty@w3.org on 2012-05-05)
  20. Re: Action-157: Update logged-in consent proposal (from derhoermi@gmx.net on 2012-05-02)
  21. RE: Action-157: Update logged-in consent proposal (from jccannon@microsoft.com on 2012-05-01)
  22. Re: Action-157: Update logged-in consent proposal (from derhoermi@gmx.net on 2012-05-01)
  23. Re: Action-157: Update logged-in consent proposal (from derhoermi@gmx.net on 2012-04-29)
  24. Re: Action-157: Update logged-in consent proposal (from wileys@yahoo-inc.com on 2012-04-28)
  25. Re: Action-157: Update logged-in consent proposal (from singer@apple.com on 2012-04-28)
  26. Re: Action-157: Update logged-in consent proposal (from singer@apple.com on 2012-04-28)
  27. RE: Action-157: Update logged-in consent proposal (from jccannon@microsoft.com on 2012-04-28)
  28. Re: Action-157: Update logged-in consent proposal (from derhoermi@gmx.net on 2012-04-27)
  29. RE: Action-157: Update logged-in consent proposal (from wileys@yahoo-inc.com on 2012-04-25)
  30. Re: Action-157: Update logged-in consent proposal (from singer@apple.com on 2012-04-25)
  31. Action-157: Update logged-in consent proposal (from wileys@yahoo-inc.com on 2012-04-24)

Related notes:

<Normative>

Sites MAY override a user's DNT preference if they have received explicit, informed consent to do so.

<Non-Normative>

In the absence of a Tracking Preference standard, many organizations have developed direct consent mechanisms for web-wide tracking. Interactions with users to obtain consent are often contextual. For example, If a service has an obvious cross-site tracking function that the user deliberately signs up for then this could be deemed to have achieved “explicit and informed” consent from a user without directly addressing its reaction to an external Tracking Preference (which wasn’t contemplated at the time the consent experience was designed). Even in these cases, organizations should consider providing Tracking Preference references in associated product or service materials such as a privacy policy, help center, or separate notice to users.

Companies claiming public compliance with the W3C Tracking Protection standard, should not seek to obtain explicit, informed consent from users in non-obvious ways such as placing these details in their Terms of Service or deeply placed within their Privacy Center if it will not be obvious to users that the nature of the service will lead them to ignore a user’s Tracking Preference based on the nature of the consent the user is granting.

Out-of-band consent will be further reinforced in user interactions through either the Header Response or Well-Known URI approaches to replying to user Tracking Preferences. This will provide a constant reminder of prior consent on each interaction and provide a resource (link) to allow the user to understand how this consent was achieved and hopefully options to alter that consent if the user chooses to do so.

Shane Wiley, 25 Apr 2012, 05:23:31

Display change log.


Matthias Schunter <matthias.schunter@intel.com>, Chair, Bert Bos <bert@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.325 2014-09-10 21:42:02 ted Exp $