10. Content Removal Policies - Submitting content removal requests
Updated 17 October 2025
This document outlines the process for submitting content removal requests on GitHub, covering various scenarios such as copyright infringement under the DMCA, trademark violations, and the unauthorized publication of private information. It advises users to familiarize themselves with the specific policies and reporting requirements for each type of content removal before submitting a request.
Submitting content removal requests
In this article
GitHub Private Information Removal Policy
We understand that copyrighted, trademarked, or private content may get published on GitHub – either accidentally or on purpose – sometimes in repositories that you do not own. Because the nature of this content varies, and because of different applicable laws, each category has its own, distinct reporting requirements outlined in our policies.
If you'd like to request that content be removed from GitHub, 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.
Please note that we're not able to help you determine which policy is appropriate for your specific situation. If you’ve reviewed the policies below and still have questions about whether or not content should be reported as copyright, trademark, or private information, we recommend consulting with independent legal counsel.
DMCA Takedown Policy
The DMCA Takedown Policy can be used to report content that you believe infringes a copyright owned by you or your organization. Once you have reviewed the policy, you may also want to review our Guide to Submitting a DMCA Takedown Notice before submitting a report.
GitHub Trademark Policy
The GitHub Trademark Policy can be used to report content that appears to use your company or business name, logo, or other trademark-protected materials in a manner that may mislead or confuse others about brand or business affiliation.
GitHub Private Information Removal Policy
The GitHub Private Information Removal Policy can be used to report data that is private (confidential and poses a security risk), but that is not necessarily protected by copyright or trademark.
Users in India can contact GitHub's Grievance Officer.
About this template
What is this template?
10. Content Removal Policies - Submitting content removal requests is a free, ready-to-use Data Protection & Privacy template you can open, customize, and download on GitLaw. It gives you a professionally structured starting point, so you never have to draft from a blank page. The wording is plain and modern, organized into clear sections that are easy to read, edit, and adapt to your own situation before you share or sign it.
When should you use it?
Reach for this Data Protection & Privacy template whenever you need a reliable agreement quickly and want to be sure the essentials are covered. It suits individuals, freelancers, startups, and established businesses alike. Instead of paying for a document drafted from scratch, you can start here, tailor the details to your arrangement, and have a polished draft ready in minutes. This version is drafted with India and United States of America in mind, though you should always review the final wording against the laws that apply to you.
What's typically included?
A well-drafted Data Protection & Privacy usually sets out the parties involved, the scope of the agreement, and each side's rights and responsibilities. Expect sections covering key terms and definitions, how long the agreement lasts, how it can be ended, and what happens if something goes wrong. This template brings those building blocks together in a sensible order, so you can focus on the specifics rather than worrying about what to include. Open it to read the full document, then sign up to edit, negotiate, and e-sign it directly in GitLaw.