Grant of Security Interest In order to secure the Obligations Sample Clauses

Grant of Security Interest In order to secure the Obligations each Pledgor grants a Lien in, pledges and assigns the following collateral, whether now existing or hereafter acquired or arising (the “Collateral”), to the Administrative Agent: (a) the Guarantor’s rights, under the Fund Documents, to the Capital Commitments and Capital Contributions of each Investor; (b) the Guarantor’s rights, under the Fund Documents, to make Capital Calls and enforce each Investor’s obligation to make Capital Contributions; (c) all of the Guarantor’s rights, titles, and interests in each Collateral Account, any successor or substitute accounts, all funds therein or credited xxxxxxx, and all documents evidencing each account; and (d) all proceeds of the foregoing. 2.
AutoNDA by SimpleDocs

Related to Grant of Security Interest In order to secure the Obligations

  • Priority of Agreements This DPA shall govern the treatment of Student Data in order to comply with the privacy protections, including those found in FERPA and all applicable privacy statutes identified in this DPA. In the event there is conflict between the terms of the DPA and the Service Agreement, Terms of Service, Privacy Policies, or with any other bid/RFP, license agreement, or writing, the terms of this DPA shall apply and take precedence. In the event of a conflict between Exhibit H, the SDPC Standard Clauses, and/or the Supplemental State Terms, Exhibit H will control, followed by the Supplemental State Terms. Except as described in this paragraph herein, all other provisions of the Service Agreement shall remain in effect.

  • Liens Create, incur, assume or suffer to exist any Lien upon any of its property, assets or revenues, whether now owned or hereafter acquired, other than the following:

  • Data Security The Provider agrees to utilize administrative, physical, and technical safeguards designed to protect Student Data from unauthorized access, disclosure, acquisition, destruction, use, or modification. The Provider shall adhere to any applicable law relating to data security. The provider shall implement an adequate Cybersecurity Framework based on one of the nationally recognized standards set forth set forth in Exhibit “F”. Exclusions, variations, or exemptions to the identified Cybersecurity Framework must be detailed in an attachment to Exhibit “H”. Additionally, Provider may choose to further detail its security programs and measures that augment or are in addition to the Cybersecurity Framework in Exhibit “F”. Provider shall provide, in the Standard Schedule to the DPA, contact information of an employee who XXX may contact if there are any data security concerns or questions.

  • Student Data Property of LEA All Student Data transmitted to the Provider pursuant to the Service Agreement is and will continue to be the property of and under the control of the LEA. The Provider further acknowledges and agrees that all copies of such Student Data transmitted to the Provider, including any modifications or additions or any portion thereof from any source, are subject to the provisions of this DPA in the same manner as the original Student Data. The Parties agree that as between them, all rights, including all intellectual property rights in and to Student Data contemplated per the Service Agreement, shall remain the exclusive property of the LEA. For the purposes of FERPA, the Provider shall be considered a School Official, under the control and direction of the LEA as it pertains to the use of Student Data, notwithstanding the above.

  • Termination of Contract The Department may terminate the Contract for refusal by the Contractor to comply with this section by not allowing access to all public records, as defined in Chapter 119, F. S., made or received by the Contractor in conjunction with the Contract.

  • Conditions Precedent The effectiveness of this Amendment is subject to the satisfaction of all of the following conditions precedent:

  • NOTE For Community-­‐Based TLDs Only] Obligations of Registry Operator to TLD Community. Registry Operator shall establish registration policies in conformity with the application submitted with respect to the TLD for: (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the community-­‐based TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies. Registry Operator agrees to implement and be bound by the Registry Restrictions Dispute Resolution Procedure as set forth at [insert applicable URL] with respect to disputes arising pursuant to this Section 2.19. Registry Operator shall implement and comply with the community registration policies set forth on Specification 12 attached hereto.]

  • Security Notwithstanding anything herein to the contrary, except for Section 27, to the extent requested by Indemnitee and approved by the Board, the Company may at any time and from time to time provide security to Indemnitee for the Company’s obligations hereunder through an irrevocable bank line of credit, funded trust or other collateral. Any such security, once provided to Indemnitee, may not be revoked or released without the prior written consent of Indemnitee.

  • Events of Default Any of the following shall constitute an Event of Default:

  • Debts and Delinquencies Contractor agrees that any payments due under this Contract shall be applied towards any debt or delinquency that is owed to the State of Texas.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!