- From: Shane Wiley <wileys@yahoo-inc.com>
- Date: Thu, 11 Jul 2013 06:49:38 +0000
- To: Rigo Wenning <rigo@w3.org>
- CC: "public-tracking@w3.org" <public-tracking@w3.org>, Rob van Eijk <rob@blaeu.com>
Rigo, Two different conversations that are being blended here (similar response just sent to Ed Felton) so I want to be clear that your two questions are specifically targeted to each independently: Q: You're building a uniquely identified profile (event-linkable), but the DAA definition is such that the profiling is not tracking? A: No - Aggregate Scoring is NOT event linkable. A unique ID and an aggregated score are all that remain from the actual event that occurred. For example, cookie ID 1234 has an interest score of 4 for off-road vehicles. Q: And this because the UID sent by the user agent was replaced by an internal UID, thus the collection is not "linked to a _specific_ user, computer, or device. Because the new UID makes that the user is not "specific" anymore? A: No - now we are discussing de-identification. In the 'de-identified but event linkable' process the unique ID for a "specific" user/device is removed (replaced with something that is not directly linked to the specific/actual user/device) but still allows the events to be linked to one another. Again, the ONLY utility allowed for this data is analytics alone. - Shane -----Original Message----- From: Rigo Wenning [mailto:rigo@w3.org] Sent: Wednesday, July 10, 2013 7:17 PM To: Shane Wiley Cc: public-tracking@w3.org; Rob van Eijk Subject: Re: tracking-ISSUE-215: data hygiene approach / tracking of URL data and browsing activity [Compliance June] On Wednesday 10 July 2013 17:52:57 Shane Wiley wrote: > Incorrect - no permitted use is needed as aggregate scoring is "not > tracking" in that there is no retention of a user's cross-site > browsing history in this case. DNT compliance is removing the linkage > between browsing activity and a user/device. Do I understand you correctly: You're building a uniquely identified profile (event-linkable), but the DAA definition is such that the profiling is not tracking? And this because the UID sent by the user agent was replaced by an internal UID, thus the collection is not "linked to a _specific_ user, computer, or device. Because the new UID makes that the user is not "specific" anymore? Would this change if we would say: Tracking is the collection and retention, or use of activity across non- affiliated websites linked to a specific user, computer, device, or profile? --Rigo
Received on Thursday, 11 July 2013 06:50:56 UTC