Exclusion of Indirect Sample Clauses

Exclusion of Indirect. Damages Subject to section the “Limitation of Restrictions” section below, in no event shall either party have any liability to the other party under or in relation to this Agreement whether in contract, tort or under any other theory of liability for:
AutoNDA by SimpleDocs
Exclusion of Indirect. Damages No Contractor shall be responsible to another for indirect or consequential loss or damages such as but not limited to loss of profit, loss of revenue, or loss of contracts.

Related to Exclusion of Indirect

  • EXCLUSION OF INDIRECT DAMAGES EXCEPT WITH RESPECT TO CUSTOMER’S ACCESS TO OR DISCLOSURE OF THE APPLICATION OTHER THAN IN COMPLIANCE WITH THE LICENSE GRANTED IN THIS AGREEMENT, NEITHER PARTY WILL BE LIABLE TO THE OTHER PARTY (NOR TO ANY PERSON CLAIMING RIGHTS DERIVED FROM THE OTHER PARTY’S RIGHTS) FOR INCIDENTAL, INDIRECT, CONSEQUENTIAL, SPECIAL, PUNITIVE, OR EXEMPLARY DAMAGES OF ANY KIND (INCLUDING LOST PROFITS, LOSS OF OR DAMAGE TO DATA, LOSS OF BUSINESS, OR OTHER ECONOMIC DAMAGE), WHETHER ARISING IN CONTRACT, TORT (INCLUDING NEGLIGENCE) OR OTHERWISE, AND REGARDLESS OF WHETHER THE PARTY LIABLE OR ALLEGEDLY LIABLE WAS ADVISED, HAD OTHER REASON TO KNOW, SHOULD HAVE ANTICIPATED, OR IN FACT KNEW OF THE POSSIBILITY THEREOF. IN NO EVENT SHALL EITHER PARTY BE LIABLE FOR COSTS OF PROCUREMENT OF SUBSTITUTE GOODS BY ANYONE. THE PROVISIONS OF THIS PARAGRAPH ARE INDEPENDENT OF, SEVERABLE FROM, AND TO BE ENFORCED INDEPENDENTLY OF ANY OTHER ENFORCEABLE OR UNENFORCEABLE PROVISION OF THIS AGREEMENT.

  • Notification of Illness Nurses should notify the Medical Center of absence from work because of illness as far in advance as possible, but at least three and one-half (3 ½) hours before the start of the nurse’s shift. Repeated failure to give such minimum notification will result in reduction of otherwise payable sick leave for that shift by two (2) hours. Repeated failure as used in this section means more than twice every two years.

  • Limitation of Indemnity 31.3.1 Subject to Clause 31.9, an indemnity by either Party under any provision of this Agreement will be without limitation to any indemnity by that Party under any other provision of this Agreement.

  • Notification of Incidents If Contractor becomes aware of or has reasonable suspicion of a privacy incident or security incident regarding any State data, Contractor must report such incident to the State and the State Chief Information Security Officer as soon as possible, but no later than twenty-four (24) hours after such incident. The decision to notify the affected data subjects and the form of such notice following report of a privacy incident or security incident are the responsibility of the State. Notwithstanding anything to the contrary in this Contract, Contractor will indemnify, hold harmless and defend the State and its officers, and employees for and against any claims, damages, costs and expenses related to any privacy incident or security incident involving any State data. For purposes of clarification, the foregoing sentence shall in no way limit or diminish Contractor’s obligation(s) to indemnify, save, hold harmless, or defend the State under any other term of this Contract. Contractor will reasonably mitigate any harmful effects resulting from any privacy incident or security incident involving any State data.

  • Notification of Individuals To notify individuals of the breach or unauthorized use or disclosure when notification is required under state or federal law and to pay any costs of such notifications, as well as any costs associated with the breach. The County Compliance Manager shall approve the time, manner and content of any such notifications.

  • Verification of Illness Written verification by an approved licensed medical practitioner or other satisfactory proof of illness or family illness may be required at the discretion of the department head.

  • Indemnification of ICANN (a) Registry Operator shall indemnify and defend ICANN and its directors, officers, employees, and agents (collectively, “Indemnitees”) from and against any and all third-­‐party claims, damages, liabilities, costs, and expenses, including reasonable legal fees and expenses, arising out of or relating to intellectual property ownership rights with respect to the TLD, the delegation of the TLD to Registry Operator, Registry Operator’s 1 Subject to further approvals. operation of the registry for the TLD or Registry Operator’s provision of Registry Services, provided that Registry Operator shall not be obligated to indemnify or defend any Indemnitee to the extent the claim, damage, liability, cost or expense arose: (i) due to the actions or omissions of ICANN, its subcontractors, panelists or evaluators specifically related to and occurring during the registry TLD application process (other than actions or omissions requested by or for the benefit of Registry Operator), or (ii) due to a breach by ICANN of any obligation contained in this Agreement or any willful misconduct by ICANN. This Section shall not be deemed to require Registry Operator to reimburse or otherwise indemnify ICANN for costs associated with the negotiation or execution of this Agreement, or with monitoring or management of the parties’ respective obligations hereunder. Further, this Section shall not apply to any request for attorney’s fees in connection with any litigation or arbitration between or among the parties, which shall be governed by Article 5 or otherwise awarded by a court of competent jurisdiction or arbitrator. [Alternative Section 7.1(a) text for intergovernmental organizations or governmental entities: “Registry Operator shall use its best efforts to cooperate with ICANN in order to ensure that ICANN does not incur any costs associated with claims, damages, liabilities, costs and expenses, including reasonable legal fees and expenses, arising out of or relating to intellectual property ownership rights with respect to the TLD, the delegation of the TLD to Registry Operator, Registry Operator’s operation of the registry for the TLD or Registry Operator’s provision of Registry Services, provided that Registry Operator shall not be obligated to provide such cooperation to the extent the claim, damage, liability, cost or expense arose due to a breach by ICANN of any of its obligations contained in this Agreement or any willful misconduct by ICANN. This Section shall not be deemed to require Registry Operator to reimburse or otherwise indemnify ICANN for costs associated with the negotiation or execution of this Agreement, or with monitoring or management of the parties’ respective obligations hereunder. Further, this Section shall not apply to any request for attorney’s fees in connection with any litigation or arbitration between or among the parties, which shall be governed by Article 5 or otherwise awarded by a court of competent jurisdiction or arbitrator.”]

  • Protection of Investments 1. All investments, whether direct or indirect, made by investors of one Contracting Party shall enjoy a fair and equitable treatment in the territory of the other Contracting Party.

  • Separation of Insureds All liability policies shall provide cross-liability coverage as would be afforded by the standard ISO (Insurance Services Office, Inc.) separation of insureds provision with no insured versus insured exclusions or limitations.

  • TERMINATION OF INSURANCE A. Your policy will lapse if you do not pay your premium when due.

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