This document provides a guide on how to submit a DMCA takedown notice on GitHub. It outlines the requirements and steps needed for processing a takedown notice, emphasizing the need for specificity in identifying the copyrighted work and the alleged infringement. The document advises consulting a legal professional before proceeding and underscores that false information can result in legal consequences. It also mentions the possibility of a counter-notice from the accused party. The guide further provides instructions on submitting the notice through GitHub's form or via email, and mentions alternative methods like physical mail, while noting the longer response time. The document is intended to ensure proper compliance with the DMCA process for content removal on GitHub.

This legal document describes GitHub's use of cookies to provide and secure its websites, along with analyzing their usage to enhance user experience. It provides transparency on data utilization, collection, and sharing, and lists specific cookies used, their purposes, and expiration periods. Users can subscribe to updates and manage their cookie preferences, which may prove useful for understanding and managing data privacy and consent related to cookies on GitHub's platform.

This document outlines the procedures for submitting content removal requests on GitHub under three distinct policies: the DMCA Takedown Policy for reporting copyright-infringing content, the GitHub Trademark Policy for addressing misuse of trademark-protected materials, and the GitHub Private Information Removal Policy for handling private data concerns. Each policy has specific reporting requirements, and submitters are encouraged to familiarize themselves with the appropriate policy before filing a report. GitHub advises consultation with legal counsel for assistance in determining the relevant policy for specific situations.

This Mutual Non-Disclosure Agreement (MNDA) is used to protect confidential information shared between two parties for a specified purpose. It defines how confidential information should be handled, outlining obligations for the receiving party to use the information only for the agreed purpose, restrict further disclosures, and ensure protection standards. Exceptions to confidentiality obligations, conditions for required disclosures by law, and processes for the return or destruction of information upon termination are also detailed. The agreement is governed by specified state laws and enforceable in designated jurisdictions, with provisions allowing equitable relief for breaches. It binds both parties to adhere to confidentiality terms throughout the defined period, ensuring legal recourse in maintaining the discretion of sensitive information exchanged.

This document outlines a Design Partner Agreement developed to establish a collaboration between a provider and a partner for early access to a product. The agreement includes Terms on Product Access, Program Participation, Feedback Provision, Fees, Confidentiality, and Intellectual Property. Governing law and chosen courts for disputes are specified. It also includes provisions on Term & Termination, Disclaimer of Warranties, Confidential Handling, and Ownership of Feedback. The agreement ensures that the partner participates in the program, receives benefits, and that the provider develops the product using partner feedback. The document can be used by technology vendors to formalize cooperation terms with design partners for product development and improvement.

The legal document is GitHub's Terms of Service. It outlines the terms under which the GitHub services can be used, focusing on the rights and responsibilities of users and GitHub itself. This document can be used to clarify the legal relationship between GitHub and its users, outlining user rights, content ownership, account management, acceptable use policies, and payment obligations. It also details the conditions for account termination and GitHub's liability limitations. Legal professionals and GitHub users can reference this document to understand their rights and obligations when using GitHub's services.

The Cloud Service Agreement outlines the terms for accessing a cloud-based service provided by a specified vendor to a customer. It covers details such as the effective date, governing laws, subscription and pilot period specifics, fees, payment processes, auto-renewal conditions, use limitations, and available technical support. The document also includes clauses on representations and warranties, indemnification, and terms for service level agreements. It serves as a comprehensive framework for both parties to agree upon the usage, responsibilities, and limitations associated with the cloud service, ensuring legal clarity and protection.

This document can be used by GitHub Enterprise customers to understand which subprocessors are authorized to process their data. It provides a list of authorized subprocessors, their processing descriptions, processing locations, and corporate locations. This information helps customers comply with data protection regulations, like the GDPR, by giving them transparency into who processes their data and where, ensuring they can trust GitHub's handling of their personal and customer data.

This document is a template for a non-binding Letter of Intent (LOI) designed to outline the preliminary terms and intentions for a potential agreement between two parties. It serves as a basis for negotiating a future definitive agreement and includes sections for specifying product details, functionality, fees, and launch date. The document allows customization, including confidentiality options that can be tailored to the parties' preferences. It is intended to facilitate initial discussions and clarify mutual intentions without creating any binding commitments, except for confidentiality provisions, which may be formalized according to selected options.

This legal document is a partnership agreement that outlines the terms and obligations between two parties, referred to as the Company and the Partner. It can be used to formalize the cooperative relationship between the parties, detailing their respective obligations, payment terms, trademark licensing, and confidentiality commitments. The agreement provides a comprehensive framework for managing the partnership, including details on payment processes, governing law, liability, indemnification, and procedures for disputes and termination. It also outlines licensing arrangements and brand usage, ensuring both parties are clear on responsibilities and limitations. This document serves as a critical legal tool to protect each party's interests and ensure smooth collaboration within a defined legal structure.