<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.2.2" -->
<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/"
	>

<channel>
	<title>rkgblog &#187; Privacy</title>
	<link>http://www.rimmkaufman.com/rkgblog</link>
	<description>observations on web marketing, paid search, and website effectiveness.</description>
	<pubDate>Fri, 29 Aug 2008 18:15:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>
	<language>en</language>
			<item>
		<title>Interview: Attorney Marty Eisenstein On Nexus, Gift Cards, The FTC, CAN-SPAM, And Other Legal Best Practices For Online Retailers</title>
		<link>http://www.rimmkaufman.com/rkgblog/2008/01/17/marty-interview/</link>
		<comments>http://www.rimmkaufman.com/rkgblog/2008/01/17/marty-interview/#comments</comments>
		<pubDate>Thu, 17 Jan 2008 19:29:41 +0000</pubDate>
		<dc:creator>Alan Rimm-Kaufman</dc:creator>
		
	<dc:subject>Interviews</dc:subject>
	<dc:subject>Privacy</dc:subject>
	<dc:subject>Web Marketing</dc:subject><dc:subject>brann isaacson</dc:subject><dc:subject>can spam</dc:subject><dc:subject>facta</dc:subject><dc:subject>Interviews</dc:subject><dc:subject>mail order rule</dc:subject><dc:subject>Martin Eisenstein</dc:subject><dc:subject>Marty Eisenstein</dc:subject><dc:subject>nexus</dc:subject><dc:subject>privacy</dc:subject><dc:subject>quill</dc:subject><dc:subject>sales tax</dc:subject><dc:subject>use tax</dc:subject>
		<guid isPermaLink="false">http://www.rimmkaufman.com/rkgblog/2008/01/17/marty-interview/</guid>
		<description><![CDATA[Marty I. Eisenstein is a senior partner with  Brann Isaacson, a law firm specializing in direct marketing law.  Marty shared his thoughts on tax law, gift cards, and general legal best practices for online retailers.
]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.brannlaw.com/person.php?pid=12"><img src='http://www.rimmkaufman.com/content/1163.Marty07001profile.jpg' alt='martin i eisenstein'  class="imgR"/></a></p>
<blockquote><p>Nexus is something that many retailers have, but do not know they have.  Some people compare nexus  to leprosy. I don’t think it’s quite that bad, but it can be a hidden disease.   Prudent direct marketers are careful not to trip the nexus wire. <br /><br />
&#8211; Martin Eisenstein </p></blockquote>
<p><a href="http://www.brannlaw.com/person.php?pid=12">Marty I. Eisenstein</a> is a senior partner with <a href="http://www.brannlaw.com/info.php?info_id=1">Brann Isaacson</a>, a Maine law firm specializing in direct marketing law.  </p>
<p>Brann Isaacson&#8217;s <a href="http://www.brannlaw.com/info.php?info_id=3">client list</a> reads like a <em>Who&#8217;s Who</em> of direct marketing, and Marty and the firm are actively involved in the direct marketing industry and the legislative arena. </p>
<p>Marty shared his thoughts on tax law, gift cards, and legal best practices for online retailers in this podcast.</p>
<p>Listen to podcast: <strong><a href="http://www.rimmkaufman.com/content/Martin_Eisenstein_Interview_2008-1-11.mp3">Martin_Eisenstein_Interview_2008-1-11.mp3</a><br />
</strong></p>
<hr />
<h1> Marty Eistenstein Transcript </h1>
<p><em><strong>Alan Rimm-Kaufman:</strong>	Hello everyone.  This is Alan Rimm-Kaufman and I’m delighted to be here today with <a href="http://www.brannlaw.com/person.php?pid=12">Marty I. Eisenstein</a> of <a href="http://www.brannlaw.com/info.php?info_id=1">Brann &#038; Isaacson</a>.  Hello, Marty!</em></p>
<p><strong>Marty Eisenstein: 	</strong>Hi, Alan!  How are you?</p>
<p><em><strong>Alan:  </strong> Great.  And it&#8217;s it’s wonderful to  speak to you.</em></p>
<p><strong>Marty:</strong>	Good to speak to you too.</p>
<p><em><strong>Alan:	</strong>You are an attorney at a law firm that specializes in direct marketing.</em></p>
<p><strong>Marty:	</strong>That’s correct.  Direct marketing and online law.  We used to call it &#8220;catalog law&#8221;, but you know now that we’ve moved into the 21st century we’ve gone even past &#8220;direct marketing law&#8221; and we now call it &#8220;online law&#8221;.</p>
<p><em><strong>Alan:</strong>	Online marketing.  Online retailing.  Both are very young businesses.     Are there many federal statutes that cover these areas?</em></p>
<p><strong>Marty: </strong>	Not many.  Most of the laws that have been adopted in this area have been by the state legislatures.  There are three specific federal statutes and laws that apply in this area.  And then there are a hodge podge of state laws and that’s what makes the area very challenging law.  </p>
<p><img src='http://www.rimmkaufman.com/content/mainepuffinsmall.jpg' alt='maine puffin' class="imgR"/></p>
<p>The three federal laws are one which is a federal statute that was adopted three or four years ago called the <a href="http://www.ftc.gov/bcp/conline/pubs/buspubs/canspam.shtm">Can-Spam</a> act.  It governs outgoing email, when you can send an email and what you need to put in the email.  CAN-SPAM is a federal statute.  </p>
<p>The second federal law is a regulation under the Federal Trade Commission Act.  And it applies – it was formerly called the <a href="http://www.ftc.gov/bcp/conline/pubs/buspubs/mailorder.shtm">Mail Order Rule</a>, but it applies to online marketers as well.  And it relates to what promises you make in terms of shipping items to purchasers of products.  So it basically says that if you commit by advertisement or by your telephone conversation to a specific shipping date, you need to follow that shipping date.  And if you don’t commit to a specific shipping date, the default is a 30-day shipping date.  In the event you’re not able to meet either one of those dates then you need to notify your customer.  </p>
<p>And depending upon the circumstances, you either need the customer’s affirmative permission to continue to supply the item to the customer or you need – or you can go on the principle of opt out.  Namely that unless you hear from the customer you can continue to ship the merchandise.</p>
<p><em><strong>Alan:	</strong>And the third?</em></p>
<p><strong>Marty:</strong>	 The third statute is called <a href="http://en.wikipedia.org/wiki/Fair_and_Accurate_Credit_Transactions_Act">FACTA</a>.  It applies not only to online marketers, it applies to any retail merchant that receives credit cards and payment.  And obviously online marketers will receive, in large part, credit cards.  What that law basically says is that you cannot &#8212; that is,  a direct marketer cannot &#8212; record the last five digits of the credit card number.  It’s a couple year old law and it’s a not very well known law, but there have been a number of lawsuits against online marketers including against some larger companies for failure to observe that law.</p>
<p><em><strong>Alan:	</strong>In short, the Can-Spam law governs email practices.  The Mail Order Rule governs getting shipments out the door quickly.  And the FACTA law governs how to store credit card data.</em></p>
<p><strong>Marty:	</strong>That’s correct.</p>
<p><em><strong>Alan:	</strong>Which  poses the greatest risk to an online retailer?  </p>
<p>If you were speaking to a CEO of a direct marketing firm, which would one these should be top on their list?</p>
<p><img class="imgL" src='http://www.rimmkaufman.com/content/mainecoast.jpg' alt='maine coast' /></p>
<p></em><strong>Marty:	</strong>I would say that each one of those has equal prominence.  </p>
<p>But I would think that the more prominent issue for an online marketer are the state laws and in particularly the privacy laws.  An increasingly hot area in the law is privacy.  </p>
<p>And you get those regs from both FACTA, but more importantly from the state laws.   I would say is you would follow the guide of the squeakiest wheel, which usually tends to be the California laws.</p>
<p><em><strong>Alan:	</strong>So, retailers should pay particular attention to the state statutes?<br />
</em><br />
<strong>Marty:	</strong>Yes.</p>
<p><em><strong>Alan:	</strong>But earlier in the call you described the state regs as a hodge-podge of rules.<br />
</em><br />
<strong>Marty:	</strong>Yes, that’s correct.</p>
<p><em><strong>Alan:	</strong>If you simply follow the California laws, is that enough?  Or do the different state laws disagree?<br />
</em><br />
<strong>Marty:	</strong>Well, following the California law is often the safest course.  </p>
<p>Unfortunately, you’re not absolutely safe unfortunately because even though you may be operating an online site from your location in pristine Maine, you would still be subject to the state laws if you sell and market to customers in those states.  Yes, the states laws  are a hodge podge, and they can be divergent. </p>
<p> But what has tended to happen is that California has been out front as it is in other areas, but particularly online marketing.  California has been setting the standard.  And by and large the other states have followed suit, but not precisely.  </p>
<p><img src='http://www.rimmkaufman.com/content/mainelighthousesmall.jpg' alt='maine light house'  class="imgL"/></p>
<p>There are some states, for example in the privacy area, that not only require some of the California standards, but set a separate standard that basically requires adopting a privacy policy.  Which most online marketers have &#8212;  but that is not necessarily required by every states’ laws.  But there are a couple states that do require having a privacy policy.</p>
<p><em><strong>Alan:</strong>Suppose you took all the areas of the law that relate to online retailing &#8212; those might include email, fair trade,  pricing, intellectual property,  trademark, tax,  and so forth &#8212;  and you wrote those down for each of the states.  That is, tallying laws from all states in all areas, how many laws need an online retailer be aware of and abide by?  Is this a list of 10, of 50, of 100?<br />
</em><br />
<strong>Marty:</strong>	No, I would say it’s more – it’s greater than 10 and probably fewer than 50 different areas is what you’re talking about.  </p>
<p>But, yes, there are a multitude of laws that a company would have to contend with.  </p>
<p>For example, the interesting question   tax law.  There are 6,000 jurisdictions that have state taxes.  Now an online marketer is required to comply with each state’s tax laws.  That means  file tax returns,  collect sales tax in the case of a sales tax, and to remit the sales tax if it has nexus with a particular state or jurisdiction.</p>
<p>When I said 6,000 jurisdictions, that includes both states and local jurisdictions like municipalities and counties.  The same standard of nexus is not true for other areas of the law like privacy, like consumer protection.  We’ll talk a little bit about consumer protection in a bit.</p>
<p><em><strong>Alan:	</strong>Can you define <a href="http://en.wikipedia.org/wiki/Sales_tax">&#8220;nexus&#8221; </a>for folks that aren’t familiar with it?<br />
</em></p>
<p><strong>Marty:</strong>	Sure.  It’s a lawyer’s Latin term that has been  over abused.  But basically &#8220;nexus&#8221; means having a physical presence in a state, which would consist of maintaining employees in a state, owning property in a state, and/or having a sales representative try to develop sales of products in your state.</p>
<p><em><strong>Alan:</strong>If I’m an online retailer in states where I have property, employees, sales agents, and so forth, then I have established nexus. What does establishing nexus mean to me?</em></p>
<p><strong>Marty:</strong>	If you establish nexus, not only do you have to satisfy all the other standards that we talked about, privacy etcetera, but you are required to, on all your taxable products which is basically everything that you sell into a state with certain exceptions, you’re required to collect tax.  </p>
<p>And if you don’t collect the sales tax, the state’s sales tax and local taxes as well, if you don’t collect the sales tax the direct marketer –- the online marketer is liable for that tax.  </p>
<p>And if you don’t remit the tax  you’re then liable for interest and penalty.  </p>
<p>And penalties can be up to 25% of the amount of the tax.  </p>
<p>So an online marketer gets a double whammy in effect by the fact that it’s a tax that really is not the marketer’s, the retailer’s responsibility.  It’s customer’s responsibility.  It’s just acting as an agent for the state.  So if it doesn’t collect the tax it’s responsible not only for the tax, but also for interest on that tax as if it never had – as if it had that money and was using that money, which it was not.  </p>
<p><img src='http://www.rimmkaufman.com/content/cascobay.JPG' alt='casco bay maine' class="imgR"/></p>
<p>And then it’s responsible to boot, to add insult to injury, for &#8212; sometimes for penalties.</p>
<p><em><strong>Alan:	</strong>Is nexus something that a retailer files for?<br />
</em><br />
<strong>Marty:	</strong>No, it’s not.  </p>
<p>It’s something that many retailers have, but they do not know they have.  Some people have analogized it to leprosy.  I don’t think it’s quite that bad.  But it can be a hidden disease.  So a prudent direct marketer – the largest – the larger of my clients who are online marketers, direct marketers internally look at and make sure that they do not trip the nexus trip wire.</p>
<p><em><strong>Alan:	</strong>I worked in the catalog industry.  There,  nexus was a very common concept.  We took many careful legal steps to avoid creating nexus.   </p>
<p>Since working in online marketing, I&#8217;ve found nexus is rarely discussed.  The concept doesn’t seem to be on the radar.  Some online sites even use brazen banners claiming  “No sales tax.”  (Which isn&#8217;t strictly true: even if the retailer doesn&#8217;t collect the tax as per <a href="http://supct.law.cornell.edu/supct/html/91-0194.ZO.html">Quill</a>, the consumer is still responsible for <a href="http://en.wikipedia.org/wiki/Use_tax">use tax</a>.)</p>
<p>Why don’t the web pure players care?  They’re seem to be just ignoring the use tax issue.</p>
<p> Are the catalogers just too conservative, or are the online folk just insane?</em></p>
<p><strong>Marty:</strong>	I don’t think it’s either one.  I don’t think catalogers are too onservative because I think almost all catalogers also have an online presence of course.  You know in these days of multi-stage retailing of course they have an online presence.  Everyone has an online presence.  </p>
<p>But I think what happens is for the start-ups for the online marketers who only have a presence online, they believe that they don’t have bricks and mortars in a state.  </p>
<p>They don’t have a retail store so they mistakenly think they’re safe.  </p>
<p>As for the online retailers,  I don’t think there’s a phenomenon of them being crazy or cowboys.  I just don’t think they’re looking closely enough at the potential implications of some of the their activities.  </p>
<p>Because there are a number of activities that you would say – one would say, “Well, I don’t know.  I don’t really have an employee in this state.”  But you may, for example, have an affiliate relationship where you have – you commission out to independent contractors sales leads.  That potentially can create nexus. </p>
<p><em><strong>Alan:	</strong>There’s a whole affiliate marketing industry where retailers pay affiliates nationwide on a percentage of sales they deliver.  Would that be creating nexus in every state?</em></p>
<p><strong>Marty:</strong>	It could. </p>
<p>Yes, it could.  That’s why structure and looking at the relationships is very important.<br />
The legal details of the affiliate contract matter a great deal.  Structuring those contracts so that they don&#8217;t create nexus is is an important thing that an online marketer should do.</p>
<p><em><strong>Alan:	</strong>Earlier you had said that there might be between 10 and  50 state statutes that a nationwide direct retailer  must be aware of. </em></p>
<p><strong>Marty:	</strong>That was on a state-by-state basis.  There are well over 100, if you count all the statutes from all of the states.</p>
<p><em><strong>Alan:	</strong>Yes, all laws from all states, that&#8217;s the disturbingly large number I was referring to.  So with hundreds  of these statutes with which an online retailer is obligated to comply, how does a retailer know even what all these laws are?</em></p>
<p><strong>Marty:</strong>	Not to toot my horn, but we&#8217;ve  compiled a list of state statues in the privacy area. And  I’ve complied a list of state statutes for gift cards.  </p>
<p>(I realize you haven’t asked me about gift cards yet.) </p>
<p>Compiling and maintaining the lists is difficult, but not impossible.  Generally you have to stay aware of those laws.  A retailer could either employee people  or reach out to consultants to help you and navigate the overwhelming number of state and federal statutes governing online retail.<br />
<img src='http://www.rimmkaufman.com/content/lobsterboat.jpg' alt='maine lobster boat' class="imgL"/></p>
<p><em><strong>Alan:</strong>	You’ve graciously before offered to share those lists with the folks on our blog.  </em></p>
<p><strong>Marty:</strong>	Yes.  I think I&#8217;ve also  shared also with you the privacy standards.  I also have a schematic on the CAN-Spam law, and on the mail order rule. Your listeners may  want to look at those as well.<br />
<em><br />
<strong>Alan:	</strong>Fantastic.  Thank you for allowing us to share those.  They&#8217;re an amazingly valuable resource for online retailers.   </em></p>
<p><strong>Marty:</strong>	Sure.</p>
<p><em><strong>Alan:	</strong>You mentioned gift cards.  Gift cards are a huge  business these days.  That  industry is growing like a weed.  What are the legal issues around gift cards?</em></p>
<p><strong>Marty:	</strong>Gift card laws basically fall into three categories of statutes.  </p>
<p>One is the Federal Trade Commission statute, which is a general standard that prohibits unfair and deceptive trade practices.  And the FTC has entered this – the fray against KMart and other companies of that nature – not of that nature, but against other companies because they failed to conspicuously disclose that there was a, for example a dormancy fee.  And a dormancy fee means if there’s a fee – if you don’t activate, don’t use the gift card within a certain time period.  So you have the Federal Trade Commission statute and enforcement as one category. </p>
<p>You have a second category, which are the state laws, a list of which I’ve made available to you previously.  And those laws say some states prohibit expiration dates of gift cards.  Some states prohibit these kind of dormancy fees.  In other words fees for not using the gift card.  California is a good example of states that – California and Massachusetts are good examples of states that prohibit expiration dates.</p>
<p>There are a couple state statutes – I think Florida is one &#8212; which  prohibit dormancy fees.  But these statutes are being adopted with increasing regularity.  So dormancy fees are really   a treacherous area.  </p>
<p>I update my Gift Card regulation chart every month.  I have to, because the state laws are changing so rapidly. </p>
<p>And then there’s a third area, which is the hidden tax.  States don’t call it a tax of course.  They call it a &#8220;revenue enhancer&#8221;.  They call it &#8220;protection for the consumer.&#8221;  Those are  called the <a href="http://en.wikipedia.org/wiki/Escheat">escheat</a> laws. </p>
<p>About 26 states escheat.  What the escheat laws  require is the turnover of the face value or some portion of the face value of the gift certificate to the state if the proper owner of the gift certificate or gift card does not redeem the gift card within a specific time frame.  They&#8217;re a monetary obligation on the part of a holder such as a seller of gift cards to  certain states.</p>
<p>They&#8217;re complicated; the full details are well beyond this conversation.</p>
<p><em><strong>Alan:	</strong>So the &#8220;breakage&#8221;, as the unused portion of gift cards is commonly caller &#8212; the breakage doesn’t just go to the retailer?</em></p>
<p><strong>Marty:</strong>	No, no.  Breakage doesn’t go to the retailer.  It does in certain states, but then there’s a whole series of tests that the retailer should be aware of to make sure it does not get into a bind.  </p>
<p>The problem with the escheat laws is that there is generally not a statute of limitations. </p>
<p>And again like tax laws, the escaheat laws have an interest provision and a penalty provision in the event of failure to remit the proper amount due to a state.  </p>
<p>The small spot of good news in the gift card area is that there are 25 states or so that do not escheat gift cards.</p>
<p><em><strong>Alan:	</strong>The complexity of all these regs are staggering.  The state-by-state differences are staggering.  And the fact that these laws are so dynamic &#8212; that you have to update your tables of state laws each month &#8212; that level of change is also  staggering.<br />
</em><br />
<strong>Marty:	</strong>Well, we have a great staff at Brann &#038; Isaacson. </p>
<p>Again it sounds like I’m selling Brann &#038; Isaacson, and I probably am.  But we do have a great staff and we  monitor all the publications, all the state laws.  And they help me update my charts.  I’m not doing that myself, but I have great people who work for me who do that important work.<br />
<em><br />
<strong>Alan:	</strong>Online retail is certainly a specialized area of the law.  Retailers selling online and direct have to pay attention to the all the applicable state and federal laws to avoid getting in hot water.</em></p>
<p><strong>Marty:	</strong>Absolutely.  </p>
<p> I’ve been consulted by other lawyers in the field who say these details are beyond them.  It really literally is a minefield.  Other lawyers turn to our firm or to other professionals who specialize in this complicated area.</p>
<p><em><strong>Alan:	</strong>   General counsel may not be skilled in all these nuances.</em></p>
<p><strong>Marty:</strong>	Correct.</p>
<p><em><strong>Alan:</strong>	As we wrapping up this most interesting conversation,   what is your top legal tip for online retailers?</em></p>
<p><strong>Marty:	</strong> The most important tip I can offer is &#8220;be proactive.&#8221;</p>
<p>By that, I mean retailers mst  establish sound policies and practices &#8212; protocols I call them &#8212; review whatever policies and protocols regularly. </p>
<p>Why establish and review protocols?  Several reasons.  </p>
<p>One reason is that in case of a lawsuit the first thing that is asked for, whether it’s a government agency or a class action, is what are your polices and protocol.  </p>
<p>The second reason is that the retailer, unbeknownst to senior management, may have a policy and protocol that is directly violative – that directly violates the law or that it may not even be following.  A lot of companies, for example, adopted privacy policies.  They basically copied another company’s privacy policy.</p>
<p><em><strong>Alan:	</strong> Very common.</em></p>
<p><strong>Marty:	</strong>But then they do not then follow those privacy policies.  Well, there are a number of court cases that have said those privacy policies are really a contract with your customer.  And if you don’t abide by that contract, your customer has a real right to sue you for what is called breach of contract.  And then you might be exposed to many levels of damages. </p>
<p>The sharks out there are not only the federal and state governments, but there are class action lawyers who bring lawsuits based upon small damages to individuals.  But when those small damages to individuals are aggregated, they become very large very fast.  And many of the state statutes permit the recovery of attorney’s fees.  </p>
<p>So the exposures are very large and the potential publicity and time that it takes management to address these issues after the fact makes a lot of – dictates that companies really should be looking at this before the fact.  </p>
<p>That&#8217;s why I advise, &#8220;be proactive.&#8221;</p>
<p><em><strong>Alan:</strong>	A little up front work can mitigate a lot of risk down the road if something later goes awry.</em></p>
<p><strong>Marty:</strong>	Exactly right.  &#8220;An ounce of prevention.&#8221;</p>
<p><em><strong>Alan:</strong>	 I appreciate your generous advice and your tips on the complexities of our legal systems, state and Federal. </em></p>
<p><strong>Marty:</strong>	Thanks Alan.</p>
<hr />
<p>Listen to podcast: <strong><a href="http://www.rimmkaufman.com/content/Martin_Eisenstein_Interview_2008-1-11.mp3">Martin_Eisenstein_Interview_2008-1-11.mp3</a><br />
</strong></p>
<a href="http://www.rimmkaufman.com/rkgblog/tag/brann-isaacson" rel="tag">brann isaacson</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/can-spam" rel="tag">can spam</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/facta" rel="tag">facta</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/interviews" rel="tag">Interviews</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/mail-order-rule" rel="tag">mail order rule</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/martin-eisenstein" rel="tag">Martin Eisenstein</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/marty-eisenstein" rel="tag">Marty Eisenstein</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/nexus" rel="tag">nexus</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/privacy" rel="tag">privacy</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/quill" rel="tag">quill</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/sales-tax" rel="tag">sales tax</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/use-tax" rel="tag">use tax</a><p class="akst_link"><div class="sharethisdiv">
<a href="http://www.rimmkaufman.com/rkgblog/?p=673&amp;akst_action=share-this"  title="Email, post to del.icio.us, etc." id="akst_link_673" class="akst_share_link" rel="noindex nofollow">Share this post</a> (via email, Digg, Delicious, etc)
</div>
</p>]]></content:encoded>
			<wfw:commentRss>http://www.rimmkaufman.com/rkgblog/2008/01/17/marty-interview/feed/</wfw:commentRss>
<enclosure url="www.rimmkaufman.com/content/Martin_Eisenstein_Interview_2008-1-11.mp3" length="" type="" />
<enclosure url="http://www.rimmkaufman.com/content/Martin_Eisenstein_Interview_2008-1-11.mp3" length="18610076" type="audio/mpeg" />
		</item>
		<item>
		<title>Google Held To Higher Privacy Standard?</title>
		<link>http://www.rimmkaufman.com/rkgblog/2007/04/30/google-held-to-higher-privacy-standard/</link>
		<comments>http://www.rimmkaufman.com/rkgblog/2007/04/30/google-held-to-higher-privacy-standard/#comments</comments>
		<pubDate>Mon, 30 Apr 2007 13:49:19 +0000</pubDate>
		<dc:creator>Alan Rimm-Kaufman</dc:creator>
		
	<dc:subject>Privacy</dc:subject><dc:subject>privacy</dc:subject>
		<guid isPermaLink="false">http://www.rimmkaufman.com/rkgblog/?p=398</guid>
		<description><![CDATA[Matt Cutts and Tim O'Reilly  note that Google is being held to a higher privacy standard than other firms who have far far more data on us (e.g. ISPs, credit card companies, credit bureaus, etc).  They're right.   ]]></description>
			<content:encoded><![CDATA[<p>Independently, <a href="http://www.mattcutts.com/blog/google-and-privacy/">Matt Cutts</a> and <a href="http://radar.oreilly.com/archives/2007/04/google_and_priv.html">Tim O&#8217;Rielly </a> wrote posts on Google and privacy last week.   Matt and Tim both note that Google is being held to a higher privacy standard than other firms who have far far more data on us (e.g. ISPs, credit card companies, credit bureaus, etc).  And they&#8217;re right.   </p>
<p>Our ISPs see every click we make.  Many ISPs then turn around and sell our clickstreams to aggregators like ComScore.  We don&#8217;t have an option to opt-out, and the ISPs don&#8217;t share the revenue from those clickstreams with the clickstream creators (us). Similarly, the credit organizations  see our every transaction, sell those data for profit, and have remarkably  sloppy data practices to boot.  I once found a car loan listed on my credit report that wasn&#8217;t mine.  The bureau removed that  at my request, but the casualness of their match logic was sobering. Others have noted this sloppiness too.  In a comment on Tim&#8217;s post, <a href="http://www.linuxworld.com/community/">Don Marti</a> of Linuxworld suggests one reason privacy debates focus on Google is because they can actually collect data accurately: <em>We hold Google to a higher standard because they&#8217;re smarter and have better data. Equifax customers can buy a credit report on me that says I started working two years before I was born.</em></p>
<p>The realization that other orgs know more about us than Google clearly doesn&#8217;t absolve Google from scrutiny of how and why it collects data. Rather, this realization should motivate citizens (and our goverment officials)  to drag these other organizations (ISPs, credit card companies, credit bureaus, etc) as well into the bright lights of the modern privacy debate.</p>
<a href="http://www.rimmkaufman.com/rkgblog/tag/privacy" rel="tag">privacy</a><p class="akst_link"><div class="sharethisdiv">
<a href="http://www.rimmkaufman.com/rkgblog/?p=398&amp;akst_action=share-this"  title="Email, post to del.icio.us, etc." id="akst_link_398" class="akst_share_link" rel="noindex nofollow">Share this post</a> (via email, Digg, Delicious, etc)
</div>
</p>]]></content:encoded>
			<wfw:commentRss>http://www.rimmkaufman.com/rkgblog/2007/04/30/google-held-to-higher-privacy-standard/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Google Promises To Forget</title>
		<link>http://www.rimmkaufman.com/rkgblog/2007/03/15/google-promises-to-forget/</link>
		<comments>http://www.rimmkaufman.com/rkgblog/2007/03/15/google-promises-to-forget/#comments</comments>
		<pubDate>Fri, 16 Mar 2007 01:17:28 +0000</pubDate>
		<dc:creator>Alan Rimm-Kaufman</dc:creator>
		
	<dc:subject>Privacy</dc:subject>
	<dc:subject>Web Marketing</dc:subject>
	<dc:subject>Google</dc:subject><dc:subject>clickstream</dc:subject><dc:subject>google</dc:subject><dc:subject>privacy</dc:subject>
		<guid isPermaLink="false">http://www.rimmkaufman.com/rkgblog/2007/03/15/google-promises-to-forget/</guid>
		<description><![CDATA[Google overhaul its privacy policies, will dump user-specific search data more than 18 months stale.]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.technewsworld.com/story/56321.html">From TechNewsWorld:</a></p>
<blockquote><p>Google announced Wednesday it will soon overhaul its privacy policies. Under the new plan, all information logged from its search users &#8212; keyword queries, IP addresses, and cookies, for example &#8212; will be scrubbed after 18 to 24 months. Privacy advocates say it&#8217;s a step in the right direction, but see much room for improvement.</p></blockquote>
<p>From the  civil liberties perspective, it is comforting that perhaps <a href="http://en.wikipedia.org/wiki/John_Battelle">Battelle </a>was wrong and <a href="http://battellemedia.com/archives/000647.php">clickstreams won&#8217;t be eternal</a>.</p>
<p>From an IT perspective, this will certainly save them some disk space.</p>
<p>From a direct marketing perspective, 18 months is plenty &#8212; purging stale data will have no material impact on any of Google&#8217;s targeting efforts.</p>
<a href="http://www.rimmkaufman.com/rkgblog/tag/clickstream" rel="tag">clickstream</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/google" rel="tag">google</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/privacy" rel="tag">privacy</a><p class="akst_link"><div class="sharethisdiv">
<a href="http://www.rimmkaufman.com/rkgblog/?p=322&amp;akst_action=share-this"  title="Email, post to del.icio.us, etc." id="akst_link_322" class="akst_share_link" rel="noindex nofollow">Share this post</a> (via email, Digg, Delicious, etc)
</div>
</p>]]></content:encoded>
			<wfw:commentRss>http://www.rimmkaufman.com/rkgblog/2007/03/15/google-promises-to-forget/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Mailinator: Disposable Public Email Addresses</title>
		<link>http://www.rimmkaufman.com/rkgblog/2007/03/13/mailinator-disposable-public-email-addresses/</link>
		<comments>http://www.rimmkaufman.com/rkgblog/2007/03/13/mailinator-disposable-public-email-addresses/#comments</comments>
		<pubDate>Tue, 13 Mar 2007 12:18:13 +0000</pubDate>
		<dc:creator>Alan Rimm-Kaufman</dc:creator>
		
	<dc:subject>Privacy</dc:subject>
	<dc:subject>Code</dc:subject>
	<dc:subject>Web Marketing</dc:subject><dc:subject>code</dc:subject><dc:subject>privacy</dc:subject>
		<guid isPermaLink="false">http://www.rimmkaufman.com/rkgblog/?p=318</guid>
		<description><![CDATA[Need a temporary email to receive a registration from a website?  Try Mailinator.]]></description>
			<content:encoded><![CDATA[<p>Need a temporary email to receive a registration from a website?  Try <a href="http://mailinator.com/">Mailinator</a>.    No cost, no passwords, no delay, no hassle.</p>
<p>From the <a href="http://www.mailinator.com/faq.jsp">FAQ</a>:</p>
<blockquote><p>
<strong>Mailinator is a new kind of mail service.</strong> The biggest difference is that you don&#8217;t need to sign up. Any email name you can think of already exists at mailinator.com. Want goofy@mailinator.com? You got it. Want to be SuperGuy? BoohaBunny? FredInPants? No problem. They all already exist just waiting for you to check your mail.</p>
<p><strong>How is Mailinator different than some other webemail? Say, Yahoo or Hotmail?</strong><br />
The differences are easy to list. Generally speaking however, anything you can do with Mailinator, you can do with some other email service. In fact, you can do more with other services since they allow you to actually send email (Mailinator only receives).<br />
The differences are:</p>
<p>    * Mailinator requires no sign-up. To create an account, you send email to it.<br />
    * You cannot send email from Mailinator.<br />
    * Your Mailinator email inbox can be read by anyone. There is no security here. If they know (or guess) your email address, they can read your mail.<br />
    * You cannot delete your email here (you can&#8217;t reply either), after a few hours, all email is auto-deleted.<br />
    * Mailinator has strict rules about what kind of email it receives. Plain text is best, html is filtered. Images, attachments, and fancy stuff is simply stripped away.</p>
<p><strong>Why is this good?</strong><br />
In our internet world, you often need an email address NOW. Signing up for an email service takes time - that&#8217;s probably ok for most emailing, but every now and then you need a quick email address for just a single email. After that you don&#8217;t care what happens to it. Given that such disposable email is ready at your disposal, you can avoid giving out your real email address when you are afraid of getting spammed. Instead, make up any address @mailinator.com on the spot and go check it later.</p></blockquote>
<p>(And following up on yesterday&#8217;s post on <a href="http://www.rimmkaufman.com/rkgblog/2007/03/12/database-scaling-war-stories/">scaling databases</a>, Paul Tyma provides a blog post <a href="http://mailinator.blogspot.com/2007/01/architecture-of-mailinator.html">describing the architecture and strategies</a> he uses to handle 4.5 to 6  million emails per day on  a single server.  And not a big server at that:   &#8220;A very modest machine with an AMD 2Ghz Athlon processor, 1G of ram (although it really doesn&#8217;t need that much), and a boring (IDE , low-performance) 80G hard drive. And honestly, its really not very busy at all.&#8221;)</p>
<p>Kudos to Paul for providing such a useful service, and also for sharing his strategies for accomplishing it on such modest hardware. </p>
<a href="http://www.rimmkaufman.com/rkgblog/tag/code" rel="tag">code</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/privacy" rel="tag">privacy</a><p class="akst_link"><div class="sharethisdiv">
<a href="http://www.rimmkaufman.com/rkgblog/?p=318&amp;akst_action=share-this"  title="Email, post to del.icio.us, etc." id="akst_link_318" class="akst_share_link" rel="noindex nofollow">Share this post</a> (via email, Digg, Delicious, etc)
</div>
</p>]]></content:encoded>
			<wfw:commentRss>http://www.rimmkaufman.com/rkgblog/2007/03/13/mailinator-disposable-public-email-addresses/feed/</wfw:commentRss>
		</item>
		<item>
		<title>11% of Sites Vulnerable To SQL Injection: Is Yours?</title>
		<link>http://www.rimmkaufman.com/rkgblog/2006/09/27/11-of-sites-vulnerable-to-sql-injection-is-yours/</link>
		<comments>http://www.rimmkaufman.com/rkgblog/2006/09/27/11-of-sites-vulnerable-to-sql-injection-is-yours/#comments</comments>
		<pubDate>Wed, 27 Sep 2006 16:04:32 +0000</pubDate>
		<dc:creator>Alan Rimm-Kaufman</dc:creator>
		
	<dc:subject>Privacy</dc:subject>
	<dc:subject>Code</dc:subject>
	<dc:subject>Web Marketing</dc:subject><dc:subject>michael sutton</dc:subject><dc:subject>online hack</dc:subject><dc:subject>online retailer</dc:subject><dc:subject>retail hacking</dc:subject><dc:subject>secure e commerce</dc:subject><dc:subject>sql injection</dc:subject>
		<guid isPermaLink="false">http://www.rimmkaufman.com/rkgblog/?p=106</guid>
		<description><![CDATA[Preventing SQL injection isn't all that hard -- yet 11% of sites haven't got it right yet.]]></description>
			<content:encoded><![CDATA[<p><a href="http://portal.spidynamics.com/blogs/msutton/archive/2006/09/26/How-Prevalent-Are-SQL-Injection-Vulnerabilities_3F00_.aspx">Michael Sutton</a> wrote about a simple tool he wrote which uses Google to find sites vulnerable to SQL injection.  (I wrote about <a href="http://www.rimmkaufman.com/articles/web-security-for-catalogers/toc.html">SQL injection as it relates to online retailers</a> in Catalog Success article last year.)</p>
<p>Sutton found 11% of the sites in his study have vulnerabilities.  That&#8217;s a huge rate.</p>
<p>Sutton&#8217;s tool was written to assess the scope of the problem.  The same technique could modified, easily, to attack sites en masse using an automated &#8216;bot.  Scary.</p>
<p>Talk to your web folks.  Make sure they&#8217;ve secured your site. Don&#8217;t allow any raw inputs to reach your database (SQL injection) or your HTML output (cross-site scripting).  </p>
<p>Preventing SQL injection isn&#8217;t all that hard &#8212; yet 11% of sites haven&#8217;t got it right yet.</p>
<a href="http://www.rimmkaufman.com/rkgblog/tag/michael-sutton" rel="tag">michael sutton</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/online-hack" rel="tag">online hack</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/online-retailer" rel="tag">online retailer</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/retail-hacking" rel="tag">retail hacking</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/secure-e-commerce" rel="tag">secure e commerce</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/sql-injection" rel="tag">sql injection</a><p class="akst_link"><div class="sharethisdiv">
<a href="http://www.rimmkaufman.com/rkgblog/?p=106&amp;akst_action=share-this"  title="Email, post to del.icio.us, etc." id="akst_link_106" class="akst_share_link" rel="noindex nofollow">Share this post</a> (via email, Digg, Delicious, etc)
</div>
</p>]]></content:encoded>
			<wfw:commentRss>http://www.rimmkaufman.com/rkgblog/2006/09/27/11-of-sites-vulnerable-to-sql-injection-is-yours/feed/</wfw:commentRss>
		</item>
		<item>
		<title>AOL Search Data Release: Class Action Lawsuit Filed</title>
		<link>http://www.rimmkaufman.com/rkgblog/2006/09/26/aol-search-data-release-class-action-lawsuit-filed/</link>
		<comments>http://www.rimmkaufman.com/rkgblog/2006/09/26/aol-search-data-release-class-action-lawsuit-filed/#comments</comments>
		<pubDate>Tue, 26 Sep 2006 14:54:00 +0000</pubDate>
		<dc:creator>Alan Rimm-Kaufman</dc:creator>
		
	<dc:subject>Privacy</dc:subject>
	<dc:subject>Business</dc:subject><dc:subject>aol</dc:subject><dc:subject>privacy</dc:subject>
		<guid isPermaLink="false">http://www.rimmkaufman.com/rkgblog/?p=105</guid>
		<description><![CDATA[Search data not be used for commercial purposes?  Too much money at stake -- never going to happen.]]></description>
			<content:encoded><![CDATA[<p>Danny Sullivan at SEW comments on a <a href="http://blog.searchenginewatch.com/blog/060926-075713">class action lawsuit filed against AOL for releasing search data.</a></p>
<p>Only a tiny number of the 658,000 affected individuals suffered any real damage to their privacy.  But a small number did.  If I were the judge, I&#8217;d throw out the class in favor of individual suits.</p>
<p>According to <a href="http://www.techcrunch.com/2006/09/25/suit-filed-against-aol-seeks-to-block-search-history-storage/">TechCrunch</a>, </p>
<blockquote><p>The suit also demands that user search data not appear in further search results and not be used for commercial or non-commercial purposes. Though this is probably an unrealistic demand to make, it&#8217;s also a broad attack on many of the most interesting developments on the web today.</p></blockquote>
<p>Search data not be used for commercial purposes?  Too much money at stake &#8212; never going to happen.</p>
<p>The greatest impact this suit will have is increasing the awareness of search logs in the public consciousness.  Look for evening news and 60 Minutes coverage on web privacy over the next few weeks.</p>
<p>Check out the AOL logs for yourself: <a href="http://data.aolsearchlogs.com/search/do.cgi">data.aolsearchlogs.com</a></p>
<p>Amusing cartoon from xkcd about the logs:</p>
<p align="center">
<a href="http://xkcd.com/c155.html"><img src="http://imgs.xkcd.com/comics/search_history.png" height="125" border="1"/></a>
</p>
<p>(not making light of a very serious issue &#8212; just find the cartoon funny)</p>
<a href="http://www.rimmkaufman.com/rkgblog/tag/aol" rel="tag">aol</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/privacy" rel="tag">privacy</a><p class="akst_link"><div class="sharethisdiv">
<a href="http://www.rimmkaufman.com/rkgblog/?p=105&amp;akst_action=share-this"  title="Email, post to del.icio.us, etc." id="akst_link_105" class="akst_share_link" rel="noindex nofollow">Share this post</a> (via email, Digg, Delicious, etc)
</div>
</p>]]></content:encoded>
			<wfw:commentRss>http://www.rimmkaufman.com/rkgblog/2006/09/26/aol-search-data-release-class-action-lawsuit-filed/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Web Signatures and Soft Cookies: Guessing The Identity of Anonymous Site Visitors</title>
		<link>http://www.rimmkaufman.com/rkgblog/2006/09/24/web-signatures-and-soft-cookies-guessing-the-identity-of-anonymous-site-visitors/</link>
		<comments>http://www.rimmkaufman.com/rkgblog/2006/09/24/web-signatures-and-soft-cookies-guessing-the-identity-of-anonymous-site-visitors/#comments</comments>
		<pubDate>Mon, 25 Sep 2006 02:49:18 +0000</pubDate>
		<dc:creator>Alan Rimm-Kaufman</dc:creator>
		
	<dc:subject>Privacy</dc:subject>
	<dc:subject>Web Marketing</dc:subject><dc:subject>Browsing Data</dc:subject><dc:subject>identifying anonymous</dc:subject><dc:subject>Padmanabhan</dc:subject><dc:subject>signatures</dc:subject><dc:subject>soft cookie</dc:subject><dc:subject>yang</dc:subject>
		<guid isPermaLink="false">http://www.rimmkaufman.com/rkgblog/?p=102</guid>
		<description><![CDATA[Some day, in far distant future -- I'd predict about five years out -- sites might be able to make reasonable guesses as who is using the site, just by their browsing behavior.]]></description>
			<content:encoded><![CDATA[<p>Padmanabhan and Yang published an interesting paper called  <a href="http://knowledge.wharton.upenn.edu/papers/1323.pdf?CFID=1747473&#038;CFTOKEN=77260991">Click Tracks On The Web: Are There Signatures In Web Browsing Data?</a> </p>
<p>Their answer:  yes, there seem to be such signatures.</p>
<p>What&#8217;s a web browsing signature?  And why would online retailers care?</p>
<p>Just people have characteristic walking patterns, typing patterns, and online writing patterns, it turns out that people have characteristic ways of using websites.  </p>
<p>And just as aggregate patterns of whorls and arches in a fingerprint can sometimes identify an individual, statistical measures of web usage can sometimes identify an online visitor.  </p>
<p>In short: even if someone doesn&#8217;t log in to your website, you might be able to make a good guess as to who they are using the time they visit, how long the stay, and how they click across your site.    </p>
<p>You could think of a click signature as a &#8220;soft cookie&#8221; &#8212; you&#8217;re not 100% sure of the user&#8217;s identity, but you might have a reasonable guess.</p>
<p>Not this year, however.  Today&#8217;s sites aren&#8217;t advanced enough, and clickstreams aren&#8217;t well enough understood (or even stored) well enough.    But maybe, some day, in far distant future &#8212; I&#8217;d predict about five years out &#8212; sites might be able to make reasonable guesses as who is using the site, just by their browsing behavior.</p>
<p>How could browsing signatures help an online retailer?</p>
<ul>
<li> Fraud.  P &#038; Y propose this approach as a way to detect possible fraud: &#8220;Alert! The user in session 12345 is attempting to check out using Jane Smith&#8217;s credit card, yet the user in session 12345  uses our site very differently than Jane Smith typically does.  Investigate for potential credit card fraud.&#8221;
</li>
<li> Targeting.  P &#038; Y don&#8217;t discuss targeting, but a site could guess the identity of an anonymous visitor to serve relevant offers: &#8220;Alert! The user in session 67890 has similiar click sigature to Bob Jones, who often buys fishing equipment from us &#8212; serve fishing ads across site to this user.&#8221;
</li>
<li> Multichannel tracking.  P &#038; Y don&#8217;t discuss multichannel, but a retailer might be able to use click signatures to match anonymous web visits back to known web users, and then back to offline marketing: &#8220;Attention! The user in session 456789 has a similar click signature to Mary Thompson, to whom we just mailed a fall test catalog.  That version seems particularly effective at getting older women to our site.&#8221;
</li>
</ul>
<p>Again, this software doesn&#8217;t really exist yet, and won&#8217;t for a long time.</p>
<p>I predict  the major search engines will be among the first to try out this technology: &#8220;The searcher in session 33445566 isn&#8217;t logged in but we suspect it is 123456789 so we can maximize paid click revenue by favoring ads in categories 998, 776, and 554.&#8221;  </p>
<p>It will be several more years before click signatures become standard enough to be rolled into e-commerce platforms for retailers.  (<a href="http://www.google.com/search?as_q=mod_softcookie&#038;num=10&#038;hl=en&#038;ie=ISO-8859-1&#038;btnG=Google+Search&#038;as_epq=Version+4.0&#038;as_oq=&#038;as_eq=%22List-Post%22&#038;lr=&#038;as_ft=i&#038;as_filetype=&#038;as_qdr=all&#038;as_occt=any&#038;as_dt=i&#038;as_sitesearch=httpd.apache.org&#038;safe=off">mod_softcookie</a> standard in Apache 4.0, perhaps?)</p>
<p>Still, it is intriguing to consider the long-term implications of click signatures.  And these patterns remind us, yet again, how <em>non</em>-anonymous our web sessions are.</p>
<p><em><br />
(Tech details: Using ComScore panel data, P &#038; Y looked 50,000 users interacting with the &#8220;5 most popular online sites&#8221; in the data across all of 2004.  P &#038; Y characterized each session using five crude metrics &#8212; session duration, session pages viewed, session average time per page, session start time of day, session start day of week &#8212; and characterized each user-site pair by the mean, median, variance, min and max of these metrics.  P &#038; Y used binary search to find the best level of aggregation for a <a href="http://en.wikipedia.org/wiki/Classification_tree">j4.8 classification tree</a>.  What I find most amazing is that this very crude five metric approach worked at all &#8212; I&#8217;d've thought they&#8217;d need much more detailed click stream information to get any predictive power.)</em></p>
<a href="http://www.rimmkaufman.com/rkgblog/tag/browsing-data" rel="tag">Browsing Data</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/identifying-anonymous" rel="tag">identifying anonymous</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/padmanabhan" rel="tag">Padmanabhan</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/signatures" rel="tag">signatures</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/soft-cookie" rel="tag">soft cookie</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/yang" rel="tag">yang</a><p class="akst_link"><div class="sharethisdiv">
<a href="http://www.rimmkaufman.com/rkgblog/?p=102&amp;akst_action=share-this"  title="Email, post to del.icio.us, etc." id="akst_link_102" class="akst_share_link" rel="noindex nofollow">Share this post</a> (via email, Digg, Delicious, etc)
</div>
</p>]]></content:encoded>
			<wfw:commentRss>http://www.rimmkaufman.com/rkgblog/2006/09/24/web-signatures-and-soft-cookies-guessing-the-identity-of-anonymous-site-visitors/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Fatals To Browser</title>
		<link>http://www.rimmkaufman.com/rkgblog/2006/09/18/fatals-to-browser/</link>
		<comments>http://www.rimmkaufman.com/rkgblog/2006/09/18/fatals-to-browser/#comments</comments>
		<pubDate>Mon, 18 Sep 2006 16:38:35 +0000</pubDate>
		<dc:creator>Alan Rimm-Kaufman</dc:creator>
		
	<dc:subject>Privacy</dc:subject>
	<dc:subject>Miscellany</dc:subject><dc:subject>error messages</dc:subject><dc:subject>hacker</dc:subject><dc:subject>security hole</dc:subject>
		<guid isPermaLink="false">http://www.rimmkaufman.com/rkgblog/?p=96</guid>
		<description><![CDATA[Never send informative error messages to the browser.]]></description>
			<content:encoded><![CDATA[<p>Last night, came across this error message visiting a well-known site:</p>
<blockquote><p>Microsoft OLE DB Provider for SQL Server error &#8216;80004005&#8242;<br />
The log file for database &#8216;xxx&#8217; is full. Back up the transaction log for the database to free up some log space.<br />
/XXXX.asp, line 2208 </p></blockquote>
<p>
Try as much as possible never to send internal error messages to the browser.  Write them to internal logs.  Such public disclosures can provide hackers helpful information to attack your site.   More on <a href="http://www.rimmkaufman.com/articles/web-security-for-catalogers/onepage.html">web security for online retailers</a></p>
<a href="http://www.rimmkaufman.com/rkgblog/tag/error-messages" rel="tag">error messages</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/hacker" rel="tag">hacker</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/security-hole" rel="tag">security hole</a><p class="akst_link"><div class="sharethisdiv">
<a href="http://www.rimmkaufman.com/rkgblog/?p=96&amp;akst_action=share-this"  title="Email, post to del.icio.us, etc." id="akst_link_96" class="akst_share_link" rel="noindex nofollow">Share this post</a> (via email, Digg, Delicious, etc)
</div>
</p>]]></content:encoded>
			<wfw:commentRss>http://www.rimmkaufman.com/rkgblog/2006/09/18/fatals-to-browser/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Staying Private, II</title>
		<link>http://www.rimmkaufman.com/rkgblog/2006/08/24/staying-private-ii/</link>
		<comments>http://www.rimmkaufman.com/rkgblog/2006/08/24/staying-private-ii/#comments</comments>
		<pubDate>Fri, 25 Aug 2006 01:05:30 +0000</pubDate>
		<dc:creator>Alan Rimm-Kaufman</dc:creator>
		
	<dc:subject>Privacy</dc:subject>
	<dc:subject>Web Marketing</dc:subject>
	<dc:subject>SEM</dc:subject><dc:subject>aol search logs</dc:subject><dc:subject>eff</dc:subject><dc:subject>foxyproxy</dc:subject><dc:subject>online advertising</dc:subject><dc:subject>PPC</dc:subject><dc:subject>privacy</dc:subject><dc:subject>tor; foxy proxy; privacy policy</dc:subject>
		<guid isPermaLink="false">http://www.rimmkaufman.com/rkgblog/?p=73</guid>
		<description><![CDATA[Could an increased interest/awareness of online privacy harm online advertisers by hampering their ability to track? No, I don't think so. ]]></description>
			<content:encoded><![CDATA[<p>Surfing the <a href="http://news.com.com/AOLs+disturbing+glimpse+into+users+lives/2100-1030_3-6103098.html">AOL / Google search logs</a> is indeed scary (data <a href="http://data.aolsearchlogs.com/search/do.cgi">here</a>), so I wanted to try out <a href="http://www.eff.org/deeplinks/archives/004868.php">EFF&#8217;s privacy suggestions</a>.  Myself, I found installing <a href="http://foxyproxy.mozdev.org/">FoxyProxy</a> and <a href="http://tor.eff.org/">Tor</a>  to be pretty simple.
<p> Question: Could an increased interest/awareness of online privacy harm online advertisers by hampering their ability to track?  (We online advertisers aren&#8217;t Big Brother, we just need to match ad sales to ad cost to buy more of the effective ads and less of the ineffective.)  </p>
<p> No, I don&#8217;t think so.  I believe the overwhelming majority (guess: 99.5% plus) of <a href="http://www.rimmkaufman.com/rkgblog/2006/08/17/staying-private/">web users won&#8217;t care enough about the privacy issue</a> to change their habits or install anonymizing technology.  The only long-term concern would be if future browsers automatically and by default used proxies and cookie blocking for identity obfuscation, and I don&#8217;t see that happening any time soon.     The greatest impact to online advertisers may be in increased public (mis)perception about tracking and cookies.  Good idea to make sure your <a href="http://www.rimmkaufman.com/privacy-policy">privacy policy</a> is honest, accurate, non-alarming, and written in plain English.</p>
<a href="http://www.rimmkaufman.com/rkgblog/tag/aol-search-logs" rel="tag">aol search logs</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/eff" rel="tag">eff</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/foxyproxy" rel="tag">foxyproxy</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/online-advertising" rel="tag">online advertising</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/ppc" rel="tag">PPC</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/privacy" rel="tag">privacy</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/tor%3B-foxy-proxy%3B-privacy-policy" rel="tag">tor; foxy proxy; privacy policy</a><p class="akst_link"><div class="sharethisdiv">
<a href="http://www.rimmkaufman.com/rkgblog/?p=73&amp;akst_action=share-this"  title="Email, post to del.icio.us, etc." id="akst_link_73" class="akst_share_link" rel="noindex nofollow">Share this post</a> (via email, Digg, Delicious, etc)
</div>
</p>]]></content:encoded>
			<wfw:commentRss>http://www.rimmkaufman.com/rkgblog/2006/08/24/staying-private-ii/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Staying Private</title>
		<link>http://www.rimmkaufman.com/rkgblog/2006/08/17/staying-private/</link>
		<comments>http://www.rimmkaufman.com/rkgblog/2006/08/17/staying-private/#comments</comments>
		<pubDate>Thu, 17 Aug 2006 13:56:50 +0000</pubDate>
		<dc:creator>Alan Rimm-Kaufman</dc:creator>
		
	<dc:subject>Privacy</dc:subject>
	<dc:subject>Miscellany</dc:subject><dc:subject>cookies</dc:subject><dc:subject>eff</dc:subject><dc:subject>login</dc:subject><dc:subject>privacy</dc:subject><dc:subject>track</dc:subject>
		<guid isPermaLink="false">http://www.rimmkaufman.com/rkgblog/?p=68</guid>
		<description><![CDATA[The  EFF has an interesting post on  How To Keep Your Search History Private.]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://www.eff.org ">EFF</a> put up  interesting post on <a href="http://www.eff.org/deeplinks/archives/004868.php">How To Keep Your Search History Private</a>.</p>
<p> Regularly flush cookies?    Takes too much time.  Lose the advantages of logging in?  Too inconvenient.   No vanity searches? Come on &#8212; ego too large.  : )
</p>
<p>
The sensible EFF recommendations are  too complicated for the inexperienced web user and  too inconvenient for the experienced user.
</p>
<p>
Only (1) ardent privacy heads and (2) reasonably  smart badguys will take the time.<br />
For the majority of us, our online search tracks will be logged in the <a href="http://battellemedia.com/archives/000063.php">database of intentions</a> for just about forever&#8230;
</p>
<p> Idle speculation: I wonder if Brin and Page follow the EFF&#8217;s advice?</p>
<a href="http://www.rimmkaufman.com/rkgblog/tag/cookies" rel="tag">cookies</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/eff" rel="tag">eff</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/login" rel="tag">login</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/privacy" rel="tag">privacy</a>, <a href="http://www.rimmkaufman.com/rkgblog/tag/track" rel="tag">track</a><p class="akst_link"><div class="sharethisdiv">
<a href="http://www.rimmkaufman.com/rkgblog/?p=68&amp;akst_action=share-this"  title="Email, post to del.icio.us, etc." id="akst_link_68" class="akst_share_link" rel="noindex nofollow">Share this post</a> (via email, Digg, Delicious, etc)
</div>
</p>]]></content:encoded>
			<wfw:commentRss>http://www.rimmkaufman.com/rkgblog/2006/08/17/staying-private/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
