How do organizations with BYOD policy handle code theft? Some corporations have a Bring Your Own Device (BYOD) policy, and some may allow their employees to take their laptops home for usage. What if an employee takes the code and develops something outside of their employment scope? An organization may be able to file a patent infringement lawsuit if their code is used, but what if a malicious employees steals non patented or patent pending code and sell it to someone else? How do the organizations handle these cases? EDIT: I agree with the copyright answer. I will search it further on the law Stack exchange site as suggested in the answer and the comments. This is different from the other question because there they OP is asking about ways to protect the source code. I am interested in impact of code theft and ways to handle it.
Patents are not that relevant in this case. Software patents are unenforceable in most parts of the world anyway. What matters here is copyright. Every work contract has a clause that everything an employee creates as part of their employment is copyrighted by the company. So using company-owned code to build an own project would be a copyright violation. There are also other legal tools in some jurisdiction which can be used against employees trying to misuse intellectual company property. But that's a topic for Law Stackexchange. Also, this isn't really related to a BYOD policy. Being able to bring your own device to work and then back home might make data theft more convenient, but isn't required. There are many other ways to steal sourcecode, like USB drives or uploading them to the internet. To prevent the first you would have to design your software development offices like a supermax prison facility with meter-high walls (so nobody can throw a device over it) and strip searches on everyone leaving the building. This is neither feasible nor reasonable for anything below matters of national security. To prevent the second, you would have to completely prevent internet access from developer workstations, which would greatly impede the productivity of any software developer. So most companies do not even try to physically prevent employees from stealing sourcecode. They rather rely on the legal safeguards and on maintaining a mutual trust relationship with their employees. It might seem counter-intuitive to some, but when you do not treat your employees like potential criminals they are in fact less likely to betray you.
I'll ignore whether a recipe is actually a good example, but I assume you're asking how a person who owns the exclusive rights to copy a thing (copyright) or to use a thing (patent) can allow multiple other entities to copy or use the thing. This is possible by granting each a non-exclusive licence. In the case that the piece of knowledge is not protected by any intellectual property regime, the holder of the information could just treat it as a secret. The information holder could enter into contracts to sell that information to various entities, each promising in return not to further disclose that information. This is the case for lots of sports data.
Intentional sabotage of a TSA computer system is almost certainly a serious crime and would also almost surely give rise to civil liability, although you might avoid both if you warned the TSA that the phone was set up to intentionally break their system, in which case it might be confiscated as contraband. If the product had a "feature" unknown to you and that you had no reasonable reason to know of that caused the harm, you would ultimately have no criminal or civil liability, although the manufacturer might be strictly liable to the TSA under a product liability theory, and you would probably be detained as a witness to figure out what happened. If the product had a "feature" that broke the TSA computer that could be de-activated and that you meant to de-active but carelessly failed to, you would have negligence liability to the government and might or might not have criminal liability (I'm not enough of an expert in the relevant statutes to know). You might be liable for a strict liability Federal Communications Commission offense for having a device that is in violation of their regulations.
Assuming that the police have a warrant to seize your cell phone, the scope of what can be seized is specified in the warrant. It is not automatic that seizing a phone entails seizure of some or all online accounts (e.g. automatic backups, collections of passwords in a Google account) and it does not automatically &quot;freeze&quot; or block a person's access to their accounts including phone accounts. It's not that it is impossible to seize an account, it's that it is not automatic: it has to be in the scope of the warrant. Here is a collection of petition templates, asking the court to allow the seizure of various things for various reasons (mostly electronic), including access to bank accounts. If the police suspect that information might be available online after it has been deleted from a phone, they would need to include online accounts in the scope of the petition(s). There is even a template for &quot;give me everything&quot;, called &quot;Frankenstein&quot;.
No. Only the company owns the copyright, not its shareholders. A company is a separate legal entity with its own capacity to own property. Copyright is property, not infection that can be spread onto whoever is close enough. Pretty much like shareholders can't just share the use of the company's tangible assets, they can't wet their beaks in the copyright. As a shareholder, what you could do is to appoint a director/CEO that will give you license to copy (or even transfer the copyright) — if you have enough shares to fire the current CEO and put yours. The CEO will get into legal trouble with other shareholders/creditors, but you'll still enjoy your right to copy.
This is similar to giving a hammer and needing to state to one is not responsible if the taker uses it to hit their head with. I believe this is the wrong analogy to use here. It would be more like giving somebody a hammer and saying you are not responsible if the head flies off and injures you. There is a concept in &quot;things&quot; you obtain called &quot;fitness for purpose&quot;, so if you download open-source software like a registry cleaner, and it deletes your entire registry, the &quot;WTFPL&quot; doesn't absolve the authors of liability. Explicitly denying any kind of &quot;fitness for purpose&quot; or warranty helps shield the author from legal claims (even if they are meritless) because it kills it out of the gate. It's possible that the WTFPL license granter/author could still be sued and have to defend themselves in court because it isn't explicitly stated that there is no warranty or fitness for purpose. Open source does not mean that it's &quot;use at your own risk&quot;, which is why there are so many types of licenses and disclaimers. From comments: Thank you for this very clear answer. Does the fact that someone willingly retrieves free code with no control of the provider changes anything? (vs a software vendor which provides code suitable for A and B, in exchange for money) I think closer to your hammer analogy where I would sue the producer of hammer XXX, a hammer I found on the street or which was given to me without involvement of vendor XXX. No, this doesn't change anything. The software vendor here is the person who writes the code, even if they don't charge for it. They are the ones who license the software and they are the ones who take some level of responsibility for it. In this case, the software author is the &quot;hammer producer&quot; that you would sue... If you buy &quot;Registry Cleaner XL&quot; from Best Buy and it bricks your computer, you don't sue Best Buy, you sue the person who authored the software. In pretty much every case, the author is the responsible party, not the vendor, and it is the author who licenses it, not the vendor (the vendor just acts as an intermediary).
It is illegal to make copies of copyrighted materials without license. In the case of software, obviously it will be illegal to make copies by copying and installing the software without a license, but we are not talking about that. If I have a legitimate license of say Photoshop, and I start the application, parts or all of the code will be loaded into the RAM of my computer, which is a copy. According to copyright law, it is legal for me to make that copy. You are allowed to copy legitimately owned software into RAM to execute it. If your copy of Photoshop is illegal, and you start the application, the copy that is made into RAM is again copyright infringement. Having read the software license for the software that you get when you buy a Mac, it seems that if you steal my computer and just start the operating system, you are committing copyright infringement, and it seems that if you buy such a stolen computer and just start the operating system, you are committing copyright infringement as well, because the license that I received when I purchased the computer covers anyone using it with my permission, and covers anyone who legally buys the computer from me, but doesn't cover a thief. Now does this affect the work that you did? No, you have the full copyright on your work. Copyright law doesn't require that your tools are all used legitimately.
You would have to look at your contract with the company or the company's rules. Some companies have clauses that say they own things you develop while working for them and some don't. Without knowing your specific company's policy, it is impossible to say.