- From: Jonathan Mayer <jmayer@stanford.edu>
- Date: Thu, 27 Jun 2013 23:17:19 -0400
- To: David Singer <singer@apple.com>
- Cc: "public-tracking@w3.org Group WG" <public-tracking@w3.org>
Received on Friday, 28 June 2013 03:17:39 UTC
David, This definition is trying to get at two issues. First, privacy risks flow from the very collection of certain information (e.g. linkable non-protocol information). Second, the standard should prohibit certain collection practices. Much like the June Draft usage of the term "tracking," the intent here is to reflect the aims and sweep of the compliance document. Other sections of text provide detail, including that protocol information can be used. Best, Jonathan On Thursday, June 27, 2013 at 6:49 PM, David Singer wrote: > Can you tell us what you mean by 'collect' (that distinguishes it from 'retain', and that allows use of in-transaction data for satisfying the transaction)? > > > On Jun 26, 2013, at 5:57 , Jonathan Mayer <jmayer@stanford.edu (mailto:jmayer@stanford.edu)> wrote: > > > I would propose that we not define "tracking" within the TCS document. > > > > In the alternative, if the group elects to proceed with a definition, I would propose this small change: > > > Tracking is the collection, retention, or use of data records that are, or can be, associated with a specific user, user agent, or device. > > > > > > This definition encompasses collection of information, unlike the June Draft text. > > David Singer > Multimedia and Software Standards, Apple Inc. > >
Received on Friday, 28 June 2013 03:17:39 UTC