4

Ask HN: Using an LLC to protect side project IP

 2 years ago
source link: https://news.ycombinator.com/item?id=30658602
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

Ask HN: Using an LLC to protect side project IP

Ask HN: Using an LLC to protect side project IP 24 points by jackfruit2 4 hours ago | hide | past | favorite | 28 comments Suppose you had an LLC or could form one whilst employed by another company and you have signed an assignments clause. Could one create own IP under the LLC (owned by the LLC) to protect the IP from that assingment clause, whilst being employed by the second company?

I apprecitate that this is probably one for a lawyer, but wanted to get some thoughts on this approach for protect one's side projects.

IANAL, but this sounds like "no." If you've signed an agreement with EmploymentCorp that any IP you create will be owned by EmploymentCorp, you can't create MyLLC and sign an agreement with MyLLC that the IP you're creating will be owned by MyLLC.

You can't sign two simultaneous agreements assigning your IP to two different companies. Imagine Amazon hires you and has you agree to assign any IP to them. You then get a second (simultaneous) job with Apple and you agree to assign any IP to them. At some point, a court is going to step in if there's a problem and figure out how to unwind the mess. If the second company is an LLC that's owned by you, the court isn't going to be amused and say "well, it's clearly not a scheme by the owner to get out of an assignment clause."

If you've signed away your IP as part of your employment, there isn't going to be One Simple Trick™ to get around that. Even if the court decided "yes, we have to treat this as if you were employed by two companies that have no relation to you," EmploymentCorp could simply sue you for not assigning them the IP, win, and then take your assets as compensation - including your ownership of the LLC.

You personally are still liable for complying with your agreement. If you violate that, your employer might sue you for breaching the agreement. Given that one of your assets is the LLC that "owns" the IP you didn't assign to your employer, that kinda makes it easy. If lots of other people owned a part of the other LLC/company, that makes it harder to unwind, but that doesn't let you or the LLC off the hook. Did the LLC's management know that you had an agreement with EmploymentCorp to give them the IP you were creating? Assuming you're the majority shareholder and/or otherwise in charge, yes. So the LLC knowingly entered into an agreement to "steal" EmploymentCorp's IP (using the word steal a bit loosely here, but it fits enough).

You're basically talking about signing an agreement with your LLC that you know violates your employment agreement and signing the agreement as an officer of the LLC that the LLC knows violates the employment agreement of the person (you). Seems like that creates plenty of liability on both sides of the coin.

s.gif
> You're basically talking about signing an agreement with your LLC that you know violates your employment agreement and signing the agreement as an officer of the LLC that the LLC knows violates the employment agreement of the person (you). Seems like that creates plenty of liability on both sides of the coin.

Not only that, but it very quickly moves the nature of the liability from civil to criminal, which then has potential further impact on you in the future.

How far do you want to go? If you are really worried about lawsuits. You can create a shell company registered in Cayman Islands and pay to have someone run it as CEO. Extract royalities to cryto.

My guess is your company will never know just use different github accounts. If they find out they may fire you but to bring a lawsuit to take the ip would be costly and rarely worth it.

Some assignment clauses are absurdly wide like "any IP you create belongs to us". This would imply absurd outcomes like when a software engineer signed that clause as part of their work contract for software company X, but also records music on weekends or reads audiobooks for librivox or stuff like that, and it's now unclear whether the IP in that music or those audiobooks might also belong to company X.

I think it's safe to assume that any such absurdly-wide assignment clause would end up unenforceable in a court of law and can thus be safely ignored.

s.gif
> I think it's safe to assume that any such absurdly-wide assignment clause would end up unenforceable in a court of law and can thus be safely ignored.

Since you're apparently not a lawyer, you haven't read the employment contract and you don't even know what state this person lives in, telling them they can safely ignore a contract that they signed seems rather irresponsible.

The only reasonable advice to give here is the usual: Consult a lawyer who is licensed to practice in your local jurisdiction.

If possible, make it opensource with AGPL license and invite few friends to send some initial contribution, viola now you are not the only one who owns all the IPs, also your employer will be most probably stay away from it due to licensing requirements of opensourcing all the changes made. Alternatively you can create a project with your friend as main owner and contribute to it with same AGPL license. You can also contribute to it as an anonymous contributor. flip side is you will have to get explicit full ownership of the code with MIT/BSD/WTFPL type license via documented way(verified Email works fine).
I'll take this opportunity to plug my own question to the folks on HN - does anybody know how much protection an LLC generally provides you w.r.t. lawsuits and such? I'm currently looking at doing software consulting for a startup, but indemnification clauses have been touchy for the people I've talked to (and I'm paranoid about losing more than I gain in an unfortunate situation). My lawyer has told me that "piercing the corporate veil" is difficult and an LLC should protect me relatively well, but a good friend told me that I should basically always limit my liability to the amount I've been paid as in his opinion the LLC would be of questionable utility. I know HN isn't the place for legal advice, just wondering if anyone has friendly opinions.

I tried googling this, but the SEO spam is so bad I always converge to the same damn sites. Maybe google search for legal layperson questions is the next big thing?

s.gif
Generally speaking, an LLC is going to protect you from debt that your company owes. So, you won’t lose your personal assets if your company goes out of business. However, it doesn’t protect you from criminal harm, nor does it protect you if you mix business and personal expenses. (e.g. if you personally guarantee a loan for your company, you’re still on the hook)

I’m just someone who has taken law courses in undergrad, not a lawyer, and you really should talk to one if you are seriously considering this. They will have much better feedback for your particular situation and questions like this will not be expensive to have answered.

s.gif
My guess is the scenario they're worried about is neither debts nor criminal harm, but civil liability. Like say the counterparty claims you had an implicit warranty regarding X, but in fact you didn't, and that they suffered damages as a result. Then can they go after your personal funds to recover damages (if they win)?
s.gif
According to this [0] I wouldn’t rely on an LLC to protect me from torts, especially if it’s a single member LLC. It also says that it varies by state, so this is an even better reason to chat with a lawyer about the particular issues you’re concerned about and how your state would treat it.

[0]: https://www.nolo.com/legal-encyclopedia/limited-liability-pr...

s.gif
This is a fantastic question. I would love an informed answer to this question from someone who's actually been on the other side of a lawsuit in a 1-person company.

For context, as a layman, when I Googled this a while ago, the understanding I came away with was that while there can be some benefit to form an LLC in this regard, in reality it's Very Hard (TM) for a 1-person company to truly avoid the risk of the corporate veil getting pierced (regardless of the kind—LLC or whatever). The way I understood it, the entity suing you will look for any and all excuses in your records to try to pierce the corporate veil—and these can include anything from "mixed personal & corporate funds" to "did not properly keep detailed minutes of corporate actions", to other things I'm not aware of. And when there's only 1 person in the company, it's generally more difficult to abide by all the formalities in practice and keep proper documentation of them and convince others that you are indeed keeping doing things properly, whereas with 2+ people, it's much easier, and as a result of that fact (IIRC) judges are apparently much less likely to pierce the corporate veil when there are multiple people in a company.

But as I mentioned, I'm a total layman here, and I would love more info from someone who actually has any legal experience with this kind of concern.

s.gif
I don’t think you should be signing indemnification clauses at all. Think what you’re agreeing to - you’re going to defend the company in court on your own dime when they get sued?
No, that does not work. IP you create is currently governed by a contract with Company A. Signing a different contract with Company B will only make you more liable as both contracts must be adhered to, and if they both claim all IP then the only valid move is to never create any IP.

Get your current employer to approve your project through an addendum or find other employment, and in the future do not sign contracts you do not want to follow by the letter.

An IP agreement with an employer typically has the employee assign rights in any IP the employee develops to the employer. That gives the employer ownership of anything the employee personally develops. Creating an LLC wouldn’t change that since the employee is the one creating the IP, not the LLC. If others are involved in the LLC, the LLC could own IP developed by them (assuming they haven’t assigned their rights away to a different company), but not to IP (even IP yet to be developed) already assigned to a different company.

Ideally, the IP agreement with the employer is limited in scope so that the only IP assigned is that which relates to the employer’s products (e.g., a company that develops medical records software might not claim IP rights to a game the employee develops on the weekend). Unfortunately, many employers use overly-broad agreements, so it’s important to review the agreement. Even if the agreement is broad, the employer may be willing to amend it if the employee is working on something unrelated to the employer’s business and the work won’t affect the employee’s performance. Talk to an attorney in your state before you do anything that jeopardizes something of value to you, and definitely talk to an attorney before you concoct a scheme that opens you up to legal problems ;-)

Source: Attorney / software developer.

You can't assign something you don't own, and if you've signed an IP assignment agreement it's not yours anymore. Your best bet is to get a carve out for your specific side projects, or find a job somewhere that will accommodate you if you care enough.

*This like everything on this thread is terrible advice. You need a lawyer.

IANAL but it pays to discuss these clauses with your future employer prior to signing and to get what was discussed in writing. If you can't get it removed, modified or clarified to your satisfaction you might want to seek employment elsewhere.
There are structures you could set-up which could shield you. For example, a LLC within a S-corp, where you are share holder of the s-corp (as person, trust, or with another LLC), but not owner of the first LLC. Then the LLC holds the IP, and you are now entitled to part or full ownership through shares. However, that does not shield you from lawsuits if anyone would find out.
No that will not work. In fact, it makes it look like you’re trying to give them the run around.

The best thing you could do to protect IP for your side project is to talk to your employer and tell them what you want to work on and get a written exception for it.

I don’t think that working for two companies somehow changes a contract that you have with the first company.

If it were me, I’d simply speak with the first company to get my side project exempted.

No. In court your single member LLC is going to be treated as being effectively you.
s.gif
Said with an air of authority despite plenty of evidence that single person LLCs have a veil that is not pierced by the law.

The proper answer is, consult the precedent of prior cases in your state, that will tell you how strong the LLC holds up in any particular jurisdiction. A lawyer in your area will also know this better than a lawyer in other areas. It’s not a one-size-fits-all answer, and in general the LLC typically holds up well. Regardless of the number of members.

s.gif
What if say i involved a few family members (or other trusted people) to be "partners"? Will the law still treat it as me the individual?
s.gif
Courts take a very dim view of smart ass or "technically [X]" nonsense. It's one of the advantages of actual courts and law vs. crypto "contracts"
Without being a lawyer, and of course this is in no way to be construed as legal advice.

Most employers, especially ones with IP assignment rules, don't allow working for another company at the same time. So off the bat you're going to be having a bad time there.

Next if your employer has an IP assignment section in your contract, assuming you use none of their time (I'm going to bet lawyers will have fun with what that means), and none of their equipment, some states and some countries do not consider such terms enforceable. But in that case you don't need an LLC (and making an LLC puts you in the "don't work for another company" bucket)

The obvious question (for your lawyer, I am not your lawyer, this is not legal advice) would be whether you could even assign your IP to the LLC, if the terms of your contract are enforceable and say your spare time IP belongs to your employer, then that IP is not yours to give to the LLC.

Of course the real think you should be doing is talking to an actual lawyer rather than asking random people on the internet.

You seem to be looking for a lawyer. Asking concrete legal questions on a public forum is not a substitute.
s.gif
A similarly brusque response could be written to many, many questions on a forum.

> You seem to be looking for a doctor/lawyer/teacher/statistician/psychologist/sysadmin/_____. Asking concrete _____ questions on a public forum is not a substitute.

Does that really have a positive effect, though? In my opinion, it's not a good thing for people, especially those who aren't wealthy to enough to pay every time there's something they want to learn.

They probably know that paying someone hundreds of dollars an hour is the surest way to get a good answer but lack either the ability or the will to pay it.

s.gif
This seems to a case analogous to “I have this new, fast-growing, irregular-shaped mole on my forehead and I’m thinking of using Compound W on it. As long as I don’t get any in my eye, I should be OK, right?” and then someone suggesting “you really ought to see a doctor”.
s.gif
Hundreds of dollars per hour over the course of 15 minutes isn’t too bad of a bill.
s.gif Applications are open for YC Summer 2022
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search:

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK