Prove my work is not a trade secret violation I have recently developed a medical software application. One of my previous employers X (from 4 years ago) sells a similar application. (You can see where this is going.) X 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 X. X 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. My software simply provides a different way of managing practice that has not borrowed anything from X's software. I did sign a confidentiality agreement with X. But my system employs a non-secret process, and every feature in my system is based on knowledge generally available to all. The agreement also has a non-compete that states I cannot work for a competitor while I am employed with X. 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. Anyone has experience going through a similar scenario who can help me prepare a good reply? This is essentially what the letter from X says: X has recently learned that you are marketing a software product competitive with X’s software product which incorporates concepts, ideas, layouts, and designs from X’s software product. Similarities between your product and X’s product suggest that you have misappropriated confidential information from X, including software source code, as well as failed to return all confidential information to X upon your termination. To the extent you have created products using X's confidential information, those products are owed solely by X. Moreover, you are hereby notified that under your Confidentiality Agreement, you are prohibited from using or disclosing confidential information obtained and retained from X. 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. X hereby reserves all rights, claims, and causes of action.
Prove my work is not a trade secret violation Please don't. It's not your job to prove your innocence. The burden is on them 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. 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). 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). 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. 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). 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.
&quot;Wholly unconnected with your employment&quot; means exactly that. Anything that is not connected to your functions or processes that you use in the course of your employment that your employer would have an interest in either protecting or marketing. Writing a book about software development If you are just a software developer, this would be fine unless you were talking about a process unique to your employer. If you worked in a publishing house that wrote software development books, this would be connected and must be disclosed to your employer. Releasing an open source piece of software not specifically aimed at the industry the company is in Again, this probably fine not to disclose since it would not be something you would develop as part of your employment, or under the umbrella of your company focus market. Release a commercial piece of software not specifically aimed at or competing with the industry the company is in Same as above. Honestly though the best policy is being open. If you come to your company with your idea and tell them that it doesn't have any applications in your industry and would like to develop it in your own time, they would have a much harder leg to stand on in a court case when they finally figured out how to apply it.
The exact laws will vary by region and country, but the laws will range anywhere between illegal and almost illegal. If you want to operate as legal as possible then you will have to disclose to the buyer that the software is malware or a crypter and you should require for the buyer to sign an agreement to only use the software for legal and educational purposes. Hiding the disclosure in a long Terms of Service agreement will likely not be sufficient. You will have to explicitly advertise that the software is malware and a crypter and that you are looking for reputable tech firms to buy your software in order to improve their software. If you sell software without disclosing to the customer that the software contains malware or a crypter then you are exposing yourself to a lawsuit for products liability, invasion of privacy, fraud and misrepresentation, the cost of damages, and possibly criminal liability.
The fact that a developer is showing off work that he/she has done for other another company doesn't imply that that developer owns any copyright to the work. In Canada, see the Copyright Act, § 13 (3): Where the author of a work was in the employment of some other person under a contract of service or apprenticeship and the work was made in the course of his employment by that person, the person by whom the author was employed shall, in the absence of any agreement to the contrary, be the first owner of the copyright and § 13 (4): The owner of the copyright in any work may assign the right... In the US, see 17 U.S.C. § 201 (b): In the case of a work made for hire, the employer or other person for whom the work was prepared is considered the author for purposes of this title, and, unless the parties have expressly agreed otherwise in a written instrument signed by them, owns all of the rights comprised in the copyright. and § 201 (d): The ownership of a copyright may be transferred... "What rights should and should not be attributed to the developer?" That is a business decision to be made on a case-by-case basis. Advice about the prudent balance of copyright between an employer/client and employee/contractor is legal advice. "Is it okay to use this projects as part of the developer's portfolio?" If the developer can link to public use of a product that he/she developed for a company, then the developer is not violating copyright by simply advertising that they worked on the product and linking to, without reproducing, the work. If the developer for whatever reason maintained copyright ownership in the code and other assets, it would not be copyright infringement to reproduce those as part of the portfolio. If the developer did not maintain copyright ownership in the code or assets, reproducing those may be copyright infringement, dependent on whether the copyright owner allowed the developer to reproduce those elements, or if the reproduction is fair use. There may be other laws or contracts implicated, though: non-disclosure agreements, trademark law, among others.
This can't be right. If I modify open source code as part of the work done, by nature of the open source license that code can not become intellectual property of the client. Certainly it can. That which is "developed or produced" would be the modifications to the pre-existing code, i.e the copyright on the derivative work so created. If the base code was under a share-alike or copy-left license, then the client can only distribute it under the same license (or a compatible one, perhaps). But nothing compels the client to distribute it, and for the client's use, the client owns the copyright, without fear of any future claims by the contractor. If I have my own code/scripts/settings/templates/etc that I use as a contractor, and I modify those in the interest of coding efficiency in the interest of serving the client, it hardly seems correct that these assets become property of the Client. Those are your work, and you can choose whether to sell the copyrights to the client or not. Again, only the work done for that client would be covered under the wording quoted above, unless there is another provision that grants the client a license to use the pre-existing work which you modified for the job, which there probably ought to be. Or I suppose the agreement could assign copyrights in pre-existing work to the client, but that seems an odd choice, and the language in the question would not do that. You and the client could agree on a different provision such as: The contractor grants to the client a fully-paid, non-exclusive permanent license to use all intellectual property developed under this agreement, and any pre-existing works that may be incorporated therein. The contractor warrants that s/he is entitled to grant such license, without infringing on the intellectual property of any other person or entity. That wording would have the contractor retain all copyrights and other IP, but provide a license to the client to use it without further payment or expiration. Many other ways to structure such a provision are possible, dividing the rights up however the contractor and client can agree. The price for the work might vary depending on what rights the client obtains. Both forms, and many others, are perfectly legal, it is just a question of what the contractor chooses to sell, and what th4e client chooses to buy.
"Pastiche" is a literary, not a legal term, and as a professional coder, I would not use it to describe code that to some extent imitated other code. The legal question here is: is your code a derivative work of the code it is based on, and if it is, did you have permission to make that work. Copyright, in an Berne Convention country, which includes the EU, does not protect ideas and concepts, it protects expression. It protects the choices of words and symbols, and other forms of expression. If all you did was study example code, presented for educational purposes, and then write code that performs a similar function, using the same general techniques, then I don't think you have infringed copyright. That, after all, is why people post code to Stack Overflow and similar sites, to allow them to learn how to use specific coding techniques, including in commercial projects. I have used techniques posted to SO to do coding as part of my paid job. The usual test for copying under US law is "substantial similarity". This takes into account cases where there is essentially only one way to say or code something. I don't know the exact tests under the various laws of various EU countries, and they will not all be the same. But I suspect that on this point they are, well, substantially similar :). I can't advise on your specific situation. But if it is as described, I don't think you have a problem.
This supposes that the patentable concept can’t be learned form the operation of the whole program and hiding the invention while making use of the invention in public is not a disclosure. However, in the US there is a famous case In re Blaisdell, 242 F.2d 779, 783, 113 USPQ 289, 292 (CCPA 1957); Hall v. Macneale, 107 U.S. 90, 96-97 (1882); Ex parte Kuklo, 25 USPQ2d 1387, 1390 (Bd. Pat. App. &amp; Inter. 1992) that concluded a public demonstration that didn’t expose the inner workings did start the clock on a bar to patentability. See previous question https://patents.stackexchange.com/questions/20886/would-the-demonstration-of-an-invention-be-considered-public-disclosure The answer (from me) has the caveat that this is a pre-AIA case and courts might come to a different answer under that current law. The U.S. has viewed public use, especially commercial public use, as disqualifying (after a grace period) but the rest of the world puts its emphasis on actual disclosure of the inventive concept so this result might be different elsewhere. One thought experiment would be to analogize with an article in a widely available journal with the words Don’t read the article that starts on page 19 on the cover. From a disclosure point of view I do not think that is different from it being possible, but illegal, to read.
Ideas (methods of playing, game mechanics, strategy, goals) cannot be protected by copyright. But any part of a creative work can. So, no copying of drawings, patterns, images, sounds, or the element. I suppose copying the software code is not an issue here, but it can, obviously, also not be copied. And nothing in your game can look like someone's else trademark.