Internap Obligations Clause Samples

Internap Obligations. Buyer and Internap shall be solidarily (within the meaning of the Civil Code of Québec) liable for all obligations under this Agreement and Internap hereby absolutely, unconditionally and irrevocably guarantees to the Sellers the due and punctual performance of all of the obligations of Buyer under this Agreement. The liabilities and obligations of Internap are subject to the terms of this Agreement and will not exceed any liability or obligation of Buyer to the Sellers under this Agreement. Internap is entitled to all rights, privileges and defenses available to Buyer with respect to any obligations or liability, including all provisions of this Agreement relating to limitation of liability and resolution of disputes. Internap hereby irrevocably waives any benefit of discussion or division and agrees that its liability under this guarantee shall be absolute and unconditional irrespective of any other circumstance which might otherwise constitute a defense available to or a legal discharge of Internap, except to the extent that such circumstance constitutes a defense for Buyer.
View Source

Related to Internap Obligations

  • Swap Obligations Neither the Company nor any of its Subsidiaries has incurred any outstanding obligations under any Swap Contracts, other than Permitted Swap Obligations. The Company has undertaken its own independent assessment of its consolidated assets, liabilities and commitments and has considered appropriate means of mitigating and managing risks associated with such matters and has not relied on any swap counterparty or any Affiliate of any swap counterparty in determining whether to enter into any Swap Contract.

  • ▇▇▇▇▇ OBLIGATIONS A ▇▇▇▇▇▇▇'s acceptance of funds directly under the Grant or indirectly through a subaward acts as acceptance of the authority of the State, under the direction of the legislative audit committee, to conduct an audit or investigation in connection with those funds. In accordance with the legislative audit committee, DFPS can request any documentation, at any time, to be sent to DFPS to a location DFPS chooses. Examples of documentation that DFPS may request include, but are not limited to: 1. Participant files in their entirety. This includes, but is not limited to: a. Progress notes. b. Action plans. c. Registration forms. d. Surveys. e. Sign-in sheets. f. Monthly tracking forms.

  • Processor Obligations 4.1 The Processor may collect, process or use Personal Data only within the scope of this DPA. 4.2 The Processor confirms that it shall process Personal Data on behalf of the Controller and shall take steps to ensure that any natural person acting under the authority of the Processor who has access to Personal Data shall only process the Personal Data on the documented instructions of the Controller. 4.3 The Processor shall promptly inform the Controller, if in the Processor’s opinion, any of the instructions regarding the processing of Personal Data provided by the Controller, breach any Data Protection Law. 4.4 The Processor shall ensure that all employees, agents, officers and contractors involved in the handling of Personal Data: (i) are aware of the confidential nature of the Personal Data and are contractually bound to keep the Personal Data confidential; (ii) have received appropriate training on their responsibilities as a data processor; and (iii) are bound by the terms of this DPA. 4.5 The Processor shall implement appropriate technical and organisational procedures to protect Personal Data, taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons. 4.6 The Processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate: (i) the pseudonymisation and encryption of Personal Data; (ii) the ability to ensure the on-going confidentiality, integrity, availability and resilience of processing systems and services; (iii) the ability to restore the availability and access to Personal Data in a timely manner in the event of a physical or technical incident; (iv) a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing. In accessing the appropriate level of security, account shall be taken in particular of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data transmitted, stored or otherwise processed. 4.7 The technical and organisational measures detailed in Exhibit B shall be at all times adhered to as a minimum security standard. The Controller accepts and agrees that the technical and organisational measures are subject to development and review and that the Processor may use alternative suitable measures to those detailed in the attachments to this DPA. 4.8 The Controller acknowledges and agrees that, in the course of providing the Services to the Controller, it may be necessary for the Processor to access the Personal Data to respond to any technical problems or Controller queries and to ensure the proper working of the Services. All such access by the Processor will be limited to those purposes.

  • ENTERPRISE SERVICES’ OBLIGATION In the event that Enterprise Services receives a public records disclosure request pertaining to records that Contractor has submitted and marked either as (a) statutorily exempt from disclosure; or (b) sensitive, Enterprise Services, prior to disclosure, will do the following: Enterprise Services’ Public Records Officer will review any records marked by Contractor as statutorily exempt from disclosure. In those situations, where the designation comports with the stated statutory exemption from disclosure, Enterprise Services will redact or withhold the record(s) as appropriate. For records marked ‘sensitive’ or for records where Enterprise Services determines that no statutory exemption to disclosure applies or is unable to determine whether the stated statutory exemption to disclosure properly applies, Enterprise Services will notify Contractor, at the address provided in the Contract, of the public records disclosure request and identify the date that Enterprise Services intends to release the record(s) (including records marked ‘sensitive’ or exempt from disclosure) to the requester unless Contractor, at Contractor’s sole expense, timely obtains a court order enjoining Enterprise Services from such disclosure. In the event Contractor fails to timely file a motion for a court order enjoining such disclosure, Enterprise Services will release the requested record(s) on the date specified. Contractor’s failure properly to identify exempted or sensitive information or timely respond after notice of request for public disclosure has been given shall be deemed a waiver by Contractor of any claim that such records are exempt or protected from public disclosure.

  • Third Party Obligations 3.1. The THIRD PARTY shall:- 3.1.1. not divulge the Confidential Information to any party other than as provided for in this Confidentiality Agreement; 3.1.2. use the Confidential Information only for the purposes necessary in providing the services for which he is engaged by the AUTHORITY; and 3.1.3. make no commercial use of the Confidential Information or any part thereof. 3.2. Notwithstanding the foregoing, the THIRD PARTY shall be entitled to make any disclosure required by law of the Confidential Information and shall notify the AUTHORITY of so doing in accordance with the provisions of paragraph 6.