<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Hazy Hot and Humid</title>
	<atom:link href="http://hazyhotandhumid.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://hazyhotandhumid.com</link>
	<description>Peter Westerman&#039;s Blog</description>
	<lastBuildDate>Sat, 11 Jun 2011 14:22:54 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>Internet Privacy for Trade Publishers</title>
		<link>http://hazyhotandhumid.com/2011/06/11/internet-privacy-trade-publishers/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=internet-privacy-trade-publishers</link>
		<comments>http://hazyhotandhumid.com/2011/06/11/internet-privacy-trade-publishers/#comments</comments>
		<pubDate>Sat, 11 Jun 2011 14:07:21 +0000</pubDate>
		<dc:creator>Peter</dc:creator>
				<category><![CDATA[Database Marketing]]></category>
		<category><![CDATA[Lead Generation]]></category>
		<category><![CDATA[Media]]></category>
		<category><![CDATA[Privacy]]></category>

		<guid isPermaLink="false">http://hazyhotandhumid.com/?p=6</guid>
		<description><![CDATA[The following is based on the notes I prepared for a recent panel discussion at the 2011 American Business Media conference (webcast available here beginning at minute 18). There are at least three things to consider when talking about privacy The law, and potential laws. What&#8217;s important to the people who make law The practical: [...]]]></description>
			<content:encoded><![CDATA[<div class="al2fb_like_button"><script src="http://connect.facebook.net/en_US/all.js#xfbml=1" type="text/javascript"></script><fb:like href="http://hazyhotandhumid.com/2011/06/11/internet-privacy-trade-publishers/" layout="standard" show_faces="true" width="450" action="like" font="tahoma" colorscheme="light" ref="AL2FB"></fb:like></div><p>The following is based on the notes I prepared for a recent panel discussion at the 2011 American Business Media conference (webcast available <a title="ABM Privacy Panel" href="http://www.tvworldwide.com/events/abm/110501/default.cfm?id=13565&amp;type=flv&amp;test=0&amp;live=0" target="_blank">here</a> beginning at minute 18).</p>
<p>There are at least three things to consider when talking about privacy</p>
<ol>
<li>The law, and potential laws. What&#8217;s      important to the people who make law</li>
<li>The practical: customer&#8217;s perceptions and      expectations of privacy when they interact with our brands. Privacy is      subjective, and it&#8217;s personal</li>
<li>The emotional. Privacy is about control and      who determines what information about a person is shared: them, or a      third-party.</li>
</ol>
<p>Unpacking &#8216;Privacy&#8217; and why business media companies should care:</p>
<ul>
<li>Most trade publishing is based on a      &#8216;give/get.&#8217; A reader gives data to a publisher and gets access to information.      The publisher &#8216;sells&#8217; that data directly (in the case of research and data      products), or indirectly as a measure of audience composition.      Increasingly sought-after is data and information specifically tied to an      individual reader/user customer. Sometimes anonymously, but more often now      not</li>
<li>Privacy is about meeting a customer&#8217;s      expectations about what information you collect, combine and store about      the and how you use it</li>
<li>Can customers trust that you have complete      control over the data and information you maintain</li>
<li>Is the data being used in a way that is      consistent with the relationship they perceive they have established with      you</li>
<li>Is the data being used to benefit the      customer&#8217;s experience with your products or brands</li>
<li>Security. Some of the information we      collect can be combined with other information to characterize the      business activities of our user&#8217;s organizations, or their roles within      their organizations that could be used for bad purposes. Leaks of such      information might also cause organizations where our readers work to bar      them from interacting with our brands.</li>
</ul>
<p>Why Trust and Expectation-Setting Make Transparency a Business Imperative</p>
<p>As an example of trust and expectation setting: take for example lead generation &#8212; a business many of us are in. In some cases, we have brands specifically built for lead generation. It&#8217;s very clear to users that when they opt-in their data will be provided to a sponsoring company.</p>
<p>What is probably not clear to them, is that we may be combining the information collected in that transaction with information collected through our other editorial brands about what they read, eseminars they&#8217;ve attended, and perhaps even responses to polling you&#8217;ve done.</p>
<p>And to push it one step further, our data may be combined with data from third-parties &#8212; and distributed externally.</p>
<p>The stakes are very high because data is indelible. One large data &#8216;leak&#8217; through a vendor is your data supply chain cannot be erased. Once the data is out, it is not coming back.</p>
<p>Disclose what you know about your customers. Privacy is subjective. Let them decide what they are comfortable with, and give them opportunities to tell you what additional value you can provide that satisfies them that they are getting an equitable exchange for the data they are providing.</p>
<p>Create incentives that directly benefit users to keep their data accurate and up to date. Make that transparent. Show how more accurate and detailed data benefits them.</p>
<p>All of us need to really get our arms around what is happening data we have supplied to 3rd-party data aggregators. Just because a person has voluntarily given us and three other organizations data about themselves, does not mean they have opted-in the have that data combined and acted on in some unexpected way. In some ways this is the thorniest issue we will be dealing with in the future. Not only figuring out how aggregators are using our data, but how to properly disclose to our customers how it is being used in a way that meets THEIR expectations of transparency about our privacy policies.</p>
<p>In the digital world, customers will always eventually figure out and broadcast your business practices to peers. This is a conversation you want to control by being transparent. Remember privacy is emotional. If you lose control of the conversation about your data-handling practices you will lose the ability to collect data because your readers will not trust you.</p>
<p>While existing law, and pending legislation generally makes exceptions for information collect in the course of business to business transactions, we do need to be wary of the increasingly blurry line between people&#8217;s business and recreational persona&#8217;s.</p>
<p>In the my early days as computer magazine publisher, we had many people receiving Dr. Dobb&#8217;s Journal at home. It was an advanced programming magazine, and many companies did not allow programmers to disclose where they worked. The analogy today is these folks use personal email addresses, and that allows marketers to append large amounts of actionable data to their business profiles &#8212; and use it to communicate with them.</p>
<p>We also need to begin considering that the information that is the life-blood of our businesses: knowledge about the products and services consumed or resold by our reader&#8217;s companies can be combined in new ways that create competitive threats to their businesses. If we are seen to be aiding corporate competitive intelligence through our data collection and sharing policies, we will find ourselves locked out businesses we need to reach.</p>
<p>Your first step in getting your arms around where your company stands, is to break this down into digestible pieces. You need to have a comprehensive understanding of:</p>
<ul>
<li>Your customer&#8217;s expectations about how you will use data they provide &#8212; or that you generate about them</li>
<li> Your businesses&#8217; data collection practices including storage, transfer and security</li>
<li> Your business partner&#8217;s security practices. How do your vendors handle personal information? Who has access to their data? Who is it shared with? Have they documented their data security practices for you?</li>
</ul>
<p>Some additional practical things you should be doing now:</p>
<p><strong>Inventory of all the data collected across your organization:</strong></p>
<ul>
<li>What is data collected?</li>
<li>How is it stored?</li>
<li>Who has access to it?</li>
<li>What is it used for internally?</li>
<li>What data is it combined with internally?</li>
<li>How is it distributed externally?</li>
<li>Audit all vendors &#8212; how are they using the data?</li>
<li>Do you really understand how data is propagating through your vendor eco-system?</li>
<li>Is there any place you have data bleeding out?</li>
<li>Create a preference center where users can see what info you have collected about them, and give them opt-out options</li>
<li>Clearly explain the value to the customer in letting you keep and maintain this information</li>
</ul>
<p>&nbsp;</p>
<div class="twttr_button">
				<a href="http://twitter.com/share?url=http://hazyhotandhumid.com/2011/06/11/internet-privacy-trade-publishers/&text=Internet Privacy for Trade Publishers" target="_blank" title="Click here if you liked this article">
					<img src="http://hazyhotandhumid.com/wp-content/plugins/twitter-plugin/images/twitt.gif" alt="Twitt" />
				</a>
			</div>]]></content:encoded>
			<wfw:commentRss>http://hazyhotandhumid.com/2011/06/11/internet-privacy-trade-publishers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

