CINXE.COM
LinkedIn Live Events API Terms of Use
<!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="AAYnjG1oZ+p4Dlj8vl777A==" data-multiproduct-name="lithograph-publish-frontend" data-service-name="lithograph-publish-frontend" data-browser-id="74ba16c7-1d54-4f7b-839f-db12416acc7d" data-page-instance="urn:li:page:d_lithograph_content;u4rOW61fT/WxFWrga5kVNg==" data-disable-jsbeacon-pagekey-suffix="false"> <link rel="canonical" href="https://www.linkedin.com/legal/l/live-events-api-terms"> <!----><!----> <!----> <!----> <!----> <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 Live Events API Terms of Use</title> <!----> <meta property="og:type" content="website"> <meta property="og:title" content="LinkedIn Live Events API Terms of Use"> <!----> <meta property="og:url" content="https://www.linkedin.com/legal/l/live-events-api-terms"> <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 Live Events API Terms of Use"> <meta name="twitter:site" content="@linkedin"> <!----> <!----> <meta name="robots" content="noarchive"> <meta name="linkedin:pageTag" content="/legal/l/live-events-api-terms"> <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-articleHeadline" data-component-type="articleHeadline"> <div class="article-headline-container"> <!----> <h1 class="article-headline t-40" data-article-title="Additional Terms for the LinkedIn Live Events API Program ">Additional Terms for the LinkedIn Live Events API Program </h1> <div class="article-meta t-14 article-meta__hairline"> <div class="article-meta__byline-container"> <p class="t-14 t-black--light" data-published-date="2022-10-13"> October 13, 2022 </p> </div> <div class="social-share"> <ul class="social-share__list share-list" title="Share via" data-share-list> <li class="share-list__item share-item"> <a href="#" class="share-item__link medium-round-muted-tertiary-button" role="button" data-tracking-control-name="_linkedin_share" data-share-type="linkedin" aria-label="Share on LinkedIn, New window will open"> <li-icon class="share-item__icon" type="linkedin-icon"></li-icon> </a> </li> <li class="share-list__item share-item"> <a href="#" class="share-item__link medium-round-muted-tertiary-button" role="button" data-tracking-control-name="_facebook_share" data-share-type="facebook" aria-label="Share on Facebook, New window will open"> <li-icon class="share-item__icon" type="facebook-icon"></li-icon> </a> </li> <li class="share-list__item share-item"> <a href="#" class="share-item__link medium-round-muted-tertiary-button" role="button" data-tracking-control-name="_twitter_share" data-share-type="twitter" aria-label="Share on Twitter, New window will open"> <li-icon class="share-item__icon" type="twitter-icon"></li-icon> </a> </li> </ul> </div> </div> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p><strong><<THE LINKEDIN LIVE EVENTS API PROGRAM IS A VETTED API PROGRAM AND YOU HAVE NO RIGHT TO USE ANY API OR DATA MADE AVAILABLE AS PART OF THIS PROGRAM UNLESS APPROVED BY LINKEDIN>> </strong></p> <p>As a LinkedIn Live Events Developer, you’ll be able to build a live events or audio/video streaming integration with LinkedIn to enable a LinkedIn-approved broadcaster to broadcast to LinkedIn from your application. When you develop using the LinkedIn Live Events Developer technology, you agree to be bound by the following terms, so please take a few minutes to review them. </p> <p>Last revised on October 13, 2022. </p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <h2>1. Introduction </h2> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>1.1 About these Additional LinkedIn Live Events API Program Terms </strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>When you develop using the LinkedIn Live Events API technology, you are entering into a legal agreement with Linkedin and agreeing to all of these Terms.<p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>By using the APIs, software, documentation, tools, and data that LinkedIn makes available to you as part of the LinkedIn Live Events API Program ("<strong>LLE Program</strong>”), you are agreeing to be bound by these Additional Terms for the LinkedIn Live Events API Program (“<strong>LLE Terms</strong>”) that are incorporated into the <a rel="" href="https://legal.linkedin.com/api-terms-of-use" target="_blank">LinkedIn API Terms of Use</a> (“<strong>API Terms of Use</strong>”) as “Additional Terms” (collectively, these “<strong>Terms</strong>”). All capitalized terms not defined herein will have the meaning given to them under the API Terms of Use. Any summaries of these LLE Terms included in the highlighted boxes reference only some of the key provisions of these LLE Terms and are not a substitute for them. As used in these LLE Terms, “<strong>LLE APIs</strong>” means APIs, software, documentation, tools, and other functionality that LinkedIn makes available as part of the LLE Program. </p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>1.2 Description of the Live Events APIs</strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>The LLE APIs currently available under the LLE Program support various broadcasting and virtual event creation, management, and broadcasting use cases.<p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>As part of the LLE Program, LinkedIn is granting approved developers the ability to integrate the LLE APIs into their live audio/video streaming, virtual event, webinar, podcasting, and audio/video editing, repurposing, and publishing applications “<strong>Event Application</strong>”) in order to: (a) make various LinkedIn Live Event services (“<strong>LLE Services</strong>”) available via their Event Applications to clients that have entered into contracts with the relevant developer for the provision of such LLE Services and have been preapproved by LinkedIn (each, a “<strong>Client</strong>”); and (b) obtain data from the LLE APIs relating to such LLE Services (“<strong>LLE Data</strong>”) for the purpose of making it available to their Clients. The LLE APIs (and LLE Services) currently available under the LLE Program (as further described below) are: (i) for creation and management of virtual events, and live audio/video broadcasts (each, an “<strong>Event</strong>”, and an Event to be broadcast to the LinkedIn Services, a “<strong>LinkedIn Event</strong>”); and (ii) for broadcasting such Events onto the LinkedIn Services. </p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>1.3 Relationship to the API Terms of Use </strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>If there is a conflict between these LLE Terms and the API Terms of Use, these LLE Terms will control. <p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>To the extent there is a conflict between these LLE Terms and the API Terms of Use, these LLE Terms will control. For the LLE Program, any reference in the API Terms of Use to: (a) “Content” (or Content made available from or through the APIs) will apply to LLE Data; (b) “Application” will apply to each Event Application; (c) “Terms” will apply to the API Terms of Use with these LLE Terms incorporated therein; and (d) “API” will apply to each LLE API. </p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>1.4 Account Manager and Authorized Client </strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>If your Events Application enables your Clients to manage LinkedIn accounts (e.g., page accounts or member profiles), such Clients must be authorized by the relevant Account Manager. <p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>The LLE APIs allow your Clients to manage accounts on certain LinkedIn Services (“<strong>LinkedIn Accounts</strong>”), such as page accounts and Member profiles via your Events Application. </p> <p>a. <u>Overview of LinkedIn Page and Profile Accounts</u>. A LinkedIn page account allows organizations to educate and engage with Members through their LinkedIn page (“<strong>Page</strong>”), which includes a high-level summary of the subject organization and posts by Page administrators (“<strong>Page Account</strong>”). A LinkedIn profile account allows Members to create a profile on the LinkedIn Services (“<strong>Member Profile</strong>”) with personal and professional details for the purposes of managing their personal brand, networking, and creating and engaging with content on the LinkedIn Services (“<strong>Member Account</strong>”). </p> <p>b. <u>Account Manager</u>. An “<strong>Account Manager</strong>” is any individual or entity that controls a LinkedIn Account, including LLE Data relating to any such LinkedIn Account. </p> <p>c. <u>Authorized Client</u>. An “<strong>Authorized Client</strong>” is any Client that is an Account Manager or that is authorized by an Account Manager to access the Account Manager’s LinkedIn Account (or LLE Data relating to any such account). An example of an Authorized Client is an external advertising or social media management agency that the Account Manager hires. For clarity, if these LLE Terms indicate that any LLE Service or LLE Data must only be made available to Authorized Clients, the reference is to the specific Authorized Client(s) permitted to access the LLE Service or LLE Data by the relevant Account Manager. </p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>1.5 LinkedIn Approved Clients </strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>The LLE Services are not available to all Members and Pages. Members and Pages must be approved for access to the LLE Services by LinkedIn.<p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>The LLE Services are not available to all Members and Pages on LinkedIn. Any Member or Page that wants to use the LLE Services must apply for access and receive approval from LinkedIn. All interested Members and Pages should review the access criteria currently located <a rel="" href="https://www.linkedin.com/help/linkedin/answer/a568503" target="_blank">here</a>. </p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>1.6 Descriptions of LLE APIs and LLE Services </strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>The LLE APIs (and LLE Services) currently available under the LLE Program are further described below. <p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>The LLE APIs (and LLE Services) currently available under the LLE Program are further described in the <a rel="" href="https://learn.microsoft.com/en-us/linkedin/consumer/integrations/live-video/" target="_blank">Live Events Developer Documentation</a>, and currently include functionality to enable: (a) the Event Application to check the LinkedIn Services to see if a particular Page Account or Member Account is authorized to broadcast Events to the LinkedIn Services; (b) a Client to schedule, promote, broadcast, and end the broadcast of a LinkedIn Event; (c) a Client to target their LinkedIn Event to a specific country, region, or language; and (d) a Client to view engagement with their LinkedIn Event in real time as the LinkedIn Event is being broadcast from within the Event Application (such engagement functionality is restricted to those developers approved by LinkedIn). </p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>1.7 Creation of a Linkedin Event </strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>If your Event Application enables a Client to create a LinkedIn Event, you must bind that Client to LinkedIn Event Agreement. <p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>You acknowledge and agree that any Client that creates a LinkedIn Event must consent to the LinkedIn Events Terms (“<strong>Events Agreement</strong>”), currently located <a rel="" href="https://www.linkedin.com/legal/l/events-terms#:~:text=Your%20Event%20must%20not%20access,%2C%20scrapers%2C%20spiders%20or%20robots.&text=If%20you%20use%20the%20Events,policy%20in%20each%20such%20form." target="_blank">here</a>. </p> <p>If your Event Application enables a Client to create a LinkedIn Event, you represent and warrant that: (a) you have the authority to bind (and hereby bind) the relevant Client to the Events Agreement; or (b) you will require your Client to agree, by written contract (including click-through terms), to the Events Agreement. </p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>1.8 Use of LLE APIs for Internal Purposes </strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>If you wish to use the LLE APIs to access LinkedIn Accounts for which you are the Account Manager, in connection with such use, you are considered an Authorized Client under these LLE Terms. <p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>If you’re using any LLE API in connection with any LinkedIn Account for which you are the Account Manager, in connection with such use: (a) any reference to an Account Manager, Authorized Client, or Client in these LLE Terms refers to you; and (b) you hereby agree to the Events Agreement in connection with your creation of a LinkedIn Event. </p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <h2>2. Review of Your LLE API Integrations </h2> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>2.1 Requesting Access to the LLE APIs</strong> </p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>In order to obtain access to the LLE APIs, you and your Event Application will be subject to LinkedIn’s developer and application vetting processes. <p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>Your Event Application and your integration of any LLE API, LLE Data, and/or LLE Service into your Event Application (collectively, your “<strong>LLE API Integration</strong>”) must be approved by LinkedIn. LinkedIn’s approval will be subject to you successfully completing its developer and application vetting (including a review of your privacy and security practices). You must ensure that all information you provide to LinkedIn in connection with such vetting processes is accurate and complete. In particular, you are not authorized to use any LLE API (or LLE Data) for any use case other than the one(s) you specify in connection with your request for access (including via an access request form) to the relevant LLE API. While LinkedIn will make reasonable efforts to respond to access requests, LinkedIn is not committing to any timeframe for such response.</p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>2.2 Changes to your LLE API Integration</strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>LinkedIn must be notified of certain changes to your LLE API Integration. <p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>If you change your LLE API Integration, you must notify LinkedIn of any change that results in: (a) any information you provided to LinkedIn as part of the developer and application vetting processes becoming inaccurate or incomplete; or (b) differences in how you use, store, delete, distribute, or otherwise make available LLE Data. Additional details are provided in the Developer Documentation. </p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>2.3 Monitoring your LLE API Integration </strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>LinkedIn may review all LLE API Integrations at any time and reserves all of its rights under these Terms. <p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>Even if LinkedIn approves your LLE API Integration (including during the vetting processes), you are responsible for ensuring that your LLE API Integration (including all use, disclosure, and storage of LLE Data) is, at all times, in compliance with: (a) these Terms (including the Developer Documentation); and (b) all other requirements or restrictions that LinkedIn separately communicates to you (e.g. during or after the relevant vetting processes). LinkedIn retains all of its rights under these Terms (including its right to suspend or discontinue your access to the LLE APIs and/or LLE Data for non-compliance with these Terms). </p> <p>LinkedIn (and/or its third-party service providers) reserves the right to monitor and audit all LLE API Integrations at any time, in LinkedIn’s discretion, including to confirm your compliance with these Terms. You will: (a) cooperate with any such review, including reasonable requests by LinkedIn for access to your Event Application and access (including physical access) to other materials, information, records, or Systems relating to such review; and (b) accommodate modifications to your LLE API Integrations required by LinkedIn as a result of its review.</p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <h2>3. Use of LLE APIs and LLE Data </h2> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>3.1 Specific Data Restrictions</strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>Certain types of LLE Data are subject to additional data restrictions as described below.<p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>Without limiting the generality of any other restrictions in these Terms, you must comply with the following data requirements and restrictions to the extent that you receive access to the indicated type of LLE Data or LLE API: </p> <p>a. <u>Analytics Data</u>. You may only use, distribute, or otherwise make available Analytics Data to provide reporting and billing to Authorized Clients. Such reporting shall relate to the performance, effectiveness, and optimization of the relevant Page Accounts or Member Accounts. “<strong>Analytics Data</strong>” means analytics on LinkedIn Accounts and on LinkedIn Events broadcast on behalf of a LinkedIn Account (along with your analysis, insights, and derivatives thereof, including Aggregated LLE Data as defined below). </p> <p>You may aggregate Analytics Data from LinkedIn Accounts controlled by different Account Managers (“<strong>Aggregated LLE Data</strong>”); provided that: (i) you maintain the specific, segregated data regarding each Account Manager’s LinkedIn Accounts as confidential and you do not disclose it to any third party (other than Authorized Clients); (ii) such Aggregated LLE Data does not include any Member Data (as defined below); (iii) such Aggregated LLE Data would not allow any third party to identify or infer any Account Manager or any user of any LinkedIn Service (or data specific to any Account Manager or user of any LinkedIn Service); (iv) you use and disclose such Aggregated LLE Data only for the purpose of providing reporting to your Clients relating to the optimization of LinkedIn Events broadcast from the Event Application to LinkedIn Accounts; and (v) any such use or disclosure is agreed to by the Account Manager that controls the relevant LinkedIn Accounts. </p> <p>If Analytics Data includes any of the data types described in Sections 3.1(c) (“Organization Profile Data and Standardized Data”) or 3.1(d) (“Member Data”), any such data is subject to the restrictions included in those sections, notwithstanding anything to the contrary in this Section 3.1(a). </p> <p>b. <u>Data Transferred to LinkedIn</u>. You represent and warrant that you have all necessary rights and a legal basis under all applicable privacy and data protection laws and regulations for the transfer of any data to LinkedIn in connection with your LLE API Integration. </p> <p>c. <u>Organization Profile Data and Standardized Data</u>. If you receive access to any organization profile data from a Page (“<strong>Organization Profile Data</strong>”), including logo, location, industry, or size of the subject organization, or any LinkedIn standardized data (“<strong>Standardized Data</strong>”), including standardized locations, industries, degrees, job functions, and other fields as specified in the Developer Documentation, you may only use and display such data via your Event Application to support the relevant LLE Services for which the data was made available to you. You must not: (i) export, transfer, or distribute any Organization Profile Data or Standardized Data to any third party (other than as necessary to transfer reporting data from LinkedIn Accounts to Authorized Clients); (ii) create any derivative of Organization Profile Data or Standardized Data (e.g. by modifying such data or by combining it with other data); (iii) misrepresent the origin of any Organization Profile Data or Standardized Data; or (iv) use any Organization Profile Data or Standardized Data for the purpose of building any product or service unrelated to your LLE API Integration. In addition, if you have access to any Microsoft Bing Maps location data, you hereby also agree: (1) to <a rel="" href="https://www.microsoft.com/en-us/maps/product/terms-april-2011" target="_blank">Microsoft Bing Maps and MapPoint Web Service End User Terms of Use and Embedded Maps Service Terms of Use</a> and the <a rel="" href="http://aka.ms/BingMapsMicrosoftPrivacy" target="_blank">Microsoft Privacy Statement</a> (collectively, the “<strong>Microsoft Terms</strong>”) in connection with your use of such data; and (2) that the Microsoft Terms shall govern in the event of a conflict with these Terms. </p> <p>d. <u>Member Data</u>. If you receive access to LLE Data that is Personal Information (as defined in the LinkedIn Data Processing Agreement for Business Development Agreements) and/or that relates to any individual user’s activities on any LinkedIn Service (collectively, “<strong>Member Data</strong>”), you may only display the Member Data via your Event Application to support the LLE Services for which the Member Data was made available to you. The relevant LLE Services are: (i) to enable an Authorized Client to create accounts or profiles on your Event Application using their own Member Data; or (ii) to enable an Authorized Client’s Page or Member Profile to view Member Data on those Members that have interacted with LinkedIn Events broadcast on behalf of such Page or Member Profile and to provide related reporting to the Authorized Client. You must not however: (1) export, transfer, or distribute any Member Data to any third party, including to any Authorized Client; (2) create a database of Member Data collected from multiple unaffiliated LinkedIn Accounts; (3) commingle or combine any Member Data (other than in connection with Subsection (i)) with any other Personal Information, including for the purpose of supplementing, verifying, or appending to user profiles, leads, or portions thereof; (4) commercialize or sell any Member Data or make any Member Data available to any data broker, information reseller, information broker, data monetization service, or similar service; (5) use Member Data for advertising, sales, or recruiting use cases (including to identify sales or marketing prospects or prospective talent for hire, for lead creation, to enhance customer data in a CRM or marketing automation platform, to build an audience list, or for ad targeting purposes); or (6) use Member Data to derive sensitive information on the relevant Member (including racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, mental or physical health conditions, citizenship or immigration status, or sexual orientation). For clarity, Member Data includes: (x) LinkedIn profile data of Members who create (or interact with) posts on the LinkedIn Service and the content or information provided by the Member (e.g., a Member’s post, comment, or reaction); and (y) Member identifiers (including person URNs/uniform resource names that are unique to your Event Application). </p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>3.2 Additional API and Data Restrictions</strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>There are also some general restrictions on your use of the LLE APIs and LLE Data as described below.<p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>You agree not to do the following: </p> <p>a. Make the LLE API Integration, or LLE Data available to any third party other than your Clients (or as otherwise set forth in these LLE Terms); </p> <p>b. Make any LLE API or LLE Data available to any developer to integrate into a product, service, or application that the developer makes available to unaffiliated customers (as opposed to internal users affiliated with the developer’s organization); </p> <p>c. Transfer to any Client more LLE Data than it needs for the optimization of LinkedIn Events broadcasted by the relevant Page Account or Member Account; </p> <p>d. Integrate any LinkedIn API, other than the LLE APIs, into your Event Application (for clarity, you may integrate the LinkedIn Self-Serve APIs into your Event Application in accordance with the API Terms of Use); </p> <p>e. Offer Authorized Clients standard targeting segments or categories that differ from targeting offered by the LLE APIs (e.g., country, region, or language targeting segments for Page Accounts); </p> <p>f. Access, collect, use, store, transfer, process, or make available LLE Data in any manner unless: (i) you have obtained the relevant rights from your Clients; and (ii) you are operating in accordance with the directions you have received from your Clients and your agreements with your Clients; </p> <p>g. Disclose the identity of Account Managers without their prior written consent; </p> <p>h. Collect LLE Data after the Authorized Client ceases to receive services from you relating to such LLE Data or requests that you no longer access such LLE Data; </p> <p>i. Allow any of your affiliates to access LLE Data in any manner other than via your Event Application as a Client in accordance with these Terms; </p> <p>j. Make any statement, representation, or warranty to any third party, either directly or indirectly: (i) indicating that you have any authority to act for or on behalf of LinkedIn or to obligate or bind LinkedIn in any way; (ii) that relates to LinkedIn, the LinkedIn Services, the LLE Program, LLE APIs, LLE Services, or the LLE Data and that is inaccurate, fraudulent, or misleading; or (iii) suggesting that you are LinkedIn’s strategic, certified, or preferred partner (other than as expressly permitted in writing by LinkedIn); or </p> <p>k. Use the LLE APIs in conjunction with LinkedIn Accounts for which you are the Account Manager to provide services (on a resale basis or otherwise) to your Clients. </p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>3.3 Suspension of Client Access </strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>You will, at LinkedIn’s request, suspend or terminate any Client’s access to your LLE API Integration or LLE Data.<p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>You will, at LinkedIn’s request (email acceptable), suspend or terminate any Client’s access to or use of your LLE API Integration or any or all LLE Data (including Stored LLE Data, as defined below) if: (a) LinkedIn suspends or terminates the Client’s (or the relevant Account Manager’s) ability to broadcast LinkedIn Events or to otherwise access the LinkedIn Services; or (b) LinkedIn, in its sole discretion, determines that providing the Client access to LLE Services or LLE Data is not in LinkedIn’s or its Members’ best interests. </p> <p>In addition, you will notify LinkedIn, and, at LinkedIn’s request (email acceptable), suspend or terminate any Client’s access to all LLE Data, if you become aware that the Client is using the LLE Data in an illegal manner or in violation of the restrictions included in these Terms.</p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <h2>4. Storage of LLE Data</h2> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>4.1 Right to Store LLE Data</strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>You must <u>not</u> store any LLE Data, except to the extent expressly permitted by the Developer Documentation. <p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>You must <u>not</u> store or cache any LLE Data, except: (a) to the extent expressly permitted by the <a rel="" href="https://learn.microsoft.com/en-us/linkedin/consumer/integrations/live-video/?context=linkedin%2Fconsumer%2Fcontext" target="_self">Developer Documentation</a>; and (b) Aggregated LLE Data. Any data that may be stored pursuant to this Section 4.1 is “<strong>Stored LLE Data</strong>”. You will take appropriate measures given the nature of the Stored LLE Data to ensure that it is kept up to date.</p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>4.2 Deletion of Stored LLE Data</strong> </p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>Stored LLE Data must be promptly deleted in certain circumstances (including when a Client ceases to receive services from you relating to its LLE Data or upon a Client’s or LinkedIn’s request). <p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>You will permanently delete (in ten (10) days or less) any Stored LLE Data that was stored on behalf of a Client: (a) if the Client ceases to receive services from you relating to such Stored LLE Data and the Stored LLE Data is no longer necessary to fulfill the Client’s business need or data retention obligations; or (b) upon the Client’s (or Account Manager’s) request. In addition, you will permanently delete (in ten (10) days or less): (a) any or all Stored LLE Data upon LinkedIn’s request (email acceptable); and/or (b) all Stored LLE Data that is Member Data upon termination of these LLE Terms. LinkedIn may require you to certify that you have complied with the deletion requirements applicable to the Stored LLE Data.</p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <h2>5. Application Requirements</h2> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>5.1 Reporting, Training, and Fees </strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>Your Event Application must allow Authorized Clients to view LLE Data separately from data relating to other non-LinkedIn platforms. <p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>If your Event Application allows your Clients to access aggregate data (for example, metrics relating to the targeting and engagement of an Event) across various digital channels on and off of LinkedIn, your Event Application must allow your Clients to separately view LLE Data. You will use commercially reasonable efforts to train your sales and Event support teams on LLE Services. You may not charge, either directly or indirectly through distribution channels, Clients any incremental fees in connection with the LLE API Integration. The foregoing does not preclude you from charging Clients for the Event Application.</p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>5.2 Security</strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>You will maintain safeguards that are designed to keep all LLE Data secure.<p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>You will maintain physical, technical, and administrative safeguards that are designed to keep all LLE Data secure and that meet or exceed industry standards for this type of data. Any request to access LLE Data on behalf of an Authorized Client must comply with all LinkedIn technical and security requirements, and LinkedIn reserves the right to deny such access in its sole discretion. </p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <h2>6. Duration and Termination</h2> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>6.1 Duration of LMA Terms</strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>These LLE Terms will continue until they terminate as described below.<p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>These LLE Terms will commence on the date you agree to them or the date you start using any LLE API (whichever occurs first) and continue until: (a) you discontinue use of all LLE APIs; (b) the API Terms of Use terminate; or (c) these LLE Terms are terminated pursuant to Section 6.2 (“Termination for Convenience”). For clarity, any termination of these LLE Terms will not automatically terminate the API Terms of Use but any termination of the API Terms of Use will automatically terminate these LLE Terms. Neither party will be liable for any costs, expenses, or damages solely as a result of termination of these LLE Terms.</p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>6.2 Termination for Convenience</strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>Either party may terminate these LLE Terms for convenience.<p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>Either party may terminate these LLE Terms for convenience for any reason at any time upon thirty (30) days’ prior written notice to the other party.</p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>6.3 Survival</strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>Even after termination, many of your obligations under these LLE Terms survive.<p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>Upon termination of these LLEA Terms, all rights granted under these LLE Terms will immediately terminate. The following sections will survive termination of these LLE Terms: all definitions, Sections 1.3 (“Relationship to the LinkedIn API Terms of Use”), 3 (“Use of LLE APIs and LLE Data”), 4 (“Storage of LLE Data”), 5.2 (“Security”), 6.3 (“Survival”), 7 (“Confidentiality”), 8 (“Indemnification”), and 9 (“Miscellaneous”). Upon request, each party will promptly destroy all Confidential Information (as defined below) of the other party in its possession, custody, or control, provided that Confidential Information contained in backup media can remain in such backup media for up to thirty (30) days or until it is deleted as part of the relevant party’s standard deletion processes, whichever occurs first. Notwithstanding the preceding requirement, each party may retain a copy of the other party’s Confidential Information as reasonably required for legal and auditing purposes. LinkedIn may request that you certify in writing your compliance with this Section.</p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <h2>7. Confidentiality</h2> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>7.1 Confidential Information </strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>Each party will protect the confidentiality of the other party’s confidential information.<p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>If either party (“<strong>Receiving Party</strong>”) under these LLE Terms gains access to Confidential Information of the other party (“<strong>Disclosing Party</strong>”), then the terms of this Section will apply. “<strong>Confidential Information</strong>” means all information disclosed under these LLE Terms that is marked or designated as confidential by the Disclosing Party or that due to the nature of the information should reasonably be known to be confidential by the Receiving Party. Each party agrees that it will not: (a) use any of the other party’s Confidential Information in any way for its own benefit or the benefit of any third party, except as expressly permitted by, or as required to implement, these LLE Terms; or (b) disclose the other party’s Confidential Information to any third party except as expressly permitted by these LLE Terms or to independent contractors who: (i) have a need to know it in order for the Receiving Party to perform its obligations or exercise its rights under these LLE Terms; and (ii) are under written confidentiality and non-use obligations at least as restrictive as those set forth in these LLE Terms and which can extend to the Confidential Information. Each party will take reasonable precautions to protect the confidentiality of the other party’s Confidential Information that are at least as stringent as it takes to protect its own Confidential Information. Information will not be deemed Confidential Information under these LLE Terms if: (1) it was publicly available or was known to the Receiving Party prior to its receipt from the Disclosing Party from a source other than one having an obligation of confidentiality to the Disclosing Party; (2) it has become publicly known, except through a breach of these LLE Terms by the Receiving Party; (3) it was rightfully communicated to the Receiving Party free of any obligation of confidence to the Disclosing Party subsequent to the time it was communicated by the Disclosing Party; or (4) it has been entirely independently developed by the Receiving Party without use of or reference to the Disclosing Party’s Confidential Information. For clarity, the fact that LLE Data is available through LinkedIn Services shall not constitute “publicly available” or “publicly known” under Subsection (1) or Subsection (2). Notwithstanding the above, the Receiving Party may disclose the Disclosing Party’s Confidential Information, without violating these LLE Terms, to the extent such disclosure is required by a valid order of a court or other governmental body having jurisdiction, provided that the Receiving Party gives the Disclosing Party reasonable prior written notice of such disclosure and makes a reasonable effort to obtain, or to assist the Disclosing Party in obtaining, a protective order preventing or limiting the disclosure and/or requiring that the Confidential Information so disclosed be used only for the purposes for which the order was issued.</p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>7.2 Residuals</strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>Receiving Party employees may further develop their general knowledge, skills, and experience, even if based on the Disclosing Party’s Confidential Information. <p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>The employees of the Receiving Party who have received or have been exposed to the Disclosing Party’s Confidential Information may further develop their general knowledge, skills, and experience (including general ideas, concepts, know-how, and techniques), which may be based on such Confidential Information. The restrictions in Section 7.1 (“Confidential Information”) will not apply to the subsequent use, and disclosures incidental to such use, by such employees of such general knowledge, skills, and experience, as unintentionally retained in their unaided memories. The receipt of or exposure to a party’s Confidential Information under these LLE Terms will not in any way limit or restrict the work assignments of any of the Receiving Party’s employees or contractors. </p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <h2>8. Indemnification</h2> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>8.1 Your Indemnification Obligations</strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>You will indemnify LinkedIn for any claims arising from your relationships with your Clients or Account Managers.<p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>You will defend, hold harmless, and indemnify LinkedIn and the LinkedIn Affiliates (and our and their respective employees, shareholders, and directors) from any claim or action brought by a third party, including all damages, liabilities, costs, and expenses, including reasonable attorneys’ fees, to the extent resulting from, alleged to have resulted from, or relating to your interactions with your Clients or with Account Managers or interactions between your Clients and Account Managers (including any claim that any contract between any of the preceding parties has been breached).</p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--reader"> <h2>9. Miscellaneous</h2> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>9.1 Communications</strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>LinkedIn may communicate with you via e-mail, regular mail, and/or postings on the Developer Site regarding the LLE Program.<p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>You agree to receive communications from LinkedIn relating to the LLE Program via e-mail, regular mail, and/or postings on the Developer Site, including communications regarding your Event Application and access to the LLE Program and LLE APIs. If you share any third party’s contact information with LinkedIn in connection with the LLE Program, you agree that you have the right to authorize LinkedIn (and hereby authorize LinkedIn) to use that information to contact the third party regarding the LLE Program.</p> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p3"> <p><strong>9.2 General Terms</strong></p> </div> </div> <div id class="component component-callout" data-component-type="callout"> <div class="callout callout-color--teal"> <li-icon type="lightbulb-icon"></li-icon> <div class="callout__content "> <h3 class="callout__headline t-16 t-black t-bold t-roman"></h3> <div class="callout__description"><p></p><p></p>These Terms supersede any and all prior agreements and other communications between the parties which relate to the subject matter of these Terms.<p></p><p></p></div> </div> <!----> </div> </div> <div id class="component component-richText" data-component-type="richText"> <div class="rich-text global-paragraph-style--p2"> <p>These Terms (including the Developer Documentation) supersede any and all prior agreements (including any LinkedIn API License Agreement – Live Video), proposals (oral and written), understandings, representations, conditions, warranties, covenants, and other communications between the parties which relate to the subject matter of these Terms. The term “include” (and all of its variants) when used in these Terms will be interpreted to be followed by the clause “without limitation” in all cases. Where written approval is required under these LLE Terms, such approval must be by a duly authorized representative of the consenting party.</p> </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>