GitLab is committed to continuing to provide value and functionality through our free and open-source software offering. In order to continue to innovate and support our growing user base, it is helpful to have in-depth knowledge of how our users are using the services, which we generate through the collection of product usage data. Additional data and insights across the platform enables us to invest more efficiently and continue to expand both the open source and paid GitLab offerings.
To achieve the foregoing, GitLab wishes to collect information about how the features and functionality of the GitLab software are used, such as the total number of projects, pipelines, issues, MRs, etc. We do not collect any information on the contents of your projects or personal information about individual users. We have separated the data we collect into two categories, Optional and Operational, and provide more details below.
SaaS software will automatically log information about interactions with the application, such as the date and time of visit, and the feature and functionality that has been clicked on or used.
Self-Managed software (Community Edition and Enterprise) information about usage from each Self-managed instance is collected through a technology called Service Ping (previously known as Usage Ping). Service Ping sends a payload containing data to GitLab. Only aggregates of usage data for each instance is sent to GitLab. You can view the exact payload of the Service Ping in the administration panel in GitLab. For air-gapped or offline customers who activated with an offline Cloud License, data can be manually downloaded to a .csv file and emailed to GitLab.
Subscription Data is a collection of license data synced securely once a day to the Customer Portal as part of Cloud Licensing. This data is required as part of GitLab's Subscription Agreement as it provides basic information on user count and instance version. This data sync helps to automate activation, provisioning, co-terms and renewals.
A full list of the Subscription Data metrics collected can be viewed here
Optional Data is a collection of usage data generated by our users that is not required to support our day-to-day operations, but provide valuable insights and knowledge GitLab can use to improve our process, product, and investment decisions. The information collected is not anonymous as it may be linked to the instance’s hostname. However, the information does not contain project names, usernames, or any other individual user data.
For example, the data helps to:
A full list of the Optional Data metrics collected can be viewed here.
Operational Data is a collection of usage data that is required to enable services like Customer Success Services. These services provide insights into usage that help customers implement and adopt the product. The information collected is not anonymous as it may be linked to the instance’s hostname. However, the information does not contain project names, usernames, or any other individual user data.
A full list of the Operational Data metrics collected can be viewed here.
At this time individual SaaS users can opt out of both Optional and Operational Data via DNT (do not track) browser settings on a per device basis. It is not possible to opt out of Subscription Data.
Free instances on both EE or CE can disable the collection of all data (operational data is not applicable to free instances) by Service-ping technology via an in-app admin setting or through modification of the configuration file. Please visit our documentation to learn more.
Instances on paid plans (EE distribution)