Links last opened 30 October 2026. Record confirmed by a person on 16 September 2026. 2 recorded changes, listed below.
GitLab contracts through GitLab Inc., registered in United States. Transfers of personal data out of the EEA are covered by EU-US Data Privacy Framework (DPF). Its trust center is published at https://trust.gitlab.com/. Its customer data processing agreement, also called a data processing addendum, is published by GitLab itself; the link is below. Its sub-processor list is published by GitLab itself; the link is below. We open those pages every day — last on 30 October 2026 — and a person last went through this record on 16 September 2026.
A US certification scheme covered by an EU adequacy decision. Transfers to a certified US organisation need no further mechanism for the certified scope.
A ready row. Replace the purpose with what your client actually uses GitLab for.
| Subprocessor | Legal entity | Country | Purpose | Transfer | DPA |
|---|---|---|---|---|---|
| GitLab | GitLab Inc. | US | Developer tools | DPF | https://handbook.gitlab.com/handbook/legal/data-processing-agreement/ |
Changes we noticed on GitLab's own pages, each with the page we saw it on. The vendor does not publish this, and neither does anyone else.
30 October 2026
GitLab added LangChain, Inc. as a subprocessor for logging related to AI-powered product features. This processor addition should be documented in your subprocessor list and may require updating your data processing records if you use GitLab's AI features.
27 September 2026
We recorded a change to the UK transfer mechanism.
Enter your website: each service it loads, what it is for and links to its own DPA, in a minute or two. No sign-up.
Worked out from the registry and what we have written: the country this vendor contracts from, the guides that answer the question this page raises, and the rest of the registry.
Six of them. All developer tools in the registry · others that transfer the same way.