Disclaimers Acknowledgements and Waivers Sample Clauses
Disclaimers Acknowledgements and Waivers
Certain Acknowledgements The Participant acknowledges and agrees (i) that the Trust, the Transfer Agent, the Distributor and their respective agents may elect to review any Order placed through the Web Order Site manually before it is executed and that such manual review may result in a delay in execution of such Order; (ii) that during periods of heavy market activity or other times, it may be difficult to place Orders via the Web Order Site and the Participant may place Orders as otherwise set forth in Attachment A; and (iii) that any transaction information, content, or data downloaded or otherwise obtained through the use of the Web Order Site are done at the Participant’s own discretion and risk. EXCEPT AS OTHERWISE SPECIFICALLY PROVIDED IN THE FUND CONNECT AGREEMENT AND TO THE EXTENT PERMITTED BY APPLICABLE LAW, THE PARTICIPANT ACKNOWLEDGES AND AGREES THAT THE WEB ORDER SITE IS PROVIDED “AS IS,” “AS AVAILABLE” WITH ALL FAULTS AND WITHOUT ANY WARRANTY OF ANY KIND. SPECIFICALLY, WITHOUT LIMITING THE FOREGOING, ALL WARRANTIES, CONDITIONS, OTHER CONTRACTUAL TERMS, REPRESENTATIONS, INDEMNITIES AND GUARANTEES WITH RESPECT TO THE WEB ORDER SITE, WHETHER EXPRESS, IMPLIED OR STATUTORY, ARISING BY LAW, CUSTOM, PRIOR ORAL OR WRITTEN STATEMENTS BY THE TRUST, THE TRANSFER AGENT, THE DISTRIBUTOR OR THEIR RESPECTIVE AGENTS, AFFILIATES, LICENSORS OR OTHERWISE (INCLUDING, BUT NOT LIMITED TO AS TO TITLE, SATISFACTORY QUALITY, ACCURACY, COMPLETENESS, UNINTERRUPTED USE, NON-INFRINGEMENT, TIMELINESS, TRUTHFULNESS, SEQUENCE, COMPLETENESS, MERCHANTABILITY OR FITNESS FOR PARTICULAR PURPOSE AND ANY IMPLIED WARRANTIES, CONDITIONS AND OTHER CONTRACTUAL TERMS ARISING FROM TRADE USAGE, COURSE OF DEALING OR COURSE OF PERFORMANCE) ARE HEREBY OVERRIDDEN, EXCLUDED AND DISCLAIMED.
Your Acknowledgements You acknowledge and agree that: 5.1 Apple may at any time, and from time to time, with or without prior notice to You (a) modify the APN, including changing or removing any feature or functionality, or (b) modify, deprecate, reissue or republish the APN APIs. You understand that any such modifications may require You to change or update Your Applications, Passes or Sites at Your own cost. Apple has no express or implied obligation to provide, or continue to provide, the APN and may suspend or discontinue all or any portion of the APN at any time. Apple shall not be liable for any losses, damages or costs of any kind incurred by You or any other party arising out of or related to any such service suspension or discontinuation or any such modification of the APN or APN APIs. 5.2 The APN is not available in all languages or in all countries or regions and Apple makes no representation that the APN is appropriate or available for use in any particular location. To 5.3 Apple provides the APN to You for Your use with Your Application, Pass, or Site, and does not provide the APN directly to any end-user. You acknowledge and agree that any Push Notifications are sent by You, not Apple, to the end-user of Your Application, Pass or Site, and You are solely liable and responsible for any data or content transmitted therein and for any such use of the APN. Further, You acknowledge and agree that any Local Notifications are sent by You, not Apple, to the end-user of Your Application, and You are solely liable and responsible for any data or content transmitted therein. 5.4 Apple makes no guarantees to You in relation to the availability or uptime of the APN and is not obligated to provide any maintenance, technical or other support for the APN. 5.5 Apple reserves the right to remove Your access to the APN, limit Your use of the APN, or revoke Your Push Application ID at any time in its sole discretion. 5.6 Apple may monitor and collect information (including but not limited to technical and diagnostic information) about Your usage of the APN to aid Apple in improving the APN and other Apple products or services and to verify Your compliance with this Agreement; provided however that Apple will not access or disclose the content of any Push Notification unless Apple has a good faith belief that such access or disclosure is reasonably necessary to: (a) comply with legal process or request; (b) enforce the terms of this Agreement, including investigation of any potential violation hereof; (c) detect, prevent or otherwise address security, fraud or technical issues; or (d) protect the rights, property or safety of Apple, its developers, customers or the public as required or permitted by law. Notwithstanding the foregoing, You acknowledge and agree that iOS, iPadOS, macOS, and watchOS may access Push Notifications locally on a user’s device solely for the purposes of responding to user requests and personalizing user experience and suggestions on device.
Consents Amendments and Waivers No amendment or waiver of any provision of this Agreement or any other Loan Document, and no consent with respect to any departure by the Company therefrom, shall be effective unless the same shall be in writing and signed by the Majority Banks (or by the Administrative Agent at the written request of the Majority Banks) and the Company (or, in the case of the Guaranty, the Parent) and acknowledged by the Administrative Agent, and then any such waiver or consent shall be effective only in the specific instance and for the specific purpose for which given; provided, that no such waiver, amendment, or consent shall, unless in writing and signed by all of the Banks and the Company (or, in the case of the Guaranty, the Parent)and acknowledged by the Administrative Agent, do any of the following: (a) increase or extend the Commitment of any Bank (or reinstate any Commitment terminated pursuant to Section 10.1); (b) postpone or delay any date fixed by this Agreement or any other Loan Document for any payment of principal, interest, fees or other amounts due to the Banks (or any of them) hereunder or under any other Loan Document; (c) reduce the principal of, or the rate of interest specified herein on any Loan, or (subject to clause (ii) below) any fees or other amounts payable hereunder or under any other Loan Document; (d) change the percentage of the Commitments or of the aggregate unpaid principal amount of the Loans which is required for the Banks or any of them to take any action hereunder; or (e) amend this Section 24, or Section 10, or any provision herein providing for consent or other action by all Banks; (f) release, amend or otherwise modify the Guaranty; and, provided, further, that (i) no amendment, waiver or consent shall, unless in writing and signed by the Administrative Agent in addition to the Majority Banks or all the Banks, as the case may be, affect the rights or duties of the Administrative Agent under this Agreement or any other Loan Document, and (ii) the Fee Letter may be amended, or rights or privileges thereunder waived, in a writing executed by the parties thereto.
Consents and Waivers The Company shall have obtained any and all consents and waivers necessary or appropriate for consummation of the transactions contemplated by this Agreement.
Representations and Acknowledgements (a) The Executive hereby represents that he is not subject to any restriction of any nature whatsoever on his ability to enter into this Agreement or to perform his duties and responsibilities hereunder, including, but not limited to, any covenant not to compete with any former employer, any covenant not to disclose or use any non-public information acquired during the course of any former employment or any covenant not to solicit any customer of any former employer. (b) The Executive hereby represents that, except as he has disclosed in writing to the Company, he is not bound by the terms of any agreement with any previous employer or other party to refrain from using or disclosing any trade secret or confidential or proprietary information in the course of the Executive’s employment with the Company or to refrain from competing, directly or indirectly, with the business of such previous employer or any other party. (c) The Executive further represents that, to the best of his knowledge, his performance of all the terms of this Agreement and as an employee of the Company does not and will not breach any agreement with another party, including without limitation any agreement to keep in confidence proprietary information, knowledge or data the Executive acquired in confidence or in trust prior to his employment with the Company, and that he will not knowingly disclose to the Company or induce the Company to use any confidential or proprietary information or material belonging to any previous employer or others. (d) The Executive acknowledges that he will not be entitled to any consideration or reimbursement of legal fees in connection with execution of this Agreement. (e) The Executive hereby represents and agrees that, during the Restricted Period, if the Executive is offered employment or the opportunity to enter into any business activity, whether as owner, investor, executive, manager, employee, independent consultant, contractor, advisor or otherwise, the Executive will inform the offeror of the existence of Sections 10, 11, 12 and 13 of this Agreement and provide the offeror a copy thereof. The Executive authorizes the Company to provide a copy of the relevant provisions of this Agreement to any of the persons or entities described in this Section 24(e) and to make such persons aware of the Executive’s obligations under this Agreement.
Amendments and Waivers (a) If the ICANN Board of Directors determines that an amendment to this Agreement (including to the Specifications referred to herein) and all other registry agreements between ICANN and the Applicable Registry Operators (the “Applicable Registry Agreements”) is desirable (each, a “Special Amendment”), ICANN may adopt a Special Amendment pursuant to the requirements of and process set forth in this Section 7.6; provided that a Special Amendment may not be a Restricted Amendment. (b) Prior to submitting a Special Amendment for Registry Operator Approval, ICANN shall first consult in good faith with the Working Group regarding the form and substance of such Special Amendment. The duration of such consultation shall be reasonably determined by ICANN based on the substance of the Special Amendment. Following such consultation, ICANN may propose the adoption of a Special Amendment by publicly posting such amendment on its website for no less than thirty (30) calendar days (the “Posting Period”) and providing notice of such proposed amendment to the Applicable Registry Operators in accordance with Section 7.9. ICANN will consider the public comments submitted on a Special Amendment during the Posting Period (including comments submitted by the Applicable Registry Operators). (c) If, within one hundred eighty (180) calendar days following the expiration of the Posting Period (the “Approval Period”), the ICANN Board of Directors approves a Special Amendment (which may be in a form different than submitted for public comment, but must address the subject matter of the Special Amendment posted for public comment, as modified to reflect and/or address input from the Working Group and public comments), ICANN shall provide notice of, and submit, such Special Amendment for approval or disapproval by the Applicable Registry Operators. If, during the sixty (60) calendar day period following the date ICANN provides such notice to the Applicable Registry Operators, such Special Amendment receives Registry Operator Approval, such Special Amendment shall be deemed approved (an “Approved Amendment”) by the Applicable Registry Operators, and shall be effective and deemed an amendment to this Agreement on the date that is sixty (60) calendar days following the date ICANN provided notice of the approval of such Approved Amendment to Registry Operator (the “Amendment Effective Date”). In the event that a Special Amendment does not receive Registry Operator Approval, the Special Amendment shall be deemed not approved by the Applicable Registry Operators (a “Rejected Amendment”). A Rejected Amendment will have no effect on the terms and conditions of this Agreement, except as set forth below. (d) If the ICANN Board of Directors reasonably determines that a Rejected Amendment falls within the subject matter categories set forth in Section 1.2 of Specification 1, the ICANN Board of Directors may adopt a resolution (the date such resolution is adopted is referred to herein as the “Resolution Adoption Date”) requesting an Issue Report (as such term is defined in ICANN’s Bylaws) by the Generic Names Supporting Organization (the “GNSO”) regarding the substance of such Rejected Amendment. The policy development process undertaken by the GNSO pursuant to such requested Issue Report is referred to herein as a “PDP.” If such PDP results in a Final Report supported by a GNSO Supermajority (as defined in ICANN’s Bylaws) that either (i) recommends adoption of the Rejected Amendment as Consensus Policy or (ii) recommends against adoption of the Rejected Amendment as Consensus Policy, and, in the case of (i) above, the Board adopts such Consensus Policy, Registry Operator shall comply with its obligations pursuant to Section 2.2 of this Agreement. In either case, ICANN will abandon the Rejected Amendment and it will have no effect on the terms and conditions of this Agreement. Notwithstanding the foregoing provisions of this Section 7.6(d), the ICANN Board of Directors shall not be required to initiate a PDP with respect to a Rejected Amendment if, at any time in the twelve (12) month period preceding the submission of such Rejected Amendment for Registry Operator Approval pursuant to Section 7.6(c), the subject matter of such Rejected Amendment was the subject of a concluded or otherwise abandoned or terminated PDP that did not result in a GNSO Supermajority recommendation. (e) If (a) a Rejected Amendment does not fall within the subject matter categories set forth in Section 1.2 of Specification 1, (b) the subject matter of a Rejected Amendment was, at any time in the twelve (12) month period preceding the submission of such Rejected Amendment for Registry Operator Approval pursuant to Section 7.6(c), the subject of a concluded or otherwise abandoned or terminated PDP that did not result in a GNSO Supermajority recommendation, or (c) a PDP does not result in a Final Report supported by a GNSO Supermajority that either (A) recommends adoption of the Rejected Amendment as Consensus Policy or (B) recommends against adoption of the Rejected Amendment as Consensus Policy (or such PDP has otherwise been abandoned or terminated for any reason), then, in any such case, such Rejected Amendment may still be adopted and become effective in the manner described below. In order for the Rejected Amendment to be adopted, the following requirements must be satisfied: (i) the subject matter of the Rejected Amendment must be within the scope of ICANN’s mission and consistent with a balanced application of its core values (as described in ICANN’s Bylaws); (ii) the Rejected Amendment must be justified by a Substantial and Compelling Reason in the Public Interest, must be likely to promote such interest, taking into account competing public and private interests that are likely to be affected by the Rejected Amendment, and must be narrowly tailored and no broader than reasonably necessary to address such Substantial and Compelling Reason in the Public Interest; (iii) to the extent the Rejected Amendment prohibits or requires conduct or activities, imposes material costs on the Applicable Registry Operators, and/or materially reduces public access to domain name services, the Rejected Amendment must be the least restrictive means reasonably available to address the Substantial and Compelling Reason in the Public Interest; (iv) the ICANN Board of Directors must submit the Rejected Amendment, along with a written explanation of the reasoning related to its determination that the Rejected Amendment meets the requirements set out in subclauses (i) through (iii) above, for public comment for a period of no less than thirty (30) calendar days; and (v) following such public comment period, the ICANN Board of Directors must (a) engage in consultation (or direct ICANN management to engage in consultation) with the Working Group, subject matter experts, members of the GNSO, relevant advisory committees and other interested stakeholders with respect to such Rejected Amendment for a period of no less than sixty (60) calendar days; and (b) following such consultation, reapprove the Rejected Amendment (which may be in a form different than submitted for Registry Operator Approval, but must address the subject matter of the Rejected Amendment, as modified to reflect and/or address input from the Working Group and public comments) by the affirmative vote of at least two-‐thirds of the members of the ICANN Board of Directors eligible to vote on such matter, taking into account any ICANN policy affecting such eligibility, including ICANN’s Conflict of Interest Policy (a “Board Amendment”). Such Board Amendment shall, subject to Section 7.6(f), be deemed an Approved Amendment, and shall be effective and deemed an amendment to this Agreement on the date that is sixty (60) calendar days following the date ICANN provided notice of the approval of such Board Amendment to Registry Operator (which effective date shall be deemed the Amendment Effective Date hereunder). Notwithstanding the foregoing, a Board Amendment may not amend the registry fees charged by ICANN hereunder, or amend this Section 7.6. (f) Notwithstanding the provisions of Section 7.6(e), a Board Amendment shall not be deemed an Approved Amendment if, during the thirty (30) calendar day period following the approval by the ICANN Board of Directors of the Board Amendment, the Working Group, on the behalf of the Applicable Registry Operators, submits to the ICANN Board of Directors an alternative to the Board Amendment (an “Alternative Amendment”) that meets the following requirements: (i) sets forth the precise text proposed by the Working Group to amend this Agreement in lieu of the Board Amendment; (ii) addresses the Substantial and Compelling Reason in the Public Interest identified by the ICANN Board of Directors as the justification for the Board Amendment; and (iii) compared to the Board Amendment is: (a) more narrowly tailored to address such Substantial and Compelling Reason in the Public Interest, and (b) to the extent the Alternative Amendment prohibits or requires conduct or activities, imposes material costs on Affected Registry Operators, or materially reduces access to domain name services, is a less restrictive means to address the Substantial and Compelling Reason in the Public Interest. Any proposed amendment that does not meet the requirements of subclauses (i) through
Risk Acknowledgement The Sub-Adviser makes no representation or warranty, express or implied, that any level of performance or investment results will be achieved by the Fund, whether on a relative or absolute basis. The Adviser understands that investment decisions made for the Fund by the Sub-Adviser are subject to various market, currency, economic, political, business and structure risks and that those investment decisions will not always be profitable.
GUARANTOR'S ACKNOWLEDGEMENT The Guarantor warrants, acknowledges and confirms to the Beneficiary that it has not entered into this Deed of Guarantee in reliance upon, nor has it been induced to enter into this Deed of Guarantee by any representation, warranty or undertaking made by or on behalf of the Beneficiary (whether express or implied and whether pursuant to statute or otherwise) which is not set out in this Deed of Guarantee.
ACKNOWLEDGEMENTS OF THE PARTIES Notwithstanding anything in this Agreementto the contrary, the parties hereto hereby acknowledge and agree to the following: (i) the Investormakes no representations or covenants that it will not engage in trading in the securities of the Company, other than the Investor will not sell short the Company's common stock at any time during this Agreement; (ii) the Company shall, by 8:30 a.m. Boston Time on the trading day following the date hereof, file a current report on Form 8-K disclosing the material terms of the transactions contemplated hereby and in the other Equity Line Transaction Documents; (iii) the Company has not and shall not provide material non-public information to the Investorunless prior thereto the Investorshall have executed a written agreement regarding the confidentiality and use of such information; and (iv) the Company understands and confirms that the Investorwill be relying on the acknowledgements set forth in clauses (i) through (iii) above if the Investoreffects any transactions in the securities of the Company. Your signature on this Signature Page evidences your agreement to be bound by the terms and conditions of the Investment Agreement and the Registration Rights Agreement as of the date first written above. The undersigned signatory hereby certifies that he has read and understands the Investment Agreement, and the representations made by the undersigned in this Investment Agreement are true and accurate, and agrees to be bound by its terms. By: /s/ Xxxxxxx X. Xxxxxxxx Xxxxxxx X. Xxxxxxxx, Director By:/s/ J. Xxxx Xxxxx J. Xxxx Xxxxx, CEO
Mutual Acknowledgement Both the Company and Indemnitee acknowledge that in certain instances, Federal law or applicable public policy may prohibit the Company from indemnifying its directors and officers under this Agreement or otherwise. Indemnitee understands and acknowledges that the Company has undertaken or may be required in the future to undertake with the Securities and Exchange Commission to submit the question of indemnification to a court in certain circumstances for a determination of the Company's right under public policy to indemnify Indemnitee.