<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Lotame joins the NAI</title>
	<atom:link href="http://www.lotame.com/blog/lotame-joins-the-nai/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lotame.com/blog/lotame-joins-the-nai/</link>
	<description>Lotame leads the market in understanding, interpreting, and activating social data.</description>
	<pubDate>Mon, 22 Mar 2010 09:34:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Lotame&#8217;s new privacy policy: incorporation by reference? &#171; privacychoice</title>
		<link>http://www.lotame.com/blog/lotame-joins-the-nai/comment-page-1/#comment-191</link>
		<dc:creator>Lotame&#8217;s new privacy policy: incorporation by reference? &#171; privacychoice</dc:creator>
		<pubDate>Tue, 28 Apr 2009 01:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.lotame.com/blog/?p=916#comment-191</guid>
		<description>[...] how the policy changes are explained in Lotame&#8217;s announcement: In connection with joining the NAI, we have made some revisions to our privacy policy. Although [...]</description>
		<content:encoded><![CDATA[<p>[...] how the policy changes are explained in Lotame&#8217;s announcement: In connection with joining the NAI, we have made some revisions to our privacy policy. Although [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://www.lotame.com/blog/lotame-joins-the-nai/comment-page-1/#comment-192</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Mon, 27 Apr 2009 18:03:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.lotame.com/blog/?p=916#comment-192</guid>
		<description>Hello, Congratulations on joining the NAI!&lt;br&gt;&lt;br&gt;Please see the privacychoice comment on your new privacy policy:&lt;br&gt;&lt;a href="http://tinyurl.com/dg4unl" rel="nofollow"&gt;http://tinyurl.com/dg4unl&lt;/a&gt;&lt;br&gt;&lt;br&gt;Can you please provide clarification on the following questions:&lt;br&gt;&lt;br&gt;1. Is Lotame incorporating by reference the NAI policies in their entirety, as written and interpreted by the NAI?  I don’t recall seeing that approach in many other privacy policies.&lt;br&gt;&lt;br&gt;Substantively, it is of course helpful for consumers to know that a particular ad network is abiding by a standard like NAI’s rules.  But it is not helpful when a consumer has to undertake a research project to figure out what those policies may be. In this case, Lotame’s link to the NAI site still leaves the consumer to find and interpret the NAI’s policy document (a PDF that is, for some reason, buried in the news release section of the NAI site, rather than in the over view of principles). &lt;br&gt;&lt;br&gt;In short, incorporating the NAI principles by reference this way is a very weak way to inform consumers of Lotame’s privacy policies.  In fact, it would be hard to say that it satisfies the NAI’s requirement in the policies themselves that each member “clearly and conspicuously” post their policies on their website.&lt;br&gt;&lt;br&gt;2. A change in the policy that is not mentioned specifically in Lotame’s announcement is the deletion of the following language from the previous policy statement:&lt;br&gt;&lt;br&gt;"In addition, we do not tailor ads based on behavioral categories that are deemed sensitive by the Network Advertising Initiative (NAI)."&lt;br&gt;&lt;br&gt;The NAI policy (in Section II(3)(iv) of the 2008 Principles) requires a consumer opt-in in order to use sensitive information for targeting; so the inference (see discussion above) is that Lotame is now bound by that rule. However, this is important enough to merit a specific statement in Lotame’s privacy policy, particularly in light of the deletion.</description>
		<content:encoded><![CDATA[<p>Hello, Congratulations on joining the NAI!</p>
<p>Please see the privacychoice comment on your new privacy policy:<br /><a href="http://tinyurl.com/dg4unl" rel="nofollow">http://tinyurl.com/dg4unl</a></p>
<p>Can you please provide clarification on the following questions:</p>
<p>1. Is Lotame incorporating by reference the NAI policies in their entirety, as written and interpreted by the NAI?  I don’t recall seeing that approach in many other privacy policies.</p>
<p>Substantively, it is of course helpful for consumers to know that a particular ad network is abiding by a standard like NAI’s rules.  But it is not helpful when a consumer has to undertake a research project to figure out what those policies may be. In this case, Lotame’s link to the NAI site still leaves the consumer to find and interpret the NAI’s policy document (a PDF that is, for some reason, buried in the news release section of the NAI site, rather than in the over view of principles). </p>
<p>In short, incorporating the NAI principles by reference this way is a very weak way to inform consumers of Lotame’s privacy policies.  In fact, it would be hard to say that it satisfies the NAI’s requirement in the policies themselves that each member “clearly and conspicuously” post their policies on their website.</p>
<p>2. A change in the policy that is not mentioned specifically in Lotame’s announcement is the deletion of the following language from the previous policy statement:</p>
<p>&#8220;In addition, we do not tailor ads based on behavioral categories that are deemed sensitive by the Network Advertising Initiative (NAI).&#8221;</p>
<p>The NAI policy (in Section II(3)(iv) of the 2008 Principles) requires a consumer opt-in in order to use sensitive information for targeting; so the inference (see discussion above) is that Lotame is now bound by that rule. However, this is important enough to merit a specific statement in Lotame’s privacy policy, particularly in light of the deletion.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
