[{"data":1,"prerenderedAt":514},["ShallowReactive",2],{"/en-us/the-source/authors/rschulman":3,"footer-en-us":34,"the-source-banner-en-us":377,"the-source-navigation-en-us":389,"the-source-newsletter-en-us":417,"footer-source-/en-us/the-source/authors/rschulman/":428,"authors-en-us":438,"categories-en-us":473,"rschulman-articles-list-en-us":474},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"config":8,"seo":10,"content":12,"type":25,"slug":26,"_id":27,"_type":28,"title":29,"_source":30,"_file":31,"_stem":32,"_extension":33},"/en-us/the-source/authors/rschulman","authors",false,"",{"layout":9},"the-source",{"title":11},"Robin Schulman",[13,23],{"componentName":14,"type":14,"componentContent":15},"TheSourceAuthorHero",{"config":16,"name":11,"role":18,"bio":19,"headshot":20},{"gitlabHandle":17},"robin","Chief Legal Officer","Robin Schulman is the Chief Legal Officer, Head of Corporate Affairs, and Corporate Secretary of GitLab Inc., the DevSecOps platform.",{"altText":11,"config":21},{"src":22},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1751463437/u2xfbudw1f8hhnkrgaoy.webp",{"componentName":24,"type":24},"TheSourceArticlesList","author","rschulman","content:en-us:the-source:authors:rschulman.yml","yaml","Rschulman","content","en-us/the-source/authors/rschulman.yml","en-us/the-source/authors/rschulman","yml",{"_path":35,"_dir":36,"_draft":6,"_partial":6,"_locale":7,"data":37,"_id":373,"_type":28,"title":374,"_source":30,"_file":375,"_stem":376,"_extension":33},"/shared/en-us/main-footer","en-us",{"text":38,"source":39,"edit":45,"contribute":50,"config":55,"items":60,"minimal":365},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"text":40,"config":41},"View page source",{"href":42,"dataGaName":43,"dataGaLocation":44},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/","page source","footer",{"text":46,"config":47},"Edit this page",{"href":48,"dataGaName":49,"dataGaLocation":44},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/content/","web ide",{"text":51,"config":52},"Please contribute",{"href":53,"dataGaName":54,"dataGaLocation":44},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/CONTRIBUTING.md/","please contribute",{"twitter":56,"facebook":57,"youtube":58,"linkedin":59},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[61,119,176,235,303],{"title":62,"links":63,"subMenu":79},"Pricing",[64,69,74],{"text":65,"config":66},"View plans",{"href":67,"dataGaName":68,"dataGaLocation":44},"/pricing/","view plans",{"text":70,"config":71},"Why Premium?",{"href":72,"dataGaName":73,"dataGaLocation":44},"/pricing/premium/","why premium",{"text":75,"config":76},"Why Ultimate?",{"href":77,"dataGaName":78,"dataGaLocation":44},"/pricing/ultimate/","why ultimate",[80],{"title":81,"links":82},"Contact Us",[83,88,93,98,103,108,113],{"text":84,"config":85},"Contact sales",{"href":86,"dataGaName":87,"dataGaLocation":44},"/sales/","sales",{"text":89,"config":90},"Support portal",{"href":91,"dataGaName":92,"dataGaLocation":44},"https://support.gitlab.com","support portal",{"text":94,"config":95},"Customer portal",{"href":96,"dataGaName":97,"dataGaLocation":44},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"text":99,"config":100},"Status",{"href":101,"dataGaName":102,"dataGaLocation":44},"https://status.gitlab.com/","status",{"text":104,"config":105},"Terms of use",{"href":106,"dataGaName":107,"dataGaLocation":44},"/terms/","terms of use",{"text":109,"config":110},"Privacy statement",{"href":111,"dataGaName":112,"dataGaLocation":44},"/privacy/","privacy statement",{"text":114,"config":115},"Cookie preferences",{"dataGaName":116,"dataGaLocation":44,"id":117,"isOneTrustButton":118},"cookie preferences","ot-sdk-btn",true,{"title":120,"links":121,"subMenu":132},"Product",[122,127],{"text":123,"config":124},"DevSecOps platform",{"href":125,"dataGaName":126,"dataGaLocation":44},"/platform/","devsecops platform",{"text":128,"config":129},"AI-Assisted Development",{"href":130,"dataGaName":131,"dataGaLocation":44},"/gitlab-duo/","ai-assisted development",[133],{"title":134,"links":135},"Topics",[136,141,146,151,156,161,166,171],{"text":137,"config":138},"CICD",{"href":139,"dataGaName":140,"dataGaLocation":44},"/topics/ci-cd/","cicd",{"text":142,"config":143},"GitOps",{"href":144,"dataGaName":145,"dataGaLocation":44},"/topics/gitops/","gitops",{"text":147,"config":148},"DevOps",{"href":149,"dataGaName":150,"dataGaLocation":44},"/topics/devops/","devops",{"text":152,"config":153},"Version Control",{"href":154,"dataGaName":155,"dataGaLocation":44},"/topics/version-control/","version control",{"text":157,"config":158},"DevSecOps",{"href":159,"dataGaName":160,"dataGaLocation":44},"/topics/devsecops/","devsecops",{"text":162,"config":163},"Cloud Native",{"href":164,"dataGaName":165,"dataGaLocation":44},"/topics/cloud-native/","cloud native",{"text":167,"config":168},"AI for Coding",{"href":169,"dataGaName":170,"dataGaLocation":44},"/topics/devops/ai-for-coding/","ai for coding",{"text":172,"config":173},"Agentic AI",{"href":174,"dataGaName":175,"dataGaLocation":44},"/topics/agentic-ai/","agentic ai",{"title":177,"links":178},"Solutions",[179,183,188,193,198,202,207,210,215,220,225,230],{"text":180,"config":181},"Application Security Testing",{"href":182,"dataGaName":180,"dataGaLocation":44},"/solutions/application-security-testing/",{"text":184,"config":185},"Automated software delivery",{"href":186,"dataGaName":187,"dataGaLocation":44},"/solutions/delivery-automation/","automated software delivery",{"text":189,"config":190},"Agile development",{"href":191,"dataGaName":192,"dataGaLocation":44},"/solutions/agile-delivery/","agile delivery",{"text":194,"config":195},"SCM",{"href":196,"dataGaName":197,"dataGaLocation":44},"/solutions/source-code-management/","source code management",{"text":137,"config":199},{"href":200,"dataGaName":201,"dataGaLocation":44},"/solutions/continuous-integration/","continuous integration & delivery",{"text":203,"config":204},"Value stream management",{"href":205,"dataGaName":206,"dataGaLocation":44},"/solutions/value-stream-management/","value stream management",{"text":142,"config":208},{"href":209,"dataGaName":145,"dataGaLocation":44},"/solutions/gitops/",{"text":211,"config":212},"Enterprise",{"href":213,"dataGaName":214,"dataGaLocation":44},"/enterprise/","enterprise",{"text":216,"config":217},"Small business",{"href":218,"dataGaName":219,"dataGaLocation":44},"/small-business/","small business",{"text":221,"config":222},"Public sector",{"href":223,"dataGaName":224,"dataGaLocation":44},"/solutions/public-sector/","public sector",{"text":226,"config":227},"Education",{"href":228,"dataGaName":229,"dataGaLocation":44},"/solutions/education/","education",{"text":231,"config":232},"Financial services",{"href":233,"dataGaName":234,"dataGaLocation":44},"/solutions/finance/","financial services",{"title":236,"links":237},"Resources",[238,243,248,253,258,263,268,273,278,283,288,293,298],{"text":239,"config":240},"Install",{"href":241,"dataGaName":242,"dataGaLocation":44},"/install/","install",{"text":244,"config":245},"Quick start guides",{"href":246,"dataGaName":247,"dataGaLocation":44},"/get-started/","quick setup checklists",{"text":249,"config":250},"Learn",{"href":251,"dataGaName":252,"dataGaLocation":44},"https://university.gitlab.com/","learn",{"text":254,"config":255},"Product documentation",{"href":256,"dataGaName":257,"dataGaLocation":44},"https://docs.gitlab.com/","docs",{"text":259,"config":260},"Blog",{"href":261,"dataGaName":262,"dataGaLocation":44},"/blog/","blog",{"text":264,"config":265},"Customer success stories",{"href":266,"dataGaName":267,"dataGaLocation":44},"/customers/","customer success stories",{"text":269,"config":270},"Remote",{"href":271,"dataGaName":272,"dataGaLocation":44},"https://handbook.gitlab.com/handbook/company/culture/all-remote/","remote",{"text":274,"config":275},"GitLab Services",{"href":276,"dataGaName":277,"dataGaLocation":44},"/services/","services",{"text":279,"config":280},"TeamOps",{"href":281,"dataGaName":282,"dataGaLocation":44},"/teamops/","teamops",{"text":284,"config":285},"Community",{"href":286,"dataGaName":287,"dataGaLocation":44},"/community/","community",{"text":289,"config":290},"Forum",{"href":291,"dataGaName":292,"dataGaLocation":44},"https://forum.gitlab.com/","forum",{"text":294,"config":295},"Events",{"href":296,"dataGaName":297,"dataGaLocation":44},"/events/","events",{"text":299,"config":300},"Partners",{"href":301,"dataGaName":302,"dataGaLocation":44},"/partners/","partners",{"title":304,"links":305},"Company",[306,311,316,321,326,331,336,340,345,350,355,360],{"text":307,"config":308},"About",{"href":309,"dataGaName":310,"dataGaLocation":44},"/company/","company",{"text":312,"config":313},"Jobs",{"href":314,"dataGaName":315,"dataGaLocation":44},"/jobs/","jobs",{"text":317,"config":318},"Leadership",{"href":319,"dataGaName":320,"dataGaLocation":44},"/company/team/e-group/","leadership",{"text":322,"config":323},"Team",{"href":324,"dataGaName":325,"dataGaLocation":44},"/company/team/","team",{"text":327,"config":328},"Handbook",{"href":329,"dataGaName":330,"dataGaLocation":44},"https://handbook.gitlab.com/","handbook",{"text":332,"config":333},"Investor relations",{"href":334,"dataGaName":335,"dataGaLocation":44},"https://ir.gitlab.com/","investor relations",{"text":337,"config":338},"Sustainability",{"href":339,"dataGaName":337,"dataGaLocation":44},"/sustainability/",{"text":341,"config":342},"Diversity, inclusion and belonging (DIB)",{"href":343,"dataGaName":344,"dataGaLocation":44},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":346,"config":347},"Trust Center",{"href":348,"dataGaName":349,"dataGaLocation":44},"/security/","trust center",{"text":351,"config":352},"Newsletter",{"href":353,"dataGaName":354,"dataGaLocation":44},"/company/contact/","newsletter",{"text":356,"config":357},"Press",{"href":358,"dataGaName":359,"dataGaLocation":44},"/press/","press",{"text":361,"config":362},"Modern Slavery Transparency Statement",{"href":363,"dataGaName":364,"dataGaLocation":44},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"items":366},[367,369,371],{"text":104,"config":368},{"href":106,"dataGaName":107,"dataGaLocation":44},{"text":109,"config":370},{"href":111,"dataGaName":112,"dataGaLocation":44},{"text":114,"config":372},{"dataGaName":116,"dataGaLocation":44,"id":117,"isOneTrustButton":118},"content:shared:en-us:main-footer.yml","Main Footer","shared/en-us/main-footer.yml","shared/en-us/main-footer",{"_path":378,"_dir":379,"_draft":6,"_partial":6,"_locale":7,"visibility":118,"id":380,"title":381,"button":382,"_id":386,"_type":28,"_source":30,"_file":387,"_stem":388,"_extension":33},"/shared/en-us/the-source/banner/the-economics-of-software-innovation-2025-08-18","banner","The Economics of Software Innovation","The Economics of Software Innovation—AI’s $750 Billion Opportunity",{"config":383,"text":385},{"href":384},"/software-innovation-report/","Get the research report","content:shared:en-us:the-source:banner:the-economics-of-software-innovation-2025-08-18.yml","shared/en-us/the-source/banner/the-economics-of-software-innovation-2025-08-18.yml","shared/en-us/the-source/banner/the-economics-of-software-innovation-2025-08-18",{"_path":390,"_dir":9,"_draft":6,"_partial":6,"_locale":7,"logo":391,"subscribeLink":396,"navItems":400,"_id":413,"_type":28,"title":414,"_source":30,"_file":415,"_stem":416,"_extension":33},"/shared/en-us/the-source/navigation",{"altText":392,"config":393},"the source logo",{"src":394,"href":395},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1750191004/t7wz1klfb2kxkezksv9t.svg","/the-source/",{"text":397,"config":398},"Subscribe",{"href":399},"#subscribe",[401,405,409],{"text":402,"config":403},"Artificial Intelligence",{"href":404},"/the-source/ai/",{"text":406,"config":407},"Security & Compliance",{"href":408},"/the-source/security/",{"text":410,"config":411},"Platform & Infrastructure",{"href":412},"/the-source/platform/","content:shared:en-us:the-source:navigation.yml","Navigation","shared/en-us/the-source/navigation.yml","shared/en-us/the-source/navigation",{"_path":418,"_dir":9,"_draft":6,"_partial":6,"_locale":7,"title":419,"description":420,"submitMessage":421,"formData":422,"_id":425,"_type":28,"_source":30,"_file":426,"_stem":427,"_extension":33},"/shared/en-us/the-source/newsletter","The Source Newsletter","Stay updated with insights for the future of software development.","You have successfully signed up for The Source’s newsletter.",{"config":423},{"formId":424,"formName":354,"hideRequiredLabel":118},1077,"content:shared:en-us:the-source:newsletter.yml","shared/en-us/the-source/newsletter.yml","shared/en-us/the-source/newsletter",{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"config":429,"seo":430,"content":431,"type":25,"slug":26,"_id":27,"_type":28,"title":29,"_source":30,"_file":31,"_stem":32,"_extension":33},{"layout":9},{"title":11},[432,437],{"componentName":14,"type":14,"componentContent":433},{"config":434,"name":11,"role":18,"bio":19,"headshot":435},{"gitlabHandle":17},{"altText":11,"config":436},{"src":22},{"componentName":24,"type":24},{"amanda-rueda":439,"andre-michael-braun":440,"andrew-haschka":441,"ayoub-fandi":442,"bob-stevens":443,"brian-wald":444,"bryan-ross":445,"chandler-gibbons":446,"dave-steer":447,"ddesanto":448,"derek-debellis":449,"emilio-salvador":450,"erika-feldman":451,"george-kichukov":452,"gitlab":453,"grant-hickman":454,"haim-snir":455,"iganbaruch":456,"jason-morgan":457,"jessie-young":458,"jlongo":459,"joel-krooswyk":460,"josh-lemos":461,"julie-griffin":462,"kristina-weis":463,"lee-faus":464,"nathen-harvey":465,"ncregan":466,"rob-smith":467,"rschulman":11,"sabrina-farmer":468,"sandra-gittlen":469,"sharon-gaudin":470,"stephen-walters":471,"taylor-mccaslin":472},"Amanda Rueda","Andre Michael Braun","Andrew Haschka","Ayoub Fandi","Bob Stevens","Brian Wald","Bryan Ross","Chandler Gibbons","Dave Steer","David DeSanto","Derek DeBellis","Emilio Salvador","Erika Feldman","George Kichukov","GitLab","Grant Hickman","Haim Snir","Itzik Gan Baruch","Jason Morgan","Jessie Young","Joseph Longo","Joel Krooswyk","Josh Lemos","Julie Griffin","Kristina Weis","Lee Faus","Nathen Harvey","Niall Cregan","Rob Smith","Sabrina Farmer","Sandra Gittlen","Sharon Gaudin","Stephen Walters","Taylor McCaslin",{"ai":402,"platform":410,"security":406},[475],{"_path":476,"_dir":477,"_draft":6,"_partial":6,"_locale":7,"config":478,"seo":480,"content":485,"type":509,"slug":510,"category":477,"_id":511,"_type":28,"title":481,"_source":30,"_file":512,"_stem":513,"_extension":33,"date":486,"description":482,"timeToRead":487,"heroImage":483,"keyTakeaways":488,"articleBody":492,"faq":493},"/en-us/the-source/ai/building-a-transparency-first-ai-strategy-7-questions-to-ask-your-devops","ai",{"layout":9,"template":479,"author":26,"featured":6,"isHighlighted":6,"authorName":11},"TheSourceArticle",{"title":481,"description":482,"ogImage":483,"config":484},"Building a transparency-first AI strategy: 7 questions to ask your DevOps provider","Learn what to ask before adopting an AI tool to avoid exposing sensitive data or compromising intellectual property rights.","https://res.cloudinary.com/about-gitlab-com/image/upload/v1751464514/nigg5kzkyyjxsjlhl45j.png",{"ignoreTitleCharLimit":118},{"title":481,"date":486,"description":482,"timeToRead":487,"heroImage":483,"keyTakeaways":488,"articleBody":492,"faq":493},"2023-11-13","5 min read",[489,490,491],"AI boosts software efficiency but requires transparency to protect privacy and IP rights.","GitLab prioritizes transparency in AI use, ensuring data protection and customer trust.","GitLab Duo offers AI benefits with clear ownership and privacy commitments.","AI enables organizations to enhance software development practices by boosting efficiency and reducing cycle times, but its use should not be at the cost of privacy and data security. Transparency around data protection and intellectual property should be a central part of any organization’s AI strategy. Transparency is even more critical for organizations using AI as part of DevOps as they need to know what they are agreeing to when using AI features and how updates will be communicated.\n\nAt GitLab, transparency is one of our [core values](https://handbook.gitlab.com/handbook/values/#transparency). As we continue to expand [GitLab Duo](https://about.gitlab.com/gitlab-duo/), our suite of AI-powered capabilities for the entire software development lifecycle, transparency remains a top priority.\n\nGitLab’s [State of AI in Software Development report](https://about.gitlab.com/developer-survey/#ai) found that teams are feeling optimistic about their adoption of AI, and 83% of respondents said it is essential to implement AI in their software development processes to avoid falling behind. However, nearly as many respondents (79%) also expressed concern about AI tools having access to their private information and intellectual property.\n\nMany of our customers ask where they should begin when evaluating a new AI tool in their software development lifecycle. To help you get better visibility into the actions your DevOps provider is taking to protect your organization’s data and intellectual property, here are seven questions you can ask (as well as how GitLab Duo stacks up).\n\n## What large language models (LLMs) power the AI features in your platform?\n\nDifferent LLMs have different strengths, so setting up your AI architecture with multiple models for specific use cases can be a path to success. However, it’s important to ensure that DevOps providers are transparent about the LLMs they utilize for their AI features as well as details about where the LLMs are hosted.\n\nGitLab Duo features aren’t powered by a single model. We have built GitLab Duo with the flexibility to use the model that provides the best result for each use case. We continue our commitment to transparency by clearly identifying the models powering GitLab Duo features in our [publicly available documentation](https://docs.gitlab.com/ee/user/ai_features.html).\n\n## Who has control of and access to the models?\n\nEvery organization must be able to identify who has control of and access to the LLMs they are using. If a third party has control and access, are they listed by the DevOps provider as a subprocessor? If affiliates have control and access, are those affiliates clearly identified as a subprocessor?\n\nGitLab Duo is powered by third-party models hosted on cloud infrastructure, and the vendors of these models and the terms on which they provide services to GitLab were chosen as they support GitLab’s commitment to privacy and the protection of customer intellectual property.\n\nWe list all our subprocessors clearly on our [subprocessors page](https://about.gitlab.com/privacy/subprocessors/), and customers can [sign up](https://about.gitlab.com/privacy/subprocessors/#sign-up) to be notified when updates are made to this page.\n\n## What protection do you provide to alleviate customer concerns related to the perceived risks of using AI-generated output?\n\nIt's essential to know what protections a DevOps provider will provide regarding AI-generated output and how that guarantee will be met.\n\nGitLab will indemnify you and protect your right to use output generated by GitLab Duo including defending you from claims that output generated from GitLab Duo infringes a third party’s intellectual property rights.\n\n## How do I get the benefit of those protections? Are the protections automatic, or do I need to take any action to receive the protections?\n\nEven if you know that your DevOps provider includes protections related to the risks of using AI-generated output, it’s important to know what limitations, if any, are associated with those protections.\n\n[GitLab protects your right to use output generated by GitLab Duo](https://handbook.gitlab.com/handbook/legal/ai-functionality-terms/) as long as you:\n1. have not modified the output;\n2. have a valid right to use your inputs;\n3. have paid for the AI feature(s); and\n4. have evaluated the output before using or otherwise relying on it.\n\nAt this time, you do not need to enable or activate any features or filters to receive this protection.\n\n## Do I retain my intellectual property (IP) rights to input entered into AI features?\n\nIP is the foundation of an organization and, therefore, you must know how a DevOps provider will handle your rights in respect to inputs that you add to AI features.\n\nWith GitLab Duo, your inputs remain your content. GitLab makes no claim of ownership in your input.\n\n## Do I own the output (or suggestions) generated from AI features?\n\nPerhaps equally important is the question of whether you own what is generated from AI features - the output and suggestions - especially if they are incorporated into your software.\n\nWhile the legal and regulatory landscape related to AI-generated output is developing, GitLab’s position is clear. GitLab does not claim ownership of any output generated by GitLab Duo. Output generated by GitLab Duo can be used at your discretion and, if a third-party claim arises from your use of the output generated GitLab Duo, GitLab will step in and defend you.\n\n## Where are the terms, policies, and commitments that govern the use of your AI features located?\n\nDevOps providers should be able to share specific documentation about how their AI features use your data.\n\nHere are the relevant resources for GitLab customers:\n- [GitLab Subscription Agreement](https://handbook.gitlab.com/handbook/legal/subscription-agreement/)\n- [AI Functionality Terms](https://handbook.gitlab.com/handbook/legal/ai-functionality-terms/)\n- [GitLab Privacy Statement](https://about.gitlab.com/privacy/)\n- [Acceptable Use Policy](https://handbook.gitlab.com/handbook/legal/acceptable-use-policy/)\n- [GitLab Duo Documentation](https://docs.gitlab.com/ee/user/ai_features.html)\n\n## Learn more\nWithout transparency from AI tool providers, organizations are unable to discern the risks around the handling of sensitive information and customer data, trade secrets, and the organization’s intellectual property rights. GitLab remains committed to privacy and transparency. With [GitLab Duo](https://about.gitlab.com/gitlab-duo/), enterprises and regulated organizations can adopt AI-powered workflows with confidence over how their sensitive data is being used.\n\nYou can learn more about GitLab’s privacy-first approach to AI in the [GitLab Duo documentation](https://docs.gitlab.com/ee/user/ai_features.html).",[494,497,500,503,506],{"header":495,"content":496},"What protections should organizations expect for AI-generated output?","Organizations should verify whether their DevOps provider offers indemnification for AI-generated output, meaning they will defend customers against legal claims related to AI-generated content. Providers should also specify whether any actions—such as reviewing AI-generated code or enabling certain features—are required to qualify for these protections.",{"header":498,"content":499},"Where can businesses find policies governing AI usage in DevOps?","AI transparency policies should be easily accessible within a provider’s subscription agreements, AI terms, privacy statements, and acceptable use policies. Organizations should review these documents to understand data handling, security commitments, and compliance requirements before integrating AI into their development workflows.",{"header":501,"content":502},"How can organizations verify the AI models used by their DevOps provider?","Before adopting AI-powered DevOps tools, organizations should ask providers which large language models (LLMs) they use, where they are hosted, and whether third-party vendors have access. A trustworthy provider should disclose this information in their documentation and offer customers a way to track changes, ensuring continued compliance with security and data protection policies.",{"header":504,"content":505},"Who owns the input and output data when using AI features?","Ownership of AI-generated content varies by provider, making it essential to clarify whether organizations retain rights over both input data (what users enter into AI tools) and output data (what AI generates). GitLab, for example, does not claim ownership of input or output data, ensuring businesses maintain control over their intellectual property.",{"header":507,"content":508},"Why is transparency important when adopting AI in DevOps?","Transparency ensures organizations understand how AI tools handle sensitive data, intellectual property, and security risks. Without clear policies from AI providers, businesses may unknowingly expose proprietary code or fail to comply with data protection regulations. A transparency-first approach helps mitigate these risks by providing visibility into AI model usage, data access, and ownership rights.","article","building-a-transparency-first-ai-strategy-7-questions-to-ask-your-devops","content:en-us:the-source:ai:building-a-transparency-first-ai-strategy-7-questions-to-ask-your-devops.yml","en-us/the-source/ai/building-a-transparency-first-ai-strategy-7-questions-to-ask-your-devops.yml","en-us/the-source/ai/building-a-transparency-first-ai-strategy-7-questions-to-ask-your-devops",1761814436193]