CINXE.COM
LinkedIn Data Processing Agreement
<!DOCTYPE html> <html lang="en"> <head> <meta name="pageKey" content="d_lithograph_content"> <!----><!----> <meta name="locale" content="en_US"> <meta id="config" data-app-id="lithograph" data-app-version="0.0.1084" data-call-tree-id="AAYoHetdfiH4HmYYWvyESA==" data-multiproduct-name="lithograph-publish-frontend" data-service-name="lithograph-publish-frontend" data-browser-id="da39cb00-88e6-4f3b-8420-2e99ff9b8652" data-page-instance="urn:li:page:d_lithograph_content;oRuNfD57SS6XX27TxX3VTA==" data-disable-jsbeacon-pagekey-suffix="false"> <link rel="canonical" href="https://legal.linkedin.com/dpa"> <!----><!----> <!----> <!----> <!----> <link rel="manifest" href="/homepage-guest/manifest.json" crossorigin="use-credentials"> <link rel="icon" href="https://static.licdn.com/aero-v1/sc/h/al2o9zrvru7aqj8e1x2rzsrca"> <script> function getDfd() {let yFn,nFn;const p=new Promise(function(y, n){yFn=y;nFn=n;});p.resolve=yFn;p.reject=nFn;return p;} window.lazyloader = getDfd(); window.tracking = getDfd(); window.impressionTracking = getDfd(); window.ingraphTracking = getDfd(); window.appDetection = getDfd(); window.pemTracking = getDfd(); </script> <!----> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <title>LinkedIn Data Processing Agreement</title> <!----> <meta property="og:type" content="website"> <meta property="og:title" content="LinkedIn Data Processing Agreement"> <!----> <meta property="og:url" content="https://www.linkedin.com/legal/l/bd-dpa"> <meta property="og:image" content="https://media.licdn.com/dms/image/v2/C5608AQHtHOx13KD3DQ/croft-frontend-shrinkToFit1024/croft-frontend-shrinkToFit1024/0/1523055583050?e=2147483647&v=beta&t=l_9a_w5YujSRloGKINiwoU0dl90ZeMuyr7ATMSucpGo"> <meta name="twitter:title" content="LinkedIn Data Processing Agreement"> <meta name="twitter:site" content="@linkedin"> <!----> <!----> <meta name="robots" content="noarchive"> <meta name="linkedin:pageTag" content="/legal/l/bd-dpa"> <meta name="litmsProfileName" content="lithograph"> <!----> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="asset-url" id="artdeco/static/images/icons.svg" content="https://static.licdn.com/aero-v1/sc/h/6sz1e821vgereyxaakx87tt4z "> <link rel="stylesheet" href="https://static.licdn.com/aero-v1/sc/h/crjcj3vgj0tgpae2eu4u9y7eb"> <!----> <!----> </head> <body dir="ltr"> <!----> <a href="#lithograph-app" class="skip-link btn-md btn-primary absolute z-11 -top-[100vh] focus:top-0"> Skip to main content </a> <!----> <div class="ssr-ui-lib__header"> <header class="navbar global-alert-offset !bg-color-background-container " style="height: 64px"> <div class="navbar__wrapper "> <a aria-label="LinkedIn" class="nav-header__logo-link false" data-tracking-control-name="nav_header_logo" data-tracking-will-navigate href="https://www.linkedin.com?trk=nav_header_logo"> <icon class="nav-header__logo-icon " data-delayed-url="https://static.licdn.com/aero-v1/sc/h/8fkga714vy9b2wk5auqo5reeb"></icon> </a> <nav aria-label="Primary" class="nav-header__guest-nav "> <ul class="nav-header__link-list "> <li class="nav-header__link-item "> <a class="nav-header__link " data-tracking-client-ingraph data-tracking-control-name="nav_header_join" data-tracking-will-navigate href="https://www.linkedin.com/signup/cold-join?trk=nav_header_join" rel="nofollow">Join now</a> </li> <li class="nav-header__link-item "> <a class="nav-header__link-button " data-tracking-client-ingraph data-tracking-control-name="nav_header_signin" data-tracking-will-navigate href="https://www.linkedin.com/uas/login?session_redirect=&amp;trk=hb_signin&trk=nav_header_signin"> Sign in </a> </li> </ul> </nav> </div> </header> </div> <main role="main"> <div id="lithograph-app"> <section id="component-container" data-attach-collapse-behavior="true"> <div id class="component component-banner" data-component-type="banner"> <div class="banner banner--v3 banner--full-width banner--dark-background banner--center banner-height-desktop--default banner-height-tablet--default banner-height-mobile--default" data-banner> <div class="banner__image-container " aria-hidden="true"> <img class="banner__image image-pin--middle-center" alt srcset="https://media.licdn.com/dms/image/v2/C4D08AQEkearrGknDFA/croft-frontend-shrinkToFit480/croft-frontend-shrinkToFit480/0/1580331338990?e=2147483647&v=beta&t=c1UynySMPh4cuvz5rQRE3abeXwc34MRRyKxOKJXf3eI 480w,https://media.licdn.com/dms/image/v2/C4D08AQEkearrGknDFA/croft-frontend-shrinkToFit767/croft-frontend-shrinkToFit767/0/1580331338904?e=2147483647&v=beta&t=efIFKOqxH5NUrpgHI3Fw-cvwJcNQcDfMTY_ug2Trkp8 767w,https://media.licdn.com/dms/image/v2/C4D08AQEkearrGknDFA/croft-frontend-shrinkToFit1920/croft-frontend-shrinkToFit1920/0/1580331338951?e=2147483647&v=beta&t=TGSTIsMqOHH-g-VHbGOoocZICCE8jpunq5nWjFYdna0 1516w,https://media.licdn.com/dms/image/v2/C4D08AQEkearrGknDFA/croft-frontend-shrinkToFit600/croft-frontend-shrinkToFit600/0/1580331338867?e=2147483647&v=beta&t=QSOSjCDAix1QlRiilfzeVXm8saKXwOnovQB1o1E5de0 600w,https://media.licdn.com/dms/image/v2/C4D08AQEkearrGknDFA/croft-frontend-shrinkToFit1200/croft-frontend-shrinkToFit1200/0/1580331339073?e=2147483647&v=beta&t=HoRhie6MzW_WmE9c2Ty6B5lMT9fZrByuSVrRMDcbEQY 1200w,https://media.licdn.com/dms/image/v2/C4D08AQEkearrGknDFA/croft-frontend-shrinkToFit1024/croft-frontend-shrinkToFit1024/0/1580331339031?e=2147483647&v=beta&t=vhNPcoa6KaZXtFzdLiI1TLMTwmRBEF3_jxm4mMkvZkU 1024w," sizes="(max-width: 480px) 480px, (max-width: 767px) 767px, (max-width: 1024px) 1024px, 1920px" src="https://media.licdn.com/dms/image/v2/C4D08AQEkearrGknDFA/croft-frontend-shrinkToFit1024/croft-frontend-shrinkToFit1024/0/1580331339031?e=2147483647&v=beta&t=vhNPcoa6KaZXtFzdLiI1TLMTwmRBEF3_jxm4mMkvZkU"> <!----> </div> <div class="banner__headline-container"> <div class="banner__position"> <!----> <h1 class="banner__headline t-48"> LinkedIn Data Processing Agreement </h1> <!----><!----> <!----> <h1 class="banner__subheadline t-24"> For Business Development Agreements </h1> <!----><!----> <div class="banner__button-container"> <!----><!----> </div> </div> </div> </div> </div> <div id class="component component-articleHeadline" data-component-type="articleHeadline"> <div class="article-headline-container"> <!----> <h1 class="article-headline t-40"></h1> <div class="article-meta t-14 false"> <div class="article-meta__byline-container"> <p class="t-14 t-black--light" data-published-date="2021-10-28"> October 28, 2021 </p> </div> <!----> </div> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p>This Data Processing Agreement (the “DPA”) is incorporated into the agreement(s) entered into by you (“Partner”) and the LinkedIn company identified on the agreement(s) (“LinkedIn”), that govern data sharing between Partner and LinkedIn (but excluding customer agreements between Partner and LinkedIn that govern Partner’s purchase of LinkedIn products and services) (“Partner Agreement”). </p> <p>This DPA governs the processing of: (1) personal data that Partner uploads or otherwise provides to LinkedIn in connection with the Partner Agreement; and (2) personal data that LinkedIn (or its members) uploads or otherwise provides to Partner in connection with the Partner Agreement. </p> <p>Collectively, the DPA (including the SCCs, as defined below) and the Partner Agreement are referred to in this DPA as the “Agreement”. In the event of any conflict or inconsistency between any of the terms of the Agreement, the provisions of the following documents (in order of precedence) shall prevail: (a) the SCCs; (b) this DPA; and (c) the Partner Agreement. Except as specifically amended in this DPA, the Partner Agreement remains unchanged and in full force and effect. </p> <p><strong>RECITALS</strong></p> <p>WHEREAS, in connection with the Partner Agreement, LinkedIn and Partner may each be Data Processors of Joint Customer Personal Information (as defined below) and, in certain cases, transfer that Joint Customer Personal Information to the other party for processing at the direction of that Joint Customer;</p> <p>WHEREAS, in connection with the Partner Agreement, LinkedIn and Partner may each be Data Controllers of Personal Information (e.g., personal data of LinkedIn members) and, in certain cases, transfer that Personal Information to the other party for that other party to act as a Data Controller of that Personal Information;</p> <p>WHEREAS, in connection with the Partner Agreement, LinkedIn and Partner may each be Data Controllers of Personal Information and, in certain cases, transfer that Personal Information to the other party for that other party to provide certain services to the other party as a Data Processor (e.g., complete an API call); and</p> <p>WHEREAS, LinkedIn and Partner wish to memorialize their obligations to one another with respect to the foregoing.</p> <p>THEREFORE, by continuing to process or transfer Personal Information as set forth above, LinkedIn and Partner agree to be bound by this DPA. If Partner does not agree to comply with the terms of this DPA, it must immediately cease processing Personal Information or uploading or otherwise transferring Personal Information to LinkedIn in connection with the Partner Agreement.</p> <p><strong>1. DEFINITIONS</strong></p> <p>“CCPA” means the California Consumer Privacy Act of 2018 together with any subordinate legislation or regulations.</p> <p>“Data Protection Requirements” means the General Data Protection Regulation, and any applicable laws, regulations and other legal requirements in the European Union or domestic laws relating to: (i) privacy, data security, consumer protection, marketing, promotion, text messaging, email, and other communications; and (ii) the use, collection, retention, storage, security, disclosure, transfer, disposal, and other processing of any personal data. Requirements may include, but are not limited to Lei Geral De Proteção de Dados (Brazil’s General Data Protection Law) and the CCPA.</p> <p>“Designated Countries” means countries in the European Union, the European Economic Area, and Switzerland.</p> <p>“EU Personal Information” means Personal Information the sharing of which pursuant to this Agreement is regulated by the General Data Protection Regulation.</p> <p>“General Data Protection Regulation” means Regulation (EU) 2016/679 of the European Parliament and of the Council together with any subordinate legislation or regulation implementing the General Data Protection Regulation.</p> <p>“Joint Customer” means a customer of both Partner and LinkedIn.</p> <p>“Joint Customer Personal Information” means any Personal Information for which a Joint Customer acts as a data controller.</p> <p>“LinkedIn Personal Information” means any Personal Information for which LinkedIn acts as a data controller.</p> <p>“Partner Personal Information” means any Personal Information for which Partner acts a data controller.</p> <p>“Personal Information” means information about an individual that (a) can be used to identify, contact or locate a specific individual, including data that Partner provides to LinkedIn from services such as applicant tracking systems (ATSs) or customer-relationship management (CRM) services at the direction of a Joint Customer; (b) can be combined with other information that can be used to identify, contact or locate a specific individual; or (c) is defined as “personal data” or “personal information” by applicable laws or regulations relating to the collection, use, storage or disclosure of information about an identifiable individual. Personal Information includes any information defined as “Personal Information” or “Personal Data” under the Partner Agreement.</p> <p>“Personal Information Breach” means any accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Personal Information processed under the Agreement.</p> <p>“Process” and its cognates mean any operation or set of operations which is performed on Personal Information or on sets of Personal Information, whether or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure, or destruction.</p> <p>“SCCs” means the European Commission Standard Contractual Clauses entered into between the parties under the Agreement.</p> <p>“Subprocessor” means any entity which provides processing services to a Data Processor, as defined in Section 5.1, in furtherance of such Data Processor’s processing on behalf of a Data Controller.</p> <p>“Supervisory Authority” means an independent public authority which is established by a European Union member state pursuant to Article 51 of the General Data Protection Regulation; or (ii) the public authority governing data protection, which has supervisory authority and jurisdiction over a Data Controller or Data Processor. </p> <p><strong>2. COMPLIANCE WITH LAWS</strong></p> <p>The parties shall each comply with their respective obligations under all applicable Data Protection Requirements. Neither Party shall knowingly perform its obligations under this Agreement in such a way as to cause the other Party to breach any of its obligations under Data Protection Requirements.<strong> </strong></p> <p><strong>3. PROCESSOR-TO-PROCESSOR SCENARIOS</strong></p> <p>Each party, to the extent that it, along with the other party, acts as a Data Processor with respect to Personal Information, will (i) comply with the instructions and restrictions set forth in its agreement(s) with the Joint Customer; and (ii) reasonably cooperate with the other party to enable the exercise of data protection rights as set forth in the Data Protection Requirements. Partner and LinkedIn both acknowledge and agree that each is acting as a Data Processor for the Joint Customer and neither party is engaging the other as a Subprocessor.</p> <p><strong>4. CONTROLLER-TO-CONTROLLER SCENARIOS</strong></p> <p>Each party, to the extent that it, along with the other party, acts as a Data Controller with respect to Personal Information, will reasonably cooperate with the other party to enable the exercise of data protection rights as set forth in the Data Protection Requirements. The parties acknowledge and agree that each is acting independently as Data Controller with respect of Personal Information and the parties are not joint controllers as defined under applicable Data Protection Requirements.</p> <p><strong>5. CONTROLLER-TO-PROCESSOR SCENARIOS</strong></p> <p><strong>5.1 Relationship of the parties. </strong>The rights, responsibilities, and obligations of the parties with regard to Sections 6-9 and 10.3 of this DPA shall be as follows:</p> <p>5.1.1<strong> </strong> For data processing operations where LinkedIn processes Personal Information on Partner’s behalf and at Partner’s direction, the term “Data Processor” refers to LinkedIn, the term “Data Controller” refers to Partner, and the term “Personal Information” refers to Partner Personal Information.</p> <p>5.1.2 For data processing operations where Partner processes Personal Information on LinkedIn’s behalf and at LinkedIn’s direction, the term “Data Processor” refers to Partner, the term “Data Controller” refers to LinkedIn, and the term “Personal Information” refers to LinkedIn Personal Information.</p> <p><strong>5.2 Scope of Processing. </strong>In the context of the scenarios described in Section 5.1 above, each party agrees to process Personal Information only for the purposes set forth in the Agreement. For the avoidance of doubt, the categories of Personal Information processed and the categories of data subjects subject to this Agreement are described in Schedule A to this DPA.</p> <p><strong>6. DATA CONTROLLER OBLIGATIONS</strong></p> <p>The parties in their capacity as Data Controller agree to:</p> <p><strong>6.1</strong> provide instructions to Data Processor and determine the purposes and general means of Data Processor’s processing of Personal Information in accordance with the Agreement; and</p> <p><strong>6.2 </strong> comply with its protection, security and other obligations with respect to Personal Information prescribed by Data Protection Requirements for Data Controllers by: (a) ensuring it has provided data subjects with all necessary information in respect of its processing of Personal Information; (b) ensuring it obtains valid consent from data subjects where required; (c) establishing and maintaining a procedure for the exercise of the rights of the individuals whose Personal Information are processed on behalf of Data Controller; (d) processing only Personal Information and other data that has been lawfully and validly collected and ensuring that such Personal Information and other data will be relevant and proportionate to the respective uses; and (e) ensuring compliance with the provisions of this DPA by its personnel or by any third party accessing or using Personal Information on its behalf.</p> <p><strong>7. DATA PROCESSOR OBLIGATIONS</strong></p> <p><strong>7.1 Processing Requirements. </strong>The parties in their capacity as Data Processor agree to:</p> <p>a. process Personal Information (i) only for the purpose of providing, supporting and improving the Data Processor’s services (including to provide insights and other reporting), using appropriate technical and organizational security measures; and (ii) in compliance with the instructions received from Data Controller. Data Processor will not use or process the Personal Information for any other purpose. Data Processor will promptly inform Data Controller in writing if it cannot comply with the requirements under Sections 5-9 and 10.3 of this DPA, in which case Data Controller may terminate the Agreement or take any other reasonable action, including suspending data processing operations;</p> <p>b. inform Data Controller promptly if, in Data Processor’s opinion, an instruction from Data Controller violates applicable Data Protection Requirements;</p> <p>c. if Data Processor is collecting Personal Information from individuals on behalf of Data Controller, follow Data Controller’s instructions regarding such Personal Information collection (including with regard to the provision of notice and exercise of choice);</p> <p>d. take commercially reasonable steps to ensure that (i) persons employed by it and (ii) other persons engaged to perform on Data Processor’s behalf comply with the terms of the Agreement;</p> <p>e. ensure that its employees, authorized agents and any Subprocessors are required to comply with and acknowledge and respect the confidentiality of the Personal Information, including after the end of their respective employment, contract, or assignment;</p> <p>f. if it intends to engage Subprocessors to help it satisfy its obligations in accordance with this DPA or to delegate all or part of the processing activities to such Subprocessors, (i) exclusive of the list of Subprocessors provided by Data Processor to Data Controller (such list for LinkedIn is available online at <a rel="" href="https://www.linkedin.com/legal/l/customer-subprocessors" target="_self">https://www.linkedin.com/legal/l/customer-subprocessors</a>), obtain the prior written consent of Data Controller to such subcontracting, such consent to not be unreasonably withheld; (ii) remain liable to Data Controller for the Subprocessors’ acts and omissions with regard to data protection where such Subprocessors act on Data Processor’s instructions; and (iii) enter into contractual arrangements with such Subprocessors binding them to provide the same level of data protection and information security to that provided for herein;</p> <p>g. upon request, provide Data Controller with Data Processor’s privacy and security policies.</p> <p><strong>7.2 Notice to Data Controller.</strong> Data Processor will inform Data Controller if Data Processor becomes aware of:</p> <p>a. any non-compliance by Data Processor or its employees with Sections 5, 7-9, and 10.3 of this DPA or the Data Protection Requirements relating to the protection of Personal Information processed under this DPA;</p> <p>b. any legally binding request for disclosure of Personal Information by a law enforcement authority, unless Data Processor is otherwise forbidden by law to inform Data Controller, for example to preserve the confidentiality of an investigation by law enforcement authorities;</p> <p>c. any notice, inquiry or investigation by a Supervisory Authority with respect to Personal Information; or</p> <p>d. any complaint or request (in particular, requests for access to, rectification or blocking of Personal Information) received directly from data subjects of Data Controller. Data Processor will not respond substantively to any such request without Data Controller’s prior written authorization, except to acknowledge receipt of the request.</p> <p><strong>7.3 Assistance to Data Controller. </strong>Data Processor will provide reasonable assistance to Data Controller regarding:</p> <p>a. any requests from Data Controller data subjects in respect of access to or the rectification, erasure, restriction, portability, blocking, or deletion of Personal Information that Data Processor processes for Data Controller. In the event that a data subject sends such a request directly to Data Processor, Data Processor will promptly send such request to Data Controller;</p> <p>b. the investigation of Personal Information Breaches and the notification to the Supervisory Authority and Data Controller data subjects regarding such Personal Information Breaches; and</p> <p>c. where appropriate, the preparation of data protection impact assessments and, where necessary, carrying out consultations with any Supervisory Authority.</p> <p><strong>7.4 Required Processing.</strong> If Data Processor is required by Data Protection Requirements to process any Personal Information for a reason other than in connection with the Agreement, Data Processor will inform Data Controller of this requirement in advance of any processing, unless Data Processor is legally prohibited from informing Data Controller of such processing (e.g., as a result of secrecy requirements that may exist under applicable European Union member state laws).</p> <p><strong>7.5 Security. </strong>Data Processor will:</p> <p>a. maintain appropriate organizational and technical security measures (including with respect to personnel, facilities, hardware and software, storage and networks, access controls, monitoring and logging, vulnerability and breach detection, incident response, and encryption of Personal Information while in transit and at rest) to protect against unauthorized or accidental access, loss, alteration, disclosure, or destruction of Personal Information;</p> <p>b. be responsible for the sufficiency of the security, privacy, and confidentiality safeguards of all Data Processor personnel with respect to Personal Information and liable for any failure by such Data Processor personnel to meet the terms of this Agreement;</p> <p>c. take appropriate steps to confirm that all Data Processor personnel are protecting the security, privacy and confidentiality of Personal Information consistent with the requirements of this DPA; and</p> <p>d. notify Data Controller of any Personal Information Breach by Data Processor, its Subprocessors, or any other third parties acting on Data Processor’s behalf without undue delay and in any event within 48 hours of becoming aware of a Personal Information Breach.</p> <p><strong>8. AUDIT, CERTIFICATION</strong></p> <p><strong>8.1 Supervisory Authority Audit.</strong> If a Supervisory Authority requires an audit of the data processing facilities from which Data Processor processes Personal Information in order to ascertain or monitor compliance with Data Protection Requirements, Data Processor will cooperate with such audit. Data Controller will reimburse Data Processor for its reasonable expenses incurred to cooperate with the audit. </p> <p><strong>8.2 Data Processor Certification. </strong>Data Processor must, upon Data Controller’s request (not to exceed one request per calendar year) by email (where LinkedIn is Data Processor, such emails shall be sent to <a rel="" href="https://legal.linkedin.com/DPO@linkedin.com" target="_blank">DPO@linkedin.com</a>; where Partner is Data Processor, Partner shall establish and provide to LinkedIn upon request a single point of contact for email correspondence regarding data protection), certify compliance with Sections 5, 7-9, and 10.3 of this DPA in writing. Data Processor will, upon Data Controller’s request, provide to Data Controller each year an opinion or Service Organization Control report provided by an accredited, third-party audit firm under the Statement on Standards for Attestation Engagements (SSAE) No. 16 (“SSAE 16”) (Reporting on Controls at a Service Organization) or the International Standard on Assurance Engagements (ISAE) 3402 (“ISAE 3402”) (Assurance Reports on Controls at a Service Organization) standards applicable to the services under the Agreement.</p> <p><strong>9. DATA RETURN AND DELETION</strong></p> <p>The parties agree that on the termination of the data processing services or upon Data Controller’s reasonable request, Data Processor shall and shall take reasonable measures to cause any Subprocessors to, at the choice of Data Controller, return all the Personal Information and copies of such data to Data Controller or securely destroy them and demonstrate to the satisfaction of Data Controller that it has taken such measures, unless Data Protection Requirements prevent Data Processor from returning or destroying all or part of the Personal Information disclosed. In such case, Data Processor agrees to preserve the confidentiality of the Personal Information retained by it and that it will only actively process such Personal Information after such date in order to comply with applicable laws. </p> <p><strong>10. DATA TRANSFERS. </strong></p> <p>With respect to a transfer of data between the parties that results in a transfer of EU Personal Information to a jurisdiction other than a jurisdiction in the European Union, the European Economic Area, or the European Commission-approved countries providing ‘adequate’ data protection, each party agrees as follows:</p> <p>10.1 <strong>Processor-to-Processor</strong>. Where both parties act as Data Processor with respect to Personal Information, the parties agree that Module 3 of the SCC’s, which applies to Processor-to-Processor relationships will apply and that the following terms apply: (i) the Data Protection Commission of Ireland shall be the Competent Supervisory Authority pursuant to Clause 13 of the SCCs; (ii) these terms shall be governed by the law of one of the European Union member states, provided such law allows for third-party beneficiary rights. The Parties agree that this shall be the law of Ireland pursuant to Clause 17 of the SCCs; (iii) any dispute arising from the SCCs shall be resolved by the courts of Ireland pursuant to Clause 18 of the SCCs; (iv) Schedule A to this DPA shall apply as Annex I of the Processor-to-Processor SCCs; (v) Schedule B to this DPA shall apply as Annex II of the Processor-to-Processor SCCs; and (vi) Schedule C to this DPA shall apply as Annex III of the Processor- to-Processor SCCs.</p> <p>10.2<strong> Controller-to-Controller</strong>. Where both parties act as Data Controller with respect to Personal Information, the parties agree that Module 1 of the SCC’s, which applies to Controller-to-Controller relationships will apply and that the following terms apply: (i) the Data Protection Commission of Ireland shall be the Competent Supervisory Authority pursuant to Clause 13 of the SCCs; (ii) these terms shall be governed by the law of one of the European Union member states, provided such law allows for third-party beneficiary rights. The Parties agree that this shall be the law of Ireland pursuant to Clause 17 of the SCCs; (iii) Any dispute arising from the SCCs shall be resolved by the courts of Ireland pursuant to Clause 18 of the SCCs; (iv) Schedule A to this DPA shall apply as Annex I of the Controller-to-Controller SCCs; and (v) Schedule B to this DPA shall apply as Annex II of the Controller-to-Controller SCCs.</p> <p>10.3 <strong>Controller-to-Processor</strong>. Where one party acts as a Data Controller and the other party acts as such party’s Data Processor with respect to Personal Information, the parties agree that Module 2 of the SCC’s, which applies to Controller-to-Processor relationships will apply and that the following terms apply: (i) the Data Protection Commission of Ireland shall be the Competent Supervisory Authority pursuant to Clause 13 of the SCCs (ii) these terms shall be governed by the law of one of the European Union member states, provided such law allows for third-party beneficiary rights. The Parties agree that this shall be the law of Ireland pursuant to Clause 17 of the SCCs; (iii) Any dispute arising from the SCCs shall be resolved by the courts of Ireland pursuant to Clause 18 of the SCCs; (iv) Schedule A to this DPA shall apply as Annex I of the Controller-to-Processor SCCs; (v) Schedule B to this DPA shall apply as Annex II of the Controller-to-Processor SCCs; and (vi) Schedule C to this DPA shall apply as Annex III of the Controller-to-Processor SCCs.<strong> </strong></p> <p><strong>11. TERM</strong></p> <p>This DPA shall remain in effect as long as either party carries out Personal Information processing operations on the Personal Information uploaded or otherwise provided by the other party pursuant to and in accordance with the Partner Agreement. </p> <p><strong>12. GOVERNING LAW, JURISDICTION, AND VENUE</strong></p> <p>Notwithstanding anything in the Agreement to the contrary, this DPA shall be governed by the laws of Ireland, and any action or proceeding related to this DPA (including those arising from non-contractual disputes or claims) will be brought in Dublin, Ireland.</p> </div> </div> <div id class="component component-articleHeadline" data-component-type="articleHeadline"> <div class="article-headline-container"> <!----> <h1 class="article-headline t-40" data-article-title=" "> </h1> <div class="article-meta t-14 article-meta__hairline"> <div class="article-meta__byline-container"> <!----> </div> <!----> </div> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <h2><strong>SCHEDULE A</strong></h2> <h2><strong>ANNEX I</strong></h2> <p><br> </p> <p><strong>A. LIST OF PARTIES</strong></p> <p><strong>A.1 Processor-to-Processor</strong></p> <p>Notes:</p> <ul> <li>If LinkedIn is sending EU Personal Information to the counterparty, LinkedIn is the Data Exporter and the counterparty is the Data Importer.</li> <li>If LinkedIn is receiving EU Personal Information from the counterparty, LinkedIn is the Data Importer and the counterparty is the Data Exporter.</li> <li>If EU Personal Information is transferred both from LinkedIn to the counterparty and from the counterparty to LinkedIn for processing on behalf of a mutual customer of LinkedIn and the counterparty, then a LinkedIn signatory to the Partner Agreement is both a Data Importer and Data Exporter and the counterparty is both a Data Importer and Data Exporter.</li> </ul> <p><strong><em>When LinkedIn is the Data Exporter:</em></strong></p> </div> </div> <div id class="component component-htmlTable" data-component-type="htmlTable"> <div class="html-table__container" data-html-table> <span id="litho-html-table-5-summary" class="screen-reader table__summary-text" aria-hidden="true" data-table-summary="true"> Categories of data subjects whose personal data is transferred </span> <table> <tbody> <tr> <td> <p><strong>Name:</strong></p> </td> <td>LinkedIn Ireland Unlimited Company</td> </tr> <tr> <td> <p><strong>Address:</strong></p> </td> <td> <p>Wilton Plaza, Wilton Place, Dublin 2 IRELAND</p> </td> </tr> <tr> <td><strong>Contact person's name, position, and contact details:</strong></td> <td> <p>Conor Bowe</p> <p>Data Protection Officer</p> <p><a rel="NOOPENER NOFOLLOW" href="mailto:DPO@linkedin.com" target="_blank">DPO@linkedin.com</a></p> <p> </p> </td> </tr> <tr> <td><strong>Activities relevant to the data transferred under these Clauses:</strong></td> <td> <p>A provider of professional networking and online talent, sales, marketing, employee engagement and learning services to members, guests and customers who are data subjects from the Designated Countries (as defined in the LinkedIn Data Processing Agreement for Business Development Agreements)</p> </td> </tr> <tr> <td><strong>Role:</strong></td> <td> <p>Processor</p> </td> </tr> </tbody> </table> </div> </div> <div id class="component component-articleHeadline" data-component-type="articleHeadline"> <div class="article-headline-container"> <!----> <h1 class="article-headline t-40"></h1> <div class="article-meta t-14 article-meta__hairline"> <div class="article-meta__byline-container"> <!----> </div> <!----> </div> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p><strong><em>When the Counterparty is the Data Importer:</em></strong></p> </div> </div> <div id class="component component-htmlTable" data-component-type="htmlTable"> <div class="html-table__container" data-html-table> <span id="litho-html-table-8-summary" class="screen-reader table__summary-text" aria-hidden="true" data-table-summary="true"> Categories of data subjects whose personal data is transferred </span> <table> <tbody> <tr> <td> <p><strong>Name:</strong></p> </td> <td>Signatory to the Partner Agreement (as defined in the LinkedIn Data Processing Agreement for Business Development Agreements)</td> </tr> <tr> <td> <p><strong>Address:</strong></p> </td> <td> <p>As set forth in the Partner Agreement, or associated with the applicable developer account</p> </td> </tr> <tr> <td><strong>Contact person's name, position, and contact details:</strong></td> <td> <p>As set forth in the Partner Agreement, or associated with the applicable developer account</p> <p> </p> </td> </tr> <tr> <td><strong>Activities relevant to the data transferred under these Clauses:</strong></td> <td> <p>As set forth in the Partner Agreement</p> </td> </tr> <tr> <td><strong>Role:</strong></td> <td> <p>Processor</p> </td> </tr> </tbody> </table> </div> </div> <div id class="component component-articleHeadline" data-component-type="articleHeadline"> <div class="article-headline-container"> <!----> <h1 class="article-headline t-40"></h1> <div class="article-meta t-14 article-meta__hairline"> <div class="article-meta__byline-container"> <!----> </div> <!----> </div> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p><strong><em>When the Counterparty is the Data Exporter:</em></strong></p> </div> </div> <div id class="component component-htmlTable" data-component-type="htmlTable"> <div class="html-table__container" data-html-table> <span id="litho-html-table-11-summary" class="screen-reader table__summary-text" aria-hidden="true" data-table-summary="true"> Categories of data subjects whose personal data is transferred </span> <table> <tbody> <tr> <td> <p><strong>Name:</strong></p> </td> <td>Signatory to the Partner Agreement</td> </tr> <tr> <td> <p><strong>Address:</strong></p> </td> <td> <p>As set forth in the Partner Agreement, or associated with the applicable developer account</p> </td> </tr> <tr> <td><strong>Contact person's name, position, and contact details:</strong></td> <td> <p>As set forth in the Partner Agreement, or associated with the applicable developer account</p> <p> </p> </td> </tr> <tr> <td><strong>Activities relevant to the data transferred under these Clauses:</strong></td> <td> <p>As set forth in the Partner Agreement</p> </td> </tr> <tr> <td><strong>Role:</strong></td> <td> <p>Processor</p> </td> </tr> </tbody> </table> </div> </div> <div id class="component component-articleHeadline" data-component-type="articleHeadline"> <div class="article-headline-container"> <!----> <h1 class="article-headline t-40"></h1> <div class="article-meta t-14 article-meta__hairline"> <div class="article-meta__byline-container"> <!----> </div> <!----> </div> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p><strong><em>When LinkedIn is the Data Importer:</em></strong></p> </div> </div> <div id class="component component-htmlTable" data-component-type="htmlTable"> <div class="html-table__container" data-html-table> <span id="litho-html-table-14-summary" class="screen-reader table__summary-text" aria-hidden="true" data-table-summary="true"> Categories of data subjects whose personal data is transferred </span> <table> <tbody> <tr> <td> <p><strong>Name:</strong></p> </td> <td>LinkedIn Corporation</td> </tr> <tr> <td> <p><strong>Address:</strong></p> </td> <td> <p>1000 West Maude Avenue, Sunnyvale, California, 94085 USA</p> </td> </tr> <tr> <td><strong>Contact person's name, position, and contact details:</strong></td> <td> <p>Kalinda Raina</p> <p>Chief Privacy Officer</p> <p>Tel.: +1 650-687-3600</p> <p>email: <a rel="NOOPENER NOFOLLOW" href="mailto:LegalTeam@linkedin.com" target="_blank">LegalTeam@linkedin.com</a></p> <p> </p> </td> </tr> <tr> <td><strong>Activities relevant to the data transferred under these Clauses:</strong></td> <td> <p>As set forth in the Partner Agreement</p> </td> </tr> <tr> <td><strong>Role:</strong></td> <td> <p>Processor</p> </td> </tr> </tbody> </table> </div> </div> <div id class="component component-articleHeadline" data-component-type="articleHeadline"> <div class="article-headline-container"> <!----> <h1 class="article-headline t-40"></h1> <div class="article-meta t-14 article-meta__hairline"> <div class="article-meta__byline-container"> <!----> </div> <!----> </div> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p><strong>A.2. Controller-to-Controller</strong></p> <p><strong><em>Data exporter(s):</em></strong></p> </div> </div> <div id class="component component-htmlTable" data-component-type="htmlTable"> <div class="html-table__container" data-html-table> <span id="litho-html-table-17-summary" class="screen-reader table__summary-text" aria-hidden="true" data-table-summary="true"> Categories of data subjects whose personal data is transferred </span> <table> <tbody> <tr> <td> <p><strong>Name:</strong></p> </td> <td>LinkedIn Ireland Unlimited Company</td> </tr> <tr> <td> <p><strong>Address:</strong></p> </td> <td> <p>Wilton Plaza, Wilton Place, Dublin 2 IRELAND</p> </td> </tr> <tr> <td><strong>Contact person's name, position, and contact details:</strong></td> <td> <p>Conor Bowe</p> <p>Data Protection Officer</p> <p><a rel="NOOPENER NOFOLLOW" href="mailto:DPO@linkedin.com" target="_blank">DPO@linkedin.com</a></p> <p> </p> </td> </tr> <tr> <td><strong>Activities relevant to the data transferred under these Clauses:</strong></td> <td> <p>A provider of professional networking and online talent, sales, marketing, employee engagement and learning services to members, guests and customers who are data subjects from the Designated Countries</p> </td> </tr> <tr> <td><strong>Role:</strong></td> <td> <p>Controller</p> </td> </tr> </tbody> </table> </div> </div> <div id class="component component-articleHeadline" data-component-type="articleHeadline"> <div class="article-headline-container"> <!----> <h1 class="article-headline t-40"></h1> <div class="article-meta t-14 article-meta__hairline"> <div class="article-meta__byline-container"> <!----> </div> <!----> </div> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p><strong><em>Data Importer:</em></strong></p> </div> </div> <div id class="component component-htmlTable" data-component-type="htmlTable"> <div class="html-table__container" data-html-table> <span id="litho-html-table-20-summary" class="screen-reader table__summary-text" aria-hidden="true" data-table-summary="true"> Categories of data subjects whose personal data is transferred </span> <table> <tbody> <tr> <td> <p><strong>Name:</strong></p> </td> <td>Signatory to the Partner Agreement</td> </tr> <tr> <td> <p><strong>Address:</strong></p> </td> <td> <p>As set forth in the Partner Agreement, or associated with the applicable developer account</p> </td> </tr> <tr> <td><strong>Contact person's name, position, and contact details:</strong></td> <td> <p>As set forth in the Partner Agreement, or associated with the applicable developer account</p> <p> </p> </td> </tr> <tr> <td><strong>Activities relevant to the data transferred under these Clauses:</strong></td> <td> <p>As set forth in the Partner Agreement</p> </td> </tr> <tr> <td><strong>Role:</strong></td> <td> <p>Controller</p> </td> </tr> </tbody> </table> </div> </div> <div id class="component component-articleHeadline" data-component-type="articleHeadline"> <div class="article-headline-container"> <!----> <h1 class="article-headline t-40"></h1> <div class="article-meta t-14 article-meta__hairline"> <div class="article-meta__byline-container"> <!----> </div> <!----> </div> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p><strong>A.3. Controller-to-Processor</strong></p> <p>Notes:</p> <ul> <li>If LinkedIn, as Data Controller, is sending EU Personal Information to the counterparty, LinkedIn is the Data Exporter and the counterparty is the Data Importer.</li> <li>If LinkedIn, as Data Processor, is receiving EU Personal Information from the counterparty, LinkedIn is the Data Importer and the counterparty is the Data Exporter.<strong> </strong></li> </ul> <p><strong><em>When LinkedIn is the Data Exporter:</em></strong></p> </div> </div> <div id class="component component-htmlTable" data-component-type="htmlTable"> <div class="html-table__container" data-html-table> <span id="litho-html-table-23-summary" class="screen-reader table__summary-text" aria-hidden="true" data-table-summary="true"> Categories of data subjects whose personal data is transferred </span> <table> <tbody> <tr> <td> <p><strong>Name:</strong></p> </td> <td>LinkedIn Ireland Unlimited Company</td> </tr> <tr> <td> <p><strong>Address:</strong></p> </td> <td> <p>Wilton Plaza, Wilton Place, Dublin 2 IRELAND</p> </td> </tr> <tr> <td><strong>Contact person's name, position, and contact details:</strong></td> <td> <p>Conor Bowe</p> <p>Data Protection Officer</p> <p><a rel="NOOPENER NOFOLLOW" href="mailto:DPO@linkedin.com" target="_blank">DPO@linkedin.com</a></p> <p> </p> </td> </tr> <tr> <td><strong>Activities relevant to the data transferred under these Clauses:</strong></td> <td> <p>A provider of professional networking and online talent, sales, marketing, employee engagement and learning services to members, guests and customers who are data subjects from the Designated Countries</p> </td> </tr> <tr> <td><strong>Role:</strong></td> <td> <p>Controller</p> </td> </tr> </tbody> </table> </div> </div> <div id class="component component-articleHeadline" data-component-type="articleHeadline"> <div class="article-headline-container"> <!----> <h1 class="article-headline t-40"></h1> <div class="article-meta t-14 article-meta__hairline"> <div class="article-meta__byline-container"> <!----> </div> <!----> </div> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p><strong><em>When the Counterparty is the Data Importer:</em></strong></p> </div> </div> <div id class="component component-htmlTable" data-component-type="htmlTable"> <div class="html-table__container" data-html-table> <span id="litho-html-table-26-summary" class="screen-reader table__summary-text" aria-hidden="true" data-table-summary="true"> Categories of data subjects whose personal data is transferred </span> <table> <tbody> <tr> <td> <p><strong>Name:</strong></p> </td> <td>Signatory to the Partner Agreement</td> </tr> <tr> <td> <p><strong>Address:</strong></p> </td> <td> <p>As set forth in the Partner Agreement, or associated with the applicable developer account</p> </td> </tr> <tr> <td><strong>Contact person's name, position, and contact details:</strong></td> <td> <p>As set forth in the Partner Agreement, or associated with the applicable developer account</p> <p> </p> </td> </tr> <tr> <td><strong>Activities relevant to the data transferred under these Clauses:</strong></td> <td> <p>As set forth in the Partner Agreement</p> </td> </tr> <tr> <td><strong>Role:</strong></td> <td> <p>Processor</p> </td> </tr> </tbody> </table> </div> </div> <div id class="component component-articleHeadline" data-component-type="articleHeadline"> <div class="article-headline-container"> <!----> <h1 class="article-headline t-40"></h1> <div class="article-meta t-14 article-meta__hairline"> <div class="article-meta__byline-container"> <!----> </div> <!----> </div> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p><strong><em>When the Counterparty is the Data Exporter:</em></strong></p> </div> </div> <div id class="component component-htmlTable" data-component-type="htmlTable"> <div class="html-table__container" data-html-table> <span id="litho-html-table-29-summary" class="screen-reader table__summary-text" aria-hidden="true" data-table-summary="true"> Categories of data subjects whose personal data is transferred </span> <table> <tbody> <tr> <td> <p><strong>Name:</strong></p> </td> <td>Signatory to the Partner Agreement</td> </tr> <tr> <td> <p><strong>Address:</strong></p> </td> <td> <p>As set forth in the Partner Agreement, or associated with the applicable developer account</p> </td> </tr> <tr> <td><strong>Contact person's name, position, and contact details:</strong></td> <td> <p>As set forth in the Partner Agreement, or associated with the applicable developer account</p> <p> </p> </td> </tr> <tr> <td><strong>Activities relevant to the data transferred under these Clauses:</strong></td> <td> <p>As set forth in the Partner Agreement</p> </td> </tr> <tr> <td><strong>Role:</strong></td> <td> <p>Controller</p> </td> </tr> </tbody> </table> </div> </div> <div id class="component component-articleHeadline" data-component-type="articleHeadline"> <div class="article-headline-container"> <!----> <h1 class="article-headline t-40"></h1> <div class="article-meta t-14 article-meta__hairline"> <div class="article-meta__byline-container"> <!----> </div> <!----> </div> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p><strong><em>When LinkedIn is the Data Importer:</em></strong></p> </div> </div> <div id class="component component-htmlTable" data-component-type="htmlTable"> <div class="html-table__container" data-html-table> <span id="litho-html-table-32-summary" class="screen-reader table__summary-text" aria-hidden="true" data-table-summary="true"> Categories of data subjects whose personal data is transferred </span> <table> <tbody> <tr> <td> <p><strong>Name:</strong></p> </td> <td>LinkedIn Corporation</td> </tr> <tr> <td> <p><strong>Address:</strong></p> </td> <td> <p>1000 West Maude Avenue, Sunnyvale, California, 94085 USA</p> </td> </tr> <tr> <td><strong>Contact person's name, position, and contact details:</strong></td> <td> <p>Kalinda Raina</p> <p>Chief Privacy Officer</p> <p>Tel.: +1 650-687-3600</p> <p>email: <a rel="NOOPENER NOFOLLOW" href="mailto:LegalTeam@linkedin.com" target="_blank">LegalTeam@linkedin.com</a></p> <p> </p> </td> </tr> <tr> <td><strong>Activities relevant to the data transferred under these Clauses:</strong></td> <td> <p>A provider of professional networking and online talent, sales, marketing, employee engagement and learning services to members, guests and customers who are data subjects from the Designated Countries</p> </td> </tr> <tr> <td><strong>Role:</strong></td> <td> <p>Processor</p> </td> </tr> </tbody> </table> </div> </div> <div id class="component component-articleHeadline" data-component-type="articleHeadline"> <div class="article-headline-container"> <!----> <h1 class="article-headline t-40"></h1> <div class="article-meta t-14 article-meta__hairline"> <div class="article-meta__byline-container"> <!----> </div> <!----> </div> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p><strong>B. DESCRIPTION OF TRANSFER</strong></p> </div> </div> <div id class="component component-htmlTable" data-component-type="htmlTable"> <div class="html-table__container" data-html-table> <span id="litho-html-table-35-summary" class="screen-reader table__summary-text" aria-hidden="true" data-table-summary="true"> Categories of data subjects whose personal data is transferred </span> <table> <tbody> <tr> <td> <p><strong>Categories of Data Subjects</strong></p> <p>The personal data transferred concern the following categories of data subjects </p> </td> <td> <p>Depending on the agreement between the data importer and data exporter:</p> <p> </p> <p>- LinkedIn members;</p> <p> </p> <p>- Potential and actual candidates and employees of the data exporter;</p> <p> </p> <p>- Sales and marketing leads of the data exporter, and</p> <p> </p> <p>- Third parties that have, or may have, a commercial relationship with the data exporter (e.g. advertisers, customers, corporate subscribers, contractors, and individual product users).</p> </td> </tr> <tr> <td> <p><strong>Categories of Personal Information Transferred</strong></p> <p>The personal data transferred concern the following categories of data<strong> </strong></p> </td> <td> <p>The data transferred is the personal data provided by the data exporter to the data importer in connection with the Partner Agreement. Such personal data may include first name, last name, email address, contact information, system and network data (e.g., IP address, cookies / beacons / browser ID, device ID / advertising ID), education, work history, and other information provided in LinkedIn member profiles, resumes, CRM data concerning sales leads and customer lists, any notes provided by the data exporter regarding the foregoing, and other activities of LinkedIn members taken on the LinkedIn platform.</p> </td> </tr> <tr> <td> <p><strong>Sensitive Data Transferred</strong></p> <p>The personal data transferred may concern the following categories of data</p> </td> <td> <p>None.</p> <p> </p> </td> </tr> <tr> <td> <p><strong>Restrictions or Safeguards for Sensitive Data</strong></p> <p>The applied restrictions or safegaurds taken with respect to any sensitive data transferred</p> </td> <td> <p>None applicable.</p> </td> </tr> <tr> <td><strong>Subject Matter of Processing</strong></td> <td> <p>The relationship of the parties as contemplated by the Partner Agreement.</p> </td> </tr> <tr> <td><strong>Nature and Purpose of Processing </strong></td> <td> <p>The transfer is intended to enable the relationship of the parties contemplated by the Partner Agreement.</p> </td> </tr> <tr> <td><strong>Frequency of Processing</strong></td> <td> <p>Continuous basis.</p> </td> </tr> <tr> <td><strong>Duration of Processing</strong></td> <td> <p>As set forth in the Partner Agreement.</p> </td> </tr> <tr> <td> <p><strong>Retention Period</strong></p> <p>The period for which the personal data will be retained, or the criteria used to determine that period</p> </td> <td> <p>The personal data transferred between the parties may only be retained for the period of time permitted under the Partner Agreement.</p> </td> </tr> </tbody> </table> </div> </div> <div id class="component component-articleHeadline" data-component-type="articleHeadline"> <div class="article-headline-container"> <!----> <h1 class="article-headline t-40"></h1> <div class="article-meta t-14 article-meta__hairline"> <div class="article-meta__byline-container"> <!----> </div> <!----> </div> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p>For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing:</p> <p>LinkedIn uses sub-processors to support its infrastructure environment, local and international providers of telecommunications and networking services, and legal entities engaged in data storage and content delivery material. Personal data processed by sub-processors is processed for the purposes and duration of the relevant underlying Partner Agreement. For more information, see Annex III, where applicable.</p> <p><strong>C. COMPETENT SUPERVISORY AUTHORITY</strong></p> <p>See Section 10 of the BD DPA.</p> </div> </div> <div id class="component component-articleHeadline" data-component-type="articleHeadline"> <div class="article-headline-container"> <!----> <h1 class="article-headline t-40"></h1> <div class="article-meta t-14 article-meta__hairline"> <div class="article-meta__byline-container"> <!----> </div> <!----> </div> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p><strong>SCHEDULE B</strong></p> <p><strong> </strong></p> <p><strong>Annex II</strong></p> <p><strong> </strong></p> <p><strong>TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA</strong></p> <p> </p> <p><strong>A. Where LinkedIn is the Data Importer the following Annex II applies:</strong> </p> <p><strong>1. General Security Measures</strong> </p> <p>Data Importer will comply with industry standard security measures (including with respect to personnel, facilities, hardware and software, storage and networks, access controls, monitoring and logging, vulnerability and breach detection, and incident response measures necessary to protect against unauthorized or accidental access, loss, alteration, disclosure or destruction of Data Exporter's Personal Information provided by Data Exporter to Data Importer), as well as with all applicable data privacy and security laws, regulations and standards. </p> <p><strong>2. Contact Information</strong> </p> <p>Data Importer's security team can be reached at security@linkedin.com for any security issues or questions related to the product.</p> <p><strong>3. Compliance</strong> </p> <p>Data Importer complies with the standards and practices set forth at the following web address: <a rel="" href="https://security.linkedin.com/trust-and-compliance" target="_self">https://security.linkedin.com/trust-and-compliance</a>. Data Exporter must contact LinkedIn for any additional information on the security certifications listed at the web address.</p> <p><strong>4. Information Security Program</strong> </p> <p>The objective of the Data Importer’s Information Security Program is to maintain the confidentiality, integrity, and availability of its computer and data communication systems while meeting necessary legislative, industry, and contractual requirements. Data Importer shall establish, implement, and maintain an information security program that includes technical and organizational security and physical measures, as well as policies and procedures to protect Data Exporter data processed by Data Importer against accidental loss; destruction or alteration; unauthorized disclosure or access; or unlawful destruction. </p> <p><strong>4.1 Secure Software Development</strong> </p> <p>Data Importer shall maintain policies and procedures to ensure that system, device, application, and infrastructure development is performed in a secure manner. This includes review and test of all Data Importer applications, products, and services for common security vulnerabilities and defects, employing defense-in-depth strategy through the use of multiple layers of security boundaries and technologies, periodic pen testing and security assessment of these services, defining baseline configurations, and requirements for patching of third party systems. </p> <p><strong>4.2 Human Resources Security</strong> </p> <p>Data Importer shall maintain a policy which defines requirements around enforcing security measures as they relate to employment status changes. This includes background checks, acknowledgement and adherence to Data Importer's security policies, and onboarding and termination for employees and third parties. </p> <p><strong>4.3 Data Classification & Protection</strong> </p> <p>Data Importer shall maintain policies and procedures for data classification and protection, along with requirements for classification of data containing Personal Information in consideration of applicable laws, regulations, and contractual obligations. Data Importer shall also maintain requirements on data encryption, rules for transmission of data, and requirements for removable media, along with requirements on how access to these data should be governed. </p> <p><strong>4.4 Network Security</strong> </p> <p>Data Importer shall maintain policies and procedures around the network infrastructure used to process Data Exporter data, establish and enforce safe network practices, and define service level agreements with internal and external network services. </p> <p><strong>4.5 Physical and Environmental Security</strong> </p> <p>Data Importer shall maintain policies and procedures for physical and environmental security, define requirements to protect areas that contain sensitive information, and ensure that critical information services be protected from interception, interference, or damage. </p> <p><strong>4.6 Business Continuity and Disaster Recovery</strong> </p> <p>Data Importer shall maintain policies and procedures to ensure that Data Importer may continue to perform business critical functions in the face of an extraordinary event. This includes data center resiliency and disaster recovery procedures for business critical data and processing functions. </p> <p><strong>5. Access Control</strong> </p> <p>Data Importer shall maintain access control measures designed to limit access to Data Importer's facilities, applications, systems, network devices, and operating systems to a limited number of personnel who have a business need for such access. Data Importer shall ensure such access is removed when no longer required and shall conduct access reviews periodically. </p> <p><strong>6. Risk Assessments</strong> </p> <p>Data Importer has a documented risk management procedure and Secure Software Development LifeCycle process. Data Importer performs risk assessments of its products and infrastructure on a regular basis, including review of the data classification policies and targeted reviews of highly sensitive data flows. </p> <p>Data Importer performs application and infrastructure level testing for every new product that is launched as well as periodic reassessments of its network, as well as feature changes. Data Importer leverages access control, and peer code review which would ensure that viruses are not introduced in the code and to detect such abuse. Data Importer uses a combination of manual penetration testing and automated tools. </p> <p><strong>7. Third-Party Risk Assessments</strong> </p> <p>Data Importer conducts security due diligence on third-party service providers to assess and monitor risk. This assessment includes a review of scope of confidential information and personal data transferred to or processed by the service provider and the purpose of the work. Data Importer will also conduct a risk assessment which may include the service provider’s organization and technical security measures, the sensitivity of any information processed by the service provider, storage limitations, and data deletion procedures and timelines. </p> <p><strong>8. Supplementary Measures</strong> </p> <p>In addition to the general security measures set out above, the Data Importer has implemented the following supplementary technical and organisational measures: </p> <ul> <li>Partner Personal Information is transferred across public networks to the Data Importer’s data centres in the United States and is stored on secured servers behind firewall. </li> <li>Data Importer encrypts all Partner Personal Information in transit across public networks depending on the Data Exporter’s ability to support encryption. Certain highly confidential data (including but not limited to passwords, authentication tokens, salary and payment information) is also encrypted at rest. LinkedIn will only use industry tested and accepted standards for cryptographic algorithms. </li> <li>Data Importer’s data is replicated across all its data centres in a secure environment. </li> <li>Data Importer employs app logic with appropriate authorization to protect tenant data. Access requests are reviewed to ensure only appropriate access is granted. Server and database access logs are retained for auditing purposes. </li> <li>Data Importer deploys industry standard security measures including ISO 27001 & ISO 27018 and PCI DDS to keep the data of our members and customers safe. </li> <li>Data Importers’ employees and contractors are trained in relation to specific technical and organisational security measures. </li> <li>Servers are monitored by both industry standard and proprietary network monitoring tools to prevent any potential security breaches. </li> <li>Corporate systems and databases are password protected. </li> <li>VPN and direct LinkedIn network access are limited to company issued or approved devices. </li> <li>Dual factor authentication is in operation for VPN access. </li> <li>Customer and member passwords are hashed and salted and stored in a separate, secure database. </li> <li>Keys to credit card database are rotated regularly. </li> <li>Active and automated monitoring of critical access logs and anomaly detection.<strong> </strong></li> </ul> <p><strong>B. Where LinkedIn is the Data Exporter the following Annex II applies:</strong></p> <p><strong>1. </strong>Data Importer will comply with industry standard security measures (including with respect to personnel, facilities, hardware and software, storage and networks, access controls, monitoring and logging, vulnerability and breach detection, and incident response measures necessary to protect against unauthorized or accidental access, loss, alteration, disclosure or destruction of Data Exporter's Personal Information provided by Data Exporter to Data Importer), as well as with all applicable data privacy and security laws, regulations and standards. </p> <p><strong>2. </strong>Data Importers’ employees and contractors must be trained in relation to specific and appropriate technical and organizational security measures.</p> <p><strong>3. </strong>Personal data is to be stored on secured servers behind firewall.</p> <p><strong>4. </strong>Data Importer’s servers are to be monitored by industry standard and, as appropriate, proprietary network monitoring tools to prevent any potential security breaches.</p> <p><strong>5. </strong>Data Importer’s corporate systems and databases must be password protected.</p> <p><strong>6. </strong>VPN and direct Data Importer network access will be limited to company-issued devices.</p> <p><strong>7. </strong>Dual factor authentication will be mandatory for VPN access.</p> <p><strong>8. </strong>Member passwords, if supplied to Data Importer, are to be hashed and salted and stored in a separate database.</p> <p><strong>9. </strong>Data Importer must retain, for one year, VPN, server, wiki, and database access logs.</p> <p><strong>10. </strong>Data Importer must segregate and limit employee access permissions.</p> <p><strong>11. </strong>If applicable, Data Importer must rotate keys to credit card database.</p> <p><strong>12. </strong>Data Importer must conduct active and automated monitoring of critical access logs and anomaly detection.</p> <p><strong>13. </strong>Data Importer has implemented appropriate safeguards proportionate to the specific risks associated with data transfers to the Data Importer’s jurisdiction.</p> <p><strong>14. </strong>Data Importer will adapt its technical and organisational measures to comply with developments in legal and regulatory requirements.</p> <p><strong>C. If LinkedIn is both a Data Importer and a Data Exporter and the counterparty to the Partner Agreement (as defined in the LinkedIn Data Processing Agreement for Business Development Agreements) is both a Data Importer and a Data Exporter (i.e., EU Personal Information is transferred both from LinkedIn to the counterparty and from the counterparty to LinkedIn for processing on behalf of a mutual customer of LinkedIn and the counterparty); The foregoing Sections A and B shall be included in Annex II.</strong></p> </div> </div> <div id class="component component-articleHeadline" data-component-type="articleHeadline"> <div class="article-headline-container"> <!----> <h1 class="article-headline t-40"></h1> <div class="article-meta t-14 article-meta__hairline"> <div class="article-meta__byline-container"> <!----> </div> <!----> </div> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <p><strong>SCHEDULE C</strong></p> <p><strong>Annex III</strong></p> <p><strong>LIST OF SUB-PROCESSORS</strong></p> <p><strong>This Annex applies only where MODULE TWO: Transfer controller to processor or MODULE THREE: Transfer processor to processor of the SCCs is used.</strong></p> <p>General authorisation is provided to the use of sub-processors, a list of which is to be made available to the parties to this Agreement on request.</p> <p>The list of sub-processors contains the following details in relation to each sub-processor:</p> <ul> <li>Name;</li> <li>Address;</li> <li>Contact person’s name, position and contact details; and</li> <li>Description of processing (including a clear delimitation of responsibilities in case several sub-processors are authorised).</li> </ul> </div> </div> <!----> </section> </div> <script src="https://static.licdn.com/aero-v1/sc/h/8hfbuq1ftcvnnx4dd5067pi0t" async></script> <script src="https://static.licdn.com/aero-v1/sc/h/dev5px9xu71l67oqmrrbimi6b" async></script> <script src="https://static.licdn.com/aero-v1/sc/h/3e9epkft4bs8unu9ky8gss8ya" async></script> </main> <footer class="li-footer bg-transparent w-full "> <ul class="li-footer__list flex flex-wrap flex-row items-start justify-start w-full h-auto min-h-[50px] my-[0px] mx-auto py-3 px-2 papabear:w-[1128px] papabear:p-0"> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <span class="sr-only">LinkedIn</span> <icon class="li-footer__copy-logo text-color-logo-brand-alt inline-block self-center h-[14px] w-[56px] mr-1" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/e12h2cd8ac580qen9qdd0qks8"></icon> <span class="li-footer__copy-text flex items-center">© 2024</span> </li> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <a class="li-footer__item-link flex items-center font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover focus:text-color-link-focus" href="https://about.linkedin.com?trk=content_footer-about" data-tracking-control-name="content_footer-about" data-tracking-will-navigate> About </a> </li> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <a class="li-footer__item-link flex items-center font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover focus:text-color-link-focus" href="https://www.linkedin.com/accessibility?trk=content_footer-accessibility" data-tracking-control-name="content_footer-accessibility" data-tracking-will-navigate> Accessibility </a> </li> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <a class="li-footer__item-link flex items-center font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover focus:text-color-link-focus" href="https://www.linkedin.com/legal/user-agreement?trk=content_footer-user-agreement" data-tracking-control-name="content_footer-user-agreement" data-tracking-will-navigate> User Agreement </a> </li> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <a class="li-footer__item-link flex items-center font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover focus:text-color-link-focus" href="https://www.linkedin.com/legal/privacy-policy?trk=content_footer-privacy-policy" data-tracking-control-name="content_footer-privacy-policy" data-tracking-will-navigate> Privacy Policy </a> </li> <!----> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <a class="li-footer__item-link flex items-center font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover focus:text-color-link-focus" href="https://www.linkedin.com/legal/cookie-policy?trk=content_footer-cookie-policy" data-tracking-control-name="content_footer-cookie-policy" data-tracking-will-navigate> Cookie Policy </a> </li> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <a class="li-footer__item-link flex items-center font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover focus:text-color-link-focus" href="https://www.linkedin.com/legal/copyright-policy?trk=content_footer-copyright-policy" data-tracking-control-name="content_footer-copyright-policy" data-tracking-will-navigate> Copyright Policy </a> </li> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <a class="li-footer__item-link flex items-center font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover focus:text-color-link-focus" href="https://brand.linkedin.com/policies?trk=content_footer-brand-policy" data-tracking-control-name="content_footer-brand-policy" data-tracking-will-navigate> Brand Policy </a> </li> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <a class="li-footer__item-link flex items-center font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover focus:text-color-link-focus" href="https://www.linkedin.com/psettings/guest-controls?trk=content_footer-guest-controls" data-tracking-control-name="content_footer-guest-controls" data-tracking-will-navigate> Guest Controls </a> </li> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <a class="li-footer__item-link flex items-center font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover focus:text-color-link-focus" href="https://www.linkedin.com/help/linkedin/answer/34593?trk=content_footer-community-guide" data-tracking-control-name="content_footer-community-guide" data-tracking-will-navigate> Community Guidelines </a> </li> <!----> <li class="li-footer__item font-sans text-xs text-color-text-low-emphasis flex flex-shrink-0 justify-start p-1 relative w-50% papabear:justify-center papabear:w-auto"> <div class="collapsible-dropdown collapsible-dropdown--footer collapsible-dropdown--up flex items-center relative hyphens-auto language-selector z-2"> <!----> <ul class="collapsible-dropdown__list hidden container-raised absolute w-auto overflow-y-auto flex-col items-stretch z-1 bottom-[100%] top-auto" role="menu" tabindex="-1"> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="العربية (Arabic)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-ar_AE" data-locale="ar_AE" role="menuitem" lang="ar_AE"> العربية (Arabic) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="বাংলা (Bangla)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-bn_IN" data-locale="bn_IN" role="menuitem" lang="bn_IN"> বাংলা (Bangla) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Čeština (Czech)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-cs_CZ" data-locale="cs_CZ" role="menuitem" lang="cs_CZ"> Čeština (Czech) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Dansk (Danish)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-da_DK" data-locale="da_DK" role="menuitem" lang="da_DK"> Dansk (Danish) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Deutsch (German)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-de_DE" data-locale="de_DE" role="menuitem" lang="de_DE"> Deutsch (German) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Ελληνικά (Greek)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-el_GR" data-locale="el_GR" role="menuitem" lang="el_GR"> Ελληνικά (Greek) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="English (English) selected" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link--selected" data-tracking-control-name="language-selector-en_US" data-locale="en_US" role="menuitem" lang="en_US"> <strong>English (English)</strong> </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Español (Spanish)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-es_ES" data-locale="es_ES" role="menuitem" lang="es_ES"> Español (Spanish) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="فارسی (Persian)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-fa_IR" data-locale="fa_IR" role="menuitem" lang="fa_IR"> فارسی (Persian) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Suomi (Finnish)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-fi_FI" data-locale="fi_FI" role="menuitem" lang="fi_FI"> Suomi (Finnish) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Français (French)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-fr_FR" data-locale="fr_FR" role="menuitem" lang="fr_FR"> Français (French) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="हिंदी (Hindi)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-hi_IN" data-locale="hi_IN" role="menuitem" lang="hi_IN"> हिंदी (Hindi) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Magyar (Hungarian)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-hu_HU" data-locale="hu_HU" role="menuitem" lang="hu_HU"> Magyar (Hungarian) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Bahasa Indonesia (Indonesian)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-in_ID" data-locale="in_ID" role="menuitem" lang="in_ID"> Bahasa Indonesia (Indonesian) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Italiano (Italian)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-it_IT" data-locale="it_IT" role="menuitem" lang="it_IT"> Italiano (Italian) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="עברית (Hebrew)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-iw_IL" data-locale="iw_IL" role="menuitem" lang="iw_IL"> עברית (Hebrew) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="日本語 (Japanese)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-ja_JP" data-locale="ja_JP" role="menuitem" lang="ja_JP"> 日本語 (Japanese) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="한국어 (Korean)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-ko_KR" data-locale="ko_KR" role="menuitem" lang="ko_KR"> 한국어 (Korean) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="मराठी (Marathi)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-mr_IN" data-locale="mr_IN" role="menuitem" lang="mr_IN"> मराठी (Marathi) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Bahasa Malaysia (Malay)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-ms_MY" data-locale="ms_MY" role="menuitem" lang="ms_MY"> Bahasa Malaysia (Malay) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Nederlands (Dutch)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-nl_NL" data-locale="nl_NL" role="menuitem" lang="nl_NL"> Nederlands (Dutch) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Norsk (Norwegian)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-no_NO" data-locale="no_NO" role="menuitem" lang="no_NO"> Norsk (Norwegian) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="ਪੰਜਾਬੀ (Punjabi)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-pa_IN" data-locale="pa_IN" role="menuitem" lang="pa_IN"> ਪੰਜਾਬੀ (Punjabi) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Polski (Polish)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-pl_PL" data-locale="pl_PL" role="menuitem" lang="pl_PL"> Polski (Polish) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Português (Portuguese)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-pt_BR" data-locale="pt_BR" role="menuitem" lang="pt_BR"> Português (Portuguese) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Română (Romanian)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-ro_RO" data-locale="ro_RO" role="menuitem" lang="ro_RO"> Română (Romanian) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Русский (Russian)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-ru_RU" data-locale="ru_RU" role="menuitem" lang="ru_RU"> Русский (Russian) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Svenska (Swedish)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-sv_SE" data-locale="sv_SE" role="menuitem" lang="sv_SE"> Svenska (Swedish) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="తెలుగు (Telugu)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-te_IN" data-locale="te_IN" role="menuitem" lang="te_IN"> తెలుగు (Telugu) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="ภาษาไทย (Thai)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-th_TH" data-locale="th_TH" role="menuitem" lang="th_TH"> ภาษาไทย (Thai) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Tagalog (Tagalog)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-tl_PH" data-locale="tl_PH" role="menuitem" lang="tl_PH"> Tagalog (Tagalog) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Türkçe (Turkish)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-tr_TR" data-locale="tr_TR" role="menuitem" lang="tr_TR"> Türkçe (Turkish) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Українська (Ukrainian)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-uk_UA" data-locale="uk_UA" role="menuitem" lang="uk_UA"> Українська (Ukrainian) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="Tiếng Việt (Vietnamese)" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-vi_VN" data-locale="vi_VN" role="menuitem" lang="vi_VN"> Tiếng Việt (Vietnamese) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="简体中文 (Chinese (Simplified))" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-zh_CN" data-locale="zh_CN" role="menuitem" lang="zh_CN"> 简体中文 (Chinese (Simplified)) </button> </li> <li class="language-selector__item" role="presentation"> <!-- Adding aria-label to both the li and the button because screen reader focus goes to button on desktop and li on mobile--> <button aria-label="正體中文 (Chinese (Traditional))" class="font-sans text-xs link block py-[5px] px-2 w-full hover:cursor-pointer hover:bg-color-action hover:text-color-text-on-dark focus:bg-color-action focus:text-color-text-on-dark language-selector__link !font-regular" data-tracking-control-name="language-selector-zh_TW" data-locale="zh_TW" role="menuitem" lang="zh_TW"> 正體中文 (Chinese (Traditional)) </button> </li> <!----> </ul> <button class="language-selector__button select-none relative pr-2 font-sans text-xs font-bold text-color-text-low-emphasis hover:text-color-link-hover hover:cursor-pointer focus:text-color-link-focus focus:outline-dotted focus:outline-1" aria-expanded="false" data-tracking-control-name="footer-lang-dropdown_trigger"> <span class="language-selector__label-text mr-0.5 break-words"> Language </span> <icon class="language-selector__label-chevron w-2 h-2 absolute top-0 right-0" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/cyolgscd0imw2ldqppkrb84vo"></icon> </button> </div> </li> </ul> <!----> </footer> <script src="https://static.licdn.com/aero-v1/sc/h/eh08muqvrde4h3hc6koyij5ti" async></script> <!----> </body> </html>