ISSUE-22: Still have "operational use" of data (auditing of where ads are shown, impression tracking, etc.)

Still have "operational use" of data (auditing of where ads are shown, impression tracking, etc.)

State:
PENDING REVIEW
Product:
Compliance Next
Raised by:
Opened on:
2011-09-21
Description:
Related Actions Items:
No related actions
Related emails:
  1. Re: Issue-22, possible other direction (from wileys@yahoo-inc.com on 2017-05-19)
  2. RE: Issue-22, possible other direction (from rob@blaeu.com on 2017-05-19)
  3. RE: Issue-22, possible other direction (from rob@blaeu.com on 2017-05-19)
  4. Re: Issue-22, possible other direction (from wileys@yahoo-inc.com on 2017-05-19)
  5. RE: Issue-22, possible other direction (from rob@blaeu.com on 2017-05-19)
  6. Re: Issue-22, possible other direction (from wileys@yahoo-inc.com on 2017-05-19)
  7. Re: Issue-22, possible other direction (from wileys@yahoo-inc.com on 2017-05-19)
  8. RE: Issue-22, possible other direction (from rob@blaeu.com on 2017-05-19)
  9. Re: Issue-22, possible other direction (from Jason@digitalcontentnext.org on 2017-05-19)
  10. Re: Issue-22, possible other direction (from singer@apple.com on 2017-05-19)
  11. Re: Issue-22, possible other direction (from wileys@yahoo-inc.com on 2017-05-19)
  12. RE: Issue-22, possible other direction (from rob@blaeu.com on 2017-05-19)
  13. Re: Issue-22, possible other direction (from wileys@yahoo-inc.com on 2017-05-19)
  14. RE: Issue-22, possible other direction (from rob@blaeu.com on 2017-05-19)
  15. Re: Issue-22, possible other direction (from wileys@yahoo-inc.com on 2017-05-19)
  16. RE: Issue-22, possible other direction (from michael.oneill@baycloud.com on 2017-05-19)
  17. Re: Issue-22, possible other direction (from singer@apple.com on 2017-05-19)
  18. Re: Issue-22, possible other direction (from singer@mac.com on 2017-05-19)
  19. RE: Issue-22, possible other direction (from rob@blaeu.com on 2017-05-18)
  20. Re: Issue-22, possible other direction (from wileys@yahoo-inc.com on 2017-05-18)
  21. Re: Issue-22, possible other direction (from alanna@iabtechlab.com on 2017-05-18)
  22. RE: Issue-22, possible other direction (from rob@blaeu.com on 2017-05-18)
  23. Re: Issue-22, possible other direction (from mts-std@schunter.org on 2017-05-18)
  24. Re: Issue-22, possible other direction (from wileys@yahoo-inc.com on 2017-05-15)
  25. FW: Issue-22, possible other direction (from rob@blaeu.com on 2017-05-15)
  26. Batch closing of TCS issues (from jbrookman@cdt.org on 2014-09-10)
  27. Agenda for May 22 call (from peter@peterswire.net on 2013-05-21)
  28. issue and action cleanup proposals (from npdoty@w3.org on 2013-05-15)
  29. Re: Mapping the "framework" to ISSUEs (from john@consumerwatchdog.org on 2013-05-07)
  30. Mapping the "framework" to ISSUEs (from jmayer@stanford.edu on 2013-05-07)
  31. Updated response to Aleecia's Template, Issue-10, Issue-17, Issue-19, Issue-22, Issue-24, Issue-25, Issue-31, Issue-49, Issue-73 (from john@consumerwatchdog.org on 2012-04-07)
  32. deeper look at agenda items (from aleecia@aleecia.com on 2012-04-07)
  33. Revised template for parties and business uses (from aleecia@aleecia.com on 2012-03-28)
  34. template for parties and business uses (from aleecia@aleecia.com on 2012-03-28)
  35. Mar-28 call (was Re: Agenda for 2012-Mar-27 call) (from aleecia@aleecia.com on 2012-03-27)
  36. Agenda for 2012-Mar-27 call (from aleecia@aleecia.com on 2012-03-27)
  37. Re: ACTION-49: Propose what the operational carve-outs for 3.6.1.2.1 (e.g. debugging by 3rd party) are (from jeff@democraticmedia.org on 2012-02-02)
  38. Re: ACTION-49: Propose what the operational carve-outs for 3.6.1.2.1 (e.g. debugging by 3rd party) are (from blsaws@gmail.com on 2012-02-01)
  39. RE: ACTION-49: Propose what the operational carve-outs for 3.6.1.2.1 (e.g. debugging by 3rd party) are (from wileys@yahoo-inc.com on 2012-02-01)
  40. RE: ACTION-49: Propose what the operational carve-outs for 3.6.1.2.1 (e.g. debugging by 3rd party) are (from wileys@yahoo-inc.com on 2012-02-01)
  41. Re: ACTION-49: Propose what the operational carve-outs for 3.6.1.2.1 (e.g. debugging by 3rd party) are (from gelman@blurryedge.com on 2012-02-01)
  42. RE: ACTION-49: Propose what the operational carve-outs for 3.6.1.2.1 (e.g. debugging by 3rd party) are (from wileys@yahoo-inc.com on 2012-02-01)
  43. RE: ACTION-49: Propose what the operational carve-outs for 3.6.1.2.1 (e.g. debugging by 3rd party) are (from wileys@yahoo-inc.com on 2012-02-01)
  44. RE: ACTION-49: Propose what the operational carve-outs for 3.6.1.2.1 (e.g. debugging by 3rd party) are (from wileys@yahoo-inc.com on 2012-02-01)
  45. Re: ACTION-49: Propose what the operational carve-outs for 3.6.1.2.1 (e.g. debugging by 3rd party) are (from gelman@blurryedge.com on 2012-02-01)
  46. Re: ACTION-49: Propose what the operational carve-outs for 3.6.1.2.1 (e.g. debugging by 3rd party) are (from jeff@democraticmedia.org on 2012-02-01)
  47. Re: ACTION-49: Propose what the operational carve-outs for 3.6.1.2.1 (e.g. debugging by 3rd party) are (from john@consumerwatchdog.org on 2012-02-01)
  48. Re: ACTION-49: Propose what the operational carve-outs for 3.6.1.2.1 (e.g. debugging by 3rd party) are (from john@consumerwatchdog.org on 2012-02-01)
  49. Re: ACTION-49: Propose what the operational carve-outs for 3.6.1.2.1 (e.g. debugging by 3rd party) are (from singer@apple.com on 2012-02-01)
  50. Re: ACTION-49: Propose what the operational carve-outs for 3.6.1.2.1 (e.g. debugging by 3rd party) are (from dwainberg@appnexus.com on 2012-01-31)
  51. RE: ACTION-49: Propose what the operational carve-outs for 3.6.1.2.1 (e.g. debugging by 3rd party) are (from wileys@yahoo-inc.com on 2012-01-30)
  52. ACTION-49: Propose what the operational carve-outs for 3.6.1.2.1 (e.g. debugging by 3rd party) are (from wileys@yahoo-inc.com on 2012-01-30)
  53. Agenda for 2012-1-10 call (from aleecia@aleecia.com on 2012-01-10)
  54. Draft: Issue 31, Minimization - to what extent will minimization be required for use of a particular exemption? (conditional exemptions) (from Sue.Glueck@microsoft.com on 2011-12-22)
  55. Issue-22, Still have 'operational use' of data (from wileys@yahoo-inc.com on 2011-12-21)
  56. Re: Compliance issues (from john@consumerwatchdog.org on 2011-12-07)
  57. Compliance issues (from aleecia@aleecia.com on 2011-12-06)
  58. Next steps on compliance issues (from aleecia@aleecia.com on 2011-12-03)
  59. More details for tomorrow AM (from mts@zurich.ibm.com on 2011-09-22)
  60. ISSUE-22: Still have 'operational use' of data (auditing of where ads are shown, impression tracking, etc.) (from sysbot+tracker@w3.org on 2011-09-21)

Related notes:

[npdoty]: should cover denial of service attacks, click fraud

21 Sep 2011, 20:39:32

During issue cleanup, noted this as Pending Review Stable, apparently covered by existing text on permitted uses.

Nick Doty, 29 May 2013, 02:27:29

Display change log ATOM feed

Chair, 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: 22.html,v 1.1 2019/02/01 09:32:36 vivien Exp $