<?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: Privacy Policy Generators, Creators, and Makers</title>
	<atom:link href="http://www.allwebdesignresources.com/webdesignblogs/graphics/privacy-policy-generators-creators-and-makers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.allwebdesignresources.com/webdesignblogs/graphics/privacy-policy-generators-creators-and-makers/</link>
	<description>Web design resources and graphics blog with lists of useful web site design tools, utilities, and articles for web designers.</description>
	<pubDate>Fri, 12 Mar 2010 16:51:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Peter Schaefer</title>
		<link>http://www.allwebdesignresources.com/webdesignblogs/graphics/privacy-policy-generators-creators-and-makers/comment-page-1/#comment-18980</link>
		<dc:creator>Peter Schaefer</dc:creator>
		<pubDate>Fri, 12 Dec 2008 15:11:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.allwebdesignresources.com/webdesignblogs/?p=434#comment-18980</guid>
		<description>Though privacy policy generators make a good effort to facilitate the seemingly daunting process of writing a Privacy Policy, i feel compelled to recommend to anyone who is considering the use of such generator to reconsider writing the document himself. I myself have wondered whether a generator would save time - a very misguided thought as it turns out. No privacy policy generator can truly capture the essence of your business accurately. Privacy Policy generators create very skimpy default content by replacing standard input fields such as  with your entries. This hardly saves time, nor does it return value. If you are in dire need of a Privacy Policy I recommend reading a Privacy Policy of your relevant competitors and drafting your own version of these policies. 

Best of luck,
&lt;a href="http://www.lautusdesign.com" title="New York Website Design" rel="nofollow"&gt;Lautus Design&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Though privacy policy generators make a good effort to facilitate the seemingly daunting process of writing a Privacy Policy, i feel compelled to recommend to anyone who is considering the use of such generator to reconsider writing the document himself. I myself have wondered whether a generator would save time - a very misguided thought as it turns out. No privacy policy generator can truly capture the essence of your business accurately. Privacy Policy generators create very skimpy default content by replacing standard input fields such as  with your entries. This hardly saves time, nor does it return value. If you are in dire need of a Privacy Policy I recommend reading a Privacy Policy of your relevant competitors and drafting your own version of these policies. </p>
<p>Best of luck,<br />
<a href="http://www.lautusdesign.com" title="New York Website Design" rel="nofollow">Lautus Design</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Graphic Design Online &#187; Privacy Policy Generators, Creators, and Makers</title>
		<link>http://www.allwebdesignresources.com/webdesignblogs/graphics/privacy-policy-generators-creators-and-makers/comment-page-1/#comment-17658</link>
		<dc:creator>Graphic Design Online &#187; Privacy Policy Generators, Creators, and Makers</dc:creator>
		<pubDate>Mon, 01 Dec 2008 09:55:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.allwebdesignresources.com/webdesignblogs/?p=434#comment-17658</guid>
		<description>[...] Read full entry [...]</description>
		<content:encoded><![CDATA[<p>[...] Read full entry [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
