Live data from Hacker News

Ask HN:Do my company own IP when I work on my personal app in freetime?

news.ycombinator.com

11–13 of 13 posts

Re: Ask HN:Do my company own IP when I work on my personal app in freetime?

#11
post #3

It depends on the law in your jurisdiction and, potentially, on promises you may have made in your employment agreement. Many jurisdictions will allow employers to enforce an IP agreement which you made as a condition of your employment, and employers in both these and under jurisdictions at least theoretically state claims to such IP in a lot of employment agreements or in appendixes to them. (e.g. buried in the Com…

Absolutely agree. I used to work in Vegas. An engineer colleague of mine specifically took a job there because (at that time?) Nevada was the only state, or one of very few, where an employer could not lay claim to his side projects - and he had at least one patent that I know of.

If you are in a place where the employer can lay claim to your side work, then that means you need them to agree to not do so in your contract. There is a demand for software engineers now, so they should sign it.

Re: Ask HN:Do my company own IP when I work on my personal app in freetime?

#12
IANAL but the issue simplified -> You own IP if:

(Developed while not employed) || (Developed in (California||Delaware||Illinois||Minnesota||North Carolina||Washington) && Developed on your own time using your own hardware) || (Your employment agreement/contract specifically assigns you IP rights)

Re: Ask HN:Do my company own IP when I work on my personal app in freetime?

#13
post #4

Read the contract you signed when you started working there - this is the kind of thing that should be covered! If you don't have a contract, then you have bigger problems anyway.

If you don't have a contract or your contract doesn't specifically mention IP you should not tell your employer about what you are doing. But approach your HR and explain the situation that you are thinking of developing an app which is unrelated to the company's lines of business and that you will be doing this entirely for your own education and in your own time using your own computer etc. Put in those terms they should not have a problem with it. Make sure you get it in writing to avoid future misunderstandings / contradictions. Then after a suitable delay, you could release your app.

As other people have pointed out, you could release your app under a different company - but then you have a similar situation of technically working for two employers. Again, that shouldn't be a problem unless there is a potential for conflict of interest.

Post reply on HN