Participant Register data updates Sample Clauses

Participant Register data updates. The beneficiaries must keep — at all times, during the action or afterwards — their information stored in the Portal Participant Register up to date, in particular, their name, address, legal representatives, legal form and organisation type.
AutoNDA by SimpleDocs
Participant Register data updates. The Associated Partners must keep — at all times, during the action or afterwards — their information stored in the Portal Participant Register up to date, in particular, their name, address, legal representatives, legal form and organisation type.
Participant Register data updates. The Recipient must keep — at all times, during the KAVA(s) or afterwards — their information stored in the Portal Participant Register up to date, in particular, their name, address, legal representatives, legal form and organization.
Participant Register data updates. The beneficiaries must keep — at all times, during the action or afterwards — their information provided to the Consortium up to date, in particular, their name, address, legal representatives, legal form and organisation type.

Related to Participant Register data updates

  • Participant Register Each Lender that sells a participation shall, acting solely for this purpose as a non-fiduciary agent of the Borrower, maintain a register on which it enters the name and address of each Participant and the principal amounts (and stated interest) of each Participant’s interest in the Loans or other obligations under the Loan Documents (the “Participant Register”); provided that no Lender shall have any obligation to disclose all or any portion of the Participant Register (including the identity of any Participant or any information relating to a Participant’s interest in any commitments, loans, letters of credit or its other obligations under any Loan Document) to any Person except to the extent that such disclosure is necessary to establish that such commitment, loan, letter of credit or other obligation is in registered form under Section 5f.103-1(c) of the United States Treasury Regulations. The entries in the Participant Register shall be conclusive absent manifest error, and such Lender shall treat each Person whose name is recorded in the Participant Register as the owner of such participation for all purposes of this Agreement notwithstanding any notice to the contrary. For the avoidance of doubt, the Administrative Agent (in its capacity as Administrative Agent) shall have no responsibility for maintaining a Participant Register.

  • Participant Representations (a) The Participant represents, warrants and agrees that it will not make any representations concerning the Funds, the Creation Units or the Shares other than those consistent with the then current Prospectus or any promotional or sales literature furnished to the Participant by the Distributor or the Trust, or any such materials permitted by clause (b) of this Section 6.

  • Participant Signature Ratification, Acceptance(A), Approval(AA), Accession(a)

  • Participant Information My address is: My Social Security Number is:

  • Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-­‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.

  • DOCUMENTATION; RECORDS OF PROCESSING Each party is responsible for its compliance with its documentation requirements, in particular maintaining records of processing where required under Data Protection Law. Each party shall reasonably assist the other party in its documentation requirements, including providing the information the other party needs from it in a manner reasonably requested by the other party (such as using an electronic system), in order to enable the other party to comply with any obligations relating to maintaining records of processing.

  • Certification Regarding Suspension or Debarment Contractor certifies under the pains and penalties of perjury that, as of the date this contract amendment is signed, neither Contractor nor Contractor's principals (officers, directors, owners, or partners) are presently debarred, suspended, proposed for debarment, declared ineligible or excluded from participation in federal programs, or programs supported in whole or in part by federal funds. Contractor further certifies under pains and penalties of perjury that, as of the date this contract amendment is signed, Contractor is not presently debarred, suspended, nor named on the State's debarment list at: xxxx://xxx.xxxxxxx.xxx/purchasing-contracting/debarment This document consists of 7 pages. Except as modified by this Amendment No. 1, all provisions of the Contract remain in full force and effect. STATE OF VERMONT CONTRACT AMENDMENT #02 It is hereby agreed by and between the State of Vermont, Office of Purchasing and Contracting (the "State") and Eastern Metal/USA-Sign , with a principal place of business in Elmira NY (the "Contractor") that the contract between them originally dated as of November 01, 2018, Contract #37342, as amended to date, (the "Contract") is hereby amended as follows:

  • Participant Responsibilities The SFS scholarship participant agrees to the following:

  • Instructions for Certification - Lower Tier Participants (Applicable to all subcontracts, purchase orders and other lower tier transactions requiring prior FHWA approval or estimated to cost $25,000 or more - 2 CFR Parts 180 and 1200)

  • 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).

Time is Money Join Law Insider Premium to draft better contracts faster.