Paradraw
17 published11 named, not published0 expected, not published97 relationships1727 clauses
Every legal document GitHub publishes, and the ones its own terms name that nobody published. Free to read.Other companies
HighStructure

GitHub Research Program Terms - GitHub Docs is drafted as if it could incorporate GitHub General Privacy Statement - GitHub Docs

GitHub Research Program Terms - GitHub Docs is a perimeter and GitHub General Privacy Statement - GitHub Docs is a notice document. ¶32 reads: "This Agreement, together with the Generally Applicable Terms and the GitHub Privacy Statement, represent the complete and exclusive statement of the agreement between you and us."

  • GRPT ¶32

    “This Agreement may only be modified by a written amendment signed by an authorized representative of GitHub. This Agreement, together with the Generally Applicable Terms and the GitHub Privacy Statement, represent the co…”

  • PP — first clause

    “GitHub General Privacy Statement”

Wrong? Ask for access to correct it.

HighStructure

GitHub Marketplace Terms of Service - GitHub Docs reads as part of the agreement, and nothing in the set refers to it

GitHub Marketplace Terms of Service - GitHub Docs is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

HighPrecedence

GitHub Enterprise Service Level Agreement - GitHub Docs reads as a commitment, but nothing incorporates it into the agreement

GitHub Corporate Terms of Service - GitHub Docs cl. 6 mentions GitHub Enterprise Service Level Agreement - GitHub Docs. No clause anywhere in the published set states that GitHub Enterprise Service Level Agreement - GitHub Docs forms part of the agreement.

Wrong? Ask for access to correct it.

HighStructure

GitHub Pre-release License Terms - GitHub Docs reads as part of the agreement, and nothing in the set refers to it

GitHub Pre-release License Terms - GitHub Docs is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

Wrong? Ask for access to correct it.

MediumGap

PP names a Data Protection Agreement we could not find published

GitHub General Privacy Statement - GitHub Docs ¶10 refers to a Data Protection Agreement. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • PP ¶10

    “Should you access a GitHub Service through an account provided by an organization, such as your employer or school, the organization becomes the Data Controller, and this Privacy Statement's direct applicability to you c…”

Wrong? Ask for access to correct it.

MediumGap

TOS names a Export Controls policy we could not find published

GitHub Terms of Service - GitHub Docs ¶73 refers to a Export Controls policy. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • TOS ¶73

    “You may not use GitHub in violation of export control or sanctions laws of the United States or any other applicable jurisdiction. You may not use GitHub if you are or are working on behalf of a Specially Designated Nati…”

Wrong? Ask for access to correct it.

MediumGap

TOS names a Enterprise Cloud Addendum we could not find published

GitHub Terms of Service - GitHub Docs ¶82 refers to a Enterprise Cloud Addendum. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • TOS ¶82

    “If you have signed up for GitHub Enterprise Cloud, the Enterprise Cloud Addendum applies to you, and you agree to its provisions.”

Wrong? Ask for access to correct it.

MediumGap

TOS names a Supplemental Terms we could not find published

GitHub Terms of Service - GitHub Docs ¶149 refers to a Supplemental Terms. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • TOS ¶149

    “Short version: You need to follow certain specific terms and conditions for GitHub's various features and products, and you agree to the Supplemental Terms and Conditions when you agree to this Agreement.”

Wrong? Ask for access to correct it.

MediumGap

TOS names a Site Policy we could not find published

GitHub Terms of Service - GitHub Docs ¶237 refers to a Site Policy. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • TOS ¶237

    “We reserve the right, at our sole discretion, to amend these Terms of Service at any time and will update these Terms of Service in the event of any such amendments. We will notify our Users of material changes to this A…”

Wrong? Ask for access to correct it.

MediumGap

GSAT names a Stripe Connected Account Agreement we could not find published

GitHub Sponsors Additional Terms - GitHub Docs ¶21 refers to a Stripe Connected Account Agreement. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • GSAT ¶21

    “(b) All Sponsorship funds contributed by Sponsors are held in the Stripe Connected Accounts FBO Sponsored Developers established and maintained by Stripe pursuant to Stripe's terms and conditions, including: The Stripe C…”

Wrong? Ask for access to correct it.

MediumGap

GSAT names a Stripe documentation we could not find published

GitHub Sponsors Additional Terms - GitHub Docs ¶104 refers to a Stripe documentation. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • GSAT ¶104

    “If you are paid through Stripe Connect, you will receive payouts on the 22nd of the month for the balance accrued since the last payout, regardless of the amount of the balance. Payout initiation dates vary by country, a…”

Wrong? Ask for access to correct it.

MediumGap

GSAT names a Stripe Recipient Agreement we could not find published

GitHub Sponsors Additional Terms - GitHub Docs ¶125 refers to a Stripe Recipient Agreement. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • GSAT ¶125

    “We use Stripe to make payouts to Sponsored Developer Accounts. The Stripe Recipient Agreement applies to your receipt of such payouts. To receive payouts from GitHub Sponsors, you must provide us accurate and complete in…”

Wrong? Ask for access to correct it.

MediumGap

GPLT names a Microsoft Product Terms we could not find published

GitHub Pre-release License Terms - GitHub Docs ¶61 refers to a Microsoft Product Terms. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

  • GPLT ¶61

    “If you license GitHub through Microsoft, these terms shall be considered an amendment to the Microsoft Product Terms for GitHub Offerings for the duration of your use of the pre-release software.”

Wrong? Ask for access to correct it.

MediumGap

GCTS relies on a statement of work that is not published

GitHub Corporate Terms of Service - GitHub Docs ¶26 relies on a statement of work. No statement of work was found anywhere in the published set.

  • GCTS ¶26

    “"Fees" means the fees Customer is required to pay GitHub to (i) use the Products during the applicable Term or (ii) receive Professional Services, as such fees are reflected on an Order Form or SOW.”

Wrong? Ask for access to correct it.

MediumGap

PP relies on a cookie list that is not published

GitHub General Privacy Statement - GitHub Docs ¶128 relies on a cookie list. No cookie list was found anywhere in the published set.

  • PP ¶128

    “The table below provides additional information about how we use different types of cookies: Purpose | Description”

Wrong? Ask for access to correct it.

LowStructure

GitHub Global Data Privacy Notice for Candidates - GitHub Docs is published but no other document refers to it

GitHub Global Data Privacy Notice for Candidates - GitHub Docs sits in the published set with no incoming reference from any other document in the corpus.

Wrong? Ask for access to correct it.

LowStructure

GitHub Research Program Terms - GitHub Docs is published but no other document refers to it

GitHub Research Program Terms - GitHub Docs sits in the published set with no incoming reference from any other document in the corpus.

Wrong? Ask for access to correct it.

LowRegister

The minimum age of a user is stated 8 times, in 3 different figures

The minimum age of a user appears in 3 documents. The figures stated are 16, 13, 18. These may each be right for a different thing. What the corpus does not do is say which figure governs which question.

  • PP ¶174 — states 16

    “We do not "sell" or "share" the personal information of known minors under 16 years of age.”

  • TOS ¶49 — states 13

    “A User must be at least 13 years of age.”

  • GSAT ¶38 — states 18

    “If you are over the age of 13 but are under 18, you can give and receive Sponsor funds, provided that Stripe, our payment processor, can collect verification information from your legal guardian.”

Wrong? Ask for access to correct it.

Held back

11 readings, on top of the 18 above

Each puts two clauses side by side that answer the same question differently, and quotes both.

Sign up free — €5 of free drawing credit, enough for your first drawing — and come back here to unlock them.

The drawing, in words

GitHub’s legal documents

GitHub publishes 17 legal documents. Its own terms name 11 more that we could not find published. Every cross-reference inside them resolves. 1 figure is stated more than once, in more than one form.

Published 17

Named, not published 11

  • Data Protection Agreement
  • Export Controls policy
  • Enterprise Cloud Addendum
  • Supplemental Terms
  • Site Policy
  • Stripe Connected Account Agreement
  • Stripe documentation
  • Stripe Recipient Agreement
  • Microsoft Product Terms
  • Statement of work
  • Cookie list

Named in GitHub’s own terms and not found in its sitemap, legal index or trust centre. It may exist and be available on request.

How they connect 64

  • 22 times a document depend on another existing
  • 20 times a document cite another document
  • 16 times a document incorporate another by reference
  • 4 times a document rely on a definition from another
  • 1 time a document say which document wins on a conflict
  • 1 time a document amend another

Read from github.com on 8 October 2026. A description of how the documents fit together, not legal advice. Is this your company?