Does my employer own code I write at home using the Visual Studio license from work?
<p>Simple question, maybe not an easy answer: my employer gave me an MSDN subscription linked to my home hotmail account.</p>

<p>Can I download Visual Studio and write code at home with this license? I would be working after business hours on my own personal projects.. Would my company own the personal project because I used their Visual Studio license?</p>

<p>edit: just to be clear: my personal project is a video game, and my company does not make games, and in fact is in a completely different industry</p>

<p>If the code is unrelated to your employment you own the copyright no matter if it is written in Visual Studio, on a piece of paper or tattooed on your butt. In the same way a sculptor owns the copyright in their sculpture even if they use someone else's chisel.</p>

<p>Using Visual Studio in this way may, however, violated your contract with your employer and/or their contract with Microsoft. Why go there? Visual Studio Community is free.</p>

<p>This would be an <a href="https://softwareengineering.stackexchange.com/questions/86555/do-i-own-copyright-of-program-i-made-in-own-time">interesting stackexchange post</a> to read. Not much legal content here but probably the same situation.</p>

<p>For the sake of a good legal argument:</p>

<p>Focussing on work for hire, since employer-employee relationship is clear and under no controversy here.</p>

<p>It is well settled law that employer own's the work product and can't have any claim on personal projects. In US, UK or common law the employer is treated as the first owner, but not deemed to be the author. Whereas in Civil law jurisdiction like Germany the ownership rights are firstly linked with the author and employer gets the ownership rights by assignment or contract. </p>

<p>Common law policy cites reason for first ownership to employers because employers provide infrastructure and facilities so that creative works can take place. This is seen as contribution of employers towards production of new works. Also they are in better position to market and exploit the product. And further to cut the transaction cost for assignment of rights like in civil law. Employees are rewarded by pay, continued employment, promotion etc. [Source: Bentley &amp; Sherman]</p>

<p><strong>The only test for this proposed question is to see whether a work is produced in the course of employment.</strong></p>

<p>It does not necessarily means the office working hours or produced at home with personal resources.</p>

<p><strong>Missing Link Software v. Magee</strong> [1991] FSR 14: </p>

<p>An employee wrote software outside work time and on his own equipment. Court found 
it to be in the course of employment and employer was given the ownership rights. </p>

<p>Reasoning: Employee was hired to write programs of the kind in dispute. It fell within the scope of tasks he was employed to carry out and he was employed at the time of writing it.</p>

<p>As I also said the area/project for which you are writing program, its proximity  with the employer's business and your duties at employment are going to be a major factor.</p>

<p>This will depend on jurisdiction, and on your employment contract.</p>

<p>In Germany, if you are a regular employee (<em>abhängig Beschäftigter</em>), then by default <strong>your employer owns all the rights to use to works you produce "to fulfill the duties imposed by the employment"</strong> (<em>in Erfüllung seiner Verpflichtungen aus einem Arbeits- oder Dienstverhältnis</em>, <a href="https://dejure.org/gesetze/UrhG/43.html" rel="nofollow noreferrer">§43 Urheberrechtsgesetz</a>).</p>

<p>So anything you produce as part of doing your job belongs to the employer(*). Conversely, if you do anything not related to your job, it's yours. It does not matter if you did it on company time or using company equipment - that may violate your employment contract and may get you fired, but does not by itself assign any rights to your employer.</p>

<p>(*) You still retain <em>authorship rights</em>, such as the right to be named as the author. These rights are inalienable in Germany (unlike e.g. in the US). However, the employer receives all rights that are practically relevant, such as the right to use and copy.</p>

<hr>

<p>Of course, in practice the boundary between "job duty" and "private work" may be a bit blurry, so it's best to play it safe and keep private stuff at home. But using a software license provided by your employer will not give them any rights to the work you produce.</p>

software