What qualifies as a Non-Compete Clause So I'm 17 and for the past few months I've been working on a programming project. My intent is to use the code for profit in the future, and because of that I've been reluctant to recruit others to work on the project. Before vacation my Entrepreneurship teacher told me something about a Non-Compete Clause, a document that if I get someone to sign online offers me legal protection from them stealing my code. I'm not sure how to set one of these up though, and if I screw this up I could potentially lose months of hard work? Any advice for confused teenager?
A noncompete clause is a section of a contract whereby one party agrees not to compete with another party. These agreements are usually (always) limited as to time, geography, and scope. In other words, if you had a dog-walking business in your neighborhood you might like to hire someone to help walk some dogs. You'd like this person to agree not to compete with you. You charge people $10 per walk and you pay this person $5 per walk so you want to stop them from walking your customers' dogs for $7. In order to get the $5 per walk from you, your employees agree to not go into the dog walking business in your neighborhood for one year. Cat-sitting? Fine. Walking dogs in other neighborhoods? Fine. Walking dogs in your neighborhood 12 months and one day after they stop working for you? Fine. The reason for the limitations is that judges throw out agreements which are too restrictive. You could not require that a person agree to never walk a dog ever again. You could not stop a person from from walking a dog anywhere in the world. You could not stop a person from working any job for any of your customers. The laws about restrictiveness are unique to each state so that's why people recommend that you talk to a lawyer. Judges honor the work you've done to build a customer base and will allow you to protect it, but they're not going to let you keep your people from ever working in the same business again. The non compete describes the limits of the protection. You need to make sure that the code that others create for you in your employment is yours. It's always a good idea to get the specifics in writing just in case something wacky happens where it looks like someone other than you might own work created while working on one of your projects. The water gets pretty muddy when people are working on their own time with their own tools, it could be very easy for them to argue that they created a thing for their own use and provided it to you for your limited use but that they otherwise own it. This is not a noncompete. It's an ownership clause, aka an IP clause.
You can't You agreed: by submitting Materials in any form to the Company, in addition to other provisions of the Terms, you automatically grant Company a royalty-free, world-wide, irrevocable, non-exclusive, and assignable right and license to use, copy, reproduce, modify, adapt, publish, edit, translate, create derivative works from, transmit, distribute, publicly display and publicly perform such Materials for the purpose of displaying and promoting the Materials on any website operated by, and in any related marketing materials produced by, the Company and its affiliates. They can keep and use your data forever and give it to whoever they want. The clause you quote doesn't alter that. All it says is that once a year, if you ask, they will tell you what information they shared and with whom. If they feel like it they will tell you how to get the information deleted.
Impressum Requirement Wow, based on your citations, you've done a lot of research on this topic. I'm just going to add one more reference, which is from the same site as your first German citation and has incredibly detailed and judicially referenced information on almost everything related to the Impressum. All my non-GitHub links are to sections of that page. Based on your research, I'm going to take it for granted that you understand that according to the Telemediengesetz (TMG), an Impressum is required on a web page if it is &quot;business-like&quot; (geschäftsmäßig), or if it helps, I prefer to word it as &quot;potentially commercial.&quot; I would have to argue that open source projects have to be seen as inherently &quot;business-like&quot; for the purposes of the TMG for two reasons: Some other legal person may have similar software as part of their business and might have the need to serve legal notifications to the owner of a GitHub project (TMG § 8 gives competitors the right to sue). Think potential copyright violations here. It is possible to build a more traditional commercial business around open source, for example what Canonical is doing around Ubuntu. Additionally, the common legal advice is to even include an Impressum on a personal blog, though I'm not aware of any court case having occurred at that level yet. In my opinion, a GitHub account can be seen as more &quot;business-like&quot; than a personal blog, and would follow that advice out of caution. I'll note that the XING situation you bring up is complicated. It centers over whether the content of XING pages is &quot;business-like&quot; according to the TMG. It may well turn out that some pages will need an Impressum and others won't. As for placing it in the project's readme.md, that might work but I have two concerns: The courts have essentially stated that the text of the link must imply that the required information under TMG § 5 is located there. For example, the words Impressum and Kontakt work, but the word Information does not. To me, &quot;readme&quot; is not sufficient, but this concern might be negated by the fact GitHub by default renders the readme.md directly on the project home page. While it has been ruled that the Impressum does not necessarily have to be directly on the home page (for GitHub, that would be the company's/users profile page), it must still be readily available in an intuitive location. I don't know if putting it in a project page satisfies the legal requirement. If it was sufficient, it's also likely that each project would have to have an Impressum so that it can't be missed. Examples The dominant pattern that I could find1 on GitHub is an off-site link to the Impressum contained in the profile page's byline right underneath the title. Examples: https://github.com/sedadigital, https://github.com/comsysto, https://github.com/znes, https://github.com/eSagu, https://github.com/TIBHannover. I'm almost certain this meets or exceeds the legal requirements. Example screenshot: Additionally, I found a few that had a repository specifically for an Impressum. Example: https://github.com/johsteffens. Since these repositories were clearly visible on the user's main page (either because there weren't enough repositories to make them span multiple pages, or because it was specifically pinned to the main page), I would argue these also meet the legal requirement for being readily available. While I didn't find any examples of it, another possibility would be to combine the above two approaches, having a link in the byline that links to an Impressum repository or some other page within GitHub. This would be useful if you didn't otherwise have an Impressum hosted elsewhere. There were also scattered examples of people placing an Impressum on a project wiki page or on an impressum.md file at the top level. However, none of the users I looked at were consistent in doing this across all their projects. Also as previously mentioned, it's questionable whether not having it on the main user profile page meets the legal requirement. The Wiki page in particular I don't think meets the requirement that it can easily be found. Found using the following Google search: site:github.com impressum -impressum.php -impressum.html -impressum.jsp -impressum-manager -github.io -issue. Exclusions meant to filter out a lot of false positives, mostly projects for websites that had their Impressum in code format meant for deploy and not for display on GitHub itself.
Contracts can say all sorts of unenforceable things, you provided an example of one of them. A person cannot be compelled to stay and work somewhere they no longer wish to work. At the risk of getting my wrist slapped for straying too far into the land of opinion, a clause like this is likely intended to take advantage of naive teenagers who will provide free employment referrals because they think they have to.
With respect to the first question, discussing an idea in a non-encrypted email is not a publication that forfeits the right to patent an idea, even though it is not 100% secure. In the same way, talking about an idea for a patent with your patent lawyer in a secluded booth of a coffee shop in person does not constitute publication of the idea for this purpose, even if someone is secretly spying on you at the time. Since I am at the moment employed by a company, even though the idea originates from myself, it seems that I should quit my job first not to have my current company have any claim over my idea. It is possible that the contract makes even ideas that you come up with yourself while employed by the company the property of the company. If so, you are legally in the wrong and the idea belongs to the company. But, proving the reality that you are stealing the idea from the company is harder if there is nothing in writing. An email discussing an idea while you are employed would have to be disclosed in litigation with your employer over whether the patent applied for belongs to you or to your employer under an employment agreement. If you didn't put it in an email, it wouldn't exist to turn over in litigation.
Restraint of trade clauses are tricky. They are only enforceable if there is a legitimate interest which needs to be protected and only to the minimum extent needed to protect that interest. Therefore, you must have specific business knowledge (algorithms, code, customer information etc.), not general knowledge (stuff taught in schools or generally available) and preventing you working for a competitor is the only reasonable way of protecting it. If this is so then 6 months is not unreasonable. Assuming that the clause is valid then for you to take a job with a competitor is a breach of contract and you would be subject to all the normal sanctions including an injunction to stop and damages. Your new employer is not exposed as they are not a party to the contract, however, if you are forced to breach your new employment contract then they can sue you too. In both cases the employer has to initiate action and it may not be worthwhile. You can take the risk if you want but you should seek legal advice.
Is there any legal doctrine whereby E's agreement with A continued to apply to E in his work for company N? No, because the parties to the non-compete agreement were Employee E and company A, not the human who owned and sold A. What about B? Do they have any standing to block E's going to work for a B's customer? No. My rationale is that the decisions you describe result in a waiver of the non-compete clause. An employment relation between B and E never existed. Thus, the only vestige of B's non-compete rights binding E that could have been preserved stem from E's former employment at A. However, that vestige disappeared at the instant B --apropos of the hospital project-- waived its non-compete clause with N. Given B's waiver with regard to N, N's failure to establish a non-compete clause with E enables the latter to conduct business with (or accept employment at) the hospital. If anything, B would have standing to sue N for negligence or related torts. But neither B nor N has any viable non-compete claims against E.
Can the name of my LLC include the phrases "Software Engineer", "Software Engineering", or similar derivations thereof? No. Not based on what you've posted. Go to the definitions to see how engineer is defined. It may be they are talking about actual structural engineers or environmental engineers, where if you're wrong people die. But based on above, you can't use the word engineer unless you're licensed as such. Is there even a license for computer engineer? This seems more like it could be a term of use but not actually descriptive of what you're doing. IDK. You'd have to see the definitions and exceptions. Can my resume, curriculum vitae, or my advertising or promotional materials accurately report the subjects I studied in college as the subject matter of "Software Engineering", to the extent that this information is true and accurate? Yes, your CV is supposed to say what you have done, and learned and especially published (lest it's just a resume), but the answer as far as promotional materials, is NO. This, because you don't post your cv on your ad's and if you put that, you will likely be found to be trying to pose as a licensed professional based on a technicality. If that happens the licensing authority will probably censure you by disallowing a license when your qualify. If asked directly by a client, am I even allowed to divulge my area of study accurately,(of course, but you'd also have to divulge the fact that you are not licensed and cannot act in that capacity) Would it be a violation of the law to claim I had engineering knowledge since I have studied (and practiced) software engineering in the past (for instance, at previous places of work in states which did not have these kinds of limitations, or for corporations which did not offer my services to the general public)? It could be if the person reports that you are soliciting work as an engineer w/out a license. It's like a person who went to law school, passed the bar, but never got sworn in. They cannot solicit business as a lawyer. Unless there is a license for being a computer programer, there is nothing barring you from using that terminology. You could be, that if you look up the definition prior to the statue, that it says something like "for the purposes of this section the term engineer means…", In which case it doesn't even apply to you.