Common use of Licensor-Administered Authentication Clause in Contracts

Licensor-Administered Authentication. Where the Licensor provides alternative methods of access and authentication beyond the Licensee-administered methods described herein, e.g. by allowing users to establish a personal login from an on-campus IP address (thereby enabling access via username and password when logging in to a website of the Licensor) or device authentication, which affiliates the device or application by use of a token, cookie, or vendor- managed proxy prefix, neither the Licensee nor any Participating Institution will be responsible or liable for claims of breach or validity of such use. Neither the Licensee nor any of the Participating Institutions shall be responsible or liable for the processing of personally identifiable information (personal data) by the Licensor in this matter as this remains its full liability.

Appears in 6 contracts

Samples: License Agreement, License Agreement, License Agreement

AutoNDA by SimpleDocs

Licensor-Administered Authentication. Where the Licensor provides alternative methods of access and authentication beyond the Licensee-administered methods described herein, e.g. by allowing users to establish a personal login from an on-campus IP address (thereby enabling access via username and password when logging in to a website of the Licensor) or device authentication, which affiliates the device or application by use of a token, cookie, or vendor- managed proxy prefix, neither the Licensee nor any Participating Institution will be responsible or liable for claims of breach or validity of such use. Neither the Licensee nor any of the Participating Institutions shall be responsible or liable for the processing of personally identifiable information (personal data) data by the Licensor in this matter as this remains its full liabilitymatter.

Appears in 5 contracts

Samples: License Agreement, License Agreement, License Agreement

Licensor-Administered Authentication. Where the Licensor provides alternative methods of access and authentication beyond the Licensee-administered methods described herein, e.g. by allowing users to establish a personal login from an on-campus IP address (thereby enabling access via username and password when logging in to a website of the Licensor) or device authentication, which affiliates the device or application by use of a token, cookie, or vendor- managed proxy prefix, neither the Licensee nor any Participating Institution will be responsible or liable for claims of breach or validity of such use. Neither the Licensee nor any of the Participating Institutions shall be responsible or liable for the processing of personally identifiable information (personal data) by the Licensor in this matter as this remains its their full liability.

Appears in 3 contracts

Samples: License Agreement, License Agreement, License Agreement

Licensor-Administered Authentication. Where the Licensor provides alternative methods of access and authentication beyond the Licensee-administered methods described herein, e.g. by allowing users to establish a personal login from an on-campus IP address (thereby enabling access via username and password when logging in to a website of the Licensor) or device authentication, which affiliates the device or application by use of a token, cookie, or vendor- vendor-managed proxy prefix, neither the Licensee nor any Participating Institution will be responsible or liable for claims of breach or validity of such use. Neither the Licensee nor any of the Participating Institutions shall be responsible or liable for the processing of personally identifiable information (personal data) by the Licensor in this matter as this remains its their full liability.

Appears in 2 contracts

Samples: License Agreement, License Agreement

Licensor-Administered Authentication. Where the Licensor provides alternative methods of access and authentication beyond the Licensee-administered methods described herein, e.g. by allowing users to establish a personal login from an on-on- campus IP address (thereby enabling access via username and password when logging in to a website of the Licensorvendor website) or device authentication, which affiliates the device or application by use of a token, cookie, or vendor- vendor-managed proxy prefix, neither the Licensee nor any Participating Institution will not be responsible or nor liable for claims of breach or validity of such use. Neither the Licensee nor any of the Participating Institutions shall be responsible or liable for the processing of personally identifiable information (personal data) data by the Licensor in this matter as this remains its full liabilityexcept that Licensee agrees not to provide any personal data to Licensor unless it has a proper legal basis for doing so.

Appears in 1 contract

Samples: Standard License Agreement

AutoNDA by SimpleDocs

Licensor-Administered Authentication. Where the Licensor provides alternative methods of access and authentication beyond the Licensee-administered methods described hereinIP addresses pursuant to Section (b), e.g. by allowing users to establish a personal login from an on-on- campus IP address (thereby enabling access via username and password when logging in to a website of the Licensor) or device authentication, which affiliates the device or application by use of a token, cookie, or vendor- vendor-managed proxy prefix, neither the Licensee nor any Participating Institution will be responsible or liable for claims of breach or validity of such use. Neither the Licensee nor any of the Participating Institutions shall be responsible or liable for the processing of personally identifiable information (personal data) by the Licensor in this matter as this remains its their full liability.

Appears in 1 contract

Samples: License Agreement

Licensor-Administered Authentication. Where the Licensor provides alternative methods of access and authentication beyond the Licensee-administered methods described herein, e.g. by allowing users to establish a personal login from an on-campus IP address (thereby enabling access via username and password when logging in to a website of the Licensor) or device authentication, which affiliates the device or application by use of a token, cookie, or vendor- vendor-managed proxy prefix, neither the Licensee nor any Participating Institution will be responsible or liable for claims of breach or validity of such use. Neither the Licensee nor any of the Participating Institutions shall be responsible or liable for the processing of personally identifiable information (personal data) by the Licensor in this matter as this remains its full liability.

Appears in 1 contract

Samples: License Agreement

Licensor-Administered Authentication. Where the Licensor provides alternative methods of access and authentication beyond the Licensee-administered methods described hereinIP addresses pursuant to Section (b), e.g. by allowing users to establish a personal login from an on-on- campus IP address (thereby enabling access via username and password when logging in to a website of the Licensor) or device authentication, which affiliates the device or application by use of a token, cookie, or vendor- vendor-managed proxy prefix, neither the Licensee nor any Participating Institution will be responsible or liable for claims of breach or validity of such use. Neither the Licensee nor any of the Participating Institutions shall be responsible or liable for the processing of personally identifiable information (personal data) by the Licensor in this matter as this remains its full liability.

Appears in 1 contract

Samples: License Agreement

Time is Money Join Law Insider Premium to draft better contracts faster.