Closed Source License with No Liability?
<p>I’m writing a closed source program with a small group of people. We will be distributing it without the code, but I’m worried about two things:</p>

<ol>
<li>If my program deletes the user’s files or causes any damage of any type, my team and I don’t want to be in legal trouble. Since it includes a web server we don’t want to get in trouble if the server breaks or goes down, causing business problems or anything else. </li>
<li>If the source code is leaked in any way, I want to not permit anyone who comes across it to distribute it. If that’s not possible, I don’t want anyone to distribute it modified. </li>
</ol>

<p>Are there any rock-solid licenses that will solve these problems? I’m in the United States, but hopefully it would be applicable elsewhere. Sorry if this the wrong site, please transfer it if it is. </p>

<blockquote>
  <ol>
  <li>If my program deletes the user’s files or causes any damage of any type, my team and I don’t want to be in legal trouble. Since it
  includes a web server we don’t want to get in trouble if the server
  breaks or goes down, causing business problems or anything else.</li>
  </ol>
</blockquote>

<p>In your Terms and Conditions (T&amp;C) or End User License Agreement (EULA), be sure to clearly address items in the sense that:</p>

<ul>
<li>use (and perhaps installation?) of the application is at the user's
risk;</li>
<li>by using the application the user agrees to release you from any
liability for any harm or losses the application might
cause to users' files &amp; systems or to any
third-party files &amp; systems;</li>
<li>the user is entirely responsible for thoroughly testing whether the
application is suitable for Production, or you can outright state that the software is not for use in Production.</li>
</ul>

<p>By reading other software licenses, you surely will have noticed that some of this types of clauses in T&amp;C/EULA are commonplace. The key is to be <em>upfront</em> to users on what to expect and/or what not to expect, preferably without the extensive legalese and fine print that is present in many "agreements".</p>

<p>Searching for certain keywords, such as <a href="http://www.leagle.com/leaglesearch?exact=end%20user%20license%20agreement" rel="nofollow noreferrer">End User License Agreement</a> or <a href="http://www.leagle.com/leaglesearch?all=software%20liability&amp;exact=end%20user%20license%20agreement" rel="nofollow noreferrer">this other query</a>, will surely be illustrative of these and other matters/concepts you need to know.</p>

<blockquote>
  <ol start="2">
  <li>If the source code is leaked in any way, I want to not permit anyone who comes across it to distribute it. If that’s not possible, I
  don’t want anyone to distribute it modified.</li>
  </ol>
</blockquote>

<p>You can include clauses to the effect of copyright protection, although I think that enforcing it is pretty much impossible or impractical.</p>

united-states software licensing privacy liability