Acuerdo de Protección de Datos de GitHub

Introducción

Las partes concuerdan que este Acuerdo de Protección de Datos ("DPA, por sus siglas en inglés) de GitHub establece sus obligaciones con respecto al procesamiento y la seguridad de los Datos personales y, cuando se declare explícitamente en los Términos del DPA, con respecto a los Datos de Clientes en conexión con los Servicios en Línea que proporciona GitHub, Inc. ("GitHub"). El DPA (incluyendo su Apéndice y Adjuntos) se celebra entre GitHub y cualquier cliente que reciba Servicios en Línea de GitHub, con base en el Acuerdo de Cliente de GitHub ("Cliente") y se incorpora como referencia en el Acuerdo de Cliente de GitHub.

En caso de que se suscite cualquier conflicto o inconsistencia entre los Términos del DPA y cualquier término adicional en el Acuerdo de Cliente de GitHub, el DPA deberá prevalecer. Las disposiciones de los Términos del DPA sustituyen cualquier otra que entre en conflicto con la Declaración de Privacidad de GitHub que, de otra forma, pudiera aplicar al procesamiento de los Datos Personales. Para mayor claridad, las Cláusulas Contractuales Estándar prevalecen sobre cualquier otro término del DPA.

Términos y Actualizaciones aplicables al DPA

Límites de las Actualizaciones

Cuando un cliente renueva o compra una suscripción nueva a un Servicio en Línea, se aplicarán los Términos del DPA vigentes en el momento y no se cambiarán durante el periodo de dicha suscripción nueva para estos Servicios en Línea.

No obstante a los límites anteriores de las actualizaciones, cuando GitHub introduzca características, suplementos o software relacionado que sean nuevos (por ejemplo, que no se incluyeran previamente en la suscripción), GitHub podría proporcionar términos o hacer actualizaciones al DPA que apliquen al uso del Cliente para dichas características, suplementos o software relacionado nuevos. Si estos términos incluyen cualquier cambio material adverso a los Términos del DPA, GitHub proporcionará una opción al cliente para utilizar las características, suplementos o software relacionado nuevos sin la pérdida de la funcionalidad existente de un Servicio en Línea generalmente disponible. En caso de que algún cliente no utilice las características, suplementos o software relacionado nuevos, no se aplicarán los términos nuevos correspondientes.

Requisitos y Regulación Gubernamental

No obstante a los límites anteriores de las actualizaciones, GitHub podrá modificar o terminar el Servicio en Línea en cualquier país o jurisdicción en donde exista un requisito u obligación gubernamental futura que (1) atenga a GitHub a cualquier regulación o requisito que no se aplique generalmente al negocio que allí opere, (2) presente una dificultad para que GitHub siga operando el Servicio en línea sin modificación y, (3) ocasione que GitHub crea que los Términos del DPA o el Servicio en Línea pudiera entrar en conflicto con cualquier requisito o obligación en cuestión.

Avisos electrónicos

GitHub podría proporcionar de forma electrónica al cliente información y avisos sobre los Servicios en Línea, incluyendo por correo electrónico, o mediante un sitio web que identifique GitHub. GitHub proporcionará un aviso de la fecha en la que lo haya hecho disponible.

Versiones Anteriores

Los Términos del DPA proporcionan aquellos de los Servicios en Línea que se encuentren vigentes actualmente. En el caso de las versiones anteriores de los Términos del DPA, el Cliente podrá contactar a su revendedor o Administrador de Cuenta de GitHub.

Definiciones

Los términos capitalizados que se utilizan pero no se definen en este DPA tendrán los medios que se proporcionan en el Acuerdo de Cliente de GitHub. Los términos que se definen a continuación se utilizan en este DPA:

CCPA” se refiere a la Ley de Privacidad de Consumidores de California, de acuerdo con lo que se establece en el Código Civil §1798.100 et seq. y sus regulaciones de implementación.

Datos de Cliente” significa todos los datos, incluyendo todos los archivos de texto, sonido, video o imágenes y software que se le proporcionen a GitHub o en nombre del cliente mediante el uso del Servicio en Línea.

"Requisitos para la Protección de Datos" significa la GDPR, las Leyes de Protección de Datos locales de la EU/EEA y cualquier ley, regulación y requisito adicional aplicable que se relacione con (a) privacidad y seguridad de datos y; (b) el uso, recolección, retención, almacenamiento, seguridad, divulgación, transferencia, eliminación y cualquier otro tipo de procesamiento de los Datos Personales.

Datos de Diagnóstico” significa los datos que GitHub recolecta u obtiene del software que un Cliente instala localmente en conexión con el Servicio en Línea. También se les conoce a los Datos de Diagnóstico como telemetría. Los Datos de Diagnóstico no incluyen Datos de Cliente, Datos Generados por el Servicio ni Datos de Servicios Profesionales.

Términos del DPA” significa tanto los términos de este DPA y cualquier otro específico del Servicio en Línea en el Acuerdo de Cliente de GitHub que complementen o modifiquen específicamente los términos de privacidad y seguridad en el presente DPA para un Servicio en Línea específico (o para una característica de un Servicio en Línea). En caso de suscitarse cualquier conflicto o inconsistencia entre el DPA y dichos términos específicos del Servicio en Línea, estos últimos prevalecerán de acuerdo con el Servicio en Línea aplicable (o con la característica de este).

GDPR” significa la Regulación (UE) 2016/679 del Parlamento Europeo y del Consejo del 27 de abril de 2016 sobre la protección de las personas naturales con respecto al procesamiento de los datos personales y sobre el movimiento de dichos datos y derogatoria de la Directiva 95/46EC (Reglamento General de Protección de Datos). En conexión con el Reino Unido, "GDPR" significa el Reglamento (UE) 2016/679 de acuerdo a como se transpuso en las leyes nacionales del Reino Unido mediante la Ley del Reino Unido y (su Salida) de la Unión Europea del 2018 y modificada por los Reglamentos de Protección de Datos, Privacidad y Comunicaciones Electrónicas del Reino Unido (Enmiendas, etc.) (Salida de la EU) del 2019 (conforme se modifiquen de vez en cuando).

Leyes de Protección de Datos Locales EU/EEA” significa cualquier legislación y regulación subordinadas que implementen la GDPR.

Los Términos Relacionados de la GDPR” significa aquellos en el Adjunto 3, bajo los cuales, GitHub, contrae compromisos vinculantes con respecto a su procesamiento e Datos Personales de acuerdo con los requisitos del Artículo 28 de la GDPR.

Afiliado de GitHub” significa cualquier entidad que controle directa o indirectamente, se le controle mediante, o esté bajo control común con GitHub.

Acuerdo de Cliente de GitHub” significa el servicio u otro(s) acuerdo(s) que ingrese el Cliente con Github para Obtener Servicios en Línea.

Declaración de Privacidad de GitHub” significa la declaración de privacidad de GitHub que se encuentra en https://docs.github.com/en/github/site-policy/github-privacy-statement.

Servicio en Línea” significa cualquier servicio o software que proporcione GitHub a un Cliente bajo el Acuerdo de Cliente de GitHub, al cual acuerde el Cliente, incluyendo las Vistas previas, actualizaciones, parches, correcciones de errores y soporte técnico.

Datos Personales” significa cualquier información que se relacione con una persona natural identificable o identificada. Una persona natural identificable es aquella que puede identificarse directa o indirectamente en partícula mediante una referencia a un identificador tal como un nombre, número de identificación, datos de ubicación, un identificador en línea o a uno o más factores específicos para identidad física, fisiológica, genética, mental, económica, cultural o social de esta.

Vista Previa” significa los Servicios en Línea que se proporcionan para propósitos de vista previa, evaluación, demostración o pruebas o versiones de pre-lanzamiento de los Servicios en Línea.

Datos de Servicios Profesionales” significa todo los datos, incluyendo archivos de texto, sonido, video, imagen o software que se proporcionen a GitHub mediante o en nombre de un Cliente (o que los Clientes autoricen a GitHub para obtener de un Servicio en Línea) o, de otro modo, que se obtengan o procesen mediante o en nombre de GitHub a través de un compromiso con GitHub para obtener Servicios Profesionales. Los Datos de Servicios Profesionales incluyen a los Datos de Soporte.

Datos Generados de los Servicios” significa los datos que se generan o derivan de GitHub mediante la operación de un Servicio en Línea. Los Datos Generados de los Servicios no incluyen a los Datos de Cliente, de Diagnóstico o de Servicios Profesionales.

Cláusulas Contractuales Estándar” significa cualquiera de los siguientes conjuntos de Cláusulas Contractuales Estándar, de acuerdo con lo aplicable en el caso individual de la transferencia de datos personales de acuerdo con la sección de este DPA llamada "Transferencias de Datos y Ubicación" a continuación:

  • las Cláusulas Contractuales Estándar (MÓDULO DOS: Transferencia de controlador a procesador), con fecha del 4 de junio de 2021, para la transferencia de datos personales de países terceros de conformidad con el Reglamento (EU) 2016/679 del Parlamento Europeo y del Consejo, de acuerdo a como se describe en el artículo 46 de la GDPR y aprobado por la Decisión Implementada de la Comisión Europea (EU) 2021/91 ("Cláusulas Contractuales Estándar (EU/EEA)"). Se exponen las Cláusulas Contractuales Estándar (EU/EEA) en el Adjunto 1.
  • las Cláusulas Contractuales Estándar (Procesadores), con fecha del 5 de febrero de 2010, para la transferencia de datos personales a los procesadores establecidos en países terceros, los cuales no garantizan un nivel adecuado de protección de datos, de acuerdo con lo descrito en el Artículo 46 de la GDPR, aprobado por la Decisión de la Comisión Europea 2010/87/EU y reconocido por las autoridades supervisoras o regulatorias del Reino Unido apara uso en conexión con la transferencia de datos desde el Reino Unido ("Cláusulas Contractuales Estándar (UK)"). Se exponen las Cláusulas Contractuales Estándar (UK) en el Adjunto 2.

Subprocesador” significa cualquier otro procesador que utiliza GitHub para procesar los Datos Personales en nombre de un Cliente en conexión con los Servicios en Línea, de acuerdo con lo descrito en el Artículo 28 de la GDPR.

Datos de Soporte” significa todos los datos, incluyendo los archivos de texto, sonido, video, imagen o software que se proporcionan a GitHub mediante o en nombre de un Cliente (o que este Cliente autoriza a GitHub para obtener de un Servicio en Línea) mediante un acuerdo con GitHub para obtener soporte técnico para los Servicios en Línea que se cubren en este acuerdo. Los Datos de Soporte son un subconjunto de Datos de Servicios Profesionales.

Los términos en minúsculas que se utilizan pero no se definen en este DPA, tales como "violación de datos personales", "procesamiento", "controlador", "procesador, "perfilamiento", "datos personales" y "sujeto de datos" tendrán el mismo significado de acuerdo con lo expuesto en el Artículo 4 de la GDPR, independientemente de si la GDRP es aplicable o no. Los términos "importador de datos" y "exportador de datos" tienen los significados que se otorgan en las Cláusulas Contractuales Estándar.

Para obtener más claridad y, de acuerdo con lo antes descrito, los datos que se definen como Datos de Clientes, Datos de Diagnóstico, Datos Generados de Servicio, y Datos de Servicios Profesionales, podrían contener Datos Personales. Para fines ilustrativos, por favor, consulta la siguiente tabla:

personal_data_types

La anterior es una representación visual de los tipos de datos que se definen en la DPA. Todos los datos personales se procesan como parte de los toros tipos de datos (de los cuales, todos incluyen a los datos no personales también). Los Datos de Soporte son un subconjunto de Datos de Servicios Profesionales. Excepto en donde se declare explícitamente de otra forma, los Términos del DPA aplican exclusivamente a los Datos Personales.

Términos Generales

Cumplimiento con las Leyes

GitHub cumplirá con todas las leyes y regulaciones aplicables a su prestación de Servicios en Línea, incluyendo la ley de notificación de violaciones de seguridad y Requisitos de Protección de Datos. Sin embargo, GitHub no es responsable del cumplimiento de ninguna ley o regulación aplicable al Cliente o a la industria de este, las cuales no sean aplicables generalmente a los proveedores de servicios de tecnologías de la información. GitHub no determina si los Datos del Cliente incluyen información sujeta a cualquier ley o regulación específicas. Todos los incidentes de seguridad están sujetos a los siguientes términos de Notificación de Incidentes de Seguridad.

Los Clientes deben cumplir con todas las leyes y regulaciones aplicables a su uso de los Servicios en Línea, incluyendo las leyes que se relacionan con los datos biométricos, la confidencialidad de las comunicaciones y los Requisitos de Protección de Datos. El Cliente es responsable de determinar si los Servicios en Línea son adecuados para el almacenamiento y procesamiento de la información sujeta a cualquier regulación o ley y para utilizar los Servicios en Línea de forma consistente con las obligaciones regulatorias y legales del Cliente. El Cliente es responsable de responder a cualquier solicitud de un tercero con respecto al uso del Servicio en Línea por parte del mismo, tal como la solicitud de retirar el contenido que se considera en la Ley de Derechos de Autor para Medios Digitales u otras leyes aplicables.

Protección de datos

Los términos de la DPA en esta sección incluyen las siguientes subsecciones:

  • Alcance
  • Naturaleza del Procesamiento de Datos; Propiedad
  • Divulgación de los Datos Procesados
  • Procesamiento de los Datos Personales; GDPR
  • Seguridad de Datos
  • Notificación de Incidentes de Seguridad
  • Transferencia de Datos y Ubicación
  • Retención y Borrado de Datos
  • Compromiso de Confidencialidad del Procesador
  • Aviso y Controles de Uso de Subprocesadores
  • Instituciones Educativas
  • Acuerdo de Cliente de CJIS, Asociado de Negocios HIPAA, Datos Biométricos
  • Ley de Privacidad de Consumidores de California (CCPA)
  • Cómo Contactar a GitHub
  • Apéndice A – Medidas de Seguridad

Ámbito

Los términos del DPA aplican a todos los Servicios en Línea.

Las vistas previas podrían emplear medidas de seguridad y privacidad menores o diferentes que aquellos tipos que se presentan habitualmente en los Servicios en Línea. A menos de que se indique lo contrario, el Cliente no deberá utilizar las Vistas Previas para procesar Datos Personales u otros que estén sujetos a requisitos de cumplimiento regulatorio o legal. Los siguientes términos en el presente DPA no aplican a las Vistas Previas: Procesamiento de Datos Personales; GDPR, Seguridad de Datos y Ley de Privacidad del Consumidor de California.

Naturaleza del Procesamiento de Datos; Propiedad

A menos de que se indique lo contrario en los Términos del DPA, GitHub utilizará y, de otra forma, procesará los Datos de Cliente y Datos Personales de acuerdo con lo descrito y sujeto a las limitaciones que se proporcionan a continuación (a) para proporcionar el Servicio en Línea al Cliente de acuerdo con las instrucciones que este mismo documentó y (b) para las operaciones de negocios legítimos de GitHub inherentes a la entrega de los Servicios en Línea al Cliente. Como entre las partes, el Cliente retendrá todos los derechos, títulos e intereses y Datos de Cliente. GitHub no adquiere derechos sobre los Datos de Cliente aparte de los que el mismo Cliente le otorgue en esta sección. Este párrafo no afecta los derechos de GitHub sobre el software o los servicios sobre los cuales GitHub otorga licencias al Cliente.

Procesamiento para proporcionar los Servicios en Línea al Cliente

Para fines de este DPA, "proporcionar" un Servicio en Línea, consiste en:

  • Entregar capacidades funcionales de acuerdo con como el Cliente y sus usuarios cuentan con licencia, los configuran y usan, incluyendo las experiencias personalizadas para los usuarios;
  • Solucionar problemas (por ejemplo, prevenir, detectar y reparar problemas) y;
  • Mejora continua (por ejemplo, instalar las actualizaciones más recientes y hacer mejoras a la productividad de los usuarios, confiabilidad, eficacia y seguridad).

Cuando se proporcionan Servicios en Línea, GitHub utilizará o procesará de cualquier otra forma los Datos personales únicamente en nombre del Cliente y de acuerdo con las instrucciones documentadas de este.

Procesamiento para las Operaciones de Negocio Legítimas de GitHub

Para propósitos de este DPA, las "operaciones de negocio legítimas de GitHub" consisten de lo siguiente, cada una como un incidente de entrega de los Servicios en Línea al Cliente: (1) administración de cuenta y facturación; (2) compensación (por ejemplo, calcular las comisiones de empleados e incentivos de los socios); (3) reportes internos y modelados de negocio (por ejemplo, proyecciones, ganancias, planeación de capacidad, estrategia de producto); (4) combatir el fraude, abuso, cibercrimen o ciberataques que pudieran afectar a GitHub o a los Servicios en Línea; (5) mejorar las funcionalidades de accesibilidad, privacidad o eficiencia energética; (6) reportes financieros y cumplimiento con las obligaciones legales (sujetas a las limitaciones de divulgación de Datos Personales que se describen más adelante); (7) la creación o administración de cuentas de usuarios finales y perfiles por parte de GitHub para los usuarios individuales del Cliente (excepto cuando el Cliente cree, administre o controle de otra forma dichas cuentas de usuario final o perfiles por sí mismo) y; (8) otros propósitos que se relacionen con los Datos Personales que no proporcione el Cliente para su almacenamiento en los repositorios de GitHub o en conexión con los Servicios Profesionales.

Cuando se realicen procesamientos para las operaciones de negocios legítimas de GitHub, GitHub no utilizará o procesará los Datos Personales de ninguna otra forma más que para: (a) crear perfiles de usuario, (b) anunciar o realizar propósitos comerciales similares, (c) vender datos o hacer corretaje de estos o (d) cualquier otro propósito diferente de aquellos que se describen en esta sección.

Divulgación de los Datos Procesados

GitHub no divulgará o proporcionará acceso a ningún Dato Procesado, excepto: (1) de acuerdo con como el Cliente lo indique; (2) de acuerdo con lo descrito en este DPA; o (3) de acuerdo con los requisitos legales. Para propósitos de esta sección, "Datos Procesados" significa: (a) Datos de Cliente; (b) Datos Personales y (c) cualquier otros datos que procese GitHub en conexión con el Ser vicio en Línea que utilice la información confidencial del Cliente bajo el Acuerdo de Cliente de GitHub. Todo el procesamiento de Datos Procesados está sujeto a la obligación de GitHub sobre la confidencialidad bajo el Acuerdo de Cliente de GitHub.

GitHub no divulgará ni proporcionará acceso de ningún Dato Procesado a las fuerzas policiales a menos de que la ley así lo requiera. Si las fuerzas policiales contactan a GitHub con una demanda de Datos Procesados, GitHub intentará redireccionar a dicha agencia para que solicite los datos directamente del Cliente. En caso de que se le obligue a divulgar o proporcionar acceso a cualquier tipo de Datos Procesados a la fuerza policial, GitHub notificará de inmediato al Cliente y proporcionará una copia de dicha demanda, a menos de que se le prohíba hacerlo explícitamente.

En el momento de que se reciba cualquier otra solicitud de terceros para obtener Datos Procesados, GitHub notificará de inmediato al Cliente a menos de que la ley lo prohiba. GitHub rechazará la solicitud a menos de que la ley exija su cumplimiento. Si la solicitud es válida, GitHub intentará redireccionar al tercero para que solicite los datos directamente del Cliente.

GitHub no proporcionará a ningún tercero: (a) acceso directo, indirecto, abierto o sin restricción a los Datos Procesados; (b) llaves de cifrado de plataforma que se utilicen para asegurar los Datos Procesados o la capacidad de librar dicho cifrado o (c) acceso a los Datos Procesados si GitHub está consciente que estos se utilizarán para propósitos diferentes a aquellos enunciados en la solicitud del tercero.

Para apoyar lo anterior, GitHub podría proporcionar información de contacto básica del Cliente al tercero.

Procesamiento de los Datos Personales; GDPR

Cualquier Dato Personal que procese GitHub en conexión con los Servicios en Línea se obtendrá como parte ya sea de los Datos de Cliente, Datos de Servicios Profesionales (incluyendo los Datos de Soporte) Datos de Diagnóstico o Datos Generados por los Servicios. Los Datos Personales que se proporcionan a GitHub mediante o en nombre del Cliente, mediante el uso del Servicio en Línea, también se consideran Datos de Cliente. Los identificadores de pseudónimo podrían incluirse en los Datos de Diagnóstico o Datos Generados por los Servicios y también se consideran Datos Personales. Cualquier Dato Personal en forma de pseudónimo o desidentificado pero no anonimizado o Dato Personal que se derive de los Datos Personales también se considera un Dato Personal.

En medida en que GitHub sea un procesador o subprocesador de los Datos Personales sujetos a la GDRP, los Términos Relacionados con la GDPR en el Adjunto 3 regirán el procesamiento y las partes también concuerdan con los siguientes términos de esta sub-sección ("Procesamiento de Datos Personales; GDPR"):

Roles y Responsabilidades del Procesador y Controlador

El Cliente y GitHub concuerdan que el Cliente es el controlador de los Datos Personales y GitHub es el procesador de estos, excepto (a) cuando el Cliente actúe como procesador de los Datos Personales, en cuyo caso, GitHub será un subprocesador o (b) de acuerdo a como se enuncie de otro modo en el Acuerdo de Cliente de GitHub o en este DPA. Cuando GitHub actúe como el procesador o subprocesador de los Datos Personales, los procesará únicamente en nombre y de acuerdo con lo documentado en las instrucciones del Cliente. El Cliente concuerda que este Acuerdo de Cliente de GitHub (incluyendo los Términos del DPA y cualquier actualización aplicable), en conjunto con la documentación del producto y el uso del Cliente y la configuración de características en los Servicios en Línea, son las instrucciones completamente documentadas del Cliente hacia GitHub para el procesamiento de los Datos Personales. Se puede encontrar la información sobre el uso y configuración de los Servicios en Línea en https://docs.github.com o en una ubicación posterior. Deberá acordarse cualquier instrucción adicional o alterna conforme al proceso para modificar el Acuerdo de Cliente de GitHub del Cliente. En cualquier instancia en donde aplique la GDPR y el Cliente sea un procesador, el Cliente garantiza a GitHub que el controlador relevante autorizó las instrucciones otorgadas, incluyendo la designación de GitHub como un procesador o subprocesador.

En medida en que GitHub utilice o procese de otra forma los Datos Personales sujetos a la GDPR para las operaciones de negocio legítimas de GitHub inherentes a la entrega de los Servicios en Línea al Cliente, GitHub cumplirá con las obligaciones de un controlador de datos independientes bajo la GDPR para dicho uso. GitHub acepta las responsabilidades añadidas de un "controlador" de datos bajo la GDPR para el procesamiento en conexión con sus operaciones legítimas de negocios para: (a) actuar en consistencia con los requisitos regulatorios, en la medida que lo requiera la GDPR y (b) proporcionar la transparencia incrementada para los Clientes y confirmar la responsabilidad de GitHub para dicho procesamiento. GitHub emplea salvaguardas para proteger los Datos Personales durante su procesamiento, incluyendo a aquellos que se identifican en este DPA y aquellos que se contemplan en el el Artículo 6(4) de la GDPR. Con respecto al procesamiento de Datos Personales bajo este párrafo, GitHub hace los compromisos descritos en las Cláusulas Contractuales Estándar que se muestran en el Adjunto 1 o el Adjunto 2 (conforme sea aplicable); para dichos propósitos, (i) cualquier divulgación de Datos Personales por parte de GitHub, de acuerdo con lo descrito en el Anexo III al Adjunto 1 o Apéndice 3 al Adjunto 2 (conforme aplique), que se haya transferido en conexión con las operaciones de negocios legítimas de GitHub se considera una "Divulgación Relevante" y (ii) los compromisos en el Anexo III al Adjunto 1 o del Apéndice 3 al Adjunto 2 (según el caso) aplicarán a dichos Datos Personales.

Procesar Detalles

Las partes reconocen y concuerdan en que:

  • Objeto del contrato. El objeto del contrato de procesamiento se limita a los Datos Personales con el alcance de la sección de este DPA denominado "Naturaleza del Procesamiento de los Datos; Propiedad", el cual se encuentra anteriormente, y la GDPR.
  • Duración del procesamiento. La duración del procesamiento tomará lugar de acuerdo con las instrucciones del Cliente y de los términos del DPA.
  • Naturaleza y propósito del procesamiento. La naturaleza y propósito del procesamiento será el proporcionar el Servicio en Línea conforme al Acuerdo de Cliente de GitHub del Cliente y para las operaciones de negocios legítimas de GitHub inherentes a la entrega del Servicio en Línea al Cliente (de acuerdo con lo descrito en la sección de este DPA que se titula "Naturaleza del Procesamiento de Datos; Propiedad", que se encuentra anteriormente).
  • Categorías de los Datos. Los tipos de Datos Personales que procesa GitHub al proporcionar el Servicio en Línea incluyen: (i) Datos Personales que elige el Cliente para incluir en los Datos del Cliente o Datos de Servicios Profesionales (incluyendo, mas no limitándose a los Datos de Soporte) y (ii) aquellos que se identifican explícitamente en el Artículo 4 de la GDPR y que podrían contenerse en los Datos Diagnósticos o Datos Generados por los Servicios. Los tipos de Datos Personales que el Cliente elige incluir en los Datos de Cliente o Datos de Servicios Profesionales (incluyendo, mas no limitándose a los Datos de Soporte) podrían ser de cualquier categoría de Datos Personales identificada en los registros que mantiene el Cliente actuando como controlador conforme al Artículo 30 de la GDPR, incluyendo las categorías de Datos Personales que se describen en el Anexo I al Adjunto 1 o en el Apéndice 1 al Adjunto 2 (conforme sea aplicable).
  • Titulares de los datos. Las categorías de titulares de los datos son representantes del Cliente y usuarios finales, tales como empleados, contratistas, colaboradores y clientes y podrían incluir cualquier otra categoría de titulares de los datos de acuerdo con lo identificado en los registros que mantiene el cliente, actuando como un controlador de conformidad con el Artículo 30 de la GDPR, incluyendo las categorías de titulares de datos que se describen en el Anexo 1 al Adjunto 1 o al Apéndice 1 al Adjunto 2 (conforme sea aplicable).

Derechos de los Titulares de los Datos; Asistencia con las Solicitudes

GitHub pondrá a disposición del Cliente, de forma consistente con la funcionalidad del Servicio en Línea y del rol de GitHub como procesador de Datos Personales de los titulares de estos, la capacidad de cumplir con las solicitudes de los titulares de datos para ejecutar sus derechos bajo la GDPR. Si GitHub recibe un formato de solicitud del titular de los datos del Cliente para ejecutar uno más de sus derechos bajo la GDPR en conexión con un Servicio en Línea por el cual GitHub es un procesador o subprocesador, GitHub redireccionará al titular de los datos para que haga su solicitud directamente con el Cliente. El cliente será responsable de responder a cualquier solicitud de este tipo, incluyendo, cuando sea necesario, utilizando la funcionalidad del Servicio en Línea. Github deberá cumplir con las soclitudes razonables que haga el Cliente para asistir la respuesta del mismo a dichas solicitudes de un sujeto de datos.

Registros de Actividades de Procesamiento

En medida en que la GPR requiera que GitHub recolecte y mantenga los registros de alguna información relacionada con el Cliente, este proporcionará dicha información a GitHub, cuando se le solicite, y la mantendrá actualizada y correcta. GitHub podría poner dicha información a disposición de la autoridad supervisora en caso de que la GDPR así lo requiera.

Seguridad de Datos

GitHub implementará y mantendrá las medidas organizacionales y técnicas adecuadas y las salvaguardas de seguridad contra la destrucción accidental o ilegal, o contra la pérdida, alteración o divulgación o acceso no autorizados a los Datos de Cliente y Datos Personales que procese en nombre y de conformidad con las instrucciones documentadas del Cliente en conexión con los Servicios en Línea. GitHub monitoreará frecuentemente el cumplimiento de estas medidas y salvaguardas y seguirá tomando los pasos adecuados a lo largo del periodo en el que el Acuerdo de Cliente de GitHub sea vigente. El Apéndice A – Salvaguardas de Seguridad contiene una descripción de las medidas técnicas y organizacionales y de las salvaguardas de seguridad que implementa GitHub.

El Cliente es el único responsable de hacer una determinación independiente de si las medidas técnicas y organizacionales y las salvaguardas de seguridad para un Servicio en Línea cumplen con los requisitos del Cliente, incluyendo todas sus obligaciones de seguridad bajo los Requisitos de Protección de Datos aplicables. El cliente reconoce y concuerda que (tomando en cuenta las tecnologías más recientes, los costos de implementación y la naturaleza, alcance, contexto y propósitos del procesamiento de sus Datos de Cliente y Datos Personales, así como el riesgo de posibilidad y gravedad variable de los derechos y libertades de las personas naturales) las medidas técnicas y organizacionales y salvaguardas de seguridad que implementa y mantiene GitHub, proporcionan un nivel de seguridad adecuado al riesgo con respecto a sus Datos Personales y Datos de Cliente. El Cliente es responsable de implementar y mantener las protecciones de privacidad y medidas de seguridad para los componentes que este proporcione o controle.

GitHub proporcionará un reporte de cumplimiento de seguridad tal como los reporte de auditoría externa SOC1, tipo 2 y SOC2, tipo 2, bajo solicitud del Cliente. El Cliente concuerda que cualquier derecho de información y auditoría que otorguen los Requisitos de Protección de Datos aplicables (incluyendo, en dado caso, el Artículo 28(3)(h) de la GDPR) se satisfarán mediante estos reportes de auditoría y, de otro modo, solo se presentarán en la medida en que el aprovisionamiento de GitHub para un reporte de cumplimiento no proporcione información suficiente o en medida en que el Cliente deba responder a una auditoría o investigación de una autoridad supervisora o regulatoria.

En caso de que el Cliente esté sujeto a una auditoría de una autoridad supervisora o regulatoria o a una investigación o que lleve a cabo una auditoría o investigación como respuesta a una solicitud de una autoridad supervisora o regulatoria que requiera la participación de GitHub y las obligaciones del Cliente no puedan satisfacerse de forma razonable (cuando sea permisible por parte de los reguladores del Cliente) mediante reportes de auditoría, documentación o información de cumplimiento que GitHub mantenga disponible generalmente a sus clientes, entonces, GitHub responderá inmediatamente a las instrucciones y solicitudes adicionales del Cliente con respecto a la información, de acuerdo con los siguientes términos y condiciones:

  • GitHub proporcionará acceso al personal con conocimientos relevantes, documentación y software de aplicaciones.
  • El Cliente y GitHub acordarán mutuamente con un acuerdo escrito previamente (se acepta también el formato de correo electrónico) sobre los requisitos del alcance, tiempos, duración, control y evidencia, en caso de que dicho requisito para estar de acuerdo no permita que GitHub retrase su cooperación de forma razonable.
  • El Cliente debe garantizar el uso de su regulador sobre una firma de auditoría de terceros independiente y acreditada durante horas hábiles habituales y con un aviso por escrito razonablemente anticipado y sujeto a los procedimientos de confidencialidad razonables. Ni el Cliente, ni sus reguladores, ni los delegados de sus reguladores deberán tener acceso a cualquier tipo de datos de otros clientes, sistemas o instalaciones de GitHub que no se involucren en los Servicios en Línea.
  • El Cliente es responsable de todos los costos y comisiones que se relacionen con la cooperación de GitHub con las auditorías regulatorias del Cliente, incluyendo todos los costos y comisiones razonables por cualquier y todos los gastos de GitHub, adicionalmente a las tasas por los servicios que lleva a cabo GitHub.
  • Si el reporte que se genere de la cooperación de GitHub con la auditoría regulatoria del Cliente involucra cualquier hallazgo que pertenezca a GitHub, el Cliente compartirá dicho reporte, hallazgos y acciones recomendadas con GitHub cuando los reguladores del Cliente así lo permitan.

Notificación de Incidentes de Seguridad

Si GitHub se hace consciente de alguna violación de seguridad que llevase a una destrucción, pérdida, alteración, divulgación o acceso no autorizados e ilegales de los Datos de Cliente o de los Datos Personales que procesa GitHub en nombre de y de acuerdo con las instrucciones documentadas del Cliente en conexión con los Servicios en Línea (cada uno de ellos un "Incidente de Seguridad"), GitHub realizará inmediatamente y sin retraso indebido (1) la notificación al cliente sobre el Incidente de Seguridad; (2) la investigación del Incidente de Seguridad y otorgamiento al Cliente de la información detallada sobre dicho Incidente de Seguridad; (3) el tomar los pasos razonables para mitigar los efectos y minimizar cualquier daño que resultara de dicho Incidente de Seguridad.

Las notificación(es) de incidentes de seguridad se entregarán a uno o más de los administradores del cliente por cualquier medio que seleccione GitHub, incluyendo el correo electrónico. Es la responsabilidad única del cliente el asegurar que mantiene información de contacto actualizada con GitHub y que su administrador monitoree y responda a cualquier notificación. El Cliente es el único responsable de cumplir con sus obligaciones según las leyes de notificación de incidentes aplicables al Cliente y de cumplir con las obligaciones de notificación de terceros relacionadas con cualquier Incidente de seguridad.

GitHub hará esfuerzos razonables para asistir al Cliente en el cumplimiento de sus obligaciones bajo el Artículo 33 de la GDPR o cualquier otra ley o regulación aplicable para notificar a la autoridad supervisora o regulatoria y a los titulares de los datos individuales sobre cualquier incidente de Seguridad.

La notificación o respuesta a un Incidente de Seguridad por parte de GitHub bajo esta sección no es un reconocimiento de GitHub sobre cualquier falta o responsabilidad con respecto al mismo.

El Cliente debe notificar a GitHub inmediatamente sobre cualquier posible mal uso de sus cuentas o credenciales de autenticación o Incidentes de Seguridad que se relacionen con el Servicio en Línea.

Transferencia de Datos y Ubicación

Los Datos Personales que procese GitHub en nombre de y de acuerdo con las instrucciones documentadas del Cliente en conexión con los Servicios en Línea no deberán transferirse a, o almacenarse y procesarse en una ubicación geográfica, con excepción de aquellas que se apeguen a los Términos del DPA y a las salvaguardas que se proporcionan más adelante en esta sección. Tomando en cuenta dichas salvaguardas, el Cliente designará a GitHub para transferir Datos Personales a los Estados Unidos o a cualquier otro país en el que GitHub o sus Subprocesadores operen y almacenen y procesen Datos Personales para proporcionar los Servicios en Línea, con excepción de lo que se describa en cualquier otra parte de los Términos del DPA.

Todas las transferencias de Datos Personales fuera de la Unión europea, del Área Económica Europea o de Suiza para proporcionar los Servicios en Línea deberán regirse por las Cláusulas Contractuales Estándar (EU/EEA) en el Adjunto 1. Todas las transferencias de Datos Personales fuera del Reino Unido para proporcionar los Servicios en Línea deberán regirse por las Cláusulas Contractuales Estándar (UK) en el Adjunto 2. Para propósitos de las Cláusulas Contractuales Estándar (UK) en el Adjunto 2, las referencias a "La Unión Europea", "UE", "El Área Económica Europea", "AEE" o un "Estado Miembro", deberán interpretarse para referirse al Reino Unido donde sea razonablemente necesario y adecuado para dar fuerza y efecto totales a las Cláusulas Contractuales Estándar (UK) con respecto a las transferencias de Datos Personales desde el Reino Unido. Esto aplica sin importar el hecho de que, desde el 31 de enero de 2020, el Reino Unido ya no es un Estado Miembro de la Unión Europea o del Área Económica Europea.

GitHub cumplirá los requisitos de las leyes de protección de datos aplicables de la Unión Europea, el Área Económica Europea, el Reino Unido y Suiza y el resto de los Requisitos de Protección de Datos, en cada caso, que tengan que ver con la transferencia de Datos Personales a los receptores o a las jurisdicciones fuera de estas. Todas estas transferencias de Datos Personales estarán, cuando sea aplicable, sujetas a las salvaguardas adecuadas de acuerdo con lo descrito en el Artículo 46 de la GDPR y dichas transferencias y salvaguardas se documentarán de acuerdo con el Artículo 30(2) de la GDPR.

Sujeto a las salvaguardas que se describen anteriormente, GitHub podría transferir, almacenar y procesar de cualquier otra forma los Datos Personales hacia o en las jurisdicciones y ubicaciones geográficas internacionales como lo considere, sujeto a su propio criterio, razonablemente necesario en conexión con los Servicios en Línea.

Retención y Borrado de Datos

Bajo la solicitud razonable del Cliente, a menos de que lo prohíba la ley, GitHub devolverá o destruirá todos los Datos de Cliente y Datos Personales que procese en nombre y de acuerdo con las instrucciones documentadas del dicho Cliente en conexión con los Servicios en Línea en todas las ubicaciones donde se almacene en los primeros 30 días desde la solicitud, suponiendo que ya no se requiera para proporcionar los Servicios en Línea o para los propósitos por los cuales se autorizó el procesamiento de dichos Datos Personales. GitHub may retain Customer Data or Personal Data to the extent required by the applicable Data Protection Requirements or other applicable law, and only to the extent and for such period as required by the applicable Data Protection Requirements or other applicable law, provided that GitHub will ensure that the Customer Data or Personal Data is processed only as necessary for the purpose specified in the applicable Data Protection Requirements or other applicable law and no other purpose, and the Customer Data or Personal Data remains protected by the Applicable Data Protection Requirements or other applicable law.

Compromiso de Confidencialidad del Procesador

GitHub will ensure that its personnel engaged in the processing of Customer Data and Personal Data on behalf of Customer in connection with the Online Services (i) will process such data only on instructions from Customer or as described in this DPA, and (ii) will be obligated to maintain the confidentiality and security of such data even after their engagement ends. GitHub shall provide periodic and mandatory data privacy and security training and awareness to its employees with access to Customer Data and Personal Data in accordance with applicable Data Protection Requirements or other applicable law and industry standards.

Aviso y Controles de Uso de Subprocesadores

GitHub may hire Subprocessors to provide certain limited or ancillary services on its behalf. Customer consents to this engagement and to GitHub Affiliates as Subprocessors. The above authorizations will constitute Customer’s prior written consent to the subcontracting by GitHub of the processing of Personal Data if such consent is required under applicable law, the Standard Contractual Clauses or the GDPR Related Terms.

GitHub is responsible for its Subprocessors’ compliance with GitHub’s obligations in this DPA. GitHub makes available information about Subprocessors on the GitHub website https://github.com/subprocessors (or a successor location). When engaging any Subprocessor, GitHub will ensure via a written contract that the Subprocessor may access and use Customer Data or Personal Data only to deliver the services GitHub has retained them to provide and is prohibited from using Customer Data or Personal Data for any other purpose. GitHub will ensure that Subprocessors are bound by written agreements that require them to provide at least the level of data protection required of GitHub by the DPA, including the limitations on disclosure of Personal Data. GitHub agrees to oversee the Subprocessors to ensure that these contractual obligations are met.

From time to time, GitHub may engage new Subprocessors. GitHub will give Customer notice (by updating the website at https://github.com/github-subprocessors-list (or a successor location) and providing Customer with a mechanism to obtain notice of that update) of any new Subprocessor in advance of providing that Subprocessor with access to Customer Data. If GitHub engages a new Subprocessor for a new Online Service, GitHub will give Customer notice prior to availability of that Online Service.

If Customer does not approve of a new Subprocessor, then Customer may terminate any subscription for the affected Online Service without penalty by providing, before the end of the relevant notice period, written notice of termination. Customer may also include an explanation of the grounds for non-approval together with the termination notice, in order to permit GitHub to re-evaluate any such new Subprocessor based on the applicable concerns. If the affected Online Service is part of a suite (or similar single purchase of services), then any termination will apply to the entire suite. After termination, GitHub will remove payment obligations for any subscriptions for the terminated Online Service from subsequent invoices to Customer or its reseller.

Instituciones Educativas

If Customer is an educational agency or institution subject to the regulations under the Family Educational Rights and Privacy Act, 20 U.S.C. § 1232g (FERPA), or similar state student or educational privacy laws (collectively “Educational Privacy Laws”), Customer shall not provide Personal Data covered by such Educational Privacy Laws to GitHub without obtaining GitHub’s prior, written and specific consent and entering into a separate agreement with GitHub governing the parties’ rights and obligations with respect to the processing of such Personal Data by GitHub in connection with the Online Services.

Subject to the above, if Customer intends to provide to GitHub Personal Data covered by FERPA, the parties agree and acknowledge that, for the purposes of this DPA, GitHub is a “school official” with “legitimate educational interests” in the Personal Data, as those terms have been defined under FERPA and its implementing regulations. Customer understands that GitHub may possess limited or no contact information for Customer’s students and students’ parents. Consequently, Customer will be responsible for obtaining any student or parental consent for any end user’s use of the Online Services that may be required by applicable law and to convey notification on behalf of GitHub to students (or, with respect to a student under 18 years of age and not in attendance at a postsecondary institution, to the student’s parent) of any judicial order or lawfully-issued subpoena requiring the disclosure of Personal Data in GitHub’s possession as may be required under applicable law.

Acuerdo de Cliente de CJIS, Asociado de Negocios HIPAA, Datos Biométricos

Except with GitHub’s prior, written and specific consent, Customer shall not provide to GitHub any Personal Data

  • relating to criminal convictions and offenses or Personal Data collected or otherwise processed by Customer subject to or in connection with FBI Criminal Justice Information Services or the related Security Policy.
  • constituting protected health information governed by the privacy, security, and breach notification rules issued by the United States Department of Health and Human Services, Parts 160 and 164 of Title 45 of the Code of Federal Regulations, established pursuant to the Health Insurance Portability and Accountability Act of 1996 (Public Law 104-191) or by state health or medical privacy laws.
  • collected as part of a clinical trial or other biomedical research study subject to, or conducted in accordance with, the Federal Policy for the Protection of Human Subjects (Common Rule).
  • covered by state, federal or foreign biometric privacy laws or otherwise constituting biometric information including information on an individual’s physical, physiological, biological or behavioral characteristics or information derived from such information that is used or intended to be used, singly or in combination with each other or with other information, to establish individual identity.

California Consumer Privacy Act (CCPA) / California Privacy Rights Act (CPRA)

If and to the extent GitHub is processing Personal Data on behalf and in accordance with the documented instructions of Customer within the scope of the CCPA, GitHub makes the following additional commitments to Customer. GitHub will process the Personal Data on behalf of Customer and will not

  • sell the Personal Data as the term “selling” is defined in the CCPA. - share, rent, release, disclose, disseminate, make available, transfer or otherwise communicate orally, in writing or by electronic or other means, the Personal Data to a third party for cross-context behavioral advertising, whether or not for monetary or other valuable consideration, including transactions for cross-context behavioral advertising in which no money is exchanged.
  • retain, use or disclose the Personal Data for any purpose other than for the business purposes specified in the DPA Terms and the GitHub Customer Agreement, including retaining, using or disclosing the Personal Data for a commercial purpose other than the business purposes specified in the DPA Terms or the GitHub Customer Agreement, or as otherwise permitted by the CCPA.
  • retain, use or disclose the Personal Data outside of the direct business relationship with Customer.
  • combine the Personal Data with personal information that it receives from or on behalf of a third party or collects from California residents, except that GitHub may combine Personal Data to perform any business purpose as permitted by the CCPA or any regulations adopted or issued under the CCPA.

Cómo Contactar a GitHub

If Customer believes that GitHub is not adhering to its privacy or security commitments, Customer may contact customer support or use GitHub’s Privacy web form, located at https://support.github.com/contact/privacy. GitHub’s mailing address is:

GitHub Privacy
GitHub, Inc.
88 Colin P. Kelly Jr. Street
San Francisco, California 94107 USA

GitHub B.V. is GitHub’s data protection representative for the European Economic Area. The privacy representative of GitHub B.V. can be reached at the following address:

GitHub B.V.
Vijzelstraat 68-72
1017 HL Amsterdam
The Netherlands

Appendix A – Security Safeguards

GitHub has implemented and will maintain for Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with GitHub services the following technical and organizational measures and security safeguards, which in conjunction with the security commitments in this DPA (including the GDPR Related Terms), are GitHub’s only responsibility with respect to the security of that data:

DomainPractices
Organization of Information SecuritySecurity Ownership. GitHub has appointed one or more security officers responsible for coordinating and monitoring the security policies and procedures.

Security Roles and Responsibilities. GitHub personnel with access to Customer Data and Personal Data are subject to confidentiality obligations.

Risk Management Program. GitHub performs an annual risk assessment.
GitHub retains its security documents pursuant to its retention requirements after they are no longer in effect.

Vendor Management. GitHub has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors.
Asset ManagementAsset Inventory. GitHub maintains an inventory of all media on which Customer Data and Personal Data is stored. Access to the inventories of such media is restricted to GitHub personnel authorized to have such access.

Asset Handling
- GitHub classifies Customer Data and Personal Data to help identify it and to allow for access to it to be appropriately restricted.
- GitHub communicates employee responsibility and accountability for data protection up to and including cause for termination.
GitHub personnel must obtain GitHub authorization prior to remotely accessing Customer Data and Personal Data or processing Customer Data and Personal Data outside GitHub’s facilities.
Human Resources SecuritySecurity Training. GitHub requires all new hires to complete security and privacy awareness training as part of initial on-boarding. Participation in annual training is required for all employees to provide a baseline for security and privacy basics.
Physical and Environmental SecurityPhysical Access to Facilities. GitHub limits access to facilities where information systems that process Customer Data and Personal Data are located to identified authorized individuals.

Physical Access to Components. GitHub maintains records of the incoming and outgoing media containing Customer Data, including the kind of media, the authorized sender/recipients, date and time, the number of media and the types of Customer Data and Personal Data they contain.

Protection from Disruptions. GitHub uses a variety of industry standard systems to protect against loss of data due to power supply failure or line interference.

Component Disposal. GitHub uses industry standard processes to delete Customer Data and Personal Data when it is no longer needed.
Communications and Operations ManagementOperational Policy. GitHub maintains security documents describing its security measures and the relevant procedures and responsibilities of its personnel who have access to Customer Data.

Data Recovery Procedures
- On an ongoing basis, but in no case less frequently than once a week (unless no Customer Data and Personal Data has been updated during that period), GitHub maintains multiple copies of Customer Data and Personal Data from which Customer Data and Personal Data can be recovered.
- GitHub stores copies of Customer Data and Personal Data and data recovery procedures in a different place from where the primary computer equipment processing the Customer Data and Personal Data is located.
- GitHub has specific procedures in place governing access to copies of Customer Data.
- GitHub logs data restoration efforts, including the person responsible, the description of the restored data and where applicable, the person responsible and which data (if any) had to be input manually in the data recovery process.

Malicious Software. GitHub has threat detection controls to help identify and respond to anomalous or suspicious access to Customer Data, including malicious software originating from public networks.

Data Beyond Boundaries
- GitHub encrypts, or enables Customer to encrypt, Customer Data and Personal Data that is transmitted over public networks.
- GitHub restricts access to Customer Data and Personal Data in media leaving its facilities.

Event Logging. GitHub logs, or enables Customer to log, access and use of information systems containing Customer Data, registering the access ID, time, authorization granted or denied, and relevant activity.
Access ControlAccess Policy. GitHub maintains a record of security privileges of individuals having access to Customer Data.

Access Authorization
- GitHub maintains and updates a record of personnel authorized to access GitHub systems that contain Customer Data.
- GitHub identifies those personnel who may grant, alter or cancel authorized access to data and resources.
- GitHub ensures that where more than one individual has access to systems containing Customer Data, the individuals have separate identifiers/log-ins where technically and architecturally feasible, and commercially reasonable.

Least Privilege
- Technical support personnel are only permitted to have access to Customer Data and Personal Data when needed.
- GitHub restricts access to Customer Data and Personal Data to only those individuals who require such access to perform their job function. GitHub employees are only granted access to production systems based on their role within the organization.

Integrity and Confidentiality

- GitHub instructs GitHub personnel to disable administrative sessions when computers are left unattended.
- GitHub stores passwords such that they are encrypted or unintelligible while they are in force.

Authentication
- GitHub uses industry standard practices to identify and authenticate users who attempt to access information systems.
- Where authentication mechanisms are based solely on passwords, GitHub requires the password to be at least eight characters long.
- GitHub ensures that de-activated or expired employee identifiers are not granted to other individuals.
- GitHub monitors, or enables Customer to monitor, repeated attempts to gain access to the information system using an invalid password.
- GitHub maintains industry standard procedures to deactivate passwords that have been corrupted or inadvertently disclosed.
- GitHub uses industry standard password protection practices, including practices designed to maintain the confidentiality and integrity of passwords when they are assigned and distributed, and during storage.

Network Design. GitHub has controls to ensure no systems storing Customer Data and Personal Data are part of the same logical network used for GitHub business operations.
Information Security Incident ManagementIncident Response Process
- GitHub maintains a record of security incidents with a description of the incidents, the time period, the consequences of the breach, the name of the reporter, and to whom the incident was reported, and details regarding the handling of the incident.
- In the event that GitHub Security confirms or reasonably suspects that a GitHub.com customer is affected by a data breach, we will notify the customer without undue delay
- GitHub tracks, or enables Customer to track, disclosures of Customer Data, including what data has been disclosed, to whom, and at what time.

Service Monitoring. GitHub employs a wide range of continuous monitoring solutions for preventing, detecting, and mitigating attacks to the site.
Business Continuity Management- GitHub maintains emergency and contingency plans for the facilities in which GitHub information systems that process Customer Data and Personal Data are located.
- GitHub’s redundant storage and its procedures for recovering data are designed to attempt to reconstruct Customer Data and Personal Data in its original or last-replicated state from before the time it was lost or destroyed.

Attachment 1 - The Standard Contractual Clauses (EU/EEA)

Controller to Processor

SECTION I

Clause 1

Purpose and scope

  1. The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) for the transfer of personal data to a third country.
  2. The Parties:
    1. the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter ‘entity/ies’) transferring the personal data, as listed in Annex I.A (hereinafter each ‘data exporter’), and
    2. the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A (hereinafter each ‘data importer’)
    have agreed to these standard contractual clauses (hereinafter: ‘Clauses’).
  3. These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.
  4. The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.
Clause 2

Effect and invariability of the Clauses

  1. These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46(2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.
  2. These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.
Clause 3

Third-party beneficiaries

  1. Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:
    1. Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;
    2. Clause 8.1(b), 8.9(a), (c), (d) and (e);
    3. Clause 9(a), (c), (d) and (e);
    4. Clause 12(a), (d) and (f);
    5. Clause 13;
    6. Clause 15.1(c), (d) and (e);
    7. Clause 16(e);
    8. Clause 18(a) and (b).
  2. Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.
Clause 4

Interpretation

  1. Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.
  2. These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.
  3. These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.
Clause 5

Hierarchy

In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail.

Clause 6

Description of the transfer(s)

The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B.

Clause 7

Docking clause

  1. An entity that is not a Party to these Clauses may, with the agreement of the Parties, accede to these Clauses at any time, either as a data exporter or as a data importer, by completing the Appendix and signing Annex I.A.
  2. Once it has completed the Appendix and signed Annex I.A, the acceding entity shall become a Party to these Clauses and have the rights and obligations of a data exporter or data importer in accordance with its designation in Annex I.A.
  3. The acceding entity shall have no rights or obligations arising under these Clauses from the period prior to becoming a Party.

SECTION II – OBLIGATIONS OF THE PARTIES

Clause 8

Data protection safeguards

The data exporter warrants that it has used reasonable efforts to determine that the data importer is able, through the implementation of appropriate technical and organisational measures, to satisfy its obligations under these Clauses.

8.1 Instructions

      <li>The data importer shall process the personal data only on documented instructions from the data exporter. The data exporter may give such instructions throughout the duration of the contract.</li>
      <li>The data importer shall immediately inform the data exporter if it is unable to follow those instructions.</li>
    

8.2 Purpose limitation

The data importer shall process the personal data only for the specific purpose(s) of the transfer, as set out in Annex I.B, unless on further instructions from the data exporter.

8.3 Transparency

On request, the data exporter shall make a copy of these Clauses, including the Appendix as completed by the Parties, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including the measures described in Annex II and personal data, the data exporter may redact part of the text of the Appendix to these Clauses prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand the its content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information. This Clause is without prejudice to the obligations of the data exporter under Articles 13 and 14 of Regulation (EU) 2016/679.

8.4 Accuracy

If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to erase or rectify the data.

8.5 Duration of processing and erasure or return of data

Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the data exporter and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf and delete existing copies. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a).

8.6 Security of processing

  1. The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter ‘personal data breach’). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subjects. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.
  2. The data importer shall grant access to the personal data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
  3. In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify the data exporter without undue delay after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the breach including, where appropriate, measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
  4. The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer.

8.7 Sensitive data

Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B.

8.8 Onward transfers

The data importer shall only disclose the personal data to a third party on documented instructions from the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union (1) (in the same country as the data importer or in another third country, hereinafter ‘onward transfer’) if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if:

  1. the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;
  2. the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 Regulation of (EU) 2016/679 with respect to the processing in question;
  3. the onward transfer is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or
  4. the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.

  5. Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation.

8.9 Documentation and compliance

  1. The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses.
  2. The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the data exporter.
  3. The data importer shall make available to the data exporter all information necessary to demonstrate compliance with the obligations set out in these Clauses and at the data exporter’s request, allow for and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or audit, the data exporter may take into account relevant certifications held by the data importer.
  4. The data exporter may choose to conduct the audit by itself or mandate an independent auditor. Audits may include inspections at the premises or physical facilities of the data importer and shall, where appropriate, be carried out with reasonable notice.
  5. The Parties shall make the information referred to in paragraphs (b) and (c), including the results of any audits, available to the competent supervisory authority on request.
Clause 9

Use of sub-processors

  1. GENERAL WRITTEN AUTHORISATION The data importer has the data exporter’s general authorisation for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the data exporter in writing of any intended changes to that list through the addition or replacement of sub-processors at least 90 days in advance, thereby giving the data exporter sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the data exporter with the information necessary to enable the data exporter to exercise its right to object.
  2. Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the data exporter), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects.(2) The Parties agree that, by complying with this Clause, the data importer fulfils its obligations under Clause 8.8. The data importer shall ensure that the sub-processor complies with the obligations to which the data importer is subject pursuant to these Clauses.
  3. The data importer shall provide, at the data exporter’s request, a copy of such a sub-processor agreement and any subsequent amendments to the data exporter. To the extent necessary to protect business secrets or other confidential information, including personal data, the data importer may redact the text of the agreement prior to sharing a copy.
  4. The data importer shall remain fully responsible to the data exporter for the performance of the sub-processor’s obligations under its contract with the data importer. The data importer shall notify the data exporter of any failure by the sub-processor to fulfil its obligations under that contract.
  5. The data importer shall agree a third-party beneficiary clause with the sub-processor whereby – in the event the data importer has factually disappeared, ceased to exist in law or has become insolvent – the data exporter shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.
Clause 10

Data subject rights

  1. The data importer shall promptly notify the data exporter of any request it has received from a data subject. It shall not respond to that request itself unless it has been authorised to do so by the data exporter.
  2. The data importer shall assist the data exporter in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights under Regulation (EU) 2016/679. In this regard, the Parties shall set out in Annex II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required.
  3. In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the data exporter.
Clause 11

Redress

  1. The data importer shall inform data subjects in a transparent and easily accessible format, through individual notice or on its website, of a contact point authorised to handle complaints. It shall deal promptly with any complaints it receives from a data subject.
  2. In case of a dispute between a data subject and one of the Parties as regards compliance with these Clauses, that Party shall use its best efforts to resolve the issue amicably in a timely fashion. The Parties shall keep each other informed about such disputes and, where appropriate, cooperate in resolving them.
  3. Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to:
    1. lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13;
    2. refer the dispute to the competent courts within the meaning of Clause 18.
  4. The Parties accept that the data subject may be represented by a not-for-profit body, organisation or association under the conditions set out in Article 80(1) of Regulation (EU) 2016/679.
  5. The data importer shall abide by a decision that is binding under the applicable EU or Member State law.
  6. The data importer agrees that the choice made by the data subject will not prejudice his/her substantive and procedural rights to seek remedies in accordance with applicable laws.
Clause 12

Liability

  1. Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any breach of these Clauses.
  2. The data importer shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data importer or its sub-processor causes the data subject by breaching the third-party beneficiary rights under these Clauses.
  3. Notwithstanding paragraph (b), the data exporter shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data exporter or the data importer (or its sub-processor) causes the data subject by breaching the third-party beneficiary rights under these Clauses. This is without prejudice to the liability of the data exporter and, where the data exporter is a processor acting on behalf of a controller, to the liability of the controller under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable.
  4. The Parties agree that if the data exporter is held liable under paragraph (c) for damages caused by the data importer (or its sub-processor), it shall be entitled to claim back from the data importer that part of the compensation corresponding to the data importer’s responsibility for the damage.
  5. Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data subject is entitled to bring an action in court against any of these Parties.
  6. The Parties agree that if one Party is held liable under paragraph (e), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its/their responsibility for the damage.
  7. The data importer may not invoke the conduct of a sub-processor to avoid its own liability.
Clause 13

Supervision

  1. [Where the data exporter is established in an EU Member State:] The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679 as regards the data transfer, as indicated in Annex I.C, shall act as competent supervisory authority.

    [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) and has appointed a representative pursuant to Article 27(1) of Regulation (EU) 2016/679:] The supervisory authority of the Member State in which the representative within the meaning of Article 27(1) of Regulation (EU) 2016/679 is established, as indicated in Annex I.C, shall act as competent supervisory authority.

    [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) without however having to appoint a representative pursuant to Article 27(2) of Regulation (EU) 2016/679:] The supervisory authority of one of the Member States in which the data subjects whose personal data is transferred under these Clauses in relation to the offering of goods or services to them, or whose behaviour is monitored, are located, as indicated in Annex I.C, shall act as competent supervisory authority.

  2. The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.

SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES

Clause 14

Local laws and practices affecting compliance with the Clauses

  1. The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.
  2. The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:
    1. the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred;
    2. the laws and practices of the third country of destination– including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards (3);
    3. any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.
  3. The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.
  4. The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.
  5. The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a).
  6. Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.
Clause 15

Obligations of the data importer in case of access by public authorities

15.1 Notification

  1. The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary with the help of the data exporter) if it:
    1. receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or
    2. becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.
  2. If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.
  3. Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.).
  4. The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.
  5. Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.

15.2 Review of legality and data minimisation

  1. The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).
  2. The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request.
  3. The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.

SECTION IV – FINAL PROVISIONS

Clause 16

Non-compliance with the Clauses and termination

  1. The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.
  2. In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).
  3. The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:
    1. the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension;
    2. the data importer is in substantial or persistent breach of these Clauses; or
    3. the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.

    In these cases, it shall inform the competent supervisory authority of such non-compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise.
  4. Personal data that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall at the choice of the data exporter immediately be returned to the data exporter or deleted in its entirety. The same shall apply to any copies of the data. The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.
  5. Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.
Clause 17

Governing law

These Clauses shall be governed by the law of one of the EU Member States, provided such law allows for third-party beneficiary rights. The Parties agree that this shall be the law of the Netherlands.

Clause 18

Choice of forum and jurisdiction

  1. Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.
  2. The Parties agree that those shall be the courts of the Netherlands.
  3. A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of the Member State in which he/she has his/her habitual residence.
  4. The Parties agree to submit themselves to the jurisdiction of such courts.

ANNEX I

to the Standard Contractual Clauses (EU/EEA)

A. LIST OF PARTIES

Data exporter(s): Customer is the data exporter
Name: see GitHub Customer Agreement
Address: see GitHub Customer Agreement
Contact person’s name, position and contact details: see GitHub Customer Agreement
Activities relevant to the data transferred under these Clauses:
The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement.
Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement
Role (controller/processor): controller (unless otherwise agreed in the Customer Agreement).

Data importer(s):
Name: GitHub, Inc.
Address: 88 Colin P Kelly Jr St, San Francisco, CA 94107, USA
Contact person’s name, position and contact details: Frances Wiet, Head of Privacy, fwiet@github.com
Activities relevant to the data transferred under these Clauses:
GitHub, Inc. is a global producer of software and services
Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement)
Role (controller/processor): processor or, depending on the agreements set forth in the Customer Agreement, subprocessor.

B. DESCRIPTION OF TRANSFER

Categories of data subjects whose personal data is transferred:

Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data:

  • Empleados, consultores y trabajadores temporales (actuales, previos o futuros) del exportador de los datos;
  • Consultores/personas de contacto del exportador de datos (personas naturales) o los empleados, consultores o trabajadores temporales de la entidad legal de las personas de contacto/consultores (actuales, futuros, pasados);
  • Users and other data subjects that are users of data exporter's services;
  • Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter.

Categories of personal data transferred:

The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data:

  • Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth);
  • Authentication data (for example user name, password or PIN code, security question, audit trail);
  • Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details);
  • Unique identification numbers and signatures (for example IP addresses, employee number, student number);
  • Pseudonymous identifiers;
  • Photos, video and audio;
  • Internet activity (for example browsing history, search history, reading and viewing activities);
  • Device identification (for example IMEI-number, SIM card number, MAC address);
  • Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences);
  • Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or
  • Any other personal data identified in Article 4 of the GDPR.

Sensitive data transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialised training), keeping a record of access to the data, restrictions for onward transfers or additional security measures:
GitHub does not request or otherwise ask for sensitive data and receives such data only if and when customers or data subjects decide to provide it.

The frequency of the transfer (e.g. whether the data is transferred on a one-off or continuous basis):

Continuous as part of the Online Services or Professional Services.

Nature of the processing:

The personal data transferred will be subject to the following basic processing activities:

  1. Duration and Object of Data Processing. The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and the data importer. The objective of the data processing is the performance of Online Services and Professional Services.
  2. Personal Data Access. For the term designated under the applicable GitHub Customer Agreement, data importer will, at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.
  3. Data Exporter’s Instructions. For Online Services and Professional Services, data importer will only act upon data exporter’s instructions.

Purpose(s) of the data transfer and further processing:

The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA.

The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period:

Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement.

For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing:

In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose. Unless a particular subcontractor is replaced ahead of time, the processing will be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer.

C. COMPETENT SUPERVISORY AUTHORITY

Identify the competent supervisory authority/ies in accordance with Clause 13:

The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679.  

ANNEX II

to the Standard Contractual Clauses (EU/EEA)

TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA

Description of the technical and organisational measures implemented by the data importer(s) (including any relevant certifications) to ensure an appropriate level of security, taking into account the nature, scope, context and purpose of the processing, and the risks for the rights and freedoms of natural persons.

  1. Data Security Certifications. Data importer holds the following data security certifications:
    • SOC 1, Type 2;
    • SOC 2, Type 2;
    • NIST, to the extent incorporated for FedRAMP Low-Impact / Tailored ATO.
  2. Personnel. Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.
  3. Data Privacy Contact. The data privacy officer of the data importer can be reached at the following address:

    GitHub, Inc.
    Attn: Privacy
    88 Colin P. Kelly Jr. Street
    San Francisco, California 94107 USA

  4. Technical and Organization Measures. The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Data Security section of the DPA are hereby incorporated into this Annex II to Attachment 1 by this reference and are binding on the data importer as if they were set forth in this Annex 2 to Attachment 1 in their entirety.

For transfers to (sub-) processors, also describe the specific technical and organisational measures to be taken by the (sub-) processor to be able to provide assistance to the controller and, for transfers from a processor to a sub-processor, to the data exporter:

Vendor management program - third-party risk program

The data importer has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors. Vendors undergo reassessment when a new business use case is requested. The data importer’s vendor risk program is structured so all of data importer’s vendors' risk assessments are refreshed two years from the last review date.

Vendors deemed high risk, such as data center providers or other vendors storing or processing data in scope for the data importer’s regulatory or contractual requirements, undergo reassessment annually.

ANNEX III

to the Standard Contractual Clauses (EU/EEA)

Additional Safeguards Addendum

By this Additional Safeguards Addendum to Standard Contractual Clauses (EU/EEA) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates.

This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (EU/EEA).

  1. Challenges to Orders. In addition to Clause 15.1 of the Standard Contractual Clauses (EU/EEA), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (EU/EEA), GitHub shall:
    1. use every reasonable effort to redirect the third party to request data directly from Customer;
    2. promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and
    3. use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.

    For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction.
  2. Indemnification of Data Subjects. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (EU/EEA) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.
  3. Conditions of Indemnification. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:
    1. GitHub engaged in a Relevant Disclosure;
    2. the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and
    3. the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.

    The data subject bears the burden of proof with respect to conditions a. though c.
    Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR.
  4. Scope of Damages. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.
  5. Exercise of Rights. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 12 of the Standard Contractual Clauses (EU/EEA). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.
  6. Notice of Change. In addition to Clause 14 of the Standard Contractual Clauses (EU/EEA), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (EU/EEA) and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by this Addendum or the Standard Contractual Clauses (EU/EEA), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract.
  7. Termination. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (EU/EEA) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.

Attachment 2 – The Standard Contractual Clauses (UK)

Execution of the GitHub Customer Agreement by Customer includes execution of this Attachment 2, which is countersigned by GitHub, Inc.

En los países donde se requiera de aprobación regulatoria para utilizar las Cláusulas Contractuales Estándar, no se podrá depender de éstas bajo la Comisión Europea 2010/87/EU (de febrero de 2010) para legitimar la exportación de datos del país en cuestión, a menos de que el cliente tenga la aprobación regulatoria requerida.

Beginning May 25, 2018 and thereafter, references to various Articles from the Directive 95/46/EC in the Standard Contractual Clauses below will be treated as references to the relevant and appropriate Articles in the GDPR.

For the purposes of Article 26(2) of Directive 95/46/EC for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, Customer (as data exporter) and GitHub, Inc. (as data importer, whose signature appears below), each a “party,” together “the parties,” have agreed on the following Contractual Clauses (the “Clauses” or “Standard Contractual Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1.

Cláusula 1: Definiciones

  1. 'personal data', 'special categories of data', 'process/processing', 'controller', 'processor', 'data subject' and 'supervisory authority' shall have the same meaning as in Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data;
  2. 'the data exporter' means the controller who transfers the personal data;
  3. 'the data importer' means the processor who agrees to receive from the data exporter personal data intended for processing on his behalf after the transfer in accordance with his instructions and the terms of the Clauses and who is not subject to a third country's system ensuring adequate protection within the meaning of Article 25(1) of Directive 95/46/EC;
  4. 'the subprocessor' means any processor engaged by the data importer or by any other subprocessor of the data importer who agrees to receive from the data importer or from any other subprocessor of the data importer personal data exclusively intended for processing activities to be carried out on behalf of the data exporter after the transfer in accordance with his instructions, the terms of the Clauses and the terms of the written subcontract;
  5. 'the applicable data protection law' means the legislation protecting the fundamental rights and freedoms of individuals and, in particular, their right to privacy with respect to the processing of personal data applicable to a data controller in the Member State in which the data exporter is established;
  6. 'technical and organisational security measures' means those measures aimed at protecting personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing.

Cláusula 2: Detalles de la transferencia

Los detalles de la transferencia y, en particular, de las categorías especiales de datos personales en donde sean aplicables se especifican en el Apéndice 1 que se encuentra más adelante, el cual forma una parte integral de las Cláusulas.

Cláusula 3: Cláusula de beneficiario tercero

  1. El titular de los datos podrá hacer valer la ley contra el exportador de datos en esta Cláusula, la Cláusula 4(b) a (i), la Cláusula 5(a) a (e), y de (g) a (j), la Cláusula 6(1) y (2), la Cláusula 8(2), y las Cláusulas 9 a 12 como beneficiario tercero.
  2. El titular de los datos podrá hacer valer la ley contra el importador de datos en esta Cláusula, la Cláusula 5(a) a (e) y (g), la Cláusula 6, Cláusula 7, Clúsula 8(2) y las Cláusulas 9 a 12, en los casos en donde el exportador de los datos haya desaparecido realmente o haya dejado de existir en la ley a menos de que alguna entidad de sucesión haya asumido las obligaciones legales integrales del exportador de datos mediante onctrato o mediante la operación legal, como resultado de que lo que asume en los derechos y obligaciones del exportador de datos, en cuyo caso, el titular de los datos podrá hacer valor esto contra dicha entidad.
  3. El sujeto de los datos puede aplicar la ley en contra del subprocesador de esta Cláusula, la Cláusula 5(a) a (e) y (g), Cláusula 6, Cláusula 7, Cláusula 8(2) y Cláusulas 9 a 12, en casos en donde tanto el exportador como el importador de los datos hayan desaparecido realmente o dejado de existir en la ley o se hayan declarado insolventes, a menos de que cualquier entidad sucesora haya asumido todas las obligaciones del exportador de los datos contractualmente o conforme a derecho que resulte en la toma de derchos y obligaciones del exportador de datos, en cuyo caso, el titular de los datos puede aplicar la ley en contra de dicha entidad. Dicha responsabilidad de terceros del subprocesador se limitará a sus propias operaciones de procesamiento bajo las Cláusulas.
  4. Las partes no se oponen a que un titular de los datos se represente mediante una asociación o cualquier otro cuerpo si dicho titular así lo desea expresamente y si la ley nacional lo permite.

Cláusula 4: Las obligaciones del exportador de los datos

El exportador de los datos acuerda y garantiza:

  1. that the processing, including the transfer itself, of the personal data has been and will continue to be carried out in accordance with the relevant provisions of the applicable data protection law (and, where applicable, has been notified to the relevant authorities of the Member State where the data exporter is established) and does not violate the relevant provisions of that State;
  2. that it has instructed and throughout the duration of the personal data processing services will instruct the data importer to process the personal data transferred only on the data exporter's behalf and in accordance with the applicable data protection law and the Clauses;
  3. that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in Appendix 2 below;
  4. that after assessment of the requirements of the applicable data protection law, the security measures are appropriate to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation;
  5. that it will ensure compliance with the security measures;
  6. that, if the transfer involves special categories of data, the data subject has been informed or will be informed before, or as soon as possible after, the transfer that its data could be transmitted to a third country not providing adequate protection within the meaning of Directive 95/46/EC;
  7. to forward any notification received from the data importer or any subprocessor pursuant to Clause 5(b) and Clause 8(3) to the data protection supervisory authority if the data exporter decides to continue the transfer or to lift the suspension;
  8. to make available to the data subjects upon request a copy of the Clauses, with the exception of Appendix 2, and a summary description of the security measures, as well as a copy of any contract for subprocessing services which has to be made in accordance with the Clauses, unless the Clauses or the contract contain commercial information, in which case it may remove such commercial information;
  9. that, in the event of subprocessing, the processing activity is carried out in accordance with Clause 11 by a subprocessor providing at least the same level of protection for the personal data and the rights of data subject as the data importer under the Clauses; and
  10. that it will ensure compliance with Clause 4(a) to (i).

Cláusula 5: Obligaciones del importador de los datos

El importador de los datos acuerda y garantiza:

  1. to process the personal data only on behalf of the data exporter and in compliance with its instructions and the Clauses; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
  2. that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the data exporter and its obligations under the contract and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the Clauses, it will promptly notify the change to the data exporter as soon as it is aware, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
  3. that it has implemented the technical and organisational security measures specified in Appendix 2 before processing the personal data transferred;
  4. that it will promptly notify the data exporter about:
    1. any legally binding request for disclosure of the personal data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation,
    2. any accidental or unauthorised access, and
    3. any request received directly from the data subjects without responding to that request, unless it has been otherwise authorised to do so;
    to deal promptly and properly with all inquiries from the data exporter relating to its processing of the personal data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred; at the request of the data exporter to submit its data processing facilities for audit of the processing activities covered by the Clauses which shall be carried out by the data exporter or an inspection body composed of independent members and in possession of the required professional qualifications bound by a duty of confidentiality, selected by the data exporter, where applicable, in agreement with the supervisory authority;
  5. to make available to the data subject upon request a copy of the Clauses, or any existing contract for subprocessing, unless the Clauses or contract contain commercial information, in which case it may remove such commercial information, with the exception of Appendix 2 which shall be replaced by a summary description of the security measures in those cases where the data subject is unable to obtain a copy from the data exporter;
  6. that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent;
  7. that the processing services by the subprocessor will be carried out in accordance with Clause 11; and
  8. to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter.

Cláusula 6: Responsabilidades

  1. Las partes concuerdan que cualquier titular de los datos que haya sufrido daños como resultado de cualquier violación a las obligaciones descritas en la Cláusula 3 o en la Cláusula 11 por parte de cualquier subprocesador tiene derecho a recibir una compensación del exportador de los datos por dicho daño sufrido.
  2. Si algún titular de los datos no puede presentar un reclamo de indemnización en contra del exportador de los datos de acuerdo con el párrafo 1, la cual se derive de una violación por parte del importador de los datos o de su subprocesador o de cualquiera de sus obligaciones que se describen en la Cláusula 3, o en la Cláusula 11, debido a que el exportador de los datos ha desaparecido realmente o dejado de existir ante la ley, o se haya declarado insolvente, el importador de los datos acuerda que el titular de los datos puede emitir un reclamo contra este como si fuera el exportador de los mismos, a menos de que alguna entidad sucesora haya asumido las obligaciones legales íntegras del exportador de los datos contractualmente o mediante la aplicación de la ley, en cuyo caso, el sujeto de los datos puede hacer valer sus derechos contra dicha entidad.

    El importador de los datos no podrá depender en argumentar una violación mediante un procesador de sus obligaciones para evitar sus propias responsabilidades.
  3. Si un titular de los datos no puede presentar un reclamo en contra del exportador o importador de los datos a los cuales se hace referencia en los párrafos 1 y 2, derivado de una violación por parte del subprocesador o por cualquiera de sus obligaciones explicadas en la Cláusula 2 o en la Cláusula 11 ya que ambos, importador y exportador, hayan desaparecido realmente o dejado de existir ante la ley, o se hayan declarado insolventes, el subprocesador acuerda que el titular de los datos podrá emitir un reclamo contra el subprocesador de los datos con respecto a sus propias operaciones de procesamiento bajo las Cláusulas como si fuera el exportador o importador de los mismos, a menos de que cualquier entidad sucesora haya asumido las obligaciones íntegras del exportador o importador de los datos contractualmente o por aplicación de la ley, en cuyo caso, el titular de los datos puede hacer valer sus derechos en contra de dicha entidad. La responsabilidad del subprocesador deberá limitarse a sus propias operaciones de procesamiento bajo las Cláusulas.

Cláusula 7: Mediación y Jurisdicción

  1. El iimportador de los datos acuerda que si el titular de los datos apelase en contra de sus derechos de beneficiario tercero y/o reclama una compensación por daños bajo las Cláusulas, el importador de los datos aceptará la decisión del titular de los datos:
    1. to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority;
    2. to refer the dispute to the courts in the Member State in which the data exporter is established.
  2. Las partes acuerdan que la elección que haga el titular de los datos no perjudicará sus derechos sustantivos o procesales para buscar remedios de acuerdo con otras disposiciones de la ley internacional o nacional.

Cláusula 8: Cooperación con las autoridades supervisantes

  1. El exportador de los datos acuerda depositar una copia de este contrato con la autoridad supervisora si así lo requiere o si dicho depósito se requiere bajo la ley de protección de datos aplicable.
  2. Las partes concuerdan que la autoridad supervisora tiene el derecho de conducir una auditoría del importador de los datos, y de cualquier subprocesador, la cual tiene el mismo alcance y está sujeta a las mismas condiciones que aplcarían en una auditoría del exportador de los datos bajo la ley de protección de datos aplicable.
  3. El importador de los datos deberá informar de manera oportuna al exportador de los datos acerca de la existencia de la legislación aplicable a éste o a cualquier subprocesador, previniendo la conducción de una auditoría al importador de los datos o a cualquier subprocesador de acuerdo con el párrafo 2. En tal caso, el exportador de datos tendrá derecho de tomar las medidas previstas en la Cláusula 5 (b).

Cláusula 9: Ley Aplicable.

Las Cláusulas deberán regirse por medio de la ley del Estado Miembro en el cual se establece el exportador de los datos.

Cláusula 10: Variación del contrato

Las partes se comprometen a no variar o modificar las Cláusulas. Esto no impide que las partes agreguen cláusulas sobre los asuntos relacionados con los negocios conforme se requieran mientras que éstas no contradigan la Cláusula.

Cláusula 11: Subprocesamiento

  1. El importador de los datos no deberá subcontratar ninguna de sus operaciones de procesamiento que se realicen en nombre del exportador de los datos bajo las Cláusulas sin el consentimiento previo y por escrito del exportador de los datos. En caso de que el importador de los datos subcontrate sus obligaciones debajo de las Cláusulas, con el consentimiento del exportador de los datos, deberá hacerlo únicamente por medio de un contrato por escrito con el subprocesador, el cual imponga las mismas obligaciones en el subprocesador que se impusieron en el importador de los datos bajo las Cláusulas. Donde sea que el subprocesador incumpla con sus obligaciones de protección de datos bajo dicho contrato por escrito, el importador de los datos deberá ser plenamente responsable del exportador de los datos por el cumplimiento de las obligaciones del subprocesador bajo dicho contrato.
  2. El contrato escrito previo entre el importador de los datos y el subprocesador también deberá proporcionar una cláusula de terceros beneficiarios de acuerdo con lo asentado en la Cláusula 3 para los casos en donde el titular de los datos no pueda preentar una reclamación de compensación como se refiere en el párrafo 1 de la Cláusula 6 en contra del exportador o del importador de los datos debido a que han desaparecido realmente o han dejado de existir ante la ley o se hayan declarado insolventes y ninguna entidad sucesora haya asumido las obligaciones legales íntegras del exportador o importador de los datos contractualmente o mediante la ley aplicable. Dicha responsabilidad de terceros del subprocesador se limitará a sus propias operaciones de procesamiento bajo las Cláusulas.
  3. Las disposiciones que se relacionan con los aspectos de protección de datos para el subprocesamiento del cntracto al cual se refiere en el párrafo 1 deberán regirse por la ley del Estado Miembro en el cual se establezca el exportador de los datos.
  4. El exportador de los datos deberá mantener una lista de contratos de subprocesamiento que se celebren bajo las Cláusulas y que el importador de los datos notifique de acuerdo con la Cláusula 5 (j), la cual se debe actualizar por lo menos una vez al año. La lista deberá estar disponible para la autoridad supervisora de protección de datos del exportador de los datos.

Cláusula 12: Obligaciones después de la terminación de los servicios de procesamiento de datos personales

  1. Las partes acuerdan que, en la terminación de la prestación de los servicios de procesamiento de datos, el importador y subprocesador de los mismos deberá, a elección del exportador, regresar todos los datos personales transferidos y las copias de los mismos al exportador de los datos o deberá destruir todos los dtos personales y certificar ante el exportador de los datos que así lo ha hecho, a menos de que la legislación impuesta en el importador de los datos impida que regrese o destrulla todos o parte de los datos personales transferidos. En dado caso, el importador de los datos justifica que garantizará la confidencialidad de los datos personales transferidos y que ya no procesará activamente dichos datos personales.
  2. El importador de los datos y el subprocesador garantizan que, bajo solicitud del exportador de los datos y/o de la autoridad supervisora, emitirán sus instalaciones de procesamiento de datos para auditoría de las medidas descritas en el párrafo 1.

Appendix 1 to the Standard Contractual Clauses (UK)

Data exporter: Customer is the data exporter. The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement.

Data importer: The data importer is GitHub, Inc., a global producer of software and services.

Data subjects: Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data:

  • Empleados, consultores y trabajadores temporales (actuales, previos o futuros) del exportador de los datos;
  • Consultores/personas de contacto del exportador de datos (personas naturales) o los empleados, consultores o trabajadores temporales de la entidad legal de las personas de contacto/consultores (actuales, futuros, pasados);
  • Users and other data subjects that are users of data exporter's services;
  • Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter.

Categories of data: The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data:

  • Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth);
  • Authentication data (for example user name, password or PIN code, security question, audit trail);
  • Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details);
  • Unique identification numbers and signatures (for example IP addresses, employee number, student number);
  • Pseudonymous identifiers;
  • Photos, video and audio;
  • Internet activity (for example browsing history, search history, reading and viewing activities);
  • Device identification (for example IMEI-number, SIM card number, MAC address);
  • Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences);
  • Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or
  • Any other personal data identified in Article 4 of the GDPR.

Processing operations: The personal data transferred will be subject to the following basic processing activities:

  1. Duration and Object of Data Processing. The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer. The objective of the data processing is the performance of Online Services and Professional Services.
  2. Scope and Purpose of Data Processing. The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA.
  3. Personal Data Access. For the term designated under the applicable GitHub Customer Agreement data importer will at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.
  4. Data Exporter’s Instructions. For Online Services and Professional Services, data importer will only act upon data exporter’s instructions as conveyed by GitHub.
  5. Personal Data Deletion or Return. Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement.

Subcontractors: In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose.

Appendix 2 to the Standard Contractual Clauses (UK)

Descripción de las medidas de seguridad técnicas y organizacionales implementadas por el importador de los datos de acuerdo con las Cláusulas 4(d) y 5(c):

  1. Personnel. Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.
  2. Data Privacy Contact. The data privacy officer of the data importer can be reached at the following address:
    GitHub, Inc.
    Attn: Privacy
    88 Colin P. Kelly Jr. Street
    San Francisco, California 94107 USA
  3. Technical and Organization Measures. The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Security Practices and Policies section of the DPA are hereby incorporated into this Appendix 2 by this reference and are binding on the data importer as if they were set forth in this Appendix 2 in their entirety.

Appendix 3 to the Standard Contractual Clauses (UK)

Additional Safeguards Addendum

By this Additional Safeguards Addendum to Standard Contractual Clauses (UK) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates.

This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (UK).

  1. Challenges to Orders. In addition to Clause 5(d)(i) of the Standard Contractual Clauses (UK), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (UK), GitHub shall:
    1. use every reasonable effort to redirect the third party to request data directly from Customer;
    2. promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and
    3. use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.

    For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction.
  2. Indemnification of Data Subjects. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (UK) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.
  3. Conditions of Indemnification. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:
    1. GitHub engaged in a Relevant Disclosure;
    2. the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and
    3. the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.

    The data subject bears the burden of proof with respect to conditions a. though c.
    Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR.
  4. Scope of Damages. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.
  5. Exercise of Rights. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 6 of the Standard Contractual Clauses (UK). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.
  6. Notice of Change. In addition to Clause 5(b) of the Standard Contractual Clauses (UK), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (UK) and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by this Addendum or the Standard Contractual Clauses (UK), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract.
  7. Termination. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (UK) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.

    Signing the Standard Contractual Clauses (UK), Appendix 1, Appendix 2 and

Attachment 3 – European Union General Data Protection Regulation Terms

GitHub makes the commitments in these GDPR Related Terms, to all customers effective May 25, 2018. These commitments are binding upon GitHub with regard to Customer regardless of (1) the version of the GitHub Customer Agreement and DPA that is otherwise applicable to any given Online Services subscription or (2) any other agreement that references this attachment.

For purposes of these GDPR Related Terms, Customer and GitHub agree that Customer is the controller of Personal Data and GitHub is the processor of such data, except when Customer acts as a processor of Personal Data, in which case GitHub is a subprocessor. These GDPR Related Terms apply to the processing of Personal Data, within the scope of the GDPR, by GitHub on behalf of Customer. These GDPR Related Terms do not limit or reduce any data protection commitments GitHub makes to Customer in the GitHub Customer Agreement or other agreement between GitHub and Customer. These GDPR Related Terms do not apply where GitHub is a controller of Personal Data.

Relevant GDPR Obligations: Articles 28, 32, and 33

  1. GitHub shall not engage another processor without prior specific or general written authorisation of Customer. In the case of general written authorisation, GitHub shall inform Customer of any intended changes concerning the addition or replacement of other processors, thereby giving Customer the opportunity to object to such changes. (Article 28(2))
  2. Processing by GitHub shall be governed by these GDPR Related Terms under European Union (hereafter “Union”) or Member State law and are binding on GitHub with regard to Customer. The subject-matter and duration of the processing, the nature and purpose of the processing, the type of Personal Data, the categories of data subjects and the obligations and rights of the Customer are set forth in the Customer’s licensing agreement, including these GDPR Related Terms. In particular, GitHub shall:
    1. process the Personal Data only on documented instructions from Customer, including with regard to transfers of Personal Data to a third country or an international organisation, unless required to do so by Union or Member State law to which GitHub is subject; in such a case, GitHub shall inform Customer of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest;
    2. ensure that persons authorised to process the Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality;
    3. take all measures required pursuant to Article 32 of the GDPR;
    4. respect the conditions referred to in paragraphs 1 and 3 for engaging another processor;
    5. taking into account the nature of the processing, assist Customer by appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the Customer’s obligation to respond to requests for exercising the data subject's rights laid down in Chapter III of the GDPR;
    6. assist Customer in ensuring compliance with the obligations pursuant to Articles 32 to 36 of the GDPR, taking into account the nature of processing and the information available to GitHub;
    7. at the choice of Customer, delete or return all the Personal Data to Customer after the end of the provision of services relating to processing, and delete existing copies unless Union or Member State law requires storage of the Personal Data;
    8. make available to Customer all information necessary to demonstrate compliance with the obligations laid down in Article 28 of the GDPR and allow for and contribute to audits, including inspections, conducted by Customer or another auditor mandated by Customer.

    GitHub shall immediately inform Customer if, in its opinion, an instruction infringes the GDPR or other Union or Member State data protection provisions. (Article 28(3))

  3. Where GitHub engages another processor for carrying out specific processing activities on behalf of Customer, the same data protection obligations as set out in these GDPR Related Terms shall be imposed on that other processor by way of a contract or other legal act under Union or Member State law, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing will meet the requirements of the GDPR. Where that other processor fails to fulfil its data protection obligations, GitHub shall remain fully liable to the Customer for the performance of that other processor's obligations. (Article 28(4))
  4. Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, Customer and GitHub shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate:
    1. the pseudonymisation and encryption of Personal Data;
    2. the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services;
    3. the ability to restore the availability and access to Personal Data in a timely manner in the event of a physical or technical incident; and
    4. a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing. (Article 32(1))
  5. In assessing the appropriate level of security, account shall be taken of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data transmitted, stored or otherwise processed (Article 32(2)).
  6. Customer and GitHub shall take steps to ensure that any natural person acting under the authority of Customer or GitHub who has access to Personal Data does not process them except on instructions from Customer, unless he or she is required to do so by Union or Member State law (Article 32(4)).
  7. GitHub shall notify Customer without undue delay after becoming aware of a Personal Data breach (Article 33(2)). Such notification will include that information a processor must provide to a controller under Article 33(3) to the extent such information is reasonably available to GitHub.

(1) The Agreement on the European Economic Area (EEA Agreement) provides for the extension of the European Union’s internal market to the three EEA States Iceland, Liechtenstein and Norway. The Union data protection legislation, including Regulation (EU) 2016/679, is covered by the EEA Agreement and has been incorporated into Annex XI thereto. Therefore, any disclosure by the data importer to a third party located in the EEA does not qualify as an onward transfer for the purpose of these Clauses.

(2) This requirement may be satisfied by the sub-processor acceding to these Clauses under the appropriate Module, in accordance with Clause 7.

(3) As regards the impact of such laws and practices on compliance with these Clauses, different elements may be considered as part of an overall assessment. Such elements may include relevant and documented practical experience with prior instances of requests for disclosure from public authorities, or the absence of such requests, covering a sufficiently representative time-frame. This refers in particular to internal records or other documentation, drawn up on a continuous basis in accordance with due diligence and certified at senior management level, provided that this information can be lawfully shared with third parties. Where this practical experience is relied upon to conclude that the data importer will not be prevented from complying with these Clauses, it needs to be supported by other relevant, objective elements, and it is for the Parties to consider carefully whether these elements together carry sufficient weight, in terms of their reliability and representativeness, to support this conclusion. In particular, the Parties have to take into account whether their practical experience is corroborated and not contradicted by publicly available or otherwise accessible, reliable information on the existence or absence of requests within the same sector and/or the application of the law in practice, such as case law and reports by independent oversight bodies.

¿Te ayudó este documento?

Política de privacidad

¡Ayúdanos a hacer geniales estos documentos!

Todos los documentos de GitHub son de código abierto. ¿Notas algo que esté mal o que no sea claro? Emite una solicitud de cambios.

Haz una contribución

O, aprende cómo contribuir.