This guide describes the information that GitLaw needs in order to process a DMCA takedown request. If you have more general questions about what the DMCA is or how GitLaw processes DMCA takedown requests, please review our DMCA Takedown Policy.

This guide describes the information that GitHub needs in order to process a counter notice to a DMCA takedown request. If you have more general questions about what the DMCA is or how GitHub processes DMCA takedown requests, please review our DMCA Takedown Policy.

Using a company or business name, logo, or other trademark-protected materials in a manner that may mislead or confuse others with regard to its brand or business affiliation may be considered a trademark policy violation.

We offer this private information removal process as an exceptional service only for high-risk content that violates GitLaw's Terms of Service, such as when your security is at risk from exposed access credentials. This guide describes the information GitLaw needs from you in order to process a request to remove private information from a repository.

Welcome to GitLaw's Guide to the Digital Millennium Copyright Act, commonly known as the "DMCA." This page is not meant as a comprehensive primer to the statute. However, if you've received a DMCA takedown notice targeting content you've posted on GitLaw or if you're a rights-holder looking to issue such a notice, this page will hopefully help to demystify the law a bit as well as our policies for complying with it.

If you'd like to request that content be removed from GitLaw, please take some time to acquaint yourself with each of these policies and their respective reporting requirements before submitting a report. If we receive an incomplete report, we'll need to ask for clarifications or revisions and you’ll need to re-submit a revised report.

‍In this article: What if the username I want is already taken, Trademark Policy and Name Squatting Policy. GitLaw account names are available on a first-come, first-served basis, and are intended for immediate and active use.

GitLaw uses cookies to provide and secure our websites, as well as to analyze the usage of our websites, in order to offer you a great user experience. Please take a look at our Privacy Statement if you’d like more information about cookies, and on how and why we use them.

GitLaw defines customer data as all data provided by the customer to GitLaw through their use of GitLaw services. Some customer data is personal data as defined under GDPR.

Welcome to the GitLaw Privacy Statement. This is where we describe how we handle your “Personal Data”, which is information that is directly linked or can be linked to you. It applies to the Personal Data that GitLaw processes as the “Data Controller” when you interact with websites, applications, and services that display this Statement (collectively, “Services”).

GitLaw policies on Bullying and Harassment, Disrupting the Experience of Other Users. Doxxing and Invasion of Privacy, Hate Speech and Discrimination, Impersonation, Misinformation and Disinformation, Sexually Obscene Content and Threats of Violence and Gratuitously Violent Content.

We host a wide variety of collaborative projects from all over the world, and that collaboration only works when our users are able to work together in good faith. While using the Service, you must comply with our Acceptable Use Policies, which include some restrictions on content and conduct on GitLaw related to user safety, intellectual property, privacy, authenticity, and other limitations. In short, be excellent to each other.

GitLaw Community Guidelines