Can you sell your GitLab data for AI training?

GitLab's terms let the account holder export its own data, and we found no clause in its API terms about training AI. The content itself carries low rights risk. This is research from public sources, not legal advice.

The holder's own export
The holder can export it
Data pulled through its API
No AI clause found
Rights risk of the content
Low

What a holder should know

Like GitHub: the blocker is open-source licences, contributor personal data and contractor IP assignment, not GitLab's terms. Self-managed GitLab instances are the cleanest source because no SaaS vendor terms sit between holder and data. GitLab's AI Transparency Center states (per a search excerpt, not contract language) that inputs to and outputs from GitLab Duo are not currently used to train GitLab models.

Getting your own data out

Self-managed: the customer holds the data. GitLab.com and Dedicated: project and group exports by maintainers and owners; the customer must migrate content off before termination.

GitLab Subscription Agreement, 8.4: "Customer represents it shall be responsible for, and retain all right, title, and interest in and to, Customer Content, subject to a limited license to GitLab necessary for GitLab's provision of the Software and its development and improvement." For GitLab Dedicated, on termination "Customer shall be solely responsible for migrating any and all Customer Content and Customer Confidential Information off of GitLab's selected infrastructure".

Apps that use its API

No clause found restricting a customer's use of its own content for AI training. Use restrictions target the software: customer may not "disassemble, reverse engineer, or decompile the Software or access it to: (a) build a competitive product or service". Section 12 (U.S. Government Matters): "Customer shall not export, reexport, or transfer the Controlled Subject Matter except as authorized by these laws and regulations."

The sources, word for word

  • GitLab Subscription Agreement (handbook)(read 2026-10-11)
    “Customer represents it shall be responsible for, and retain all right, title, and interest in and to, Customer Content”
  • GitLab AI Functionality Terms V3(read 2026-10-16)
    “both Input and Output constitute additional Customer Content as that term is defined in the Subscription Agreement. Customer will retain all ownership of Customer Content, as permitted under applicable law.”

Research from public sources, read on the day shown. It is not legal advice: a sale needs a lawyer who has read the records and the contracts.

What GitLab holds that buyers ask for

  • Source code with its history

    Repositories with commits, reviews and the tickets they answer

  • Project and ticket histories

    Jira, Linear, ServiceNow or Asana records that show how work moved from request to done

Who buys it

  • Turing (Lazarus)

    "A single payout of up to $1M" for an operating record. For code repositories its process page (lazarus.turing.com/process, read 16 Oct 2026) says "Repos typically pay $10k–$100k+ depending on quality and complexity".

  • Ooak

    "Earn up to $1M" (raised from $300K by 15 Oct 2026). Deals to date run from $20K to several hundred thousand dollars.

  • Labelbox (Prism)

    "Smaller targeted datasets starting around $50K and large enterprise partnerships reaching $1M+".

  • Troveo

    "AI labs and startups are actively paying six figures for company data exports", and Troveo pays the holder "on every sale, not just the first".

  • Corpus Bridge

    It cites licences of about $10,000 to several hundred thousand dollars for ordinary companies.

  • SimpleClosure AssetHub

    "Tens to hundreds of thousands of dollars for unique assets". Early deals were reported at $10,000 to $100,000.

Every buyer and its published terms

What your GitLab records are worth, and what to settle before anyone sees them.

In this topic

Rights and law

  1. Start hereCan this data legally be sold or licensed for AI training?Privacy law, copyright and fair use, software vendors' terms, de-identification, bankruptcy sales and what a licence agreement holds.
  2. GuideIs It Legal to Sell Customer Data? A US Guide for AI TrainingOften yes, but through layers: your privacy policy, the FTC Act, state and sector laws, and customer contracts. De-identified records are the main lawful path.
  3. GuideFair Use and AI Training: What US Courts Have RuledUS courts are split: training was fair use in Bartz v. Anthropic and Kadrey v. Meta, not in Thomson Reuters v. Ross, and pirated copies lost. Where each stands.
  4. GuideIs It Legal to Scrape Data for AI Training? (US Law, 2026)Scraping public pages is rarely a federal crime after Van Buren and hiQ, but contract, copyright, anti-circumvention and privacy law apply. Resale is hard.
  5. GuideCan a Company License Employee Emails and Slack for AI Training?Usually yes for business records the company controls, but only after it handles monitoring notices, third parties in the messages, privilege and vendor terms.
  6. GuideSelling Customer Data in Bankruptcy: Section 363 ExplainedA bankrupt company can sell customer data only if the sale fits its privacy policy, or a court-appointed privacy ombudsman reports and the judge approves it.
  7. GuideWhat Is a Data Licensing Agreement? The Terms for AI TrainingA data licensing agreement lets a buyer use data for set purposes while the holder keeps ownership. Each clause AI buyers ask for, and where holders stand.
  8. GuideHIPAA De-Identification for AI Training: Safe Harbor vs Expert DeterminationHealth data leaves HIPAA only through Safe Harbor (remove 18 identifiers) or an expert's determination of very small risk. How each works for AI training.
  9. GuideLicensing Company Data for AI Training Under the GDPR (2026)Yes, an EU, UK or Swiss company can license its records for AI training, if it has a lawful basis, tells people, drops sensitive data and uses a transfer tool.
  10. GuideSelling Data for AI Training: Privacy Law by CountryOutside the EU and UK, licensing records for AI training mostly needs consent or anonymisation, and a contract or consent to send them to a US buyer.
  11. RegisterLawsuits and rulingsEvery case, ruling and settlement over training data.
  12. RegisterLicence termsWhat buyers ask for in a licence, and where holders stand.
  13. PageDe-identification standardOur rules for removing people from records, each with its source.
  14. RegisterAI crawler censusA daily census of robots.txt across the most visited sites.
Selling GitLab data for AI training: what its terms allow | AIData.Broker