Content Removal Guidelines

DMCA (Digital Millennium Copyright Act) takedown requests

We take the intellectual property rights of others seriously and require that our users do the same. The Digital Millennium Copyright Act (DMCA) established a process for addressing claims of copyright infringement. If you own a copyright or have authority to act on behalf of a copyright owner and want to make a claim that a third party is infringing that copyright on or through GitLab’s services, Submitting a DMCA notice section below.

Submitting a DMCA notice

If you believe that someone is infringing on your copyright as the copyright owner, you can send a DMCA notice to dmca@gitlab.com.

Your DMCA notice must include the following information:

1. Identify the copyrighted work. A description of the copyrighted work that you claim is being infringed;
2. Identify the allegedly-infringing material. A description of the material you claim is infringing and that you want removed or access to which you want disabled and the URL or other location of that material;
   • Be as specific as possible. If you believe less than the whole project infringes, identify the specific project, file, or line numbers within a file a user would need to delete in order to remedy the infringement.
   • GitLab will not automatically disable forks of a project unless they are explicitly identified within the notice you send. It is your responsibility to determine that the material identified, including any fork(s) included in a notice, independently meet the notice requirements.
3. Provide contact information. Your name, title (if acting as an agent), address, telephone number, and email address;
4. Include the following statement: “I have a good faith belief that the use of the copyrighted material I am complaining of is not authorized by the copyright owner, its agent, or the law (for example, as a fair use)”;
5. Include the following statement: “The information in this notice is accurate and, under penalty of perjury, I am the owner, or authorized to act on behalf of the owner, of the copyright or of an exclusive right that is allegedly infringed”; and
6. Signature. An electronic or physical signature of the owner of the copyright or a person authorized to act on the owner’s behalf.

Notices with missing or inaccurate information cannot be processed. Upon receipt of a deficient notice, a member of our team may reach out to you for more information.

What happens next?

We will review your DMCA notice. If we verify that you have submitted the required information, we will take whatever action we deem appropriate under the DMCA, which may include the removal of the challenged content from the website or disabling access to the account(s) of the reported user(s).

Valid notices will be forwarded to the reported account owner, allowing them to submit a counter notice or remove the content from gitlab.com. If a responsive counter notice is deemed valid, we will forward it to you for further action.

Responding to a DMCA notice

If you receive a gitlab.com DMCA notice for content that is in your control, you can respond to the notice by:

1. removing the reported content from gitlab.com, or
2. if you believe your content is mistakenly the subject of the DMCA notice, you have the right to contest the notice by submitting a DMCA counter notice by following the instructions below.

If you do not respond or take no action with regard to a DMCA notice we send to you, the reported content will be made private, and we may take further action we deem appropriate under the DMCA.

Submitting a DMCA counter notice

If it is not possible to come to an agreement with the reporting copyright owner, the content owner may submit a DMCA counter notice to dmca@gitlab.com within ten (10) business days of the date of receiving our notice. If we receive a valid counter notice, we will email a copy of the notice to the copyright owner.

Your DMCA counter notice must include the following information:

1. Contact Information. Your name, title (if acting as an agent), physical address, email address, and phone number;
2. Content Identification. A reasonable identification of the material that has been removed or to which access has been blocked;
3. Statement under Perjury. Include the following statement: “I swear, under penalty of perjury, that I have a good faith belief that the material was removed or disabled as a result of mistake or misidentification of the material to be removed or disabled”;
4. Consent to Jurisdiction. Include one of following statements (as appropriate):
   • If based in the United States: “I consent to the jurisdiction of the Federal District Court for the judicial district in which my provided address is located”
   • If based outside of the United States: “I consent to the jurisdiction of any United States Federal District Court in which GitLab may be found”
5. Consent to service of process. Include the following statement: “I will accept service of process from the person who provided the original notification or an agent of such person”; and
6. Signature. An electronic or physical signature of the owner of the copyright or the person authorized to act on the owner’s behalf.

What happens next?

We will review the counter notice, and:

• if the counter notice doesn’t satisfy the DMCA requirements, we’ll request a revised submission; or
• if the counter notice is complete and valid, we’ll forward the counter notice to the person who filed the original takedown notice, advising that the challenged content will be reinstated within 10-14 business days, unless we receive a notification that the copyright owner is seeking a court order regarding this matter.

Anti-Circumvention Technology

The DMCA prohibits the circumvention of technical protection measures that prevent access to copyrighted works. If you believe that content hosted on GitLab violates this prohibition, send a complaint to dmca@gitlab.com. The complaint should include the following:

1. Identify the copyrighted work. A description of the copyrighted work that is being protected by the technical measure;
2. Identify the alleged circumventing content. Be sure to include detailed statements that describe:
   • What the technical protection measures are;
   • How the technical protection measures effectively control access to the copyrighted work; and
   • How the content hosted on GitLab is designed to circumvent those technical protection measures.
3. Provide contact information. Your name, title (if acting as an agent), address, telephone number, and email address;
4. Include the following statement: “I have a good faith belief that the use of the copyrighted material I am complaining of is not authorized by the copyright owner, its agent, or the law (for example, as a fair use)”;
5. Include the following statement: “The information in this notice is accurate and, under penalty of perjury, I am the owner, or authorized to act on behalf of the owner, of the copyright or of an exclusive right that is allegedly infringed”; and
6. Signature. An electronic or physical signature of the owner of the copyright or a person authorized to act on the owner’s behalf.

We will review your complaint and take whatever action we deem appropriate under the DMCA, including the removal of the challenged content. Furthermore, we may, in appropriate circumstances, disable access or terminate the account(s) of the reported user(s).

EU Illegal Content Reporting

The DSA requires hosting services to provide a method for people to report content that is potentially illegal in the EU.

Please use the DSA form to report content that you believe is illegal in the European Union. This form should be used by individuals claiming legal rights in the EU, as well as individuals or entities designated as trusted flaggers pursuant to the DSA. Trusted flagger reports will be prioritized for review, in accordance with the DSA. We also ask individuals who report potentially illegal content in the EU to provide clear and concise information in English, or provide an English translation, wherever possible.

GitLab may restrict access to content determined to violate the law(s) of the EU country specified in your report. If you want to report a potential violation of GitLab’s Acceptable Use Policy or Community Code of Conduct policies rather than an EU legal violation, please refer to this guide on how to report abuse. Note that if you don’t have a GitLab account, you can report potential violations by contacting the GitLab Trust and Safety team at abuse@gitlab.com.

Monthly active recipients in the European Union - Digital Services Act Article 24(2) Disclosure

The information below covers the reporting period from January 1, 2026 to June 30, 2026.

As of June 2026, GitLab.com has approximately 1,800,000 monthly average active recipients of the service in the European Union.

For non-logged-in users, our tracking relies on standard web analytics technologies. This methodology has inherent limitations, as users who access GitLab from multiple devices or browsers, or who have certain privacy settings enabled, may be counted more than once in our calculations. Conversely, multiple users sharing the same device might be undercounted. This means our reported number represents our best estimate of unique recipients based on available data. This approach is consistent with the DSA’s guidance that providers should not perform specific tracking of individuals online to avoid double counting. During the current reporting period, GitLab identified an anomalous increase in traffic patterns affecting logged‑out visitor counts on gitlab.com, which is reflected in the reported figure. GitLab is reviewing and improving its measurement methodology to better account for automated traffic and intends to implement these improvements for future reporting periods.

This information is provided solely to satisfy the requirements of the DSA and should not be used for any other purpose. This information may differ from user metrics, such as registered users, reported in other contexts.

Namespaces and other disputes

Disputes regarding namespaces, group ownership, and trademarks may be governed by other policies. Please refer to Intellectual Property on GitLab.com and our Ownership Dispute policy for further information.