Other Services and Exclusions
Other Services and Exclusions Sample Clauses
Related to Other Services and Exclusions
Limitations and Exclusions The limitation and exclusion in this Section 8 shall not apply: (i) to the extent that liability cannot be limited or excluded according to the Applicable Law; (ii) in cases of our willful misconduct and gross negligence; (iii) in cases of bodily injuries or death caused by our negligence; and (iv) in cases of our fraud or fraudulent misrepresentation.
Conditions and Exclusions Notwithstanding anything to the contrary set forth in this SLA, this SLA and Customer’s entitlement to the remedies set out in this SLA are subject to the following conditions and exclusions:
Warranty and Exclusions If you paid a charge for the IBM SaaS then the Section 17 Warranty and Exclusions is replaced in its entirety by the following:
Warranties and Exclusions 6.1 Accenture warrants that the SaaS Services provided to Client pursuant to the Agreement will comply in all material respects with the Documentation. This warranty shall not apply where: (i) the Client’s or any Authorized User's access or use of the SaaS Services is not in accordance with the Agreement or with Accenture’s instructions; (ii) modification or alteration of the SaaS Services or any systems, software or other content or materials embodied therein is made by any Party other than Accenture; or (iii) the SaaS Services are being provided free of charge, or as a trial, pre-release or as a beta release.
Monopolies and Exclusive Service Suppliers 1. Each Party shall ensure that any monopoly supplier of a service in its territory does not, in the supply of the monopoly service in the relevant market, act in a manner inconsistent with that Party's obligations under specific commitments in its Schedule in Annex III (Schedule of Specific Commitments on Trade in Services).
Scope of Limitations and Exclusions The limitation and exclusion in this Section 8 shall not apply: (i) to the extent that liability cannot be limited or excluded according to Applicable Law; (ii) in cases of willful misconduct and gross negligence; (iii) in cases of bodily injuries or death caused by our negligence; and (iv) in cases of fraud or fraudulent misrepresentation. In cases of gross negligence, liability is limited to the amount of foreseeable loss that would have been prevented through the exercise of due care.
Limitations and exclusions of liability 16.1 Nothing in this Agreement will:
LIMITATION AND EXCLUSION OF LIABILITY 1. 6. 1. Traction Software Limited does not exclude its liability (if any) to you:
Exclusion of Products and Services If a deliverable or service that is subject to this Agreement is deleted, lost, stolen, destroyed, damaged, sold, replaced, or otherwise disposed of, the CPO may exclude it from the operation of this Agreement by notifying Contractor in writing. The notice takes effect immediately on its receipt by Contractor. More than one notice may be given. When a notice is received, Contractor shall delete the charge for the excluded deliverable or service from the sum(s) otherwise due under this Agreement.
Requester and Approved User Responsibilities The Requester agrees through the submission of the DAR that the PI named has reviewed and understands the principles for responsible research use and data management of the genomic datasets as defined in the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. The Requester and Approved Users further acknowledge that they are responsible for ensuring that all uses of the data are consistent with national, tribal, and state laws and regulations, as appropriate, as well as relevant institutional policies and procedures for managing sensitive genomic and phenotypic data. The Requester certifies that the PI is in good standing (i.e., no known sanctions) with the institution, relevant funding agencies, and regulatory agencies and is eligible to conduct independent research (i.e., is not a postdoctoral fellow, student, or trainee). The Requester and any Approved Users may use the dataset(s) only in accordance with the parameters described on the study page and in the 1 If contractor services are to be utilized, PI requesting the data must provide a brief description of the services that the contractor will perform for the PI (e.g., data cleaning services) in the research use statement of the DAR. Additionally, the Key Personnel section of the DAR must include the name of the contractor’s employee(s) who will conduct the work. These requirements apply whether the contractor carries out the work at the PI’s facility or at the contractor’s facility. In addition, the PI is expected to include in any contract agreement requirements to ensure that any of the contractor’s employees who have access to the data adhere to the NIH GDS Policy, this Data Use Certification Agreement, and the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. Note that any scientific collaborators, including contractors, who are not at the Requester must submit their own DAR. Addendum to this Agreement for the appropriate research use, as well as any limitations on such use, of the dataset(s), as described in the DAR, and as required by law. Through the submission of this DAR, the Requester and Approved Users acknowledge receiving and reviewing a copy of the Addendum which includes Data Use Limitation(s) for each dataset requested. The Requester and Approved Users agree to comply with the terms listed in the Addendum. Through submission of the DAR, the PI and Requester agree to submit a Project Renewal or Project Close-out prior to the expiration date of the one (1) year data access period. The PI also agrees to submit an annual Progress Update prior to the one (1) year anniversary2 of the project, as described under Research Use Reporting (Term 10) below. By approving and submitting the attached DAR, the Institutional Signing Official provides assurance that relevant institutional policies and applicable local, state, tribal, and federal laws and regulations, as applicable, have been followed, including IRB approval, if required. Approved Users may be required to have IRB approval if they have access to personal identifying information for research participants in the original study at their institution, or through their collaborators. The Institutional Signing Official also assures, through the approval of the DAR, that other institutional departments with relevant authorities (e.g., those overseeing human subjects research, information technology, technology transfer) have reviewed the relevant sections of the NIH GDS Policy and the associated procedures and are in agreement with the principles defined. The Requester acknowledges that controlled-access datasets subject to the NIH GDS Policy may be updated to exclude or include additional information. Unless otherwise indicated, all statements herein are presumed to be true and applicable to the access and use of all versions of these datasets.
