Though CC license couldn&#39;t be revoke, could I later decide to change by license from CC BY-SA to CC BY? So though Creative Commons has stated that when things are licensed under their license, it couldn't be revoked, but could I choose to re-license under a less stricter license? Like from CC BY-SA to CC BY (giving up Share-Alike restriction) or like CC BY-NC-SA to either CC BY or CC-BY-SA. As I'm putting down restrictions, is it possible to do such things?
By the terms of the CC license, you cannot &quot;cancel&quot; or &quot;revoke&quot; it. But as the copyright owner, you may separately release under a different license: a less restrictive CC license, or a completely different license such as the GPL or the MIT license. You could even release under a more restrictive CC license, going say from a CC-BY to a CC-BY-ND or a CC-BY-SA. You could remove all mention of the earlier license from any website or app you control. Anyone who had obtained (or later obtains) a copy under the earlier release could use it or give it to others under the terms of that license, but anyone who did not so receive it, but instead gets it from you under the different terms it could only use it under the terms of the later release. By the way, although the CC license describe themselves as irrevocable, there is under US law, a five-year period during which any license grant may be canceled, provided the proper procedures are followed. This is under 17 USC 203, and the period starts 35 years after the license was granted, or 35 years after the work was published.
To answer the question in your title: Yes, software licenses are copyrighted. They are written works that involve (significant, expert) creative effort to create. The best solution would be for Grammarly to hire a lawyer and say "we want a new EULA. We think this one covers a number of points our current one doesn't". Most legal documents will be copyright for the same reason (there may be a few that are so stereotypical that there is essentially no creative effort in putting them together).
If the app (and the service accessed from the app) truly doesn't have any EULA, ToS, or license agreement, to include restrictions on reverse engineering, you can probably create an alternate front end, so long as you aren't using their logos, etc. However, their data may be a different beast, depending on the nature of it. For example, extracting data from Twitter would potentially violate Twitter's license on the original text copyright held by the authors in question. Wikipedia explicitly includes redistribution in their license agreement with authors/content creators. If all you are extracting and storing is the temperature at a particular weather station, you might have less of a concern. Anything beyond merely factual runs the risk of a copyright infringement as you store the data in your own database.
Broadly speaking, the difference is the "sharealike" clause of CC-BY-SA. Any derivative of a CC-BY-SA work must itself be licensed CC-BY-SA, whereas a derivative of an "MIT with attribution" work can be under any license the author wants. There are a number of other differences in the fine print (eg. CC forbids DRM, where MIT doesn't), but that's the big one.
united-states The license won't let you sell the .stl file. Probably you have created a derivative work, which means you can't sell it without a copyright license (and the CC-A-NC won't do). If it were licensed under CC-A you could sell it without problems (you'd have to give attribution, of course). You could also sell it under the CC-A-SA, but once you do you have no control over the result -- anyone you sold it to could give it to someone else under the terms of the license. This could work, though, if it were (say) a commission and you only expected to sell one copy. I don't know what the situation would be with the physical objects printed under any of these licenses.
No you don't. There are two copyright holders regarding the derivative work: yourself, for creating the original. the other artist, for creating the modified version. The other artist has received the right to use your original through the CC-BY license, under the condition that they attribute you appropriately. However, you have not received any rights to the other artist's work.
It would be illegal because only you are allowed to view the comic you purchased. Creating a copy of your comic (e.g photcopying, scanning etc) is not allowed, and showing others a copy of your comic is also not allowed
What are exactly the legal consequences of "All rights reserved"? Almost none. You have to explicitly grant copyright rights. You don't even need the Copyright notice for them to apply. My "almost" is because the notice makes it harder for somebody to argue "they didn't realize". Do I still need an additional SW License Agreement or is the Copyright notice above + a Disclaimer of liability sufficient? If this is free software (I know you said it isn't), do yourself (and everyone else) a favour by picking a license you like. Preferably either GPL or MIT (depending on your taste). There are far too many free licenses already. Please don't add another. (It also makes it much easier for any user of your software: "Oh yeah, GPL v2. We understand that. We can use it." as opposed to "What are the implications of using this one??" As this is not free software, I think you need a paid-for lawyer (who understands IPR in your juridiction.) Edit: In principle, I believe you don't need anything. The code is copyright, so the customer can't do anything with it (without explicit permissions that you haven't granted). However if the customer doesn't realize that or thinks you won't mind, you then have to go to court to enforce your rights (and probably end up with a disgruntled customer). A short, clear, license will make it clear to the customer what they are allowed to do, and save all that aggravation.