GitLab
Developer platform · about.gitlab.com · last read 2026-11-16
At a glance
- Is GitLab GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what GitLab itself publishes, each answer linked to its source and the date we read it.
- Does GitLab have a data processing agreement (DPA)?
- Yes. GitLab publishes a data processing agreement at handbook.gitlab.com. It gives 30 days' notice before a new subprocessor is added. It promises breach notification "without undue delay", with no number of hours. Source and date
- Does GitLab have a SOC 2 report?
- GitLab states SOC 2 Type 2 on its own page, but does not say there how to get a report. In GitLab's words: “GitLab maintains a SOC 2 Type 2 report for the Security, Confidentiality and Availability Trust Services Criteria for GitLab.com.” We read this on 2026-10-05. Source and date
- Is GitLab ISO 27001 certified?
- GitLab states ISO/IEC 27001 (2022 edition, as GitLab names it) on its own page, but does not say there how to get the certificate. In GitLab's words: “GitLab maintains ISO/IEC 27001:2022 certification for the information security management system supporting the GitLab software-as-a-service (SaaS) subscriptions, GitLab.com and GitLab Dedicated.” We read this on 2026-10-05. Source and date
- Where is GitLab's trust center?
- GitLab publishes a page it calls “Trust Center” at trust.gitlab.com. Some of its documents sit behind a request or sign-in: the page says “Get access”. The page mentions SOC 2, ISO 27001, a penetration test, subprocessors, security questionnaires and a DPA. We read it on 2026-11-03. Source and date
- How does GitLab transfer personal data out of the EU?
- GitLab's agreement relies on the EU standard contractual clauses and the EU-U.S. Data Privacy Framework. GitLab is on the official Data Privacy Framework List (status: Active). Source and date
- Does GitLab offer EU data residency?
- An EU location exists but only on the enterprise tier. Plan it needs: Ultimate. Source and date
- Who are GitLab's subprocessors?
- GitLab lists 49 third-party subprocessors; 43 of them name at least one processing country outside the EEA. We last read the list on 2026-11-02. We have recorded 1 change to it, the latest on 2026-11-02. Source and date
- How do you report a security vulnerability to GitLab?
- GitLab publishes a security.txt at gitlab.com naming https://hackerone.com/gitlab/ or https://about.gitlab.com/security/disclosure/. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
| Legal entity | GitLab Inc. |
|---|---|
| HQ | US |
| Parent company | — |
| Ultimate ownership | US |
| EU contracting entity | — |
| LEI | 9845004Y40FACG81ED49 |
| US CLOUD Act reach | Contracting entity incorporated in the US |
| Source | handbook.gitlab.com · 2026-10-08 |
Legal entity from the vendor's own terms. LEI, registered country and parent company from the Global LEI Index (GLEIF); ownership is left empty where GLEIF names no parent. The CLOUD Act row is arithmetic over those countries, not an assessment of risk.
GitLab data residency
| Region | EU data location | Minimum plan | Source | Observed |
|---|---|---|---|---|
| EU | Enterprise only | Ultimate | docs.gitlab.com | 2026-10-05 |
EU: The page is marked "Tier: Ultimate" and "Offering: GitLab Dedicated", and it lists EU AWS regions such as Europe (Frankfurt) eu-central-1 that you can pick as your primary region. It also says "costs for GitLab Dedicated differ from standard reference architecture costs" but gives no price.
The same question for every vendor: where SaaS vendors store EU data.
GitLab's subprocessor list names AWS and Google for hosting or infrastructure. Which SaaS vendors run on which cloud, and the sovereign offerings of each: sovereign clouds.
Subprocessor chain
49 third parties · 14 of the vendor's own group companies · 43 with a country outside the EEA · all read 2026-11-02
| Subprocessor | Country | Purpose |
|---|---|---|
| Adaptavist | US, EU, CA, MY, AU | Professional Services |
| Adfinis | EU, North Africa, Middle East, AU | Professional Services |
| Amazon Web Services Inc. | US | Cloud Hosting and AI-Powered Product Features |
| Anthropic, PBC | US | AI-Powered Product Features and Customer Support |
| Ascend Integrated Technology Solutions, Inc. | US, CA | Professional Services |
| Black Diamond Development, LLC | US | Professional Services |
| cc cloud GmbH | DE | Professional Services |
| ClickHouse, Inc. | US | Database Hosting |
| Cloud Ace, Inc. | JP | Professional Services |
| Cloudflare Inc. | US, EU | Content Delivery Network |
| Corewire GmbH | DE | Professional Services |
| CPrime | US | Professional Services |
| CyberChange | TR | Professional Services |
| Datamato Technologies Private Limited | IN, AE | Professional Services |
| Decagon AI, Inc. | US | First-Line Customer Support Agent |
| demicon GmbH | DE, AT, CH | Professional Services |
| DevOps Enabler & Co. | IN | Professional Services |
| Devoteam SAS | FR | Professional Services |
| DF Tech FZ-LLC | AE, SA | Professional Services |
| Eficode | US, GB, EU | Professional Services |
| Elasticsearch Inc. | US | Search Functionality and Application Logging and Debugging |
| Fireworks.ai, Inc. | US, EU | AI-Powered Product Features |
| Fivetran, Inc. | US | ELT Pipeline for Customer Support Ticketing |
| GitSimple, LLC | US | Professional Services |
| Glean Technologies, Inc. | US | AI-Powered Knowledge Base for Support Services |
| Google LLC | US | Cloud Hosting, Customer Support, and AI-Powered Product Features |
| HCS Company B.V. | EU | Professional Services |
| HiddenLayer, Inc. | US | Prompt Injection Security for AI-Powered Product Features |
| IntouchCX Disrupt Inc. | IN | Outsourced Customer Support Business Processes |
| JSaunders Solutions, LLC d/b/a NextLink Labs | US, CA | Professional Services |
| LangChain, Inc. | US | Logging for AI-Powered Product Features |
| Mailgun Technologies, Inc. | US, EU | Transactional Email APIs |
| N22 Technologies LLC | TR | Professional Services |
| Norwin Technologies LLC | US, EU, Asia Pacific, IN, MX | Professional Services |
| OpenAI, LLC | US | AI-Powered Product Features |
| OTTRA Ltd | GB, EU | Professional Services |
| Par-Tec S.p.A | EU | Professional Services |
| ReleaseTEAM | US, CA | Professional Services |
| Sfeir S.A. | FR, BE, LU | Professional Services |
| Sirius Federal | US | Professional Services |
| Snowflake Inc. | US | Data Warehouse and Analytics Services for Customer Support Ticketing |
| SPK and Associates, LLC | US | Professional Services |
| Successive Technologies | US, CA, Middle East, JP | Professional Services |
| ThunderSnow Industries Corporation | US | Professional Services |
| Trend Solutions Co., Ltd. | JP | Professional Services |
| VivaOps LLC | North America | Professional Services |
| X-RD Pty Ltd | AU | Professional Services |
| Zendesk Inc. | US | Support Services Portal |
| ZYYX Inc. | JP | Professional Services |
GitLab's own group companies listed as subprocessors (14)
| Company | Country | Purpose |
|---|---|---|
| GitLab BV | NL | Support Services |
| GitLab Canada Corp. | CA | Support Services |
| GitLab France SAS | FR | Support Services |
| GitLab GK | JP | Support Services |
| GitLab GmbH | DE | Support Services |
| GitLab Iberia, S.L. | ES | Support Services |
| GitLab India Pvt Ltd | IN | Support Services |
| GitLab Ireland Ltd | IE | Support Services |
| GitLab IT BV | NL | Support Services |
| GitLab Pty Ltd | AU | Support Services |
| GitLab Singapore Holding PTE Ltd | SG | Support Services |
| GitLab Singapore PTE Ltd | SG | Support Services |
| GitLab South Korea | KR | Support Services |
| GitLab UK Ltd | GB | Support Services |
The count outside the EEA is arithmetic over the country column, not a judgement about lawfulness. A transfer outside the EEA can be perfectly lawful; whether this one is depends on your use, not on the vendor.
Every subprocessor in the registry, and which vendors name it: subprocessors.
Processing terms
From the vendor's data processing agreement · read 2026-10-09 · handbook.gitlab.com
| Term | What the agreement says |
|---|---|
| Transfer mechanism | EU-U.S. DPF |
| Transfer mechanism | SCC module 1 |
| Transfer mechanism | SCC module 2 |
| Transfer mechanism | SCC module 3 |
| Transfer mechanism | Swiss FADP clauses |
| Transfer mechanism | other |
| Notice of new subprocessors | 30 days prior written notice of changes (SCC Clause 9(a) Option 2) |
| Notice of new subprocessors | GitLab updates the list on its website; email notifications to subscribers count as written notice; no new subprocessor is engaged before the 30-day objection period ends |
| If you object to one | Written objection within 30 days of notice, only on the ground that the addition would make Customer violate data protection or legal requirements; parties resolve it in good faith (e.g., a configuration change); deemed approved if no objection |
| Obligations passed to subprocessors | written agreement with each Sub-processor imposing substantially similar contractual obligations to GitLab's under the DPA; GitLab remains responsible for Sub-processors' acts or omissions |
| Breach notification | without undue delay |
| Deletion when the service ends | Upon request, GitLab securely destroys all Personal Data (including all copies) and confirms this to Customer, to the extent permitted by applicable law; GitLab does not automatically delete Customer groups on termination or expiry, and Customer can delete groups itself via in-product settings |
| Getting your data back | Upon request and at Customer's sole discretion, GitLab returns all Personal Data (including all copies) and confirms this, to the extent permitted by applicable law |
| Requests from data subjects | GitLab notifies Customer of a data subject request it receives, or redirects the data subject to Customer, and assists Customer with its obligations for data subject requests |
| Audit | Annual SOC 2/ISO 27001 third-party audit report provided on written request; remote self-serve audit via GitLab Trust Center and Handbook; additional audit (including inspections) may be requested if SCC/GDPR Art. 28 requirements are not met, with scope and fees mutually agreed, at customer's cost |
| Audit | Audits/inspections by Customer or an independent, accredited third-party auditor during business hours, with reasonable advance notice and confidentiality procedures; Customer bears all costs, including GitLab's time; Customer must share the report if it finds material non-compliance |
| Audit | For CCPA purposes, customer may monitor compliance through the measures in Section 13, subject to the requirements and limits in Section 13.d |
| Audit | Where the Turkish SCCs grant audit rights, customer may exercise them subject to the requirements and limitations in Section 13 of the DPA |
| Processing on your instructions | Processes Personal Data only on behalf of Customer and only on Customer's documented instructions; the DPA, Subscription Agreement, Software features/settings and user-initiated processing constitute those instructions |
| Confidentiality of staff | Access limited to personnel who need it; personnel under appropriate contractual confidentiality obligations |
| Security measures | Appropriate technical and organizational measures, set forth in Exhibit B to the DPA |
Terms as the agreement states them. Where it is silent on a term, there is no row; that is not a statement that the vendor does not offer it.
Which version applies
We found no version number or date in the agreement as we read it.
These terms side by side for every vendor: data processing agreements compared. What vendors give you for a transfer impact assessment: transfer impact assessments.
Assurance
Does GitLab have a SOC 2 report?
GitLab states SOC 2 Type 2 on its own page, but does not say there how to get a report. We read this on 2026-10-05.
- Claimed “GitLab maintains a SOC 2 Type 2 report for the Security, Confidentiality and Availability Trust Services Criteria for GitLab.com.”
Source: about.gitlab.com, 2026-10-05
Of the 114 vendors in this registry whose own pages mention SOC 2, 57 say the report is available on request, 1 links to the report itself, and 56 state it without saying how to get it. The type is the one the vendor names.
Is GitLab ISO 27001 certified?
GitLab states ISO/IEC 27001 (2022 edition, as GitLab names it) on its own page, but does not say there how to get the certificate. We read this on 2026-10-05.
- Claimed “GitLab maintains ISO/IEC 27001:2022 certification for the information security management system supporting the GitLab software-as-a-service (SaaS) subscriptions, GitLab.com and GitLab Dedicated.”
Source: about.gitlab.com, 2026-10-05
On the same list GitLab also names ISO/IEC 27017 and ISO/IEC 27018. Each standard's page says how it relates to ISO/IEC 27001.
Of the 122 vendors in this registry whose own pages state ISO/IEC 27001, 16 link to the certificate, 43 say it is available on request, and 63 state it without saying how to get it. A certificate names the certification body, the scope and the expiry date: those are the three things to check.
| Scheme | Status | Scope | Source | Observed |
|---|---|---|---|---|
| Cloud Security Alliance (CSA) Trusted Cloud Provider · CSA | Claimed | — | about.gitlab.com | 2026-10-05 |
| GDPR | Claimed | — | about.gitlab.com | 2026-10-05 |
| ISO/IEC 27001:2022 · ISO27001 | Claimed | information security management system supporting the GitLab software-as-a-service (SaaS) subscriptions, GitLab.com and GitLab Dedicated | about.gitlab.com | 2026-10-05 |
| ISO/IEC 27017:2015 · ISO27017 | Claimed | GitLab software-as-a-service (SaaS) subscriptions, GitLab.com and GitLab Dedicated | about.gitlab.com | 2026-10-05 |
| ISO/IEC 27018:2019 · ISO27018 | Claimed | GitLab software-as-a-service (SaaS) subscriptions, GitLab.com and GitLab Dedicated | about.gitlab.com | 2026-10-05 |
| SOC 2 Type 2 · SOC2T2 | Claimed | Security, Confidentiality and Availability Trust Services Criteria for GitLab.com; Security, Confidentiality and Availability Trust Services Criteria for GitLab Dedicated | about.gitlab.com | 2026-10-05 |
| VPAT | Claimed | — | about.gitlab.com | 2026-10-05 |
Claimed means the vendor asserts the scheme on its own page and offers nothing further. Available on request means the report or certificate exists but sits behind a request, a login or an NDA. Neither is a certificate we have seen. That is a distinction an auditor makes, so we make it too.
SecNumCloud, C5, ENS and HDS for every vendor, with the pages for ISO standards, SOC 2 and TISAX: certifications compared.
Official registers
| Register | Offering, as the register names it | Status | Level | Valid until | Observed |
|---|---|---|---|---|---|
| Data Privacy Framework List (US) | EU-U.S. Data Privacy Framework · GitLab | Active | non-HR data | 2027-04-29 | 2026-10-07 |
| Data Privacy Framework List (US) | Swiss-U.S. Data Privacy Framework · GitLab | Active | non-HR data | 2027-04-29 | 2026-10-07 |
| Data Privacy Framework List (US) | UK Extension to the EU-U.S. DPF · GitLab | Active | non-HR data | 2027-04-29 | 2026-10-07 |
| FedRAMP Marketplace (US) | GitLab Dedicated for Government · GitLab | FedRAMP Authorized | Moderate | — | 2026-10-07 |
| Global LEI Index (GLEIF) | GITLAB INC. · GITLAB INC. | ISSUED | US-DE | 2027-06-15 | 2026-10-08 |
- ACN qualified cloud (Italy): checked 2026-11-16, no entry under GitLab; GitLab Inc.
- ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-16, no entry under GitLab; GitLab Inc.
- CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under GitLab; GitLab Inc.
- DORA critical ICT third-party providers (ESAs): checked 2026-11-16, no entry under GitLab; GitLab Inc.
- Data Privacy Framework List (US): checked 2026-11-16, 3 entries under GitLab; GitLab Inc.
- ENS certificates of conformity (CCN, Spain): checked 2026-11-16, no entry under GitLab; GitLab Inc.
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under GitLab; GitLab Inc.
- FedRAMP Marketplace (US): checked 2026-11-16, 1 entry under GitLab; GitLab Inc.
- GPAI Code of Practice signatories (European Commission): checked 2026-11-16, no entry under GitLab; GitLab Inc.
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-16, no entry under GitLab; GitLab Inc.
What the authority publishes, not what the vendor claims. An entry covers the offering it names and nothing else: a FedRAMP authorisation for a government edition says nothing about the commercial service. No entry is not a finding about security - most vendors never apply - and an entry filed under a name not listed above would not have been found.
What an entry on the Data Privacy Framework List covers, and which vendors hold one: EU-US Data Privacy Framework.
Support window
| Product | Support period | State | SBOM | Source | Observed |
|---|---|---|---|---|---|
| GitLab | — | Not declared | unknown | docs.gitlab.com | 2026-10-11 |
Vulnerability reporting: hackerone.com, about.gitlab.com (security.txt, expires 2027-01-31; read 2026-10-17)
How other vendors publish theirs: security.txt across the registry.
Documents
Where is GitLab's trust center?
GitLab publishes a page it calls “Trust Center” at trust.gitlab.com. Some of its documents sit behind a request or sign-in. The page mentions SOC 2, ISO 27001, a penetration test, subprocessors, security questionnaires and a DPA. We read it on 2026-11-03. Open trust.gitlab.com
- Name “Trust Center”
- Request step “Get access”
Source: trust.gitlab.com, 2026-11-03. Read from the page's text, without a model; every vendor's trust center.
| Document | Disclosure | Transcription | HTTP | Observed |
|---|---|---|---|---|
| certifications | Public | full | 200 | 2026-10-05 |
| dpa | Public | full | 200 | 2026-10-09 |
| lifecycle | Public | full | 200 | 2026-10-11 |
| residency | Public | full | 200 | 2026-10-05 |
| subprocessors | Public | full | 200 | 2026-11-02 |
History
| Detected | What moved | Why | Source |
|---|---|---|---|
| 2026-11-02 | Subprocessors added LangChain, Inc. | the vendor changed it | about.gitlab.com |
Every reviewed change across the registry, newest first: vendor changes.