Assignment of Inventions in Employment Contract for Software Development I have a contract that basically says this in the Assignment section: To the fullest extent under applicable law, the Company shall own all right, title and interest in and to all Inventions (including all Intellectual Property Rights therein or related thereto) that are made, conceived or reduced to practice, in whole or in part, by me during the term of my employment with the Company and which arise out of any use of Company’s facilities or assets or any research or other activity conducted by, for or under the direction of the Company (whether or not (i) conducted at the Company’s facilities, (ii) during working hours or (iii) using Company assets), or which are useful with or relate directly or indirectly to any “ Company Interest” (meaning any product, service, other Invention or Intellectual Property Right that is sold, leased, used, proposed, under consideration or under development by the Company). I will promptly disclose and provide all of the foregoing Inventions (the “ Assigned Inventions”) to the Company. I hereby make and agree to make all assignments to the Company necessary to effectuate and accomplish the foregoing ownership. Assigned Inventions shall not include any Invention that is both (a) developed entirely on my own time, without use of any Company facilities, assets, ideas or direction and (b) not useful with or related to any Company Interest. ...If I wish to clarify that something created by me prior to my employment, which relates or may relate to the Company’s actual or proposed business, is not within the scope of the assignment of Inventions under this Agreement, then I have listed it on Appendix A . If (i) I use or disclose any Restricted Materials (including anything listed in Appendix A) when acting within the scope of my employment (or otherwise on behalf of the Company), or (ii) any Assigned Invention cannot be fully made, used, reproduced, sold, distributed, or otherwise exploited without using, misappropriating or violating any Restricted Materials, I hereby grant and agree to grant to the Company a perpetual, irrevocable, worldwide, royalty-free, non-exclusive, transferable, sublicensable right and license to use, disclose, exploit and exercise all rights in such Restricted Materials, including any Intellectual Property Rights therein. And Assurances: ...I hereby irrevocably designate and appoint the Company and its officers as my agents and attorneys-in-fact, coupled with an interest, to act for and on my behalf to execute and file any document and to perform all other lawfully permitted acts to further the purposes of the foregoing with the same legal force and effect as if executed by me. I have a couple questions. I have inventions which I'd rather not disclose, which I have documented by creating different versions and timestamping them. However, I plan on continuing to develop them on my own time as I work at a company. They are software related. First, the first two highlighted parts seem to contradict each other. The first says whether or not during working hours, the second says it's fine if it's on my own time. Wondering if this is a problem for the contract. Also wondering how valid those statements actually are. Second, they like most other companies want me to list my prior inventions. But I've asked this before to a lawyer and they said I can't simply list a title of a project such as "Photoshop-like image editor", I have to actually go into detail and describe it. And not just a few sentences, but paragraphs of detail. Not so much detail as to be like a patent in its thoroughness, but more detail than a few paragraphs PER INVENTION. But this is a security leak as I don't want to disclose my inventions even if they are simple, it's a matter of privacy. So the question is what I can do or what the reality is of the situation. And last thing is, let's say this company, a software company, is in the field of Sales and Marketing. This means they have a robust application or suite of applications, practices, and tools like CRMs, machine learning stuff, APIs, etc. They also use lots of open source programming tools. Meanwhile, let's say my inventions are in the field of Programming Tools and Application tools. It's not directly related to Sales and Marketing, but it's related pretty closely to CRMs and machine learning tools, and APIs. It's not related to their specific APIs, but it's related to APIs let's say. The question is how the line is drawn on what is considered competitive inventions. If I were to invent a new machine learning algorithm while working as a marketer or sales person at a software company, if that is considered competitive and prohibited by the contract. Oh, and "not useful with or related to any Company Interest" is very vague. The company could be interested in literally anything these days.
the first two highlighted parts seem to contradict each other. No, in this case they do not. The first highlighted portion refers to works or items produced "for or under the direction of the Company", whereas the second highlight refers to your creations that satisfy conditions (a) and (b). Where contradictions actually exist, the doctrine of contra proferentem entitles you (the non-draftsman of the contract) to adopt the portion or reasonable interpretation that favors your legal position. Also wondering how valid those statements actually are They are valid and become enforceable as soon as you sign the contract or your subsequent conduct reflects your acceptance thereof. it's a matter of privacy. So the question is what I can do or what the reality is of the situation The reality is that you are asked to sign a contract that is abusive and ridiculous. One vulnerability from describing your inventions (presumably in Appendix A) is that the employer gets "irrevocable, worldwide, etc" rights on them as soon as you "use or disclose any [items listed in Appendix A] when acting within the scope of [your] employment". This means that if instead of reinventing the wheel you share or apply any portion of your prior creations so as to enhance your productivity, you knowingly and irreversibly grant to the employer perpetual rights to those items. Legal disputes regarding APIs can become extremely intricate. And, since judges usually have no decent background on IT, even those few judges with integrity are unlikely to grasp the key subtleties that would lead to a correct ruling. "not useful with or related to any Company Interest" is very vague. The company could be interested in literally anything these days. Clauses which are too vague or excessively wide-encompassing are supposedly stricken as unconscionable, unenforceable, etc. However, I personally would foreclose upfront the risk of judicial hassle and decline the abusive contract. Legal issues aside, keep in mind that you are offering your expertise (in terms of supply &amp; demand, you are on the supply side). This fact has a less derogatory connotation than "asking for a job". Accordingly, the relation between the parties should be more leveled.
You ask permission, preferably with legal counsel to handle the details. It really is that simple. Unsurprisingly, most companies don't want to give their code away- especially to a competitor. If you even get a response, they will expect something in return i.e. money. Realistically though, it's unlikely they will respond, much less deal with you.
Patents become enforceable when granted, not before. However there is something called provisional rights (absolutely nothing to do with provisional applications). In the US, under 35 USC 154(d), if a claim in a published application is “substantially identical” to a claim that eventually issues, a patent owner can get damages of at least a reasonable royalty on units produced between the publication and notice and the issue date. Enforcement on this must await the granting of the patent. The infringer must have actual notice of the published application. It is rarely invoked see this article.
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.
Does this amount to the employer potentially paying the employee to lie to them, to no ultimate legal effect? Or will the employee have a problem if they end up with an obligation to sign a statement that is not in agreement with reality? Neither. Contract law contemplates a party's subsequent inability to comply with the terms that were established at the formation of the contract. In the Restatement (Second) of Contracts, this is referred to as supervening impracticability. See, for instance, the Restatement at § 261. In the hypothetical scenario you outline, the loss of a company laptop renders the employee's promise (namely, "to return any company-issued computers or devices") impracticable. Instead, the circumstances may entitle the employer to restitution (by the employee) for what the employee now is literally unable to return. That would be cognizable as compliance in substance.
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.
No. Only the company owns the copyright, not its shareholders. A company is a separate legal entity with its own capacity to own property. Copyright is property, not infection that can be spread onto whoever is close enough. Pretty much like shareholders can't just share the use of the company's tangible assets, they can't wet their beaks in the copyright. As a shareholder, what you could do is to appoint a director/CEO that will give you license to copy (or even transfer the copyright) — if you have enough shares to fire the current CEO and put yours. The CEO will get into legal trouble with other shareholders/creditors, but you'll still enjoy your right to copy.
From your question(s), as well as your various comments, I understand you to have two general inquiries: 1. Is there any infringement of copyright laws if you use things like the titles of books, games, apps, names, address (and any other number of things) which you will then put into datasets that will be licensed for proprietary commercial purposes? You may freely put titles, names of people, places or things into datasets without fear that you are infringing on copyright or any other laws. That is clear. Copyright law does not protect names, titles, short phrases or expressions. Even if a name, title, or short phrase is novel or distinctive it cannot be protected by copyright. So, there is no point in discussing the doctrine of fair use in this context, because Fair Use is a defense, or a legal safe harbor that is merely an exception to copyright infringement allowing people to use a copyrighted works under specific circumstances. As I understand your intended endeavor, you will not be infringing on any copyrights to the extent that you are merely using factual data, like names of copyrighted things for the purpose of creating a dataset or an application to help access it. This is why I say you need not concern yourself with the test for Fair Use with regard to this issue. The Copyright Office states clearly, despite what people may think, that there are no exclusive rights in brief combinations of words such as: • Names of products or services • Names of businesses, organizations, or groups (including the names of performing groups) • Pseudonyms of individuals (including pen or stage names) • Titles of works • Catchwords, catchphrases, mottoes, slogans, or short advertising expressions • Listings of ingredients, as in recipes, labels, or formulas. When a recipe or formula is accompanied by an explanation or directions, the text directions may be copyrightable, but the recipe or formula itself remains uncopyrightable. Hence, these things are not registrable under a copyright. While something may be potentially attached to or included in copyrighted material, is not in and of itself subject to the protections of these laws. If it (whatever it is) cannot be registered for a copyright, it is not copyrightable. Because copyright registration/notices have been optional since 1989, when the U.S. attached itself to the Berne Convention, whereby copyright protection is automatic as soon as a work is “fixed in a tangible medium of expression” (written down, recorded, painted, etc.) it’s protected. No notice is required. Registration only becomes required for litigation or enforcement purposes. But this is really extraneous to your inquiry anyway, as far as it applies to the actual data. When you get into copying whole databases for your purpose, that analysis is different. 2. You want to "scrub" the internet for information that you intend to put into your proprietary datasets and use for commercial purposes, some or most of which is already in a database or some organized form, and you want to know if there is some sort of copyright or duty owned to the person who originally databased the materials? Since ideas, procedures, principles, discoveries, and devices are all specifically excluded from copyright protection, if you want to compile this type of information from the internet for the purpose of creating datasets, or searchable databases, this is permissible. That said, there are protections for existing databases under copyright law, provided under the concept of a "compilation copyright". A compilation copyright protects the collection and creative assembling of data or other materials. Compilation copyrights protect the collection and assembling of data or other materials, such that databases are generally protected by copyright law as compilations. Under the Copyright Act, a compilation is defined as a "collection and assembling of preexisting materials or of data that are selected in such a way that the resulting work as a whole constitutes an original work of authorship." 17. U.S.C. § 101. The preexisting materials or data may be protected by copyright since the selections of materials and the form they take in an existing database may be original enough to be subject to a copyright. However, the data itself is merely information and is not protectable. The Copyright Act specifically states that the copyright in a compilation extends only to the compilation itself, and not to the underlying materials or data. 17 U.S.C. § 103(b). As a result, "compilation copyrights" can't be used to place protection upon those things that are otherwise not protectable. In the case of Feist Publications, Inc. v. Rural Telephone Service Company, Inc., the U.S. Supreme Court ruled that a compilation work such as a database must contain a minimum level of creativity in order to be protectable under the Copyright Act. Feist makes clear that even a copyright protected database does not hold the right to prevent an individual from extracting factual data from the database (so long as you're not copying the entire database as a whole). If you take an already compiled and copyrighted dataset in its entirety, you must obtain a license for its use. However, if you are merely amassing great amounts of data to then put into your own dataset, that you are free to do. The big issue will be (and you seem to realize this) where you will amass this data from. Some websites have specific licenses in place that say you cannot use or rework their content. However, many times these websites simply throw these license requirements out there for users to see, despite the fact that they may not be (and some would argue) are not enforceable. The courts have heard arguments that "contracts" (the end-user licenses) that protect databases and information on websites is beyond the protection available through copyright law should be "preempted" by the Copyright Act itself. The preemption argument goes like this: Federal law controlling something that is subject to interstate commerce or use, should be controlled by the federal laws. So,since the federal government has enacted the Copyright Act to govern any protections to any original works, states should be (arguably are) prohibited from having contradictory laws. Because of the ability of a federal statute to preempt state law, and the fact that the Copyright Act at 17 U.S.C. § 301 sets forth specific preemptions, no state may create rights that are equivalent to any of the exclusive rights provided under the Act. It is this concept of preemption that prevents copyright protection from varying depending upon the state where a work of authorship is created. Arguably, the same is true for the internet, and supposed contractual relationship created through licenses that dictates how non-copyrightable material may be used. In the case of ProCD, Incorporated v. Matthew Zeidenberg and Silken Mountain Web Services, Inc. the court examined whether an end-user of a CD ROM phone database was subject to the license, when they extracted a large portion of the database and made it available over the Internet. The database was almost the same as the type of data in the Feist case-The lower court rejected all copyright claims and found that the shrinkwrap license that controlled the end user's right to use the data was both unenforceable (as a shrink wrap license) and preempted by the Copyright Act. As a result, there was no relief available to the creator of the phone database and the end-user was free to extract the data and use it as he saw fit. However, on appeal this decision was reversed (7th circuit). The appellate court did acknowledge that the database (on the CD) was not original enough to be protected by copyright (finding no copyright infringement by the end-user); However, they did find the end-user was breach of contract, since the shrink-wrap license prohibited the end-user's conduct. What this tells us is that these licenses (on websites) may or may not be enforceable. While the 7th Circuit found a contract right pursuant to the license, despite the preemption argument, another appellate court that is more liberal may find otherwise. Also, this was a disk, not the internet, which is the "wild west" of information, largely unregulated and unlitigated as it pertains to the legality and enforceability of (some) regulations that do exist. License agreements for site use on the internet are everywhere. If you take a database from some site that has a license saying you cannot take their work and add to it, or whatever, and you do add it to other databases that are not licensed and then make your own dataset - chances are you are NOT going to be infringing on anyone's copyright. That said, you may be in breach of contract (the license) if they find out about it, and sue you (using it doesn't put you in breach; only getting sued and having a court determine you're in breach puts you in breach. It may be a distinction worth contemplation, but that is up to you). The safest, bet would be to get a license from them to rework the materials. If the material is generic enough, and will be changed enough, that you are creating your own new (copyrightable) work - I'm not sure how they would know you "scrubbed the data in contravention of their license agreement ( I have NO CLUE if there is coding or metadata attached to it such that it's identifiable in that way. I have not tech background and do not endorse taking what's not yours). But if they can and do know, they could cause problems for you. Lastly, I will just say that the internet is littered with sites that claim copyrights, or impose unenforceable licenses on material that is ripe for public use. Just because it says it's theirs does not make it so. The inverse is also true. Just because a site does not claim copyright to something, does not mean it is in the public domain. I would recommend either sticking to public domain/use sites for your scrubbing endeavors, or seeking permissions from the sites who impose licensing requirements. Short of that, I would recommend (as I already have) seeking an formal legal opinion to say that you are not imposing on anyone's copyrights (this could only be done once you showed an attorney every place you took material from, as well as what the material is), and that the licenses from sites with generalized information that may try to limit use, are unenforceable. I would do this before you invest a lot of time or money into something that is largely based on the accumulation of other peoples work product. I wish there was an answer certain, but there just isn't without seeing everything in the end.