License or not for open source code published by the manufacturer? Do I need license for the Arduino code that a company has posted in their websites when I buy their sensors to use them to my Arduino? For instance, I buy a CO2 sensor and I use the company's code in order to make this CO2 sensor work with my Arduino. Do I need license if I want to patent a machine using the latter sensor?
Unknown based on what you have posted in your question. But answer lies in the terms under which the source code is made available or licensed. The most common scenario is that such &quot;sample&quot; source code is provided as help to the purchaser of their product and you'll often see things that permit its use in conjunction with the hardware product. You'll also often see disclaimers that say the code is for demonstration purposes only and it not warrantied to do anything at all. But again, you'll need to review the actual language under which the code is provided and then understand and follow its terms and conditions.
Being or not being open source makes fairly little difference in trademark law. If a commercial firm (Yoyodyne, say) had used the name &quot;Portable Network Graphics&quot; and the abbreviation &quot;PNG&quot; in trade, and taken such further steps as would be needed to protect it in the relevant countries, that firm would have a protectable trademark. Note that in some countries, a trademark must be registered to have any protection at all (much of the EU follows this rule). In others, use in commerce can offer some protection even without registration (the US follows this rule). Had this happened (in an alternate reality) Yoyodyne could have sent a cease and desist letter when open source developers started using the mark. If the devs did not cease, Yoyodyne might have obtained an injunction, or damages for trademark infringement, or both. They could also have issued a takedown notie to the site hosting the project. But had Yoyodyne failed to defend the mark effectively and allowed it to become generic, Yoyodyne might have lost all rights to it. Also, had Yoyodyne ceased to use it in trade for a significant period, they might have lost rights. This is a place where the different laws in different countries might lead to different results. Note that &quot;Portable Network Graphics&quot; is rather descriptive, and not particularly distinctive. Descriptive marks, like &quot;Tasty Pizza&quot; generally get weaker protection, while more distinctive marks, such as &quot;LuAnn's Tastee Pizza&quot; are more strongly protected, in general. Again this depends on the country, and the specific facts. In general the first to use, or to register a mark, gets the rights. When one entity is the first to use, but a different one is first to register, things can get confusing, and results will be different in different countries. Note that a Cease and Desist letter is not a legal requirement. It is a threat of possible future legal action, and often an offer to avoid such action if the recipient does as the sender requests. The recipient can comply with the letter, wait for court action, or try to make some sort of compromise deal. Open source projects, as other answers suggest, often choose to comply.
No. GPL works are copyrighted (as are most creative works basically everywhere in the world, as soon as they're created, whether or not the author does anything about it), and copyright is what gives the GPL "teeth". Without copyright, you would generally be able to duplicate and distribute programs without any kind of license or permission from the author. Copyright law restricts your ability to do those things. The GPL is a license, which means it's a grant of permission. It says that you may copy and modify and do other things, provided that you comply with the other provisions set out in the license. Quoting from the GPL v3: You are not required to accept this License in order to receive or run a copy of the Program. [...] However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. So if you were to distribute some GPL-licensed software in a way that didn't comply with the terms of the license, the legal framework that would allow someone to sue you to stop you doing that would be copyright law.
Generally speaking, you must be Licensed, or enter a written agreement, in order to use any logos from any company, especially any time the reference is referenced commercially. There are exceptions to the rule, and some are more lenient than others, but you should always check before showing any company's trademarks or brand icons. For example, Intel® allows third parties to refer to them by name, but displaying a logo requires a license or written permission, per their Trademarks and Brands guideline. You'll find that most companies are probably willing to overlook violations of Licensing as long as the product is placed in a favorable light, since's that's basically free advertising, but you'll want to take the extra few moments and simply call them and ask. A ten minute call could save you tons in legal fees and/or fines. From what I've seen, most companies will allow use of their company name for most commercial and non-commercial uses, but reserve some logos only for licensed partners, and others still only for themselves. They will also generally specify appearance guidelines, such as rendering ® and ™ only the first time on each page of printed material, as well as a specific guideline for sentences and phrases that the name may or may not appear in. They also usually specify that such phrases may not imply that the company is a partner or representative of the company, etc. You can see Intel's Trademark Symbols and Acknowledgements page for an example of what you'd expect to be required to do. This page also gives some example sentences of acceptable and unacceptable phrases. For example: Correct Usage Look for PCs with Intel® Core™ processors. Incorrect Usage Look for PCs with Intel® Core. Mostly, they're concerned about making sure ™ is used correctly, as well as specifying that they make processors, not entire systems. You'll want to try and stay on the good side of their legal department, and represent fairly.
Can anybody create their own license? That is to say, can I for example create my own license under which I can license software? Yep. It's just a contract granting rights to use a copyrighted work. You can write your own contracts, so you can write your own software license. It's just often recommended that you don't, because common licenses are more well-understood, and inexperienced drafters may make errors that could result in problems, such as unintended restrictions, failing to restrict things that were intended to be restricted, or creating provisions that aren't enforceable in some/all jurisdictions. Can you mandate how a software will be released? Yes. Many software licenses, including GPL, do. The restrictions you describe in your example sound similar to CC BY-NC-SA. Also, would the following clause even be legal? Using this software you agree that any work and intellectual property based on or created with this software will be under the [INSERT_NAME_LICENSE] license, even after any and all code from this software is removed in a future update, or even if the work is rebuilt from the ground up I'm not entirely certain, but &quot;even after any and all code from this software is removed in a future update, or even if the work is rebuilt from the ground up&quot; seems, in my opinion, unlikely to be enforceable—especially &quot;even if the work is rebuilt from the ground up.&quot; How would you differentiate a complete rebuild from a totally new piece of software? More broadly, once your copyrighted code is no longer in the product, there's nothing for them to license from you. It's hard to imagine how you'd be able to claim that you're harmed by someone releasing a new version of a product that used to contain your code under a different license. Without harm to you, there's nothing for a court to redress.
It does mean that you cannot reuse any parts of the source code, even small simple ones. You would have to rebuild the code from scratch. There is a significant chance that the code would be "substantially similar" to the code that you were hired to build, also that if anybody else were to write a bubble sort or 24-to-am/pm conversion routine, it would look the same, where even variable names (which should describe function) are the same or very similar. In case of an infringement lawsuit, you would have to defend yourself by showing that there are only a few ways to code a given function. Copyright protects only the "expression", not the abstract idea. A linked list is an idea, which can't be protected by copyright; same with recursion, pointers, stacks, object-oriented programming... Anything that involves copy and paste is infringement. If you re-read the copyrighted code and then try to reconstruct it, you probably crossed the infringement line. If you remember the problems and solutions and accidentally write somewhat similar code, that is probably on the safe side. From the perspective of the programmer not wanting to always reinvent the wheel, it would be most useful to make a distinction in the contract between "the essentials of the customer's program" versus "incidental utility work". The difficulty will arise in saying specifically what is essential vs. incidental. For instance, I know that if I were to hire you to develop a speech-recognition system, low-level audio-acquisition and encoding would not be essential to my purpose, whereas DSP parsing routines would be the center of my interest. The programmer would then want to retain recycling rights to all non-essential code.
At least in theory an end user could be sued for infringing on a patent, especially a method claim. Given the cost of a patent lawsuit, this strikes me as extremely unlikely to happen though, unless the user in question were an extremely large company, or something on that order. Theoretically, the only difference between open-source software and proprietary software would be that availability of the source code makes it easier to prove use of a patent in open-source software. Releasing the software as open-source doesn't confer any immunity from patent law or anything like that though. Realistically, however, the chances of being sued for infringement if you're basically giving away the software in question are fairly remote. It rarely makes sense for a patent holder to spend millions of dollars on a lawsuit where they stand no chance of even recovering their cost (but no, that certainly should not be taken as legal advice that you're free to infringe on patents, or anything similar--in fact, none of this should be taken as legal advice at all). If you can actually prove that a technique was published or publicly known and used (e.g., in a product that was offered for sale) well before the patent was applied for, the patent is probably invalid (and if proven so in court, the case would normally be dismissed with prejudice, which basically means the patent holder wouldn't be able to sue anybody else for infringement of that patent). I'd note, however, that in my experience this is much less common than most people imagine--many look at (for example) the title of a patent, and assume it lacks originality because it refers to some well-known technique, and ignore the claims where it details the precise differences between the previously known technique and what the patent really covers. Just for example, the EFF used to have a web page talking about a (now long-since expired) patent on how to draw a cursor on screen. In an apparent attempt at scaring the unwary, they showed code they claimed infringed in the patent--despite the fact that the patent's "background of the invention" specifically cited the technique they showed as being previously known, and not covered by the patent.
This is possibly but not necessarily fine. The data controller (the garage) is responsible for safeguarding your personal data. They must take appropriate safety measures, but this depends a lot on their own risk assessment. For example, to protect the data from being used by employees for their personal purposes, the controller might use organizational measures like a policy “you're not allowed to do that.” Many companies allow employees to use their personal devices for work purposes (BYOD). When the data controller allows this and takes appropriate safety measures, everything is perfectly fine. The company still has to make sure that the data is only processed for legal purses and deleted afterwards. Implementing a BYOD policy in a GDPR compliant manner is difficult but not impossible. A data breach has occurred when the security measures were insufficient and your data was deleted or disclosed without authorization. Your scenario would only be a breach if the company did not have a BYOD policy and the salesman used their personal phone, and arguably then only if that device is also breached. However, do not discount the alternatives: they do have a BYOD policy and the salesman is acting within their instructions the salesman was using a company-controlled device, not their personal phone If you have good reason to believe that your data was mishandled (and these alternatives do not apply), then the GDPR offers you the following remedies: You can of course complain to the data controller, especially if they have a dedicated data protection officer. You can lodge a complaint with a supervision authority, which is the ICO in the UK. They expect you to attempt to resolve your issue with the controller first. The ICO can then decide if they want to investigate the issue. You can sue them for compliance and for actual damages suffered (you have none, though). Note that all of these alternatives are more effort than they are likely worth. In particular, the garage can always correct the problem, e.g. by getting your contact info deleted from the personal device or by creating a retroactive BYOD policy.