You are responsible for your Account's security and for all content and activity under it
You are responsible for keeping your Account secure while you use the Service. GitHub offers tools such as two-factor authentication, but the content of your Account and its security are up to you. You are responsible for all content posted and activity under your Account, even when content is posted by others who have Accounts under your Account, and for maintaining the security of your Account and password. GitHub says it cannot and will not be liable for any loss or damage from your failure to comply with this security obligation.
Supporting quotations
You are responsible for keeping your Account secure while you use our Service. We offer tools such as two-factor authentication to help you maintain your Account's security, but the content of your Account and its security are up to you.
You are responsible for all content posted and activity that occurs under your Account (even when content is posted by others who have Accounts under your Account).
You are responsible for maintaining the security of your Account and password. GitHub cannot and will not be liable for any loss or damage from your failure to comply with this security obligation.
Qualifications & exceptions
GitHub's no-liability statement is limited to loss or damage from your failure to comply with the security obligation.
Security & Safeguards · Procedure
You must promptly tell GitHub Support about unauthorized use of or access to your Account
You will promptly notify GitHub through the GitHub Support portal if you become aware of any unauthorized use of, or access to, the Service through your Account, including any unauthorized use of your password or Account.
Supporting quotations
You will promptly notify GitHub by contacting us through the [GitHub Support portal](https://support.github.com/) if you become aware of any unauthorized use of, or access to, our Service through your Account, including any unauthorized use of your password or Account.
Qualifications & exceptions
The duty arises when you become aware of the unauthorized use or access.
Security & Safeguards · Company commitment
GitHub treats private repository contents as confidential to you and protects them with at least reasonable care
Some Accounts may have private repositories, which let the User control access to Content. GitHub considers the contents of private repositories to be confidential to you and will protect them from unauthorized use, access or disclosure in the same manner it would protect its own similar confidential information, and in no event with less than a reasonable degree of care.
Supporting quotations
Some Accounts may have private repositories, which allow the User to control access to Content.
GitHub considers the contents of private repositories to be confidential to you. GitHub will protect the contents of private repositories from unauthorized use, access, or disclosure in the same manner that we would use to protect our own confidential information of a similar nature and in no event with less than a reasonable degree of care.
Qualifications & exceptions
Private repositories are available to “some” Accounts.
Security & Safeguards · Restriction or exception
GitHub personnel will not access private repository content without your consent except in five listed circumstances
You control access to the content of your private repositories. GitHub treats it as confidential to you, and GitHub personnel will not access it without your consent except for security purposes; automated scanning or manual review for known vulnerabilities, active malware, or other content known to violate the Terms of Service; assisting the repository owner with a support matter; maintaining the integrity of the Service; or complying with legal obligations if GitHub has reason to believe the contents violate the law. Another paragraph says GitHub may also be compelled by law to disclose private repository contents.
Supporting quotations
You control access to the content of your private repositories. GitHub considers the contents of private repositories to be confidential to you, as set forth in Section E.2, and GitHub personnel will not access private repository content without your consent except in the following circumstances:
for security purposes;
for automated scanning or manual review for known vulnerabilities, active malware, or other content known to violate our Terms of Service;
to assist the repository owner with a support matter;
to maintain the integrity of the Service; or
to comply with our legal obligations if we have reason to believe the contents are in violation of the law.
Additionally, we may be compelled by law to disclose the contents of your private repositories.
Qualifications & exceptions
The legal-obligations circumstance applies where GitHub has reason to believe the contents are in violation of the law.
The short version of this section also mentions access with your consent; the operative list is quoted here.
Security & Safeguards · Company commitment
GitHub says it will give notice of private repository access, except in five listed situations
GitHub will provide notice regarding its access to private repository content, unless the access is for legal disclosure, to comply with its legal obligations, where GitHub is otherwise bound by requirements under law, for automated scanning, or in response to a security threat or other risk to security.
Supporting quotations
GitHub will provide notice regarding our access to private repository content, unless for legal disclosure, to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security.
Qualifications & exceptions
The notice commitment is conditioned on none of the listed exceptions applying.