Can a group continue with app development without the member who originated the idea? Following situation: 5 friends started an app together: The idea guy, a designer, backend, android and iOS engineer. The friends worked on the app for roughly a year however the idea guy started getting more and more angry about the project taking too long to finish. Eventually he started threatening us to shut down the project if we don't work faster and tried to replace members. We refused and he eventually 'stopped' the project by removing access to all servers and cancelled paid accounts to Github and Co (most of them were held by shared accounts where he wasn't even the one paying them) Now, the 4 of us are not happy about this at all since we worked for 1 year almost every day on this thing and in our opinion this 1 guy does have no right to decide whether the project is dead or not so we want to finish it without him: Put together some money, re-purchase servers and so on. The idea guy incorporated a real company on paper but none of us signed anything, nor did he pay any of us. There are also no patents or anything like that. (When we asked him a few times to finally get the paperwork done he always avoided the question which seemed to be like he never really intended of sharing anything with us from the beginning.) The idea guy also mentioned very strongly that this idea is his property and he will pursue legal actions if we do anything without him. Certain assets like sounds, a few graphics and the project name were created by him which is obviously his IP. If we were to remove this, could the 4 of us legally continue with the project under a different name?
There is no IP in ideas Any code would by subject to copyright (who owns that copyright is itself a convoluted and separate question), however, if the 4 of you abandoned any existing code, notes and images and start over you would have no legal impediment.
You need a lawyer There is no magic phrase to do what you want. The company will care about defending their assets, while you will want to defend yours. Only a lawyer will be able to tailor the condition that makes sense based on what your job's domain covers and your side projects. It is entirely possible that your personal projects conflict with your employer's, and you must then put your personal projects on hold or risk getting sued. e.g.) developing two pieces of software that does the same thing. Your lawyer will be able to advise on how that looks and what to do. No random strangers on the internet can give you accurate advice.
I would argue that no, there is no copyright for the restored work. Independent copyright is only possible for any original material added, as previously discussed on this site. In this case, the added work was a technical process rather than a creative process, and technical processes cannot be protected by copyright. Copyright licenses would therefore be ineffective. However, I believe one could still impose a license based on owning the copy as opposed to the copyright (contract might be a better term in this case). However, if a third party managed to obtain a copy through some other avenue, any such contract would not be binding on them and nothing could be enforced against them unlike with copyright laws. Another way a license might be imposed is through patent protections, as technical processes can be protected via patents. However, I'm not as familiar with patent law, and this doesn't appear to be the claim being made.
You don't say what jurisdiction's patent laws you're interested in, and priority dates can differ in different schemes. I'm answering as to U.S. law only. In the United States, under the current hybrid "first-inventor-to-file" system, the priority date--the date that determines who "wins" if there are multiple claims to a specific invention--is, with some exceptions that I won't go into, the date of your first application. In other words, the date that the PTO got it in the mail. Once your application is submitted, it is--again, with some limitations I won't get into--prior art for the purposes of any later-submitted application. They can't get another application later, grant it first, and then deny your application based on the later-submitted application. Your application date would still win out. Could someone in the USPTO slip your application out of the stack, fudge the dates, and convince some other company to submit a similar application to get priority over you? Not as a practical matter, no. The USPTO isn't one guy in a room; it's a large organization, and the person who opens the mail, types in your application details, and sends you a receipt, isn't the same guy who knows whether your invention is any good or not. And, frankly, very few patentable inventions are going to be worth someone risking their job and/or jail time over--especially when there would be significant evidence of the misconduct--for example, your patent agent's files. So what are the chances that the examiner on your patent: 1) Is a nefarious character who has lived a life of public service long enough and wants to go rogue; 2) Has a friend in the mailroom who is also an expert in the field of your invention; and 3) Has a conduct in industry who is willing to break the law for the rights to your invention? Slim to none. And if you have an invention that is really so revolutionary that it's going to be worth so many people risking so much to steal it, odds are there will be other evidence that you were the inventor.
Use of SE is subject to the terms and conditions specified here. Section 3 says "You agree that all Subscriber Content that You contribute to the Network is perpetually and irrevocably licensed to Stack Exchange under the Creative Commons Attribution Share Alike license." That means that your contributions can be used forever. That means the stuff is there, end of story. Section 11 on Termination says "Stack Exchange may also terminate, block, or suspend any and all Services and access to the Network immediately, without prior notice or liability, in its sole discretion, for any reason or no reason at all, including but not limited to any Subscriber breaches of any of the terms or conditions of this Agreement". That means you can be banned. So, yes, what they did is legal.
Germany may be different, however in the United States this would be considered work-for-hire and the employer would be the rightful owner of the source code. Regardless of jurisdiction, and from a more practical point of view, you are better off not having a copy of the source code. Using it as reference or example in the future could easily turn into (unintentional) copyright infringement. If, in the future, you write code you would like to be able to freely keep and reuse in any project, make sure the owner/employer licenses it using something like the BSD, MIT, or ISC license.
How to send a document restricting its spread? In theory you could have the company sign a Non-Disclosure Agreement (NDA) prior to sharing the details of your project. However, your chances of enforcing the NDA seem negligible except maybe for George White's suggestion about a patent application. It is otherwise in your best interest to think of another way of showcasing your skills set. Assuming that the company signs your NDA, you have no realistic way to prevent the company from misappropriating (i.e., stealing) your idea(s). You will have no access to the company's systems to ensure that it has deleted all copies and records that could result in unauthorized disclosure. Even if you find out that the company misappropriated your information, it could be too late because the statute of limitations expired, and/or too costly --not just in terms of money-- to bring court proceedings for misappropriation.
There are basically two kinds of things one could do. One could assign or transfer intellectual property rights and contracts related to the app to the entity, or one could license the intellectual property rights to the entity. Generally speaking, in a related party transaction, everything should be in a signed writing, and a notice of the transfer of an intellectual property right that has been registered or filed with a government agency should be provided to the government agency in question. Since there are potentially copyright, patent, trademark, publicity, and contractual rights that might be associated with the app, each aspect which exists should be transferred or licensed, as the case may be. While the forms to do this aren't particular long, the concepts involved and correct terminology are subtle, so this would not be a wise undertaking to attempt on a do it yourself basis.