Third Party Record Sample Clauses

Third Party Record. Where there is a third party, complete this section.
AutoNDA by SimpleDocs

Related to Third Party Record

  • Third Party Requests In the event Apple receives a third party request for Your or Your End User’s Content or Personal Data (“Third Party Request”), Apple will (i) notify You, to the extent permitted by law, of its receipt of the Third Party Request; and (ii) notify the requester to address such Third Party Request to You. Unless otherwise required by law or the Third Party Request, You will be responsible for responding to the Request. O. School Official Status Under FERPA (20 U.S.C. § 1232g). If You are an educational agency, or organization, or acting on behalf of an educational agency, or organization, to which regulations under the U.S. Family Education Rights and Privacy Act (FERPA) apply, Apple acknowledges that for the purposes of this Agreement, Your Institution’s Personal Data may include personally identifiable information from education records that are subject to FERPA (“FERPA Records”). To the extent that Apple receives FERPA Records while acting as a data processor in providing the Service, You agree that Apple will be functioning as a “school official” as defined in 34 C.F.R. § 99.31(a)(1)(i).

  • Third Party Request Should a Third Party, including, but not limited to law enforcement, former employees of the LEA, current employees of the LEA, and government entities, contact Provider with a request for data held by the Provider pursuant to the Services, the Provider shall redirect the Third Party to request the data directly from the LEA and shall cooperate with the LEA to collect the required information. Provider shall notify the LEA in advance of a compelled disclosure to a Third Party, unless legally prohibited. The Provider will not use, disclose, compile, transfer, sell the Student Data and/or any portion thereof to any third party or other entity or allow any other third party or other entity to use, disclose, compile, transfer or sell the Student Data and/or any portion thereof, without the express written consent of the LEA or without a court order or lawfully issued subpoena. Student Data shall not constitute that information that has been anonymized or de-identified, or anonymous usage data regarding a student’s use of Provider’s services.

  • THIRD-PARTY REVENUE Subrecipient shall make every reasonable effort to obtain all available reimbursement from third parties (e.g., insurers), for which persons served hereunder may be eligible. All such third-party reimbursements received by Subrecipient shall be reported to County in the format required by County. The amount of such third-party reimbursements shall be deducted from County’s maximum obligation hereunder.

  • Third Party Reliance Each Grantor hereby consents and agrees that all issuers of or obligors in respect of any Collateral, and all securities intermediaries, warehousemen, bailees, public officials and other Persons having any interest in, possession of, control over or right, privilege, duty or discretion in respect of, any Collateral shall be entitled to accept the provisions hereof and of the Security Joinder Agreements as conclusive evidence of the right of the Administrative Agent, on behalf of the Secured Parties, to exercise its rights hereunder or thereunder with respect to the Collateral, notwithstanding any other notice or direction to the contrary heretofore or hereafter given by any Grantor or any other Person to any of such Persons.

  • Party Representatives A. The Owner’s Designated Representative authorized to act in the Owner's behalf with respect to the Project is: Xxxxx Xxxxx, Area Manager Office of Facilities Planning & Construction The Texas A&M University System 000 Xxxxxx Xxxxxx, 2nd Floor College Station, Texas 77840-7896

  • Third Party Notices Portions of the Apple Software or Services may utilize or include third party software and other copyrighted material. Acknowledgements, licensing terms and disclaimers for such material are contained in the electronic documentation for the Apple Software and Services, and Your use of such material is governed by their respective terms.

  • Third Party Material (a) The Supplier must provide Third Party Material necessary or appropriate to supply the Services.

  • Third Party Materials The Application may display, include, or make available third-party content (including data, information, applications, and other products, services, and/or materials) or provide links to third-party websites or services, including through third- party advertising ("Third-Party Materials"). You acknowledge and agree that Company is not responsible for Third-Party Materials, including their accuracy, completeness, timeliness, validity, copyright compliance, legality, decency, quality, or any other aspect thereof. Company does not assume and will not have any liability or responsibility to you or any other person or entity for any Third-Party Materials. Third-Party Materials and links thereto are provided solely as a convenience to you, and you access and use them entirely at your own risk and subject to such third parties' terms and conditions.

  • Third Party Rights A person who is not a party to this Agreement has no right under the Contracts (Rights of Third Parties) Xxx 0000 to enforce or to enjoy the benefit of any term of this Agreement.

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

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