Does a German visitor implicitly agree to a website’s Terms of Service when reading a page? When Bob visits a website and reads a page, does he implicitly agree to the website’s Terms of Service? The ToS are linked from each page (e.g., in the footer), and they say something like "By using or accessing the Service, you agree to …". Bob has no user account on this site. Bob just reads (no content submission, no product ordering, no file download). Bob is from Germany. What I found From my understanding, that would be a browse wrap, but the Wikipedia articles makes no statement about the German jurisdiction. The question What are the legal requirements for displaying a Terms &amp; Conditions link on a website? is about Australia, and seems to focus on how the link must be presented. The questions Website Registration Terms Agreement - Implicit With a Blurb or Need Checkbox? and How prominent must terms of service be? do not mention a jurisdiction. One answer to the question What if the user disagreed with the Terms of Service, but still registered on a website? says that one usually agrees implicitly, another answer says that it might be unenforceable if it’s just a link among others, but the question does not seem to be specific to a jurisdiction.
In German Law you need to give your agreement ("Willenserklärung") to a contract or in this case terms of service. This is done by telling the other part. In some cases this can also be implied by an action (example: putting your bottle of beer onto the cashiers table is an offer to buy this bottle). As a second criteria a "Willenserklärung" needs to be the exact will of the part that declares its will (the website user in this case) §§ 133, 157 BGB or that the other side (you) could only see so (not the case here as this mainly speaks of content). If you visit a website and there are terms of services, the "Willenserklärung" is only given when the user read and agreed to the terms. If he did not, the terms of service are not applied until the user agrees to them. So I would recommend to block the website until the user agreed (overlay) as you need to proof he did when in court. Additionally there are so called AGB's in Germany. Those are contracts that are used or planed for many (more than 3) uses and set by one side (you). This may apply here, so you need to follow a lot of other rules like making sure the user had access and agreed, then there are many content restrictions and so on... I recommend consulting a German Lawyer specialized on this topic as this is very complex and includes other German laws for Media too, depending on the content of your site and terms. Also note that everything said is only based on my own knowledge and can not be used as safe legal source.
The GDPR only mentions cookies once (Recital 30). (It says that cookies are personal data if they are associated with natural persons.) As far as cookies go, nothing has really changed since 2002, and the exception granted in the EU cookie directive Article 5(3) is still valid: This shall not prevent any technical storage or access for the sole purpose of carrying out the transmission of a communication over an electronic communications network, or as strictly necessary in order for the provider of an information society service explicitly requested by the subscriber or user to provide the service. If your site complies with the 2002 directive today, it will be GDPR compliant. All the "EU Cookie Law Compliance" plugins I've checked out let the admin configure the site to comply with the 2002 directive, and most let you choose between implicit consent (which is, and still will be, OK if you or third party services do not use cookies for profiling or to collect personal data), soft consent, or hard consent. The latter is however mandatory if you or third party services use cookies to for profiling or to collect personal data. However, if at least one of your cookies are used for profiling (and if you use Google analytics, you are), or if they are used to collect personal data, the exception from explicit consent quoted above does not apply and implicit consent (i.e.: "continued use of the site amounts to implicit consent to the use of cookies") has never been legal for the site. So while nothing has changed since 2002, there is a lot of misinformation about cookies floating on the Internet, and a lot of sites have their cookie banners set up wrong. You may want to do a new cookie audit for your site to verify that you comply with existing legislation.
You are processing the users IP address in order to carry out the translation to a physical location (see my comment for the technical issues with that) and an IP address is most certainly considered personal information, so yes under the GDPR you are going to need a published policy because you are both data controller and data processor. You need to inform the user of what you are doing, and you need to tell them of the legal basis for the processing (there are several under the GDPR, of which consent is only one - but in your case its going to be the easiest to justify). If you use a third party service for the location translation, you also need to inform the user of that and make available the third party services data processing policy.
To add to Nij's answer: You write I have not signed any paper document. You seem to assume that a binding contract can only be entered into in writing. This is wrong. In most countries (certainly in Germany), a binding contract generally does not require a written document. A contract can be entered into orally, or even silently ("Schlüssiges Handeln", "Implied-in-fact contract"). All that is required for a contract is that one party made a proposal, and the other party indicated their agreement, implicitly or explicitly ("Willenserklärung"). Clicking "yes" on a website can mean entering into a contract if you could reasonably be expected to understand that you were accepting certain obligations (such as that of paying a fee). So in your case, you probably entered into a valid contract, and will have to fulfill your obligation under it, which means paying. From a practical point of view: If you choose not to pay, the organizers will probably either drop the claim (if you are lucky), or they will pursue it. In that case, they can send you a "Mahnbescheid" for their claim. At that point you either pay within 14 days, or respond that you reject the claim, then there will be a trial, which you will probably lose, and pay a lot more than 40€. If you do not respond to the Mahnbescheid, you will receive a "Vollstreckungsbescheid", and then a visit by a Gerichtsvollzieher (officer of the court). My advice would be to pay and learn to properly cancel registrations.
Your issue is trademark, not copyright. If these other guys use their mark (product name) in commerce but did not register it, they have an unregistered trademark which you could be infringing. Between two users of the same trademark, the first to use in commerce wins. (There is a territorial component but with the Internet, meh.) If the trademark is registered that gives them a presumption of validity. Trademark infringement is concerned with consumer confusion. If someone uses someone else's trademark in a way that confuses consumers as to the origin of the goods, that's a problem. What this means is that if I make tires with the name Sportie and someone else makes soap also with that name Sportie there is not a high likelihood of confusion. Likewise a hotel in Washington called Runner's Cove probably doesn't infringe a shoe store in Florida with the same name. Fantasy games and fantasy books sold over the Internet? Sounds like a potential problem that you might want to clear up before the second book.
If a website's TOS has restrictions against unauthorized copying and use of anything in the site, that applies to the TOS, too. Chances are, no one will do a Google search on the exact text of their TOS to find if someone has copied it; but who knows? If they paid a legal service to draft a very specific and original TOS, they may be concerned with others copying it illegally. Beyond that, their TOS is a legal document. Your TOS is a legal document. Your users sign a contract when they click and accept. If you copy and paste a TOS, and don't understand exactly what is in it, and you and your users are bound by that TOS, what kind of legal risks do you open yourself up to? A simple Google search yields https://formswift.com/terms-of-service among others. Or try one of the many services like LegalZoom.
Impressum Requirement Wow, based on your citations, you've done a lot of research on this topic. I'm just going to add one more reference, which is from the same site as your first German citation and has incredibly detailed and judicially referenced information on almost everything related to the Impressum. All my non-GitHub links are to sections of that page. Based on your research, I'm going to take it for granted that you understand that according to the Telemediengesetz (TMG), an Impressum is required on a web page if it is &quot;business-like&quot; (geschäftsmäßig), or if it helps, I prefer to word it as &quot;potentially commercial.&quot; I would have to argue that open source projects have to be seen as inherently &quot;business-like&quot; for the purposes of the TMG for two reasons: Some other legal person may have similar software as part of their business and might have the need to serve legal notifications to the owner of a GitHub project (TMG § 8 gives competitors the right to sue). Think potential copyright violations here. It is possible to build a more traditional commercial business around open source, for example what Canonical is doing around Ubuntu. Additionally, the common legal advice is to even include an Impressum on a personal blog, though I'm not aware of any court case having occurred at that level yet. In my opinion, a GitHub account can be seen as more &quot;business-like&quot; than a personal blog, and would follow that advice out of caution. I'll note that the XING situation you bring up is complicated. It centers over whether the content of XING pages is &quot;business-like&quot; according to the TMG. It may well turn out that some pages will need an Impressum and others won't. As for placing it in the project's readme.md, that might work but I have two concerns: The courts have essentially stated that the text of the link must imply that the required information under TMG § 5 is located there. For example, the words Impressum and Kontakt work, but the word Information does not. To me, &quot;readme&quot; is not sufficient, but this concern might be negated by the fact GitHub by default renders the readme.md directly on the project home page. While it has been ruled that the Impressum does not necessarily have to be directly on the home page (for GitHub, that would be the company's/users profile page), it must still be readily available in an intuitive location. I don't know if putting it in a project page satisfies the legal requirement. If it was sufficient, it's also likely that each project would have to have an Impressum so that it can't be missed. Examples The dominant pattern that I could find1 on GitHub is an off-site link to the Impressum contained in the profile page's byline right underneath the title. Examples: https://github.com/sedadigital, https://github.com/comsysto, https://github.com/znes, https://github.com/eSagu, https://github.com/TIBHannover. I'm almost certain this meets or exceeds the legal requirements. Example screenshot: Additionally, I found a few that had a repository specifically for an Impressum. Example: https://github.com/johsteffens. Since these repositories were clearly visible on the user's main page (either because there weren't enough repositories to make them span multiple pages, or because it was specifically pinned to the main page), I would argue these also meet the legal requirement for being readily available. While I didn't find any examples of it, another possibility would be to combine the above two approaches, having a link in the byline that links to an Impressum repository or some other page within GitHub. This would be useful if you didn't otherwise have an Impressum hosted elsewhere. There were also scattered examples of people placing an Impressum on a project wiki page or on an impressum.md file at the top level. However, none of the users I looked at were consistent in doing this across all their projects. Also as previously mentioned, it's questionable whether not having it on the main user profile page meets the legal requirement. The Wiki page in particular I don't think meets the requirement that it can easily be found. Found using the following Google search: site:github.com impressum -impressum.php -impressum.html -impressum.jsp -impressum-manager -github.io -issue. Exclusions meant to filter out a lot of false positives, mostly projects for websites that had their Impressum in code format meant for deploy and not for display on GitHub itself.
Just at the offset this does not constitute legal advice, just some opinions I have on this point. Technically, you would not be prohibited to generate speech and use it however you like. Under normal circumstances any output generated by the system that does not contravene the service agreement would be your intellectual property. This would include the text and speech generated. Once you go about the request limit you would naturally be required to pay, but until that time you can use the service as a paying customer. Just to clarify this point I would like to make reference to the service license agreement, clause 3, which make reference to the following prohibitions: (a) copy, modify, create a derivative work of, reverse engineer, decompile, translate, disassemble, or otherwise attempt to extract any or all of the source code of the Services (subject to Section 3.4 below and except to the extent such restriction is expressly prohibited by applicable law); (b) use the Services for High Risk Activities; (c) sublicense, resell, or distribute any or all of the Services separate from any integrated Application; (d) create multiple Applications, Accounts, or Projects to simulate or act as a single Application, Account, or Project (respectively) or otherwise access the Services in a manner intended to avoid incurring Fees or exceed usage limits or quotas; (e) unless otherwise set forth in the Service Specific Terms, use the Services to operate or enable any telecommunications service or in connection with any Application that allows Customer End Users to place calls or to receive calls from any public switched telephone network; or (f) process or store any Customer Data that is subject to the International Traffic in Arms Regulations maintained by the Department of State. Unless otherwise specified in writing by Google, Google does not intend uses of the Services to create obligations under HIPAA, and makes no representations that the Services satisfy HIPAA requirements. If Customer is (or becomes) a Covered Entity or Business Associate, as defined in HIPAA, Customer will not use the Services for any purpose or in any manner involving Protected Health Information (as defined in HIPAA) unless Customer has received prior written consent to such use from Google. Similarly, as specified here: Customer will not, and will not allow third parties to: (i) use these Services to create, train, or improve (directly or indirectly) a similar or competing product or service or (ii) integrate these Services with any applications for any embedded devices such as cars, TVs, appliances, or speakers​ without Google's prior written permission. These Services can only be integrated with applications for the following personal computing devices: smartphones, tablets, laptops, and desktops. In addition to any other available remedies, Google may immediately suspend or terminate Customer's use of these Services based on any suspected violation of these terms, and violation of these terms is deemed violation of Google's Intellectual Property Rights. Customer will provide Google with any assistance Google requests to reasonably confirm compliance with these terms (including interviews with Customer employees and inspection of Customer source code, model training data, and engineering documentation). These terms will survive termination or expiration of the Agreement. You should also take a look at this and this. However, as per the terms of the agreement the speech generated would be your intellectual property, unless otherwise specified. Good luck!