PARTIES IDENTIFIED Sample Clauses

PARTIES IDENTIFIED. This Contract for Real Estate is between: “Seller” Xxxxxx Farms, Inc., an Iowa corporation; and “Buyer” As identified on the signature page to this Contract.
AutoNDA by SimpleDocs
PARTIES IDENTIFIED. This Agreement is between: “Sellers” First Citizens Bank, an Iowa Banking Corporation, and
PARTIES IDENTIFIED. This Contract for Real Estate is between: “Seller” Collectively Xxxxxx Xxxx Xxxx and Xxxxx X. Xxxx, a married couple, and Xxxxx Xxxxx Xxxxxx and Xxxxxx X. Xxxxxx, a married couple; and
PARTIES IDENTIFIED. This Agreement is between: “Sellers” First Citizens Bank (f/k/a First Citizens National Bank), Trustee of the Xxxx X. Xxxxxx Revocable Trust Agreement dated May 8, 2002 (a/k/a the Xxxx X. Xxxxxx Residuary Trust Agreement dated May 8, 2002); and
PARTIES IDENTIFIED. This Agreement/Contract is entered into effective _____________________(DATE) through ______________________(DATE) between Drake University, hereinafter called “Drake” and ___COMPANY NAME____ hereinafter called “Company” Drake University’s principal place of business is at 0000 Xxxxxxxxxx, Xxx Xxxxxx, XX 00000. ___________ principal place of business is at ______________________________________________.
PARTIES IDENTIFIED. This Agreement is among: “Sellers” Xxxxxxx X. Xxxxxx and Xxxxxx X. Xxxxxx, a married couple, Xxxxxx X. Xxxxxx, unmarried, Xxxxxxx X. Xxxxxx and Xxxxxx X. Xxxxxx, a married couple, Xxxx X. Xxxxxx and Xxxxx X. Xxxxxx, a married couple, Xxxxx X. Xxxxxx and Xxxxx X. Xxxxxx, a married couple and Xxxxx X. Xxxxxx, unmarried, collectively and
PARTIES IDENTIFIED. This Agreement is between: “Sellers” A&K Feed & Grain Co, Inc., an Iowa corporation; and
AutoNDA by SimpleDocs
PARTIES IDENTIFIED. This Contract for Real Estate is between:

Related to PARTIES IDENTIFIED

  • If Identified If the HSP is Identified it will:

  • Customer Identification Unless Elastic has first obtained Customer's prior written consent, Elastic shall not identify Customer as a user of the Products, on its website, through a press release issued by Elastic and in other promotional materials.

  • Product Identification Before removal from Sale Area, unless Contracting Officer determines that circumstances warrant a written waiver or adjustment, Purchaser shall:

  • Non-Identification Approved Users agree not to use the requested datasets, either alone or in concert with any other information, to identify or contact individual participants from whom data and/or samples were collected. Approved Users also agree not to generate information (e.g., facial images or comparable representations) that could allow the identities of research participants to be readily ascertained. These provisions do not apply to research investigators operating with specific IRB approval, pursuant to 45 CFR 46, to contact individuals within datasets or to obtain and use identifying information under an 2 The project anniversary date can be found in “My Projects” after logging in to the dbGaP authorized-access portal. IRB-approved research protocol. All investigators including any Approved User conducting “human subjects research” within the scope of 45 CFR 46 must comply with the requirements contained therein.

  • User Identification 6.2.5.1 Access to each Party’s corporate resources will be based on identifying and authenticating individual users in order to maintain clear and personal accountability for each user’s actions.

  • Client identification 9.1. The Company has the right to require the Client to confirm his/her registration information specified when opening a trading account. To do so, the Company may ask the Client at its own discretion and at any time to provide a notarized electronic copy of his/her identification document, bank statement or public utilities xxxx as a proof of residence. In particular cases, the Company may ask the Client to provide a photo of him/her holding his/her ID near his/her face. The detailed client identification requirements are set out in the “AML policies” section on the Company’s official site.

  • De-identified Information De-identified Information may be used by the Operator only for the purposes of development, product improvement, to demonstrate or market product effectiveness, or research as any other member of the public or party would be able to use de-identified data pursuant to 34 CFR 99.31(b). Operator agrees not to attempt to re-identify De-identified Information and not to transfer De-identified Information to any party unless (a) that party agrees in writing not to attempt re- identification, and (b) prior written notice has been given to LEA who has provided prior written consent for such transfer. Operator shall not copy, reproduce or transmit any De-identified Information or other Data obtained under the Service Agreement except as necessary to fulfill the Service Agreement.

  • T1 IDENTIFICATION PROCEDURES During the restoration of service after a disaster, BellSouth may be forced to aggregate traffic for delivery to a CLEC. During this process, T1 traffic may be consolidated onto DS3s and may become unidentifiable to the Carrier. Because resources will be limited, BellSouth may be forced to "package" this traffic entirely differently then normally received by the CLECs. Therefore, a method for identifying the T1 traffic on the DS3s and providing the information to the Carriers is required.

  • Contractor’s Staff Identification Contractor shall provide, at Contractor’s expense, all staff providing services under this Contract with a photo identification badge.

  • Vendor Identity and Contact Information It is Vendor’s sole responsibility to ensure that all identifying vendor information (name, EIN, d/b/a’s, etc.) and contact information is updated and current at all times within the TIPS eBid System and the TIPS Vendor Portal. It is Vendor’s sole responsibility to confirm that all e-correspondence issued from xxxx-xxx.xxx, xxxxxxx.xxx, and xxxxxxxxxxxxxxxx.xxx to Vendor’s contacts are received and are not blocked by firewall or other technology security. Failure to permit receipt of correspondence from these domains and failure to keep vendor identity and contact information current at all times during the life of the contract may cause loss of TIPS Sales, accumulating TIPS fees, missed rebid opportunities, lapse of TIPS Contract(s), and unnecessary collection or legal actions against Vendor. It is no defense to any of the foregoing or any breach of this Agreement that Vendor was not receiving TIPS’ electronic communications issued by TIPS to Vendor’s listed contacts.

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