Should offline users of an online video game be forced to accept ToS? In the context of a video game that has online and offline play. An account is needed to play online, but no account is required to play offline. Assuming the user must accept some terms while signing up, is it necessary to show a legal document for a user only playing offline? The game also uses CC 3.0 licensed assets. Are these valid reasons to create some terms the user must accept while playing offline? Could both online and offline documents be merged into one that the user must accept in the first launch of the game?
"Terms of Service" implies that you are providing a service. If it's offline, you probably aren't doing that. You can still have a license agreement that applies. If certain types of CC licenses are involved, you may even be required to.
It's not illegal to say things in your profile. SE requires you to license your content to them on a non-exclusive basis pursuant to CC BY-SA 4.0. &quot;Non-exclusive&quot; means that you can also license the material to others on some other basis, e.g. CC0. In that case, a person who uses your material can rely on the other license that you granted. If SE wanted to, it could prohibit putting licenses in a user profile, in which case you would have to promulgate your more generous license elsewhere.
For your example of items with Marvel characters on them for sale by people and companies not licensed by Marvel, Redbubble clearly states that We ask, rather we beg, that you remember this when you are posting work on Redbubble. If you make sure that all the works you upload consist of your very own, original ideas and are not infringing on the intellectual property or publicity rights of another... (from https://help.redbubble.com/hc/en-us/articles/201579195 ) and further, Redbubble has full contact information for the submission of Notice and Takedown Reports by each real trademark owner. There are many individuals who upload products which use unlicensed artwork in violation of trademarks, and Redbubble acknowledges this and gives recourse to the license holder to inform them so they can remove the items. It's not a perfect system, but Redbubble it seems makes every effort to help police their market. ( Teepublic has a very clear policy statement, too: https://www.teepublic.com/copyright-policy ) Many companies - such as Marvel - employ agents to regularly check such websites and issue takedown demands to the sites; the sites in turn remove the products, and in some instances, ban the individual from using the site again. In the case of Amazon, there can be two types of products sold that use trademarked artwork and characters: items sold by legitimate businesses that have license agreements with the trademark owners and who have the products sold by Amazon itself; and items sold on the Amazon marketplace by individuals who open Amazon Marketplace accounts themselves and don't have licenses. Amazon will be sure to check the products they sell; they will have a takedown notices system for their marketplace vendors. eBay is somewhat the same way; there is a mix of individuals and businesses on eBay, but eBay doesn't operate an umbrella sell/ship by eBay, like Amazon. It's kind of a whack-a-mole situation on the Interwebs. How much time/money does a company spend to chase down trademark infringement? Is it worth going to court for persistent violators? (These are, for the most part, civil cases, not criminal). Violators can always open a new account on sites such as Redbubble and eBay under a different name. And it starts all over again.
Your confusion might be caused by the fact that even with a contract, only the data necessary for that contract is covered under the GDPR. So yes, while there might be an &quot;execution of contract&quot; under the T&amp;C, this would only cover necessary data. That means you can't ask arbitrary signup data under the guise of a contract. If you need to deliver a physical product, you can store a physical address. If it's an online service, you can store an email address or similar handle. But you can't mix the two. A physical address is unnecessary for the execution of a contract that's not physical in nature. Now, you mention &quot;consent&quot;. Under GDPR, this is a distinct justification besides &quot;execution of contract&quot;. You might have consent to store a physical address in addition to an online address, e.g. if you offer a customer to physically mail a password request form. This consent is additional to the contract. Also note that the bit above only covers the lawful reasons for the processing of personal data (article 6). You also have to obey the other GDPR rules, e.g. fully inform the user, make sure that consent is freely given, etc.
The GCIDE dictionary itself is licensed under GPL-3.0. It consists of a bunch of files with markup, no software involved. Indeed, the GPL can also be applied to non-software works, though it is unusual. When you use material under some license, you must comply with the terms of the license. In case of the GPL, there are two highly relevant conditions: Everyone who receives a copy of the covered work (original or modified, in whole or in part) must receive the complete corresponding source code of the work, under the terms of the GPL-3.0. If you create a derivative work of the covered work, the derivative work can only be distributed under the GPL-3.0. However, selling the covered material is perfectly fine. The GPL does not forbid you to make money, however you must not profit from your requirement to provide the corresponding source code. Here, the core question is whether your mobile game would be a derivative work of the GPL-licensed dictionary. If your game merely loads the dictionary as a data file, I don't think they would form a single derived work. However, if you compile the dictionary into your app, this would be more difficult to argue. Ultimately, what is a derivative work will depend on a court. It could therefore be helpful to keep your app as clearly non-derivative as possible. I would avoid baking the dictionary into the app's binary but store it separately as a data file, would show attribution notices in reasonable places (e.g. a screen with attribution notices and the complete license text), and would make it possible for users to export a copy of the dictionary files. Furthermore, the GPL-3.0 may require you to allow users to modify this file, for example by making it possible to import a modified dictionary into your app.
The section you quote as clearly saying a thing is not clearly saying the thing. However: you cannot pass on or resell any license keys seems to say a thing clearly. However, one could argue that it's the sharer of the account who is in the wrong, and not the person receiving and passing on the account. I'd say that that piece of the agreement, combined with this: must not... let other people get access to anything we've made in a way that is unfair or unreasonable says that, yes, they are out of bounds.
According to the current version of the TOS: You own the rights to the content you create and post on Medium. By posting content to Medium, you give us a nonexclusive license to publish it on Medium Services, including anything reasonably related to publishing it (like storing, displaying, reformatting, and distributing it). In consideration for Medium granting you access to and use of the Services, you agree that Medium may enable advertising on the Services, including in connection with the display of your content or other information. We may also use your content to promote Medium, including its products and content. We will never sell your content to third parties without your explicit permission. This explicitly says you own your content, although Medium has some rights to do some things. And they won't sell it without permission, so unless Medium itself is publishing this book, it would seem to be copyright infringement. (Of course, I don't know what the TOS said when you originally wrote the article.) If what was copied was not copyrightable (like a quote from the Constitution, or a simple uncreative graph of something obvious) then it wouldn't be infringement. But your article was probably more than that.
Pretty much everything you need to know about the ownership and licensing of your material on Medium is in the Medium TOS you contractually agreed to when you signed up with the service. Basically, you granted Medium a license to use the work, but you did not agree to an exclusive license nor turn over copyright to them. Part of that Terms of Service – Medium Policy reads: Content rights &amp; responsibilities You own the rights to the content you create and post on Medium. By posting content to Medium, you give us a nonexclusive license to publish it on Medium Services, including anything reasonably related to publishing it (like storing, displaying, reformatting, and distributing it). In consideration for Medium granting you access to and use of the Services, you agree that Medium may enable advertising on the Services, including in connection with the display of your content or other information. We may also use your content to promote Medium, including its products and content. We will never sell your content to third parties without your explicit permission. You’re responsible for the content you post. This means you assume all risks related to it, including someone else’s reliance on its accuracy, or claims relating to intellectual property or other legal rights. You’re welcome to post content on Medium that you’ve published elsewhere, as long as you have the rights you need to do so. By posting content to Medium, you represent that doing so doesn’t conflict with any other agreement you’ve made. By posting content you didn’t create to Medium, you are representing that you have the right to do so. For example, you are posting a work that’s in the public domain, used under license (including a free license, such as Creative Commons), or a fair use. We can remove any content you post for any reason. You can delete any of your posts, or your account, anytime. Processing the deletion may take a little time, but we’ll do it as quickly as possible. We may keep backup copies of your deleted post or account on our servers for up to 14 days after you delete it. Pertaining to presenting Medium content in an iFrame on another site, this is reasonably close to not allowing that: You may not do, or try to do, the following: ... (2) access or search the Services by any means other than the currently available, published interfaces (e.g., APIs) that we provide;... You can use Embed Code Generator | Embedly to embed an iFrame of a Medium page on another site. But contacting Medium via the email at the bottom of the TOS would tell you for sure if it is OK. Comments on your pieces on Medium do belong to the owner. And You own the rights to the content you create and post on Medium. appears to cover the idea of copying your material from Medium to your own site. If in doubt, ask them.