Common use of OSS AND THIRD PARTY LICENSING CONSIDERATIONS Clause in Contracts

OSS AND THIRD PARTY LICENSING CONSIDERATIONS. Developer understands and agrees that BlackBerry shall not be responsible or liable for the Third-Party Commercial Software or Open Source Software, nor will BlackBerry warrant or support such software. Developer’s access and use of the Third-Party Commercial Software or Open Source Software, and any liability, responsibility, warranties, or support are expressly disclaimed by BlackBerry.

Appears in 3 contracts

Samples: QNX Development License Agreement, QNX Development License Agreement, QNX Development License Agreement

AutoNDA by SimpleDocs

OSS AND THIRD PARTY LICENSING CONSIDERATIONS. Developer Customer understands and agrees that BlackBerry shall not be responsible or liable for the Third-Party Commercial Software or Open Source Software, nor will BlackBerry warrant or support such software. DeveloperCustomer’s access and use of the Third-Party Commercial Software or Open Source Software, and any liability, responsibility, warranties, warranties or support are expressly disclaimed by BlackBerry.

Appears in 2 contracts

Samples: QNX Development License Agreement, QNX Development License Agreement

OSS AND THIRD PARTY LICENSING CONSIDERATIONS. Developer Notwithstanding anything else herein, Partner understands and agrees that BlackBerry shall not be responsible or liable for the Third-Party Commercial Software or Open Source Software, nor will BlackBerry warrant or support such software. DeveloperPartner’s access and use of the Third-Party Commercial Software or Open Source Software, and any liability, responsibility, warranties, or support are expressly disclaimed by BlackBerry.

Appears in 2 contracts

Samples: QNX Development License Agreement, QNX Development License Agreement

OSS AND THIRD PARTY LICENSING CONSIDERATIONS. Developer Notwithstanding anything else herein, Customer understands and agrees that BlackBerry shall not be responsible or liable for the Third-Party Commercial Software or Open Source Software, nor will BlackBerry warrant or support such software. DeveloperCustomer’s access and use of the Third-Party Commercial Software or Open Source Software, and any liability, responsibility, warranties, or support are expressly disclaimed by BlackBerry.

Appears in 2 contracts

Samples: QNX Development License Agreement, QNX Development License Agreement

AutoNDA by SimpleDocs

OSS AND THIRD PARTY LICENSING CONSIDERATIONS. Developer Customer understands and agrees that BlackBerry shall not be responsible or liable for the Third-Party Commercial Software or Open Source Software, nor will BlackBerry warrant or support such software. DeveloperCustomer’s access and use of the Third-Party Commercial Software or Open Source Software, and any liability, responsibility, warranties, or support are expressly disclaimed by BlackBerry.

Appears in 1 contract

Samples: QNX Development License Agreement

OSS AND THIRD PARTY LICENSING CONSIDERATIONS. Developer Partner understands and agrees that BlackBerry shall not be responsible or liable for the Third-Party Commercial Software or Open Source Software, nor will BlackBerry warrant or support such software. DeveloperPartner’s access and use of the Third-Party Commercial Software or Open Source Software, and any liability, responsibility, warranties, or support are expressly disclaimed by BlackBerry.

Appears in 1 contract

Samples: QNX Development License Agreement

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