GitLab

GPST ¶32 points at Section 6.1, which is not in the document

GitLab Professional Services Terms ¶32 reads: "GitLab represents and warrants that its provision of Professional Services under an SOW or Order Form will be rendered in a professional and workmanlike manner. If GitLab fails to meet the foregoing warranty, upon Customer's written notice, within ninety (90) days after completion of the applicable…" It cites Section 6.1. No such clause appears anywhere in GitLab Professional Services Terms.

• GPST ¶32

  “GitLab represents and warrants that its provision of Professional Services under an SOW or Order Form will be rendered in a professional and workmanlike manner. If GitLab fails to meet the foregoing warranty, upon Custom…”

Wrong? Ask for access to correct it.

GPST ¶5 points at Section 2.3, which is not in the document

GitLab Professional Services Terms ¶5 reads: ""Change Order" means any change to an SOW or Order Form, as applicable, as described in Section 2.3 below." It cites Section 2.3. No such clause appears anywhere in GitLab Professional Services Terms.

• GPST ¶5

  “"Change Order" means any change to an SOW or Order Form, as applicable, as described in Section 2.3 below.”

Wrong? Ask for access to correct it.

GPST ¶34 points at SECTION 6.1, which is not in the document

GitLab Professional Services Terms ¶34 reads: "WARRANTY DISCLAIMER. SECTION 6.1 SETS FORTH GITLAB'S EXCLUSIVE WARRANTY WITH REGARD TO THE PROFESSIONAL SERVICES, AND IS IN LIEU OF ALL OTHER WARRANTIES. GITLAB DOES NOT MAKE ANY OTHER WARRANTY OF ANY KIND, WHETHER EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, AND TO THE MAXIMUM EXTENT PERMITTED BY APPL…" It cites SECTION 6.1. No such clause appears anywhere in GitLab Professional Services Terms.

• GPST ¶34

  “WARRANTY DISCLAIMER. SECTION 6.1 SETS FORTH GITLAB'S EXCLUSIVE WARRANTY WITH REGARD TO THE PROFESSIONAL SERVICES, AND IS IN LIEU OF ALL OTHER WARRANTIES. GITLAB DOES NOT MAKE ANY OTHER WARRANTY OF ANY KIND, WHETHER EXPRE…”

Wrong? Ask for access to correct it.

TPA cl. 12.2 points at Section 10.2, which is not in the document

Technology Partner Agreement cl. 12.2 reads: "12.2. Neither Party shall assign, delegate, subcontract or otherwise transfer, directly or by operation of law, any of the rights or obligations of this Agreement nor any part or all of this Agreement without the prior written consent of the other Party. Any attempt to transfer, assign, delegate or…" It cites Section 10.2. No such clause appears anywhere in Technology Partner Agreement.

• TPA cl. 12.2

  “12.2. Neither Party shall assign, delegate, subcontract or otherwise transfer, directly or by operation of law, any of the rights or obligations of this Agreement nor any part or all of this Agreement without the prior w…”

Wrong? Ask for access to correct it.

GitLab Privacy Statement is drafted as if it could incorporate GitLab Subscription Agreement

GitLab Privacy Statement is a public notice and GitLab Subscription Agreement is part of the agreement. ¶52 reads: "We use your Personal Data to provide the Services you have subscribed to, and to complete and administer the contract you have entered into with GitLab, which includes the Subscription Agreement, the Website Terms of Use, event and training agreements, and any…"

• PP ¶52

  “We use your Personal Data to provide the Services you have subscribed to, and to complete and administer the contract you have entered into with GitLab, which includes the Subscription Agreement, the Website Terms of Use…”

• TOS — first clause

  “GitLab Subscription Agreement”

Wrong? Ask for access to correct it.

GitLab Privacy Statement is drafted as if it could incorporate GitLab Terms of Use

GitLab Privacy Statement is a public notice and GitLab Terms of Use is part of the agreement. ¶52 reads: "We use your Personal Data to provide the Services you have subscribed to, and to complete and administer the contract you have entered into with GitLab, which includes the Subscription Agreement, the Website Terms of Use, event and training agreements, and any…"

• PP ¶52

  “We use your Personal Data to provide the Services you have subscribed to, and to complete and administer the contract you have entered into with GitLab, which includes the Subscription Agreement, the Website Terms of Use…”

• UT — first clause

  “GitLab Terms of Use”

Wrong? Ask for access to correct it.

GitLab Privacy Statement is drafted as if it could incorporate GitLab Acceptable Use Policy

GitLab Privacy Statement is a public notice and GitLab Acceptable Use Policy is part of the agreement. ¶66 reads: "To enforce the Terms of Use, Acceptable Use Policy and other legal terms that govern our Services | Account Information Profile Information Content you provide through the use of the Services"

• PP ¶66

  “To enforce the Terms of Use, Acceptable Use Policy and other legal terms that govern our Services | Account Information Profile Information Content you provide through the use of the Services”

• AUP — first clause

  “GitLab Acceptable Use Policy”

Wrong? Ask for access to correct it.

Reseller/Referral Agreement is drafted as if it could incorporate GitLab Subscription Agreement

Reseller/Referral Agreement is a perimeter and GitLab Subscription Agreement is part of the agreement. cl. 1.16 reads: "Terms and Conditions - Means Gitlab's standard terms and conditions applicable to the Products and Services, including GitLab's Subscription Agreement and Professional Services Agreement located at https://about.gitlab.com/terms, as may be updated in GitLab's…"

• RA cl. 1.16

  “1.16. Terms and Conditions - Means Gitlab's standard terms and conditions applicable to the Products and Services, including GitLab's Subscription Agreement and Professional Services Agreement located at https://about.gi…”

• TOS — first clause

  “GitLab Subscription Agreement”

Wrong? Ask for access to correct it.

Reseller/Referral Agreement is drafted as if it could incorporate GitLab Subscription Agreement

Reseller/Referral Agreement is a perimeter and GitLab Subscription Agreement is part of the agreement. cl. 2.1 reads: "For the avoidance of doubt, the Parties acknowledge and agree the terms and conditions stated within this Agreement, an Exhibit, and an executed Order Form shall govern with respect to all matters contemplated herein."

• RA cl. 2.1

  “2.1. GitLab and Partner hereby establish the Partnership(s) described in one or more Exhibits as selected by the Parties in the Cover Page. Except as may be expressly set forth in an Exhibit, this Agreement and all Exhib…”

• TOS — first clause

  “GitLab Subscription Agreement”

Wrong? Ask for access to correct it.

Reseller/Referral Agreement is drafted as if it could incorporate GitLab Subscription Agreement

Reseller/Referral Agreement is a perimeter and GitLab Subscription Agreement is part of the agreement. cl. 2.3 reads: "Free Software shall be subject to all other terms and conditions in this Agreement."

• RA cl. 2.3

  “2.3. Partner and GitLab acknowledge and agree that Free Software may be limited in functions, features, maintenance, support and contain other limitations not present in Software purchased. Unless otherwise agreed to bet…”

• TOS — first clause

  “GitLab Subscription Agreement”

Wrong? Ask for access to correct it.

Technology Partner Agreement is drafted as if it could incorporate GitLab Subscription Agreement

Technology Partner Agreement is a perimeter and GitLab Subscription Agreement is part of the agreement. cl. 3.4 reads: "Should Partner meet the eligibility requirements of the Alliance Program, as determined in GitLab's sole discretion, the grant and use of the GitLab Free Software shall be subject to the applicable terms within GitLab's Subscription Agreement, which can be fou…"

• TPA cl. 3.4

  “3.4. Partner and GitLab acknowledge and agree that GitLab Free Software may be limited in functions, features, maintenance, support and contain other limitations not present in GitLab Software purchased. For more informa…”

• TOS — first clause

  “GitLab Subscription Agreement”

Wrong? Ask for access to correct it.

Technical and Organizational Security Measures for GitLab Cloud Services reads as a commitment, but nothing incorporates it into the agreement

GitLab Privacy Statement § we work hard to protect your personal data mentions Technical and Organizational Security Measures for GitLab Cloud Services. No clause anywhere in the published set states that Technical and Organizational Security Measures for GitLab Cloud Services forms part of the agreement.

• PP § we work hard to protect your personal data

  “We work hard to protect your Personal Data. We employ administrative, technical, and physical security controls where appropriate, to protect your information from unauthorized access or destruction. For more information…”

• SEC — first clause

  “Technical and Organizational Security Measures for GitLab Cloud Services”

Wrong? Ask for access to correct it.

GitLab API Terms of Use reads as a commitment, but nothing incorporates it into the agreement

GitLab Terms of Use ¶14 mentions GitLab API Terms of Use. No clause anywhere in the published set states that GitLab API Terms of Use forms part of the agreement.

• UT ¶14

  “Using GitLab's publicly-available APIs | GitLab API Terms of Use”

• GATU — first clause

  “GitLab API Terms of Use”

Wrong? Ask for access to correct it.

GitLab Website Terms of Use reads as part of the agreement, and nothing in the set refers to it

GitLab Website Terms of Use is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

• GWTU — first clause

  “GitLab Website Terms of Use”

Wrong? Ask for access to correct it.

GitLab Professional Services Terms reads as part of the agreement, and nothing in the set refers to it

GitLab Professional Services Terms is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.

• GPST — first clause

  “GitLab Professional Services Terms”

Wrong? Ask for access to correct it.

GitLab for Open Source Program Agreement reads as a commitment, but nothing incorporates it into the agreement

GitLab Terms of Use ¶19 mentions GitLab for Open Source Program Agreement. No clause anywhere in the published set states that GitLab for Open Source Program Agreement forms part of the agreement.

• UT ¶19

  “GitLab for Open Source Program** | GitLab for Open Source Program Agreement”

• GOSP — first clause

  “GitLab for Open Source Program Agreement”

Wrong? Ask for access to correct it.

GitLab for Education Program Agreement reads as a commitment, but nothing incorporates it into the agreement

GitLab Terms of Use ¶18 mentions GitLab for Education Program Agreement. No clause anywhere in the published set states that GitLab for Education Program Agreement forms part of the agreement.

• UT ¶18

  “GitLab for Education Program* | GitLab for Education Program Agreement”

• GEPA — first clause

  “GitLab for Education Program Agreement”

Wrong? Ask for access to correct it.

GitLab Testing Agreement reads as a commitment, but nothing incorporates it into the agreement

GitLab Terms of Use ¶39 mentions GitLab Testing Agreement. No clause anywhere in the published set states that GitLab Testing Agreement forms part of the agreement.

• UT ¶39

  “Testing Agreement (February 28, 2025 - May 19, 2026) | Legacy GitLab Testing Agreement V5”

• GTA — first clause

  “GitLab Testing Agreement”

Wrong? Ask for access to correct it.

S names a Philanthropy Policy we could not find published

Sustainability ¶148 refers to a Philanthropy 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.

• S ¶148

  “For the calendar year 2026, we will limit the in-kind program to 5,000 seats, which was approved by finance and the board in the Philanthropy Policy. Each organization will be eligible for up to 20 seats. This will allow…”

Wrong? Ask for access to correct it.

“Order Form” is used 83 times across 7 documents and no published document defines it

The published set uses the capitalised term “Order Form” 83 times, in 7 documents that create obligations: GitLab Subscription Agreement, Reseller/Referral Agreement, GitLab Professional Services Terms, Agile Planning Terms, GitLab Duo AI Terms (Additional Terms), GitLab Terms of Use and EU Data Act Supplemental Terms. Searching all 27 published documents for a definition of it — in each of the forms this set uses elsewhere: (the “Order Form”), (“Order Form”), and “Order Form” means — returns nothing.

Searched 27 documents, 2,221 clauses. No match.

Wrong? Ask for access to correct it.

“Customer Content” is used 26 times across 4 documents and no published document defines it

The published set uses the capitalised term “Customer Content” 26 times, in 4 documents that create obligations: GitLab Subscription Agreement, GitLab Duo AI Terms (Additional Terms), GitLab Testing Agreement and EU Data Act Supplemental Terms. Searching all 27 published documents for a definition of it — in each of the forms this set uses elsewhere: (the “Customer Content”), (“Customer Content”), and “Customer Content” means — returns nothing.

Searched 27 documents, 2,221 clauses. No match.

Wrong? Ask for access to correct it.

RA names a Master Partner Agreement we could not find published

Reseller/Referral Agreement ¶3 refers to a Master Partner 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.

• RA ¶3

  “Before submitting a Deal Registration, please review the Master Partner Agreement.”

Wrong? Ask for access to correct it.

S names a Expense Policy we could not find published

Sustainability ¶75 refers to a Expense 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.

• S ¶75

  “Local travel only - mileage, train, taxi/rideshares. Must follow and comply with the current limits of our Expense Policy. Code under their individual travel category and use the "GiveLab" classification in Navan”

Wrong? Ask for access to correct it.

CRG names a Ownership Dispute policy we could not find published

Content Removal Guidelines ¶61 refers to a Ownership Dispute 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.

• CRG ¶61

  “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.”

Wrong? Ask for access to correct it.

EDAS names a Transition Notice we could not find published

EU Data Act Supplemental Terms ¶7 refers to a Transition Notice. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.

• EDAS ¶7

  “Customer may request Transition Services by providing sixty (60) days' written notice to GitLab ("Transition Notice Period"). Following expiration of the Transition Notice Period, GitLab shall provide Transition Services…”

Wrong? Ask for access to correct it.

TOS relies on a price list that is not published

GitLab Subscription Agreement ¶21 relies on a price list. No price list was found anywhere in the published set.

• TOS ¶21

  “"Effective Price" means the actual price paid by Customer (List Price minus any applicable discount(s)) as set forth on an Order Form or as purchased via the Website.”

Wrong? Ask for access to correct it.

TOS relies on a statement of work that is not published

GitLab Subscription Agreement ¶35 relies on a statement of work. No statement of work was found anywhere in the published set.

• TOS ¶35

  “"Supplemental Services" means additional capacity, functionality, storage, professional and success services and/or other elements that Customer may procure separately for additional Fees. Supplemental Services may be pu…”

Wrong? Ask for access to correct it.

GitLab Legal is published but no other document refers to it

GitLab Legal sits in the published set with no incoming reference from any other document in the corpus.

• SUB — first clause

  “GitLab Legal”

Wrong? Ask for access to correct it.

GitLab Accessibility Conformance Report International Edition is published but no other document refers to it

GitLab Accessibility Conformance Report International Edition sits in the published set with no incoming reference from any other document in the corpus.

• GACR — first clause

  “GitLab Accessibility Conformance Report International Edition”

Wrong? Ask for access to correct it.

Reseller/Referral Agreement is published but no other document refers to it

Reseller/Referral Agreement sits in the published set with no incoming reference from any other document in the corpus.

• RA — first clause

  “Reseller/Referral Agreement”

Wrong? Ask for access to correct it.

The minimum age of a user is stated 4 times, in 2 different figures

The minimum age of a user appears in 3 documents. The figures stated are 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 ¶48 — states 13

  “With the exception of Educational Licenses, users must be at least 13 years of age to create an account.”

• GLER ¶22 — states 18

  “Law enforcement officials who believe that notification would jeopardize an investigation should obtain an appropriate court order that specifically prohibits customer notification, such as an order issued under 18 U.S.C…”

Wrong? Ask for access to correct it.