Este documento está traducido del inglés. En caso de conflicto, incertidumbre o aparente inconsistencia entre esta versión y la versión en inglés de este documento, la versión en inglés es la versión controladora. Si tienes sugerencias para mejorar nuestra traducción, por favor abre una propuesta en nuestro repositorio site-policy.

Subprocesadores y cookies de GitHub

En este artículo

Effective date: August 8, 2019

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 SubprocessorDescription of ProcessingLocation of Processing
AutomatticBlogging serviceEstados Unidos
AWS AmazonData hostingEstados Unidos
Braintree (PayPal)Subscription credit card payment processorEstados Unidos
ClearbitMarketing data enrichment serviceEstados Unidos
DiscoverOrgMarketing data enrichment serviceEstados Unidos
EloquaMarketing campaign automationEstados Unidos
FrontSupport inbox systemEstados Unidos
Google AppsInternal company infrastructureEstados Unidos
Google AnalyticsWebsite analytics and performanceEstados Unidos
LinkedIn NavigatorMarketing data enrichment serviceEstados Unidos
LithiumCommunity forum software providerEstados Unidos
Magic RobotCampaign reporting (Salesforce Add-on)Estados Unidos
MailChimpCustomer ticketing mail services providerEstados Unidos
MailgunTransactional mail services providerEstados Unidos
MicrosoftCompute infrastructureEstados Unidos
Monday.comTeam collaboration and project management platformEstados Unidos
NexmoSMS notification providerEstados Unidos
OracleCorporate financial systemEstados Unidos
Salesforce.comCustomer relations managementEstados Unidos
SegmentData analytics platformEstados Unidos
SendgridTransactional mail services providerEstados Unidos
StripePayment providerEstados Unidos
TwilioSMS notification providerEstados Unidos
ZendeskCustomer support ticketing systemEstados Unidos
ZuoraCorporate billing systemEstados Unidos

When we bring on a new 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 utiliza cookies para hacer que las interacciones con nuestro servicio sean fáciles y significativas. We use cookies (and similar technologies, like HTML5 localStorage) to keep you logged in, remember your preferences, provide information for future development of GitHub, and to advertise GitHub's products and services to you on third party sites.

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. We use cookies to keep you logged in, remember your preferences, and provide information for future development of GitHub. For security reasons, we use cookies to identify a device. By using our website, you agree that we can place these types of cookies on your computer or device. Si desactivas tu navegador o la capacidad de tu dispositivo para aceptar estas cookies, no podrás iniciar sesión ni utilizar los servicios de GitHub. On certain areas of the website, we may also use cookies to identify you and/or your device to advertise GitHub products and services to you on third party sites.

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

Name of CookieReason
user_sessionThis cookie is used to log you in.
logged_inThis cookie is used to signal to us that the user is already logged in.
dotcom_userThis cookie is used to signal to us that the user is already logged in.
_gh_sessThis cookie is used for temporary application and framework state between pages like what step the user is on in a multiple step form.
tzThis cookie allows your browser to tell us what time zone you're in.
gist_user_sessionThis cookie is used by Gist when running on a separate host.
saml_csrf_tokenThis cookie is set by SAML auth path method to associate a token with the client.
saml_return_toThis cookie is set by the SAML auth path method to maintain state during the SAML authentication loop.
gist_oauth_csrfThis 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_siteThis 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_siteThis cookie is set to ensure that browsers that support SameSite cookies can check to see if a request originates from GitHub.
_gaThis cookie is used by Google Analytics.
_gatThis cookie is used by Google Analytics.
_gidThis cookie is used by Google Analytics.
_octoThis cookie is used by Octolytics, our internal analytics service, to distinguish unique users and clients.
trackerThis 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" (DNT) 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 responde a las señales DNT del navegador y sigue el estándar W3C para responder a las señales DNT. 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.

If you have not enabled DNT on a browser that supports it, cookies on some parts of our website will track your online browsing activity on other online services over time, though we do not permit third parties other than our analytics and service providers to track GitHub users' activity over time on GitHub. We use these cookies to allow us to advertise GitHub products and services to you on third party websites and services. We also 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 personal information 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, and to track our advertising campaigns on third party websites and services. 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

Pages at URLs that contain any of the following domains and paths (including any subdomains or subpaths) on our sites 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.

  • (if you are logged out or do not have an account, this is the page you will see when you go to

Pregunta a una persona

¿No puedes encontrar lo que estás buscando?