How to protect my idea in another country? I have an idea about possible creation of a product that in my opinion would be on demand among smartphone users. I have found a potential company In Switzerland and I think about offering them my idea. I am planning to patent my project before presenting it to them, however it seems like it would cost me a lot of money to apply for a patent in Switzerland due to my financial capabilities and considering that I am from a different country it is impossible for me to apply for a patent, but I really need to somehow protect my project before showing it! Do you know another way to do it? I would be glad to hear your opinion about this issue!
You can file a U.S. provisional patent application now, which you can then convert into a regular ("nonprovisional") application within a year. The provisional application is relatively simple and inexpensive, and it will give you an opportunity to explore your business possibilities and assess whether you want to spend more money on patent work later. It will also leave your options open for filing a PCT (Patent Cooperation Treaty) application that can be the basis of a later application in Switzerland (and many other countries as well, if you so choose). This way, you won't have to pursue the expensive translation and European filing fees until much farther down the road, but you'll still have the benefit of the original filing date of the provisional application. Another benefit of the provisional application: if you aren't ready to convert it within a year, you can simply abandon it and it will go unpublished, keeping all the information in it secret.
There are three questions relevant to this issue: Who owned the copyright in the first place? Was the copyright transferred? If not, was a license given to the site to use the content? In general, under most countries' laws, the person who creates an original work owns the copyright. The person with the copyright has the right to copy and distribute the work, and the right to prevent others from doing so. In some cases, such as where a work is created as a "work for hire" by certain employees under certain circumstances, the initial copyright is held by a third party. You will need a lawyer familiar with your jurisdiction and your circumstances to determine if this is the case. Finally, even if you own the copyright, you can license others to use your content. This may be in an express written document, or it may be an implied license--implied, for instance, by the act of posting it on their blog. The existence and scope of such a license is, again, something that will have to be determined based on your country's specific laws and your specific situation. The bottom line is: if you submitted articles to that blog, you can't complain that they posted them. Depending on the license in effect, you might be able to get them taken down, or you might not. You need a lawyer, not the internet, to tell you what your rights are in this very specific case.
could this mean my employer owns the idea and anything I develop --since I would use the same technology for my idea that I do at work? No, unless by &quot;technology&quot; you mean the employer's materials or resources (see condition 3 of the clause). Your remark that &quot;this is completely and utterly unrelated to [employer's] business model&quot; survives items 1 and 2. Likewise, working on your idea outside hours survives the corresponding part of item 3. Would this also mean that any open-source software I develop outside of work automatically belongs to my employer? No, unless the software you develop is &quot;based on [your] knowledge [etc.] of (COMPANY)&quot;.
It depends upon how much money is at stake. You could have a patent search done and consult a patent lawyer help you to evaluate your risk based upon the results. This would cost several thousand dollars but probably less than $10,000 (these amounts are much less than the cost of trying to get a patent for your app). If you do this and there is anyone who has an arguable infringement claim, you would ultimately have to decide for yourself, informed by the search results and your patent lawyer's advice, what to do. Even in a low risk case, you might be sued. Even in a high risk case, the patent holder might decide not to sue you for some reason (patents of the kind you are worried about are weak and often don't hold up in court, about 50% of patent cases that go to trial end up finding that the patent is invalid and that would be higher with a patent of the type you are worried about, but of course, it costs money to go to trial so people often pay nuisance settlements to avoid litigation). You could, instead, launch your app without a patent search and see if anyone sends you a cease and desist letter and then decide what to do from there, possibly consulting a patent lawyer at that point if necessary. It only makes sense to search in advance if your investment and potentially profits from the app are significantly greater than the cost of the patent consultation. If you've invested $100,000 in making the app and expect to make $200,000 of profits from the app, you should definitely confer with a patent lawyer up front. If you've invested $1,000 in making the app and expect to make $2,000 of profits from the app, you should move forward until such time, if ever, as you receive a cease and desist letter from someone claiming to have a patent that covers your app. Somewhere in between those amounts, what to do is a business decision and a judgment call.
Ideas aren't property Your employer does not own your ideas. However, neither do you. Ideas are not something that is protected by intellectual property law. To be IP, you need more than an idea. What is IP? The most common types are: Patents - protect inventions and new processes Trade marks - protect logos, words and other branding Copyright - protects art, writing, music, film, and computer programs Registered designs - protects the visual design of a product Circuit layout rights - protect layout designs or plans of integrated circuits used in computer-generated designs Plant breeders rights - protect the commercial rights of new plant varieties. The normal operation of IP law is that if a person is engaged under a contract of service (e.g. an employment contract) then their employer owns all the IP they make which includes progress towards something that might be IP (e.g. all the work that leads up to a patentable invention). However, if they are engaged under a contract for service (e.g. an independent contractor), then the worker owns the IP. The work the employer owns is generally limited to work in the course of the employment. So if you are a software developer they will generally own all code you write that is useful for their business but won't own the romantic novel you write in your spare time. In either case, the specific contract can override the default assumption. What can you do? You can certainly use the idea for the app but you can't use anything that is subject to your employer's IP. That means you can't use any code or copy the user interface - it all has to be redeveloped from scratch. You also can’t develop something that would be of use to their business while you are still an employee.
There is something called the exhaustion doctrine that says that once the holder of a patent sells a patented device, they have relinquished control over that particular instance of the patent implementation. Anyone who legally purchases this hardware has the right to run whatever software they want on it, as long the software is otherwise legal (software designed to defeat DRM would be an example of software that is is not legal).
If you have a truly novel and non-obvious game idea, you could patent it, and that would cost many tens of thousands of dollars if not hundreds of thousands of dollars (U.S.) in legal fees, etc. and probably a couple of years of patent prosecution, if your idea has not already entered the public domain through public display or sale. Most ideas for games are either not novel, or would be obvious to a person skilled in designing games. But, if your idea is really and truly new, you could do it.
Basically, you cannot do it. You are required to include the MIT license in any derivative work. However, that holds only for the parts that you import from this other project. You can identify which parts of the final product are copied from the MIT-licensed program (and indicate "these parts are subject to the following MIT license"), and then you can do whatever you want with the remainder that you wrote. The downside of not licensing your material is that nobody can use it. To use it, people would need permission, which is what a license is. If you don't license it, you don't give permission, so people can't use it. You presumably want to subject your own contribution to different licensing conditions, so then you would state those conditions and clearly indicate what parts of the code you wrote.