ISSUE-143: Activating a Tracking Preference must require explicit, informed consent from a user

Reciprocal Consent

Activating a Tracking Preference must require explicit, informed consent from a user

State:
CLOSED
Product:
Tracking Preference Expression (DNT)
Raised by:
Shane Wiley
Opened on:
2012-04-25
Description:
As we've developed draft text for obtaining explicit, informed consent from a user for out-of-bound user granted exceptions, it's equally important that activation of a tracking preference be coupled with the same explicit, informed consent.

For example, activating a tracking preference should require explicit language identifying this as an option and informing the user of the scope of the option's application.

For example, an security software package should NOT activate DNT by default (with an explanation buried deeply in their TOS or help center) and the user must explicitly select this option upon install/use of the product.

Using this same test, I don't believe there is "explicit, informed" consent from users activating DNT within IE9's Traffic Protection Lists and this should be called out when a TPL is activated.

To further support this view, much like response headers allow a party to respond to articulate when they've received out-of-band consent, I request that a similar element be added to request headers. In this model, a new data element would need to be added (perhaps in the extension) for a party to articulate that they have captured a user's consent to activate DNT and identify themselves in this manner as the "capturee" of the consent. It'll be vital that web browser vendors lock down the ability for a 3rd party tool or extension to mimic their signature in this process and only allow 3rd party tools to activate DNT on a user's behalf by articulating who they are.

This way, if industry feels a party is inappropriately setting a tracking preference, we can take steps to discover which headers are coming from this party and take steps to request the party move to an "explicit, informed" consent model prior to honoring the DNT headers coming from the implementation of their tool.
Related Actions Items:
No related actions
Related emails:
  1. Re: Status of ISSUE-143 (from jbrookman@cdt.org on 2014-02-25)
  2. RE: Status of ISSUE-143 (from wileys@yahoo-inc.com on 2014-02-21)
  3. Status of ISSUE-143 (from jbrookman@cdt.org on 2014-02-19)
  4. Re: Mapping the "framework" to ISSUEs (from john@consumerwatchdog.org on 2013-05-07)
  5. Mapping the "framework" to ISSUEs (from jmayer@stanford.edu on 2013-05-07)
  6. Re: ISSUE-161: Discussion of semantics and alternatives to "!" (from mts-std@schunter.org on 2013-04-16)
  7. Re: ISSUE-161: Discussion of semantics and alternatives to "!" (from singer@apple.com on 2013-04-16)
  8. Re: ISSUE-161: Discussion of semantics and alternatives to "!" (from jmayer@stanford.edu on 2013-04-15)
  9. Re: ISSUE-161: Discussion of semantics and alternatives to "!" (from mts-std@schunter.org on 2013-04-15)
  10. RE: Batch closing of TPE-related issues (response by April 16) (from michael.oneill@baycloud.com on 2013-04-15)
  11. Re: Batch closing of TPE-related issues (response by April 16) (from mts-std@schunter.org on 2013-04-15)
  12. ISSUE-161: Discussion of semantics and alternatives to "!" (was: Batch closing) (from mts-std@schunter.org on 2013-04-15)
  13. Re: Batch closing of TPE-related issues (response by April 16) (from john@consumerwatchdog.org on 2013-04-12)
  14. Re: Batch closing of TPE-related issues (response by April 16) (from jmayer@stanford.edu on 2013-04-12)
  15. Re: Batch closing of TPE-related issues (response by April 16) (from david@appnexus.com on 2013-04-12)
  16. RE: Batch closing of TPE-related issues (response by April 16) (from michael.oneill@baycloud.com on 2013-04-12)
  17. Batch closing of TPE-related issues (response by April 16) (from mts-std@schunter.org on 2013-04-12)
  18. Re: user interface/user education (from npdoty@w3.org on 2013-04-09)
  19. Re: Proposed Resolution to ISSUE-151 : User Agent Requirement: Be able to handle an exception request (from rob@blaeu.com on 2013-03-19)
  20. RE: Proposed Resolution to ISSUE-151 : User Agent Requirement: Be able to handle an exception request (from wileys@yahoo-inc.com on 2013-03-19)
  21. Re: Proposed Resolution to ISSUE-151 : User Agent Requirement: Be able to handle an exception request (from singer@apple.com on 2013-03-18)
  22. RE: Approach to ISSUE-167: Multiple site exception (from wileys@yahoo-inc.com on 2013-03-18)
  23. RE: Proposed Resolution to ISSUE-151 : User Agent Requirement: Be able to handle an exception request (from wileys@yahoo-inc.com on 2013-03-18)
  24. Re: TPWG agenda for Wednesday, January 16 (from jmayer@stanford.edu on 2013-01-30)
  25. Re: TPWG agenda for Wednesday, January 16 (from singer@apple.com on 2013-01-29)
  26. Re: ISSUE Cleanup: Please reconfirm your support of Raised ISSUES (by Jan 30) (from jmayer@stanford.edu on 2013-01-24)
  27. Re: Batch closing of issues (ISSUE-144, ISSUE-187, ISSUE-190, ISSUE-173, ISSUE-138) [pls Respond by Jan 30] (from jmayer@stanford.edu on 2013-01-24)
  28. Re: ISSUE Cleanup: Please reconfirm your support of Raised ISSUES (by Jan 30) (from david@networkadvertising.org on 2013-01-21)
  29. ISSUE Cleanup: Please reconfirm your support of Raised ISSUES (by Jan 30) (from mts-std@schunter.org on 2013-01-21)
  30. RE: Sitecom adds Do Not Track to its routers (from wileys@yahoo-inc.com on 2012-12-03)
  31. Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from chris.mejia@iab.net on 2012-11-21)
  32. Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from CPedigo@online-publishers.org on 2012-11-17)
  33. Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from singer@apple.com on 2012-11-16)
  34. RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from CPedigo@online-publishers.org on 2012-11-16)
  35. Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from singer@apple.com on 2012-11-16)
  36. RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from CPedigo@online-publishers.org on 2012-11-16)
  37. Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from singer@apple.com on 2012-11-16)
  38. Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from achapell@chapellassociates.com on 2012-11-16)
  39. Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from singer@apple.com on 2012-11-16)
  40. Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from Brooks.Dobbs@kbmg.com on 2012-11-16)
  41. Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from singer@apple.com on 2012-11-15)
  42. Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from ifette@google.com on 2012-11-15)
  43. Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from singer@apple.com on 2012-11-15)
  44. Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from justin@cdt.org on 2012-11-14)
  45. RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from wileys@yahoo-inc.com on 2012-11-14)
  46. Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from justin@cdt.org on 2012-11-14)
  47. RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from Vincent.Toubiana@alcatel-lucent.com on 2012-11-14)
  48. Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from ifette@google.com on 2012-11-13)
  49. RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from wileys@yahoo-inc.com on 2012-11-13)
  50. Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from justin@cdt.org on 2012-11-13)
  51. Re: Modifying a DNT Header (ISSUE-153, ACTION-285) (from david@networkadvertising.org on 2012-11-09)
  52. Re: Modifying a DNT Header (ISSUE-153, ACTION-285) (from singer@apple.com on 2012-11-09)
  53. Re: Modifying a DNT Header (ISSUE-153, ACTION-285) (from ifette@google.com on 2012-11-08)
  54. Re: Modifying a DNT Header (ISSUE-153, ACTION-285) (from david@networkadvertising.org on 2012-11-08)
  55. Re: Modifying a DNT Header (ISSUE-153, ACTION-285) (from tlr@w3.org on 2012-11-08)
  56. Re: Modifying a DNT Header (ISSUE-153, ACTION-285) (from James.Grimmelmann@nyls.edu on 2012-11-08)
  57. Re: Modifying a DNT Header (ISSUE-153, ACTION-285) (from david@networkadvertising.org on 2012-11-08)
  58. RE: Modifying a DNT Header (ISSUE-153, ACTION-285) (from wileys@yahoo-inc.com on 2012-11-08)
  59. RE: Modifying a DNT Header (ISSUE-153, ACTION-285) (from wileys@yahoo-inc.com on 2012-11-08)
  60. Re: Modifying a DNT Header (ISSUE-153, ACTION-285) (from david@networkadvertising.org on 2012-11-08)
  61. Re: Modifying a DNT Header (ISSUE-153, ACTION-285) (from tlr@w3.org on 2012-11-08)
  62. RE: Modifying a DNT Header (ISSUE-153, ACTION-285) (from wileys@yahoo-inc.com on 2012-11-08)
  63. Re: Modifying a DNT Header (ISSUE-153, ACTION-285) (from joe@cdt.org on 2012-11-08)
  64. RE: Modifying a DNT Header (ISSUE-153, ACTION-285) (from wileys@yahoo-inc.com on 2012-11-07)
  65. Re: Modifying a DNT Header (ISSUE-153, ACTION-285) (from walter.van.holst@xs4all.nl on 2012-11-07)
  66. RE: Modifying a DNT Header (ISSUE-153, ACTION-285) (from wileys@yahoo-inc.com on 2012-11-07)
  67. Re: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from rigo@w3.org on 2012-11-02)
  68. RE: ACTION-212: Draft text on how user agents must obtain consent to turn on a DNT signal (from wileys@yahoo-inc.com on 2012-11-01)
  69. Re: ISSUE-4 and clarity regarding browser defaults (from tisrael@cippic.ca on 2012-07-27)
  70. Re: ISSUE-4 and clarity regarding browser defaults (from James.Grimmelmann@nyls.edu on 2012-07-27)
  71. RE: ISSUE-4 and clarity regarding browser defaults (from wileys@yahoo-inc.com on 2012-07-27)
  72. Re: ISSUE-4 and clarity regarding browser defaults (from david@networkadvertising.org on 2012-07-27)
  73. Re: ISSUE-4 and clarity regarding browser defaults (from david@networkadvertising.org on 2012-07-27)
  74. Re: ISSUE-4 and clarity regarding browser defaults (from tisrael@cippic.ca on 2012-07-27)
  75. RE: ISSUE-4 and clarity regarding browser defaults (from wileys@yahoo-inc.com on 2012-07-27)
  76. Re: ISSUE-4 and clarity regarding browser defaults (from James.Grimmelmann@nyls.edu on 2012-07-27)
  77. RE: ISSUE-4 and clarity regarding browser defaults (from wileys@yahoo-inc.com on 2012-07-27)
  78. Re: ISSUE-4 and clarity regarding browser defaults (from tisrael@cippic.ca on 2012-07-27)
  79. RE: ISSUE-4 and clarity regarding browser defaults (from wileys@yahoo-inc.com on 2012-07-27)
  80. Re: ISSUE-4 and clarity regarding browser defaults (from singer@apple.com on 2012-07-27)
  81. RE: ISSUE-4 and clarity regarding browser defaults (from wileys@yahoo-inc.com on 2012-07-27)
  82. Re: ISSUE-4 and clarity regarding browser defaults (from Brooks.Dobbs@kbmg.com on 2012-07-27)
  83. Re: ISSUE-4 and clarity regarding browser defaults (from tisrael@cippic.ca on 2012-07-27)
  84. Re: ISSUE-4 and clarity regarding browser defaults (from James.Grimmelmann@nyls.edu on 2012-07-27)
  85. RE: ISSUE-4 and clarity regarding browser defaults (from wileys@yahoo-inc.com on 2012-07-26)
  86. Re: ISSUE-4 and clarity regarding browser defaults (from singer@apple.com on 2012-07-26)
  87. Re: ISSUE-4 and clarity regarding browser defaults (from tisrael@cippic.ca on 2012-07-26)
  88. Re: ISSUE-4 and clarity regarding browser defaults (from john@consumerwatchdog.org on 2012-07-26)
  89. RE: ISSUE-4 and clarity regarding browser defaults (from mike@iab.net on 2012-07-26)
  90. Re: ISSUE-4 and clarity regarding browser defaults (from jeff@democraticmedia.org on 2012-07-26)
  91. Re: ISSUE-4 and clarity regarding browser defaults (from tisrael@cippic.ca on 2012-07-26)
  92. RE: ISSUE-4 and clarity regarding browser defaults (from mike@iab.net on 2012-07-26)
  93. Re: Support for ISSUE 143 - EDUCATED Consumer Choice Should Be REQUIRED (from jmayer@stanford.edu on 2012-07-08)
  94. Re: Support for ISSUE 143 - EDUCATED Consumer Choice Should Be REQUIRED (from tisrael@cippic.ca on 2012-07-07)
  95. Re: Support for ISSUE 143 - EDUCATED Consumer Choice Should Be REQUIRED (from mts-std@schunter.org on 2012-07-07)
  96. RE: Today's call: summary on user agent compliance (from wileys@yahoo-inc.com on 2012-06-13)
  97. RE: Considering browser vendor as a third party (from wileys@yahoo-inc.com on 2012-06-10)
  98. Re: Considering browser vendor as a third party (from jmayer@stanford.edu on 2012-06-10)
  99. RE: Considering browser vendor as a third party (from wileys@yahoo-inc.com on 2012-06-10)
  100. Re: Considering browser vendor as a third party (from jmayer@stanford.edu on 2012-06-10)
  101. RE: Considering browser vendor as a third party (from wileys@yahoo-inc.com on 2012-06-10)
  102. RE: ISSUE-4 and clarity regarding browser defaults (from wileys@yahoo-inc.com on 2012-06-03)
  103. Re: ISSUE-4 and clarity regarding browser defaults (from jeff@democraticmedia.org on 2012-06-03)
  104. RE: ISSUE-4 and clarity regarding browser defaults (from wileys@yahoo-inc.com on 2012-06-03)
  105. Re: ISSUE-4 and clarity regarding browser defaults (from vp@iabeurope.eu on 2012-06-03)
  106. Re: ISSUE-4 and clarity regarding browser defaults (from jeff@democraticmedia.org on 2012-06-03)
  107. Re: ISSUE-4 and clarity regarding browser defaults (from fielding@gbiv.com on 2012-06-02)
  108. Re: ISSUE-4 and clarity regarding browser defaults (from jbrookman@cdt.org on 2012-06-02)
  109. RE: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance] (from kevsmith@adobe.com on 2012-06-01)
  110. Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance] (from manu16m@gmail.com on 2012-05-31)
  111. Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance] (from ifette@google.com on 2012-05-31)
  112. Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance] (from heatherwest@google.com on 2012-05-31)
  113. Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance] (from aleecia@aleecia.com on 2012-05-31)
  114. Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance] (from gelman@blurryedge.com on 2012-05-31)
  115. Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance] (from mike@iab.net on 2012-05-31)
  116. Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance] (from gelman@blurryedge.com on 2012-05-30)
  117. Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance] (from ifette@google.com on 2012-05-30)
  118. RE: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance] (from jbrookman@cdt.org on 2012-05-30)
  119. Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance] (from gelman@blurryedge.com on 2012-05-30)
  120. Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance] (from ifette@google.com on 2012-05-30)
  121. Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance] (from gelman@blurryedge.com on 2012-05-30)
  122. RE: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance] (from wileys@yahoo-inc.com on 2012-05-30)
  123. Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance] (from justin@cdt.org on 2012-05-30)
  124. Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance] (from chris.mejia@iab.net on 2012-05-30)
  125. tracking-ISSUE-149: Compliance section for user agents [Tracking Definitions and Compliance] (from sysbot+tracker@w3.org on 2012-05-30)
  126. ACTION-203 : Text for transitive model (from rigo@w3.org on 2012-05-25)
  127. Re: tracking-ISSUE-143 (Reciprocal Consent): Activating a Tracking Preference must require explicit, informed consent from a user [Tracking Preference Expression (DNT)] (from rob@blaeu.com on 2012-05-02)
  128. tracking-ISSUE-143 (Reciprocal Consent): Activating a Tracking Preference must require explicit, informed consent from a user [Tracking Preference Expression (DNT)] (from sysbot+tracker@w3.org on 2012-04-25)

Related notes:

Closed (unless I receive further input by April 16):
- We will continue this discussion as part of ISSUE-194.

Matthias Schunter, 15 Apr 2013, 10:41:01

Display change log ATOM feed


Matthias Schunter <matthias.schunter@intel.com>, Carl Cargill <cargill@adobe.com>, Chairs, 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 $