<?xml version="1.0" encoding="UTF-8"?><rss version="2.0">	<channel>		<title>Time for a Data Diet? Deciding What Customer Information to Keep -- and What to Toss - Knowledge@Wha Comments</title>		<language>en-us</language>		<link>http://knowledge.wharton.upenn.edu/article.cfm?articleid=2186</link>		<description>Comments from Time for a Data Diet? Deciding What Customer Information to Keep -- and What to Toss - Knowledge@Wha</description><item>
<title>edward</title><link>http://knowledge.wharton.upenn.edu/article.cfm?articleid=2186#IDComment17660338</link><description>our privacy is not safe anymore </description><pubDate>Thu, 26 Mar 2009 23:59:04 +0000</pubDate><guid>http://knowledge.wharton.upenn.edu/article.cfm?articleid=2186#IDComment17660338</guid></item><item>
<title>Albert Gouyet</title><link>http://knowledge.wharton.upenn.edu/article.cfm?articleid=2186#IDComment17267683</link><description>I definitively agree with you.  You don&amp;#039;t analyze on personally identifiable information such as credit card or social security number so why keep it? I can think of some cases where data is augmented over time or keeping a full address allows very precise geo-targeting but most the time your behavioral analytics tools don&amp;#039;t need any PII.  I do take exception to your point about aggregating data as this will depend on the application.  At Quantivo, we help retailers and online sites find value in their purchase and web analytics data - understanding market baskets, loyalty, click patterns, etc.  The value is in the details of the individual transactions and would be lost with any aggregation.  But your first point about minimizing the data is still correct: throw away any attributes you don&amp;#039;t need or cannot act on.  Warm regards,  Albert Gouyet Quantivo Corporation &lt;a href=&quot;http://www.quantivo.com&quot; target=&quot;_blank&quot;&gt;www.quantivo.com&lt;/a&gt; </description><pubDate>Fri, 20 Mar 2009 02:12:47 +0000</pubDate><guid>http://knowledge.wharton.upenn.edu/article.cfm?articleid=2186#IDComment17267683</guid></item>	</channel></rss>