Assignment of Inventions with Employer I have signed assignment of inventions with my employer. The exact wordings is not available to me - however I remember vaguely that it dealt with all inventions by employees being company's property. My question is if I invent a system or develop a product in my spare time (outside office hours) and using my own personal resources (laptop, devices, personal time and effort etc...) will that still be in danger of being attacked by assignment of inventions? Can I safely assume that such property will fully be mine? (I am asking because I remember reading in a reputed book - Business Law for Entrepreneurs) that any invention/developed product can be claimed by employer even if it is produced outside normal hours of employment with personal resources - Since it is done during the term period of employment. I would love see someone shed light on this aspect since the above sounds too draconian.
The answer will depend upon the state law that is applicable, assuming you are in the U.S. Patent law is federal law but patents and patent applications are considered personal property, like a car, and the ownership and transfer of that property is governed by state law. The terms you imagine are in your agreement are too draconian in California, for example. Please get a copy of what you signed and edit your question to include key points and indicate your state.
You say the permission was "public", therefore I am going to assume that it cannot be argued that there was no agreement. There are two possibilities: If Company B has given consideration for the promise then there is a binding contract and Company A may be able to end it but could not seek redress for when it was in place. If there is no contract then the principle of promissory estoppel should have essentially the same effect. An agreement, including an IP licence, does not have to be in writing nor does it have to have any particular form.
Critique I'm technically a director of a company ... You either are or you aren't - there is no "technically" involved. ... is not currently trading ... And doing nothing can create a conflict of interest? How? You mustn’t be involved either directly or indirectly with any other trade or business competing in or conflicting with the interests of our Company. "competing or conflicting" is the key here - if the "other trade or business" can adversely affect the performance of your employer then you have a conflict, if not, you don't. are only related in such that they are both technology based but otherwise are unrelated. Sorry, but that is so vague as to be totally useless - what company today is not "technology based"? Pharmaceutical companies are technology based, so are construction companies, so are law firms but one would hardly call them "related". Solution Conflicts of interest are easy: If you don't think you have a conflict of interest and they don't think you have a conflict of interest then you don't have a conflict of interest. If either or both of you do; then you do. Tell them about it! Conflicts of interest are a problem because people think that if you are keeping secrets then you are doing it for a nefarious purpose! In 90% of cases declaring the potential conflict resolves the conflict because the other party says "That! Don't be silly; that's not a problem!" or words to that effect. In the 99.9% of the remaining 10% of cases then sensible people can come up with sensible solutions, for example: If you want to be involved with another business whilst working for us then you’ll need to get a letter from the Director of your area confirming that they’re happy for you to do this.
As far as I can see this means that I sign away any rights I currently have to any IP and also that I sign all rights to any IP I create whilst working for the company. The hiring manager says that I have this wrong and that it only means anything related to work that I would undertake during my employment with the company. Based on the quoted language, the hiring manager is correct. The key phrase is &quot;all rights to all material created in the course of your employment with the Company&quot; This means things created as part of your new job. It does not mean copyrights or other IP you now own, nor does it mean rights to things you create outside of work hours, unrelated to your job, not as part of any work assignment, and not created on work premises or using work equipment. You might want to confirm this by talking with a local lawyer with some IP experience and some employment law experience. A one-time consult should be available at a fairly small cost. The section about &quot;whether now existing or created in the future&quot; refers not to existing IP, but to existing kinds of IP and existing laws. If the UK should pass a new &quot;algorithm rights &quot; law next year, this language attempts to make sure that such rights are covered without needing you to sign a revised contract. Note that this phrase occurs as part of the definition of the term &quot;Intellectual Property Right&quot;, and it is limited by the phrase &quot;in respect of the material created by you in the course of your employment.&quot; A contract that attempted to claim all existing IP you may hold that is unrelated to your employment, or one which tried to claim IP having no relation to your future employment might be held void as against public policy. In any case, if it was ambiguous, any such ambiguity should be resolved against the drafter of the contract (here the company) and in favor of the other party. A separate email might be taken into account as showing what your &quot;meeting of the minds&quot; was with the company insofar as the contract language is ambiguous. It will not, however, be effective in changing the plain meaning of the contract.
The idea for an app is not subject to copyright. Only the artifacts of the app itself (sourcecode, images, texts, sounds, etc.) can be. So if one only copies the idea and creates their own version of all the other assets, then they are not violating copyright. However, in some cases, ideas can be subject to patents. But patents on software are tricky. First of all, only new ideas can be patented. When a supposed new idea was already published before, then that's called &quot;prior art&quot; and you can not patent it. Then getting a patent means a lot of investment in money and time (which is very different from copyright which you get automatically the moment you make something copyright-worthy). So not everything that could theoretically be patented gets patented. And then, many jurisdictions do not recognize software patents at all, and those which do have different limits on what is and is not patentable when it comes to software. This means patents are rarely a concern when copying the app idea of someone else, but not never. And another possible concern is the third pillar of intellectual property: Trademarks. This protects the name of the app. Trademark law oversimplified forbids to create a competing product with a name which might confuse customers. So if you created StevesSuperCoolAppForCoolPeople and I create StevesSuperCoolAppForCoolPeople - Simplified Edition, then I would be violating your trademark, because my product name sounds as if it was your product, when it is in fact an unrelated product with a similar purpose.
The general rule is that the author of the software owns the copyright, so that would be the student. This is regardless of whether the student writes the code for fun, or for a thesis. If a student is hired to write that code, then it kind of depends on the university rules, and who hires the student. In the case of a "work for hire", the employer owns the copyright. However, it is non-trivial to determine whether that principle is applicable in the case of a student hired by the university. In part, it depends on which country this is in because work for hire laws are not exactly the same everywhere, and in part it depends on the details of the employment my a university. In a typical US institution RA appointment, it would come down to university policy – some universities declare that copyright in all student-written software is retained by the student. You would need to look for something resembling an "IP Policy" – here is a sample, note that such policies are subject to revision.
If you are on Tier 4 (students on full-time degree), you have more restrictions besides the number of hours. One of this is no self-employment (which includes freelance and consultancy or creating your own company).
Person A has to have created the data to hold copyright; for most kinds of data this has no legal effect because facts are not protected by copyright. A mineable database probably does not have the necessary creative elements for copyright. An algorithm is not protected by copyright (it might be patented). Person C's program is copyrighted. The product created by D is probably copyrighted, depending on what degree of creativity is involved in their transformation. If the transformation is automatic then no, but if creative judgments are applied to the output of the program then maybe. Though the resulting product is another database of facts, and the facts cannot be protected. In terms of "using the model", only C and possibly B have any control. If it is necessary to validate the software using A's data and A has kept the data secret, C might negotiate with A to use the data, in order to complete his program, and that could give A some interest in the program.