This Cookie Policy supplements the information contained in our Privacy Statement and explains how we use cookies and related technologies to manage and provide our GitLab websites, products and services; collectively referred to as the "Services."
Cookies are small text files placed on your computer. Pixels are small amounts of code on a web page or in an email that provide a method to deliver content, such as a graphic image on a webpage.
GitLab uses cookies to:
Cookies are sometimes placed by GitLab, known as first-party cookies, and sometimes third-party cookies are set by our service providers, such as Google Analytics who provides analytics and interest-based advertising. When third-party cookies are set by service providers, they are providing a service or function to GitLab, as well as achieving the service provider's own purposes. GitLab cannot control how third-party cookies are used. You can review how Google Analytics collects and processes data by visiting: https://policies.google.com/technologies/partner-sites. If you don't want Google Analytics to be used in your browser, you can install the Google Analytics Opt-out Browser Ad-On by visiting: https://tools.google.com/dlpage/gaoptout/.
GitLab has unified our cookie management tool across all GitLab domains providing users with a central location to manage your cookie preferences. With the exception of "strictly necessary" cookies that are essential for the Services to operate, you will be able to opt-in, opt-out, or adjust your cookie preferences for all other cookie categories. Please note that disabling some cookies may cause certain features of the Services to not function properly. This tool can be accessed by clicking on the Cookie Preferences link (titled Do Not Sell or Share My Personal Information for California and Connecticut residents) located in the footer or header of each webpage.
Most web browsers also allow you to delete cookies already placed, which may delete the settings and preferences controlled by those cookies, including advertising preferences. You can find instructions to remove any cookies that have been created in the cookie folder of your browser at https://allaboutcookies.org/manage-cookies/.
"Do Not Track" (DNT) is a privacy preference you can set in your web browser to indicate that you do not want to be tracked. GitLab responds to DNT signals and respects a user's track preference expression for client-side events.
Similar to DNT signals, "Global Privacy Control" (GPC) is a privacy preference you can set in your web browser to notify websites that you do not want your Personal Data shared with or sold to independent third-parties without your consent. GitLab honors GPC in those jurisdictions where its recognition is required by applicable law, such as California and Colorado.
Service providers may participate in self-regulatory programs that provide ways to opt out of analytics and interest-based advertising, which you can access at:
Most email clients have settings which allow you to prevent the automatic downloading of images, which will disable web beacons in the email messages you read.
On mobile devices, advertising IDs provided by the platform may be collected and used similar to cookie IDs. You may use the controls on iOS and Android operating systems that allow you to limit tracking and/or reset the advertising IDs.
GitLab utilizes four categories of cookies: strictly necessary cookies, functional cookies, performance and analytics cookies, as well as targeting and advertising cookies. You can read more about each of these types of cookies and view the cookies within each category that can be found in the Services by clicking on the Cookies Preferences link (titled Do Not Sell or Share My Personal Information for California and Connecticut residents) located in the footer or header of each webpage.