<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>data retention - Securing Innovation</title>
<link>http://www.securinginnovation.com/articles/innovation_management/</link>
<description></description>
<language>en-us</language>
<copyright>Copyright 2008</copyright>
<lastBuildDate>Wed, 16 Jan 2008 14:02:54 -0500</lastBuildDate>
<pubDate>Mon, 10 Nov 2008 04:11:56 -0500</pubDate>
<generator>http://www.movabletype.org/?v=3.34</generator>
<docs>http://blogs.law.harvard.edu/tech/rss</docs> 

<item>
<title>The Disconnect Between IP and Data Retention Policies</title>
<description><![CDATA[<p class="MsoNormal">In the wake of all the corporate misdeeds of the early 2000&rsquo;s, a lot of corporate attention is now focused on data retention policies. New eDiscovery guidelines for Electronically Stored Information (ESI), Sarbanes-Oxley requirements, and HIPPA have companies of all sizes scrambling to put in place rules that govern how long data is kept around. </p>
<p class="MsoNormal"><o:p></o:p>Data retention policies define how long data must be stored. The philosophy is that data should be deleted in its entirety as soon as it is no longer needed for either a business or regulatory purpose. Let&rsquo;s be honest, &ldquo;data retention&rdquo; really means &ldquo;data destruction&rdquo;. The real goal of these policies is to avoid future legal problems by getting rid of data on a schedule . Companies want to do this as soon as they are no longer legally responsible for the data.<o:p> <br />
</o:p></p>
<p class="MsoNormal">Given that data lifecycles vary a lot, most retention policies are based on classes of data. Classes group like types of data together. You can then assign each class its own retention policy. Each policy must account for a number of factors, especially the lifespan of data. One class of data (for example check images) may have a retention policy of years. For another, it might only be weeks. My shopping list has a lifespan of only about two hours.<o:p> <br />
</o:p></p>
<p class="MsoNormal">Intellectual property, as a class, has a very long lifespan. At any point in time, there may be a need to produce prior art. This is true long after a copyright, patent, or trademark is no longer in force. For trade secrets, the lifespan of the data may be the lifespan of the business. A great example of long-lived intellectual property is the formula for Coke. It has been kept a trade secret for over 100 years. <br />
</p>
<p class="MsoNormal"><o:p></o:p>Unfortunately, practically all corporate information can contain important intellectual property. That PowerPoint presentation used for internal sales training might contain your new secret sauce. How about that ancient product design? Absolutely. It&rsquo;s full of prior art, some of which might still be found in your current products. Even the agenda for last week&rsquo;s engineering meeting might contain valuable information that, in the future, may help provide the central idea for a new product line.<o:p> None of this can be thrown away automatically.<br />
</o:p></p>
<p class="MsoNormal">This presents an obvious disconnect between many data retention policies and intellectual property needs. To resolve this situation it's important to keep at least one copy of anything that <em>might </em>have intellectual property in it. It is also important to have a process in place to review potential intellectual property.&nbsp; <em>No matter how you do it, wholesale deletion of data without review will inevitably result in the destruction of valuable intellectual property.</em><o:p></o:p></p>
<p class="MsoNormal">At the end of the day, it&rsquo;s important to remember that nearly infinite lifespan of intellectual property means nearly infinite retention. Otherwise, you may not be able to back up a claim or&nbsp; will inadvertently reveal a trade secret.&nbsp; <span style="">You might also find yourself without that great idea that has suddenly become really important. <br />
</span></p>]]></description>
<link>http://www.securinginnovation.com/2008/01/articles/innovation-management/the-disconnect-between-ip-and-data-retention-policies/</link>
<guid isPermaLink="false">http://www.securinginnovation.com/2008/01/articles/innovation-management/the-disconnect-between-ip-and-data-retention-policies/</guid>
<category>Innovation Management</category><category>data retention</category>
<pubDate>Wed, 16 Jan 2008 14:02:54 -0500</pubDate>
<author>tpetrocelli@ip.com (Tom Petrocelli)</author>

</item>


</channel>
</rss>