GENERAL EXCLUSIONS We do not insure for loss caused directly or indirectly by any of the following. Such loss is excluded regardless of any other cause or event contributing concurrently or in any sequence to the loss. These exclusions apply whether or not the loss event results in widespread damage or affects a substantial area.
LIMITATION AND EXCLUSION OF LIABILITY 1. 6. 1. Traction Software Limited does not exclude its liability (if any) to you:
1. 6. 1. 1. for personal injury or death resulting from Traction Software Limited’s negligence;
2. 6. 1. 2. for any matter for which it would be illegal for Traction Software Limited to exclude or to attempt to exclude its liability; or
3. 6. 1. 3. for fraud.
2. 6. 2. Traction Software Limited makes no express warranties with respect to the Software and Traction Software Limited hereby excludes (to the fullest extent permissible in law), all conditions, warranties (including without limitation any warranty that the Software will meet your requirements or that its operation will be uninterrupted or error free) and stipulations, express (other than those set out in this License) or implied, statutory, customary or otherwise which, but for such exclusion, would or might subsist in favour of you. Except as set out in this License you assume the entire risk as to the quality and performance of the Software.
3. 6. 3. Subject to clause 6. 1 Traction Software Limited will be under no liability to you whatsoever (whether in contract, tort (including negligence), breach of statutory duty, restitution or otherwise) for any injury, death, damage or direct, indirect or consequential loss (all three of which terms include, without limitation, pure economic loss, loss of profits, loss of business, loss of data, loss of savings, depletion of goodwill and like loss) howsoever caused arising out of or in connection with:
1. 6. 3. 1. the Software, or the manufacture or sale or supply, or failure or delay in supply, of the Software by Traction Software Limited or on the part of Traction Software Limited’s employees, agents or sub-contractors;
2. 6. 3. 2. any breach by Traction Software Limited of any of the express or implied terms of this License;
3. 6. 3. 3. any use made of the Software; or
4. 6. 3. 4. any statement made or not made, or advice given or not given, by or on behalf of Traction Software Limited.
4. 6. 4. Subject to clause 6. 1 and without prejudice to clauses 6. 2 and 6. 3 , Traction Software Limited’s aggregate liability under this License(whether in contract, tort (including negligence), breach of statutory duty, restitution or otherwise) for any injury, death, damage or direct or consequential loss (all three of which terms include without limitation of profits, loss of business, depletion of goodwill and like loss) howsoever caused (other than for death or personal injury caused by Traction Software Limited’s negligence) will be limited to the higher of the price paid by you to use the Software or USD $1 00.
5. 6. 5. You acknowledge that the above provisions of this clause 6 are reasonable given the charges made (if any) for the Software and you will accept such risk and/or insure accordingly.
6. 6. 6. Any rights that you have as a consumer are not affected by this clause 6.
Applicable Law and Exclusive Forum The validity, interpretation, and performance of this Agreement and of the Warrants shall be governed in all respects by the laws of the State of New York. Subject to applicable law, the Company hereby agrees that any action, proceeding or claim against it arising out of or relating in any way to this Agreement shall be brought and enforced in the courts of the State of New York or the United States District Court for the Southern District of New York, and irrevocably submits to such jurisdiction, which jurisdiction shall be exclusive forum for any such action, proceeding or claim. The Company hereby waives any objection to such exclusive jurisdiction and that such courts represent an inconvenient forum. Notwithstanding the foregoing, the provisions of this paragraph will not apply to suits brought to enforce any liability or duty created by the Exchange Act or any other claim for which the federal district courts of the United States of America are the sole and exclusive forum. Any person or entity purchasing or otherwise acquiring any interest in the Warrants shall be deemed to have notice of and to have consented to the forum provisions in this Section 9.3. If any action, the subject matter of which is within the scope the forum provisions above, is filed in a court other than a court located within the State of New York or the United States District Court for the Southern District of New York (a “foreign action”) in the name of any warrant holder, such warrant holder shall be deemed to have consented to: (x) the personal jurisdiction of the state and federal courts located within the State of New York or the United States District Court for the Southern District of New York in connection with any action brought in any such court to enforce the forum provisions (an “enforcement action”), and (y) having service of process made upon such warrant holder in any such enforcement action by service upon such warrant holder’s counsel in the foreign action as agent for such warrant holder.
Standard of Care; Uncontrollable Events; Limitation of Liability SMC shall use reasonable professional diligence to ensure the accuracy of all services performed under this Agreement, but shall not be liable to the Company for any action taken or omitted by SMC in the absence of bad faith, willful misfeasance, negligence or reckless disregard by it of its obligations and duties. The duties of SMC shall be confined to those expressly set forth herein, and no implied duties are assumed by or may be asserted against SMC hereunder. SMC shall maintain adequate and reliable computer and other equipment necessary or appropriate to carry out its obligations under this Agreement. Upon the Company's reasonable request, SMC shall provide supplemental information concerning the aspects of its disaster recovery and business continuity plan that are relevant to the services provided hereunder. Notwithstanding the foregoing or any other provision of this Agreement, SMC assumes no responsibility hereunder, and shall not be liable for, any damage, loss of data, delay or any other loss whatsoever caused by events beyond its reasonable control. Events beyond SMC's reasonable control include, without limitation, force majeure events. Force majeure events include natural disasters, actions or decrees of governmental bodies, and communication lines failures that are not the fault of either party. In the event of force majeure, computer or other equipment failures or other events beyond its reasonable control, SMC shall follow applicable procedures in its disaster recovery and business continuity plan and use all commercially reasonable efforts to minimize any service interruption. SMC shall provide the Company, at such times as the Company may reasonably require, copies of reports rendered by independent public accountants on the internal controls and procedures of SMC relating to the services provided by SMC under this Agreement. Notwithstanding anything in this Agreement to the contrary, in no event shall SMC, its affiliates or any of its or their directors, officers, employees, agents or subcontractors be liable for exemplary, punitive, special, incidental, indirect or consequential damages, or lost profits, each of which is hereby excluded by agreement of the parties regardless of whether such damages were foreseeable or whether either party or any entity has been advised of the possibility of such damages.
Limitation of Vendor Indemnification and Similar Clauses This is a requirement of the TIPS Contract and is non-negotiable TIPS, a department of Region 8 Education Service Center, a political subdivision, and local government entity of the State of Texas, is prohibited from indemnifying third-parties (pursuant to the Article 3, Section 52 of the Texas Constitution) except as otherwise specifically provided for by law or as ordered by a court of competent jurisdiction. Article 3, Section 52 of the Texas Constitution states that "no debt shall be created by or on behalf of the State … " and the Texas Attorney General has opined that a contractually imposed obligation of indemnity creates a "debt" in the constitutional sense. Tex. Att'y Gen. Op. No. MW-475 (1982). Thus, contract clauses which require TIPS to indemnify Vendor, pay liquidated damages, pay attorney's fees, waive Vendor's liability, or waive any applicable statute of limitations must be deleted or qualified with ''to the extent permitted by the Constitution and Laws of the State of Texas." Does Vendor agree? Yes, I Agree TIPS, a department of Region 8 Education Service Center, a political subdivision, and local government entity of the State of Texas, does not agree to binding arbitration as a remedy to dispute and no such provision shall be permitted in this Agreement with TIPS. Vendor agrees that any claim arising out of or related to this Agreement, except those specifically and expressly waived or negotiated within this Agreement, may be subject to non-binding mediation at the request of either party to be conducted by a mutually agreed upon mediator as prerequisite to the filing of any lawsuit arising out of or related to this Agreement. Mediation shall be held in either Camp or Titus County, Texas. Agreements reached in mediation will be subject to the approval by the Region 8 ESC's Board of Directors, authorized signature of the Parties if approved by the Board of Directors, and, once approved by the Board of Directors and properly signed, shall thereafter be enforceable as provided by the laws of the State of Texas. Does Vendor agree? Yes, Vendor agrees Does Vendor agree? Yes, Vendor agrees Vendor agrees that nothing in this Agreement shall be construed as a waiver of sovereign or government immunity; nor constitute or be construed as a waiver of any of the privileges, rights, defenses, remedies, or immunities available to Region 8 Education Service Center or its TIPS Department. The failure to enforce, or any delay in the enforcement, of any privileges, rights, defenses, remedies, or immunities available to Region 8 Education Service Center or its TIPS Department under this Agreement or under applicable law shall not constitute a waiver of such privileges, rights, defenses, remedies, or immunities or be considered as a basis for estoppel. Does Vendor agree? Yes, Vendor agrees Vendor agrees that TIPS and TIPS Members shall not be liable for interest or late-payment fees on past-due balances at a rate higher than permitted by the laws or regulations of the jurisdiction of the TIPS Member. Funding-Out Clause: Vendor agrees to abide by the applicable laws and regulations, including but not limited to Texas Local Government Code § 271.903, or any other statutory or regulatory limitation of the jurisdiction of any TIPS Member, which requires that contracts approved by TIPS or a TIPS Member are subject to the budgeting and appropriation of currently available funds by the entity or its governing body.
PROCEDURE FOR NOTIFICATION AND APPLICATION FOR INDEMNIFICATION (a) Indemnitee agrees to notify promptly the Company in writing upon being served with any summons, citation, subpoena, complaint, indictment, information or other document relating to any Proceeding, claim, issue or matter therein which may be subject to indemnification, hold harmless or exoneration rights, or advancement of Expenses covered hereunder. The failure of Indemnitee to so notify the Company shall not relieve the Company of any obligation which it may have to Indemnitee under this Agreement, or otherwise.
(b) Indemnitee may deliver to the Company a written application to indemnify, hold harmless or exonerate Indemnitee in accordance with this Agreement. Such application(s) may be delivered from time to time and at such time(s) as Indemnitee deems appropriate in his or her sole discretion. Following such a written application for indemnification by Indemnitee, Indemnitee’s entitlement to indemnification shall be determined according to Section 12(a) of this Agreement.
New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to:
(1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute;
(2) Limit unsuccessful logon attempts;
(3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions;
(4) Authorize wireless access prior to allowing such connections;
(5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity;
(6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions;
(7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles;
(8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services;
(9) Enforce a minimum password complexity and change of characters when new passwords are created;
(10) Perform maintenance on organizational systems;
(11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance;
(12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1;
(13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital;
(14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse;
(15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas;
(16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems;
(17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems;
(18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception);
(19) Protect the confidentiality of Student Data at rest;
(20) Identify, report, and correct system flaws in a timely manner;
(21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems;
(22) Monitor system security alerts and advisories and take action in response; and
(23) Update malicious code protection mechanisms when new releases are available.
Governance and Anticorruption The Borrower, the Project Executing Agency, and the implementing agencies shall (a) comply with ADB’s Anticorruption Policy (1998, as amended to date) and acknowledge that ADB reserves the right to investigate directly, or through its agents, any alleged corrupt, fraudulent, collusive or coercive practice relating to the Project; and
Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-‐level domain strings across the Internet, certain top-‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.
Rights Protection Mechanisms and Abuse Mitigation ‐ Registry Operator commits to implementing and performing the following protections for the TLD:
i. In order to help registrars and registrants identify inaccurate data in the Whois database, Registry Operator will audit Whois data for accuracy on a statistically significant basis (this commitment will be considered satisfied by virtue of and for so long as ICANN conducts such audits).
ii. Work with registrars and registrants to remediate inaccurate Whois data to help ensure a more accurate Whois database. Registry Operator reserves the right to cancel a domain name registration on the basis of inaccurate data, if necessary.
iii. Establish and maintain a Domains Protected Marks List (DPML), a trademark protection service that allows rights holders to reserve registration of exact match trademark terms and terms that contain their trademarks across all gTLDs administered by Registry Operator under certain terms and conditions.
iv. At no cost to trademark holders, establish and maintain a Claims Plus service, which is a notice protection mechanism that begins at the end of ICANN’s mandated Trademark Claims period.
v. Bind registrants to terms of use that define and prohibit illegal or abusive activity.
vi. Limit the use of proxy and privacy registration services in cases of malfeasance.
vii. Consistent with the terms of this Registry Agreement, reserve the right to exclude from distribution any registrars with a history of non-‐compliance with the terms of the Registrar Accreditation Agreement.
viii. Registry Operator will be properly resourced to perform these protections.
