When SBA Sample Clauses

When SBA is the holder of the Note, this document and all documents evidencing or securing this Loan will be construed in accordance with federal law.
AutoNDA by SimpleDocs
When SBA is the holder of the Note, this Agreement will be construed and enforced under federal law, including SBA regulations. Secured Party or SBA may use state or local procedures for filing papers, recording documents, giving notice, enforcing security interests or liens, and for any other purposes. By using such procedures, SBA does not waive any federal immunity from state or local control, penalty, tax or liability. As to this Agreement, Borrower may not claim or assert any local or state law against SBA to deny any obligation, defeat any claim of SBA, or preempt federal law.

Related to When SBA

  • Note for Victorian customers In Victoria, a retailer must obtain a customer’s ‘explicit informed consent’ to base the customer’s bill on an estimation, unless the meter cannot be read or the metering data is not obtained.

  • Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.

  • Attachment  C_ CONTRACT AFFIRMATIONS For purposes of these Contract Affirmations, HHS includes both the Health and Human Services Commission (HHSC) and the Department of State Health Services (DSHS). System Agency refers to HHSC, DSHS, or both, that will be a party to this Contract. These Contract Affirmations apply to all Contractors and Grantees (referred to as “Contractor”) regardless of their business form (e.g., individual, partnership, corporation). By entering into this Contract, Contractor affirms, without exception, understands, and agrees to comply with the following items through the life of the Contract:

  • Contract Use by State Agencies To the extent applicable, the Contract does not prohibit state agencies from using their delegated purchasing authority to procure similar goods and services from other sources.

  • Personally Identifiable Information (PII); Security a. If Grantee or any of its subcontractors may or will create, receive, store or transmit PII under the terms of this Agreement, Grantee must provide for the security of such PII, in a form acceptable to Florida Housing, without limitation, non-disclosure, use of appropriate technology, security practices, computer access security, data access security, data storage encryption, data transmission encryption, security inspections and audits. Grantee shall take full responsibility for the security of all data in its possession or in the possession of its subcontractors and shall hold Florida Housing harmless for any damages or liabilities resulting from the unauthorized disclosure of loss thereof. b. If Grantee or any of its subcontractors may or will create, receive, store or transmit PII under the terms of this Agreement, Grantee shall provide Florida Housing with insurance information for stand-alone cyber liability coverage, including the limits available and retention levels. If Grantee does not carry stand-alone cyber liability coverage, Grantee agrees to indemnify costs related to notification, legal fees, judgments, settlements, forensic experts, public relations efforts, and loss of any business income related to this Agreement. c. Grantee agrees to maintain written policies and procedures for PII and/or data classification. This plan must include disciplinary processes for employees that violate these guidelines. d. Grantee agrees at all times to maintain reasonable network security that, at a minimum, includes a network firewall. e. Grantee agrees to protect and maintain the security of data with protection security measures that include maintaining secure environments that are patched and up to date with all appropriate security updates as designated by a relevant authority (e.g. Microsoft notifications, Common Vulnerabilities and Exposures (CVE) database, etc.) Grantee agrees that PII shall be appropriately destroyed based on the format stored upon the expiration of any applicable retention schedules. f. Grantee agrees that any and all transmission or exchange of system application data with Florida Housing and/or any other parties shall take place via secure Advanced Encryption Standards (AES), e.g. HTTPS, FTPS, SFTP or equivalent means. All data stored as a part of backup and recovery processes shall be encrypted, using AES. g. If Grantee reasonably suspects that a cybersecurity event or breach of security has occurred, they must notify Florida Housing’s Contract Administrator within 48 hours. h. In the event of a breach of PII or other sensitive data, Grantee must abide by provisions set forth in Section 501.171, Fla. Stat. Additionally, Grantee must immediately notify Florida Housing in writing of the breach and any actions taken in response to such a breach. As the information becomes available the statement must include, at a minimum, the date(s) and number of records affected by unauthorized access, distribution, use, modification or disclosure of PII; Grantee’s corrective action plan; and the timelines associated with the corrective action plan.

  • Joint Funded Project with the Ohio Department of Transportation In the event that the Recipient does not have contracting authority over project engineering, construction, or right-of-way, the Recipient and the OPWC hereby assign certain responsibilities to the Ohio Department of Transportation, an authorized representative of the State of Ohio. Notwithstanding Sections 4, 6(a), 6(b), 6(c), and 7 of the Project Agreement, Recipient hereby acknowledges that upon notification by the Ohio Department of Transportation, all payments for eligible project costs will be disbursed by the Grantor directly to the Ohio Department of Transportation. A Memorandum of Funds issued by the Ohio Department of Transportation shall be used to certify the estimated project costs. Upon receipt of a Memorandum of Funds from the Ohio Department of Transportation, the OPWC shall transfer funds directly to the Ohio Department of Transportation via an Intra- State Transfer Voucher. The amount or amounts transferred shall be determined by applying the Participation Percentages defined in Appendix D to those eligible project costs within the Memorandum of Funds. In the event that the Project Scope is for right-of-way only, notwithstanding Appendix D, the OPWC shall pay for 100% of the right-of-way costs not to exceed the total financial assistance provided in Appendix C.

  • Banking Services and Swap Agreements Each Lender or Affiliate thereof providing Banking Services for, or having Swap Agreements with, any Loan Party or any Subsidiary or Affiliate of a Loan Party shall deliver to the Administrative Agent, promptly after entering into such Banking Services or Swap Agreements, written notice setting forth the aggregate amount of all Banking Services Obligations and Swap Agreement Obligations of such Loan Party or Subsidiary or Affiliate thereof to such Lender or Affiliate (whether matured or unmatured, absolute or contingent). In furtherance of that requirement, each such Lender or Affiliate thereof shall furnish the Administrative Agent, from time to time after a significant change therein or upon a request therefor, a summary of the amounts due or to become due in respect of such Banking Services Obligations and Swap Agreement Obligations. The most recent information provided to the Administrative Agent shall be used in determining which tier of the waterfall, contained in Section 2.18(b), such Banking Services Obligations and/or Swap Agreement Obligations will be placed.

  • Payment of Checks, Drafts and Orders Subject to Section 9.5, the Assuming Institution agrees to pay all properly drawn checks, drafts and withdrawal orders of depositors of the Failed Bank presented for payment, whether drawn on the check or draft forms provided by the Failed Bank or by the Assuming Institution, to the extent that the Deposit balances to the credit of the respective makers or drawers assumed by the Assuming Institution under this Agreement are sufficient to permit the payment thereof, and in all other respects to discharge, in the usual course of conducting a banking business, the duties and obligations of the Failed Bank with respect to the Deposit balances due and owing to the depositors of the Failed Bank assumed by the Assuming Institution under this Agreement.

  • 240104 Vendor Agreement If responding to Part 1 the Vendor Agreement Signature Form (Part 1) must be downloaded from the “Attachments” section of the IonWave eBid System, reviewed, properly completed, and uploaded to this location. If Vendor has proposed deviations to the Vendor Agreement (Part 1), Vendor may leave the signature line of this page blank and assert so in the Attribute Questions and those shall be addressed during evaluation. Vendor must upload their current IRS Tax Form W-9. The legal name, EIN, and d/b/a's listed should match the information provided herein exactly. This form will be utilized by TIPS to properly identify your entity. Claim Form.pdf

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

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