Third Party Access. Client is prohibited from disclosing data from the Data Set to any third party without obtaining written permission from Oracle.
Third Party Access. 6.1 You can instruct a TPP to access information on your Account or initiate certain Transactions from your Account provided such TPP has identified itself to us and it has acted in accordance with the relevant regulatory requirements. We will treat any instruction from an TPP as if it was from you or an Account Manager.
6.2 We may deny a TPP access to your Account if we are concerned about unauthorised or fraudulent access by that TPP. setting out the reason for such denial. Before doing so, we will tell you that we intend to deny access and give our reasons for doing so, unless it is not reasonably practicable, in which case we will immediately inform you afterwards. In either case, we will tell you in the manner in which we consider most appropriate in the circumstances. We will not tell you if doing so would compromise our security measures or would otherwise be unlawful.
6.3 If you have provided consent to a TPP to access the data in your Account to enable them to provide account information services to you or initiate Transactions on your behalf, you consent to us sharing your information with the TPP as is reasonably required for them to provide their services to you. You must let us know if you withdraw this permission and we recommend you let the TPP know. On notification from you, we will not provide such TPP access to your Account or the data in it.
Third Party Access. Customer may allow its Authorized Users and Affiliates to use the Technology and access the Services solely for Customer’s internal business purposes, provided that (i) Customer ensures its Authorized Users and Affiliates comply with the terms of this Agreement and (ii) Customer shall be liable towards UiPath as if their acts and omissions would have been Customer’s own. Upon request, Customer will provide UiPath with details and use reports of all Authorized Users and Affiliates having received access to the Technology.
Third Party Access. (a) The Contractor shall provide for third party access to the structures, facilities, installations, equipment and other property within the Contract Area on reasonable terms and conditions.
(b) The Contractor shall use all reasonable efforts to negotiate a satisfactory agreement for third party access, and where mutual agreement can not be reached, the Designated Authority after consultation with the Joint Commission, shall set the terms for such third party access after taking into account internationally accepted principles, Good Oil Field Practice and operational requirements and standards.
Third Party Access. If, to the extent permitted by Section 4.10, you grant express permission to a Regulated Third Party to access or connect to your Coinbase Account(s), either through the Regulated Third Party's product or service or through the Site, you acknowledge that granting permission to a Regulated Third Party to take specific actions on your behalf does not relieve you of any of your responsibilities under this Agreement. You are fully responsible for all acts or omissions of any Regulated Third Party with access to your Coinbase Account(s) and any action of such Regulated Third Party shall be considered to be an action authorised by you. Further, you acknowledge and agree that you will not hold Coinbase responsible for, and will indemnify Coinbase from, any liability arising out of or related to any act or omission of any Regulated Third Party with access to your Coinbase Account(s).
Third Party Access. Each party to this Agreement (each, a “Contracting Party”) shall be and remain fully responsible and liable for all actions and omissions by any third party using or accessing ITWS through or on behalf of such Contracting Party (including through the use of any applicable identification numbers, passwords, or other access keys or credentials in the possession of the Contracting Party, or under any unique identifiers assigned to such Contracting Party with respect to ITWS), including without limitation any third party agent or service provider permitted, directed, and/or authorized by such Contracting Party to access and/or act through or upon ITWS with respect to any Accounts or Orders. Any such third party shall be bound by the terms and conditions of this Agreement applicable to the Contracting Party, and any failure by such third party to comply with the terms of this Agreement shall constitute a breach of this Agreement by the Contracting Party. The Contracting Party shall be liable for such third parties’ compliance with the terms of this Agreement to the same extent as if the Contracting Party itself had acted or failed to act instead of the third party.
Third Party Access. Subject to the terms and conditions of this Service Schedule, you have the non-exclusive right to authorize access to DiaLinx Services to your employees and/or to any third party (including the right to sell such DiaLinx Service). You agree that if you offer DiaLinx Service other than to your bona fide employees, you will do so only pursuant to a binding agreement incorporating terms substantially similar to those stated in Section 14 (Mandatory Flow-down Terms) of this Service Schedule.
Third Party Access. 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.
Third Party Access. By granting access to third parties outside the United States of America access to the Business Associate’s products or services, the Covered Entity accepts and agrees to the Business Associate’s Release Agreement for Third Party Access.
Third Party Access. Outside Entity and its Authorized Users are expressly prohibited from allowing any third-party entity, agent or subcontractor to access the EHR via CareLink or otherwise.
