Affiliates and Third Parties If the Asset Representations Reviewer processes the PII of the Issuer’s Affiliates or a third party when performing a Review, and if such Affiliate or third party is identified to the Asset Representations Reviewer, such Affiliate or third party is an intended third-party beneficiary of this Section 4.10, and this Agreement is intended to benefit the Affiliate or third party. The Affiliate or third party may enforce the PII related terms of this Section 4.10 against the Asset Representations Reviewer as if each were a signatory to this Agreement.
Unaffiliated Third Parties Nothing herein shall impose any duty upon the Transfer Agent in connection with or make the Transfer Agent liable for the actions or omissions to act of unaffiliated third parties such as, by way of example and not limitation, airborne services, the U.S. mails and telecommunication companies, provided, if the Transfer Agent selected such company, the Transfer Agent shall have exercised due care in selecting the same.
Obligations to Third Parties Each party warrants and represents that this Agreement does not conflict with any contractual obligations, expressed or implied, undertaken with any Third Party.
Consent of Third Parties If any provision of this Agreement is dependent on the consent of any third party and such consent is withheld, the Parties hereto shall use their reasonable best efforts to implement the applicable provisions of this Agreement to the fullest extent practicable. If any provision of this Agreement cannot be implemented due to the failure of such third party to consent, the Parties hereto shall negotiate in good faith to implement the provision in a mutually satisfactory manner.
Parent Right to Access and Challenge Student Data The LEA shall establish reasonable procedures pursuant to which a parent, as that term is defined in 105 ILCS 10/2(g), may inspect and/or copy Student Data and/or challenge the accuracy, relevance or propriety of Student Data, pursuant to Sections 5 and 7 of ISSRA (105 ILCS 10/5; 105 ILCS 10/7) and Section 33 of SOPPA (105 ILCS 85/33). The Provider shall respond to any request by the LEA for Student Data in the possession of the Provider when Provider cooperation is required to afford a parent an opportunity to inspect and/or copy the Student Data, no later than 5 business days from the date of the request. In the event that a parent contacts the Provider directly to inspect and/or copy Student Data, the Provider shall refer the parent to the LEA, which shall follow the necessary and proper procedures regarding the requested Student Data.
Notice to Third Parties Licensee shall give written notice, prior to the first sale of Licensed Product, to any Third Party to which it sells Licensed Product of the restrictions contained in this Section 5, and Licensee shall use its best endeavors, without prejudice to any other provision of this Agreement, to ensure that such Third Parties will undertake to abide by the restrictions contained in this Section 5 and will assist the MPP and Pfizer in securing compliance with this Section 5 and the restrictions which it contemplates.
ICANN Access Registry Operator shall provide bulk access to the zone files for the TLD to ICANN or its designee on a continuous basis in the manner ICANN may reasonably specify from time to time. Access will be provided at least daily. Zone files will include SRS data committed as close as possible to 00:00:00 UTC.
Use of Interconnection Facilities by Third Parties 6551 Error! Hyperlink reference not valid.9.9.1 Purpose of Interconnection Facilities. 6551
Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-‐to-‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.
No Obligations to Third Parties Except as otherwise expressly provided herein, the execution and delivery of this Agreement shall not be deemed to confer any rights upon, nor obligate any of the parties hereto, to any person or entity other than the parties hereto.
