copyright intellectual-property non-compete
Prove my work is not a trade secret violation
<p>I have recently developed a medical software application. One of my previous employers <em>X</em> (from 4 years ago) sells a similar application. (You can see where this is going.)</p>

<p><em>X</em> is now alleging that I might have stolen the code and created my own version but that is truly not the case: Every line of code has been written from scratch, and is entirely different from that of <em>X</em>.</p>

<p><em>X</em> is also alleging trade secret violation (without even looking at the software) but everything this software does is based on public domain knowledge. Managing patients, Exams, Bills, etc. are all public knowledge. Specific tests that go in each exam have been made based on material read from books that I can prove.</p>

<p>My software simply provides a different way of managing practice that has not borrowed anything from <em>X</em>'s software.</p>

<p>I did sign a confidentiality agreement with <em>X</em>.  But my system employs a non-secret process, and every feature in my system is based on knowledge generally available to all.</p>

<p>The agreement also has a non-compete that states I cannot work for a competitor while I am employed with <em>X</em>.</p>

<p>The agreement was signed in year 2001 in Oregon. I am now in Canada and my company is registered in Canada, trying to sell software in United States.</p>

<p>Anyone has experience going through a similar scenario who can help me prepare a good reply?</p>

<p>This is essentially what the letter from <em>X</em> says:</p>

<blockquote>
  <p><em>X</em> has recently learned that you are marketing a
  software product competitive with <em>X</em>’s software
  product which incorporates concepts, ideas, layouts, and designs from
  <em>X</em>’s software product. Similarities between your
  product and <em>X</em>’s product suggest that you have
  misappropriated confidential information from <em>X</em>,
  including software source code, as well as failed to return all
  confidential information to <em>X</em> upon your
  termination. To the extent you have created products using <em>X</em>'s
  confidential information, those products are owed solely by <em>X</em>.
  Moreover, you are hereby notified that under
  your Confidentiality Agreement, you are prohibited from using or
  disclosing confidential information obtained and retained from
  <em>X</em>. Failure to comply with this obligation will
  result in immediate legal action against you and any persons acting in
  concert with you to seek injunctive relief, compensatory and treble
  damages, and attorney fees. <em>X</em> hereby reserves all
  rights, claims, and causes of action.</p>
</blockquote>

<blockquote>
  <p>Prove my work is not a trade secret violation</p>
</blockquote>

<p>Please don't.</p>

<p>It's not your job to prove your innocence. <strong>The burden is on them</strong> to be specific, explain fully, and prove specific claims about your actions. In other words, don't justify, don't explain, and don't defend yourself to them. </p>

<p>It's actually best you do not say anything to them, and just forward the letter to your legal counsel (Since you're selling software to be used in the medical field, I assume you already have some kind of legal counsel). </p>

<p>For instance, even saying something as innocuous as "Managing patients, Exams, Bills etc are all public knowledge." could be used against you. Because it establishes the fact that you've been working on those features with them and that you've been working on those features with your new company (which doesn't necessarily follow, for all they know, you could have purchased a library module from someone else with those exact features). </p>

<p>In other words, even if you were to reply with such an innocuous-sounding statement, you could be saving them months of cross-border discovery and litigation about some of their claims (even if you believed you were being entirely reasonable by defending yourself). But at the same time, don't take what I'm saying to mean that you should lie to them about which features you recently worked on. </p>

<p>When I say that you shouldn't be talking to them. I mean that you should not be talking to them. You shouldn't be engaging with them and you shouldn't be giving them any shred of information whatsoever (implied or otherwise). It's not your job to make their job any easier. Do not reply to them. Don't even acknowledge the receipt of the letter (unless you already did by signing for it, which can't be helped). </p>

<p>Use a legal intermediary. Give the letter to your own legal counsel (whether you signed for the letter, or not) and leave any reply to him or her (assuming he/she thinks this warning letter even warrants a response). And if this former employer gives you a phone call, kindly refer them to your legal counsel without saying another word. </p>

<p>The code is one thing, but what about <strong>concepts, ideas, layouts, and designs</strong>?</p>

<p>Setting aside the question of the appropriate court for this action (Federal Court in Oregon or a court in Canada) you need to really think about your product and any components of the product which find their most minuscule source at Company X. Not that you will be liable for these tiny things, but they are the threshold level for where your analysis needs to start.</p>

<p>The problem here is not just trade secrets but any intellectual property including design and layout which could raise trade dress issues. Of course, that stuff is not secret. Ideas on the other hand - they will need to prove that you used ideas which a) are independently valuable because of their secrecy and b) actively protected.</p>

<blockquote>
  <p><strong><a href="http://www.oregonlaws.org/ors/646.461">Oregon Uniform Trade Secret Act</a></strong> Trade secret means information, including a drawing, cost data, customer list, formula, pattern,
  compilation, program, device, method, technique or process that:<br>
  (a) Derives independent economic value, actual or potential, from not
  being generally known to the public or to other persons who can obtain
  economic value from its disclosure or use; and<br>
  (b) Is the subject of efforts that are reasonable under the
  circumstances to maintain its secrecy.</p>
</blockquote>

<p>and </p>

<blockquote>
  <p><strong>Canada's <a href="http://www.ulcc.ca/en/uniform-acts-new-order/older-uniform-acts/537-josetta-1-en-gb/uniform-actsa/trade-secrets-act/730-uniform-trade-secrets-act-1989">Uniform Trade Secrets Act (1989)</a></strong> "trade secret" means any information that</p>
  
  <p>(a) is, or may be, used in a trade or business,<br>
  (b) is not generally
  known in that trade or business<br>
  (c) has economic value because it is
  not generally known, and<br>
  (d) is the subject of efforts that are
  reasonable under the circumstances to prevent it from becoming
  generally know.</p>
  
  <p>(2) For the purposes of the definition trade secret "information"
  includes information set out, contained or embodied in, but not
  limited to, a formula, pattern, plan, compilation, computer program,
  method, technique, process, product, device or mechanism.</p>
</blockquote>

<p>In Oregon, a person might reply to such a letter with the question: <em>So that I may properly respond to your letter, please tell me which <strong>concepts, ideas, layouts, and designs</strong> are trade secrets and how I have misappropriated them.</em></p>

<blockquote>
  <p>The employer is now alleging that I might have stolen the code and created my own version but that is truly not the case. Every line of code has been written from scratch.</p>
</blockquote>

<p>This should be easy to demonstrate if it comes to that. There are automated tools which can measure similarity of source code pretty reliably (up to renaming and reordering). You could get an expert witness to endorse the results of such a comparison if it's not possible to do it convincingly yourself.</p>

<blockquote>
  <p>The employer is also alleging trade secret violation (without even looking at the software) but everything this software does is based on public domain knowledge. Managing patients, Exams, Bills etc are all public knowledge. Specific tests that go in each exam have been made based on material read from books that I can prove.</p>
</blockquote>

<p>Your employer will bear the burden of proof to show you are using their trade secrets. That means they will need to demonstrate you are doing something that they figured out how to do and that it's not something that's generally known in the industry. Consider what, if anything, makes your software unique - how is it different from your former employer's offering and from the offering of other companies? If it doesn't do anything not done by others besides your former employer, you have nothing to worry about. If it does things your employer's software doesn't, you're probably still OK, unless the employer can show that you knew they were planning on this new feature and just got to it first. If your software does some things that were unique to your former employer's software, then you need to concentrate on those things and figuring out whether you might have unwittingly used their trade secrets in your program. If the stuff is trivial or obvious, you may not be in trouble; but you might be if nobody else is doing it (since if it were useful and obvious, it stands to reason others would be doing it too).</p>

<blockquote>
  <p>Anyone has experience going through a similar scenario who can help me prepare a good reply?</p>
</blockquote>

<p>There are a few strategies here. Have their lawyers contacted you in writing? If not, you might simply ignore these complaints if you feel you are genuinely in the right. IF you have been contacted by their lawyers, you could either ignore it unless they sue, or you could discuss it with a lawyer and have a formal response written based on the merits of the former employer's claim. If you have already been sued, absolutely go get a lawyer and start figuring out whether you are in the clear (that's what it sounds like based on your perhaps biased description) or in the wrong (even if unintentionally).</p>

<p>By the way - what is your former employer asking you to do? Pay them money? Take your site down? I wouldn't do any of it without having a lawyer tell me to but if they just want an acknowledgment or something it might be easier to get it in writing and do what they want. But I wouldn't take the site down or pay them anything without the lawyer.</p>

<p>Note that you might be in violation of a non-compete clause separately from claims of copyright or trade secret violations. Even if it's your own code and your own ideas, even demonstrably so, you might be prevented legally from benefiting from them for some period of time and in some market. If you have a non-compete with them and you're in a jurisdiction which recognizes it as valid, you are almost certainly in violation and I'd go see that lawyer yesterday.</p>

<p>I am not a lawyer. I am not a lawyer.</p>

<p>They can reverse engineer your code to prove their secret has been stolen. As Stephan Branczyk points out, your help is not needed in this process. Your lawyers only response should be:</p>

<blockquote>
  <p>No trade secrets were stolen, all demands are refused. (or whatever the technical term is, i am neither a lawyer nor a native speaker)</p>
</blockquote>

<p>I wouldn't even ask or discuss what trade secrets exactly, they have to come forward with a valid claim. Don't give them anything except the one line, maybe after concrete claims add:</p>

<blockquote>
  <p>Your letter from Nth October does not contain a valid claim about stolen property, ...</p>
</blockquote>

<p>They could be trying to get hands on your code because it does something cool they want or because they want o falsify evidence that you stole from them. If ever, only give the code to a court appointed expert.</p>

<p>And really, don't talk to them, not in letters, mails, chats, not on the phone, not in person, never. Whatever they do, always just point them to your lawyer and make clear they are paying his fees because of their unsubstantial claims.</p>

<p>Btw, I wrote a medical patient database a while back, I think you both stole my trade secrets! I was for example using a database, with tables, and it had an UI .. it just doesn't sound like the kind of software where you can have trade secrets like some cool algorithms or lots of research to get it running.</p>

<p>Also be aware the might find your post here, so don't disclose too much, what could be stolen or not.</p>

<p>Prepare for many rounds of "you have stolen" .. "have not" .. document everything, you will need it, don't give them new information, never get emotional and escalate. Really, this could run for years like this, make sure you get to the i-don't-care-about-their-claims state pretty fast or they will win by annoying you out of business.</p>

<p>Your non-compete timeframe doesn't start when you signed the non-compete, it starts when you actually separate from them.  For instance, you signed in 2001, worked until 2011, and now it's 2015.  If, for example, your non-compete period was 5 years, you are still within it.</p>

<p>However, more and more courts are striking down onerous, career-killing non-compete clauses as being overreaching and not tenable.  Especially for those who are not equity-owners.</p>

<p>I agree with the earlier answers that suggest you limit your discussions with Company X.  The letter they sent was a fishing expedition, you have no responsibility to respond, and depending on how you <em>do</em> respond, it could open you up to a further discovery/subpoena process.  For example, if you even said that it was you that wrote the new code, they can establish plausibility that a trade secret <em>may</em> have leaked, even if perhaps inadvertently, and use that as a valid reason to demand discovery.</p>

<p>If you reply at all, say something to the effect:  "Dear Company X, we are in receipt of your letter dated mm-dd-yyyy. You've made some incendiary and concerning claims, which are however too generalized for us to determine their merit or lack thereof.  Thank you, Company Y."</p>

<p>In legal terms, they have no valid claims. What's more important is to know what they want to achieve.</p>

<ol>
<li>Do they fear your competing product and want to ban it from the market?</li>
<li>Are they looking for some compensation payment i.e. free money?</li>
<li>Does someone there dislike you and just wants to hurt you?</li>
<li>Does someone feel injustice has been done and wants to see justice?</li>
<li>Do they just want to put on a show so other employees don't get encouraged to actually steal trade secrets?</li>
</ol>

<p>If it is number 1, their lawyer will already have told them that they can try to scare you into voluntarily retracting the product and if that doesn't work they are out of options. A letter from a lawyer should end this.</p>

<p>If it is 2, the mere mention of a lawyer will make the problem going away, because their costs will be higher than their profit.</p>

<p>If it is number 3, you need to be careful about contacting them. If you call them over the phone (unrecorded) they can later claim you admitted stealing trade secrets during that call, or you threatened them, which can make court costs more expensive.</p>

<p>If it's number 4 you have an actual problem. If you still have friends at the company you might be able to make them talk sense to the person responsible.</p>

<p>If it's number 5 they just want there to be a short and very cheap fight, which will probably mean just a few letters from a lawyer from each side. </p>

<p>The best option is, if you still have some old friends at the company who you can trust, ask them what's going on. Knowing what exactly is going on may allow you to resolve this quickly and free your mind from any worries.</p>

<p>Also respond to their letter in writing, rejecting their claim while giving as little information as possible. If they want to look at the code tell them "no". Giving them information willingly lowers their cost which is not something you want to do.</p>
