How to stop GitLab training AI on your data
What the policy itself says, plan by plan. Where GitLab publishes the steps, they're here in its own words, read from an archived copy of the page that gives them. Where it doesn't, this page says so instead of inventing a menu path.
All plans (GitLab Duo / AI Functionality)
GitLab wrote dedicated AI terms, defined the inputs precisely, and left the question out. The terms define "Input" as what the customer provides plus the supporting Customer Content processed to generate Output, and state that both Input and Output are Customer Content that the customer continues to own. They name GitLab Models as the ones GitLab hosts. The single training sentence in the document is the one quoted here, and it runs the other way: a warranty from the customer not to train a competitor. Nothing says whether GitLab may train its own models on Input. The handbook privacy page is no help either — all three of its "training" references are the annual privacy training GitLab staff complete. The terms do say where the answer would live: "these Terms, along with the Agreement and the DPA, govern Customer's access to and use of AI Functionality and GitLab Models" — the subscription agreement and the data processing addendum, neither of which this site archives. And the handbook page read here is not GitLab's privacy statement; it links onward to the customer-facing "GitLab Privacy Statement", a further document. So "left out" overstates it: the question is routed to documents out of frame, which is the pointer pattern rather than pure silence.
Did a step here not work, or does GitLab offer a control this page doesn't mention? Tell us and we'll correct it.