copyright california intellectual-property
To what extent, if any, do I have ownership over, and rights to, works I create on my own time?
<p>I am a software engineer in California. If I create a piece of software, <em>in my own time, using my own equipment</em>, do I own the copyright on that creation, or does my employer?</p>

<p>I see things such as <a href="https://github.com/snapframework/snap-server/commit/5e4850d4cb74c75e706df509b90befc95263746a" rel="noreferrer">"Google asserts copyright, even on work I do in my own time"</a> (<a href="https://news.ycombinator.com/item?id=1969979" rel="noreferrer">HN discussion</a>). In the HN discussion, someone asserts,</p>

<blockquote>
  <p>California law is pretty clear, if you do it on your own time, on your own equipment, it's yours.</p>
</blockquote>

<p>Sadly, he does not cite a source for this. The closest I'm able to find is in California's Labor Code §2870,</p>

<blockquote>
  <p>(a) Any provision in an employment agreement which provides that an employee shall assign, or offer to assign, any of his or her rights in an invention to his or her employer shall not apply to an invention that the employee developed entirely on his or her own time without using the employer’s equipment, supplies, facilities, or trade secret information except for those inventions that either:</p>
  
  <ol>
  <li><p>Relate at the time of conception or reduction to practice of the invention to the employer’s business, or actual or demonstrably anticipated research or development of the employer; or</p></li>
  <li><p>Result from any work performed by the employee for the employer.</p></li>
  </ol>
  
  <p>(b) To the extent a provision in an employment agreement purports to require an employee to assign an invention otherwise excluded from being required to be assigned under subdivision (a), the provision is against the public policy of this state and is unenforceable.</p>
</blockquote>

<p>However, this uses the text <em>"rights in an invention"</em>; does that cover copyright? (Is this the correct law?) Does "Relate … to the employer's business" cover the entirety of software engineering, or just the particular software engineering my employer does? Otherwise, what law is there that backs up the above claim, if any? Or does my employer own copyright on everything down to the love letters I write?</p>

<blockquote>
  <p>However, this uses the text "rights in an invention"; does that cover copyright?</p>
</blockquote>

<p>Yes.</p>

<blockquote>
  <p>(Is this the correct law?)</p>
</blockquote>

<p>It certainly seems to be.</p>

<blockquote>
  <p>Does "Relate … to the employer's business" cover the entirety of software engineering, or just the particular software engineering my employer does?</p>
</blockquote>

<p>Imagine that you work for a company that writes trading software.  In your spare time, you develop a photo editing tool.  Do you think a court would find that your project "related to the employer's business"?  I do not.</p>

<blockquote>
  <p>Or does my employer own copyright on everything down to the love letters I write?</p>
</blockquote>

<p>Google does not own everything their employees create; they only claim to.  If someone challenged them on it, a court would decide, and probably not in their favor. </p>

<blockquote>
  <p>Does "Relate … to the employer's business" cover the entirety of
  software engineering, or just the particular software engineering my
  employer does?</p>
</blockquote>

<p>Entirety? That's a very loaded word. Elements of software engineering go beyond the type of engineering. For example if you spent all your time at work developing an innovative workflow which allowed coding faster and more accurately, the employer owns the workflow. If you then utilized this workflow to support your off-the-clock software creation efforts (of a software product different from your employer's) you will find yourself in a gray area. (Of course that assumes that the workflow is protectable.)</p>

<p>It's not just time and equipment that create software. </p>

<p>As was stated, this sort of thing comes down to what your employer tries to assert and how hard they push, and then how hard you push back. This pushing is often motivated by the financial value of the work and you might be able to resolve the problem through licensing agreements.</p>
