GitHub Subprocessors and Cookies

Effective date: May 25, 2018

GitHub provides a great deal of transparency regarding how we use your data, how we collect your data, and with whom we share your data. To that end, we provide this page, which details our subprocessors, how we use cookies, and where and how we perform any tracking on GitHub.

GitHub Subprocessors

When we share your information with third party subprocessors, such as our vendors and service providers, we remain responsible for it. We work very hard to maintain your trust when we bring on new vendors, and we require all vendors to enter into data protection agreements with us that restrict their processing of Users' Personal Information (as defined in the Privacy Statement).

Name of Subprocessor Description of Processing Location of Processing
Box Corporate document storage United States
Braintree (PayPal) Subscription credit card payment processor United States
DocuSign Contract signature processor United States
Dropbox Corporate document storage United States
Front Support inbox system United States
Google Apps Internal company infrastructure United States
Google Analytics Website analytics and performance United States
Lithium Community forum software provider United States
MailChimp Customer ticketing mail services provider United States
Mailgun Transactional mail services provider United States
Nexmo SMS notification provider United States
Oracle Corporate financial system United States Customer relations management United States
Sendgrid Transactional mail services provider United States
Twilio SMS notification provider United States
Zendesk Customer support ticketing system United States
Zuora Corporate billing system United States

When we bring on a new vendor or other subprocessor who handles our Users' Personal Information, or remove a subprocessor, or we change how we use a subprocessor, we will update this page. If you have questions or concerns about a new subprocessor, we'd be happy to help. Please contact us via Privacy contact form.

Cookies on GitHub

GitHub uses cookies to make interactions with our service easy and meaningful. We use cookies (and similar technologies, like HTML5 localStorage) to keep you logged in, remember your preferences, and provide information for future development of GitHub.

A cookie is a small piece of text that our web server stores on your computer or mobile device, which your browser sends to us when you return to our site. Cookies do not necessarily identify you if you are merely visiting GitHub; however, a cookie may store a unique identifier for each logged in user. The cookies GitHub sets are essential for the operation of the website, or are used for performance or functionality. By using our website, you agree that we can place these types of cookies on your computer or device. If you disable your browser or device’s ability to accept cookies, you will not be able to log in or use GitHub’s services.

GitHub sets the following cookies on our users for the following reasons:

Name of Cookie Reason
user_session This cookie is used to log you in.
logged_in This cookie is used to signal to us that the user is already logged in.
dotcom_user This cookie is used to signal to us that the user is already logged in.
_gh_sess This cookie is used for temporary application and framework state between pages like what step the user is on in a multiple step form.
tz This cookie allows your browser to tell us what time zone you're in.
gist_user_session This cookie is used by Gist when running on a separate host.
saml_csrf_token This cookie is set by SAML auth path method to associate a token with the client.
saml_return_to This cookie is set by the SAML auth path method to maintain state during the SAML authentication loop.
gist_oauth_csrf This cookie is set by Gist to ensure the user that started the oauth flow is the same user that completes it.
__Host-user_session_same_site This cookie is set to ensure that browsers that support SameSite cookies can check to see if a request originates from GitHub.
__Host-gist_user_session_same_site This cookie is set to ensure that browsers that support SameSite cookies can check to see if a request originates from GitHub.
_ga This cookie is used by Google Analytics.
_octo This cookie is used by Octolytics, our internal analytics service, to distinguish unique users and clients.
tracker This cookie tracks the referring source for signup analytics.

Certain pages on our site may set other third party cookies. For example, we may embed content, such as videos, from another site that sets a cookie. While we try to minimize these third party cookies, we can’t always control what cookies this third party content sets.

Tracking on GitHub

"Do Not Track" is a privacy preference you can set in your browser if you do not want online services — specifically ad networks — to collect and share certain kinds of information about your online activity from third party tracking services. GitHub does not currently respond differently to an individual browser's Do Not Track setting. If you would like to set your browser to signal that you would not like to be tracked, please check your browser's documentation for how to enable that signal. There are also good applications that block online tracking, such as Privacy Badger.

We do not track your online browsing activity on other online services over time and we do not host third-party advertising on GitHub that might track your activity on our site. We do have agreements with certain vendors, such as analytics providers, who help us track visitors' movements on certain pages on our site. Only our vendors, who are collecting data on our behalf, may collect data on our pages, and we have signed data protection agreements with every vendor who collects this data on our behalf. We use the data we receive from these vendors to better understand our visitors' interests, to understand our website's performance, and to improve our content. Any analytics vendor will be listed in our Subprocessor List above, and you may see a list of every page where we collect this kind of data below.

Google Analytics

We use Google Analytics as a third party analytics service, but we don’t use it for advertising purposes. We use Google Analytics to collect information about how our website performs and how our users, in general, navigate through and use GitHub. This helps us evaluate our users' use of GitHub; compile statistical reports on activity; and improve our content and website performance. Google provides further information about its own privacy practices and offers a browser add-on to opt out of Google Analytics tracking.

Pages on GitHub where analytics may be enabled

The following pages on our main site may have analytics or other tracking code enabled. If you would like to prevent us from collecting information about your browsing activity on GitHub, you may use a tracking blocker such as Privacy Badger or opt out of Google Analytics tracking.

Ask a human

Can't find what you're looking for?

Contact us