Multiple Access Agreements Sample Clauses

Open Split View

Download

Share

Cite

Multiple Access Agreements. The Operator may not be nominated under more than one Access Agreement for the purposes of this Agreementthis Deed.

Sample 1

Save

Copy

Related to Multiple Access Agreements

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

• User Agreements In order to receive certain LDC Databases, Member shall restrict use of these Databases to only those of its employees or consultants within its control who, in advance of gaining access to the specified Databases, have signed any necessary separate user agreements. The specific Databases for which such user agreements are required will be indicated by LDC and the terms and provisions of any such User Agreements supersede the terms of the Membership Agreement. Member may elect not to receive LDC Databases for which separate user agreements are required. Member shall maintain all signed user agreements on file for inspection by LDC upon its request and shall terminate access to the specified LDC Databases to individuals for whom the conditions contained in the user agreement no longer apply. To the extent that any of Member's consultants gain access to any LDC Databases, Member shall be responsible and liable for the actions and omissions of those consultants as though they were the actions of Member.

• Acceptable Use Policy Agreement I understand that I must use school IT systems in a responsible way, to ensure that there is no risk to my safety or to the safety and security of the IT systems and other users. For my own personal safety: • I understand that the school will monitor my use of the IT systems, email and other digital communications. • I will treat my username and password like my toothbrush – I will not share it, nor will I try to use any other person’s username and password. • I will be aware of “stranger danger”, when I am communicating on-line. • I will not disclose or share personal information about myself or others when on-line. • If I arrange to meet people off-line that I have communicated with on-line, I will do so in a public place and take an adult with me. • I will immediately report any unpleasant or inappropriate material or messages or anything that makes me feel uncomfortable when I see it on-line. I understand that everyone has equal rights to use technology as a resource and: • I understand that the school IT systems are primarily intended for educational use and that I will not use the systems for personal or recreational use unless I have permission to do so. • I will not try (unless I have permission) to make large downloads or uploads that might take up internet capacity and prevent other users from being able to carry out their work. • I will not use the school IT systems for on-line gaming, on-line gambling, internet shopping, file sharing, or video broadcasting (e.g. YouTube), unless I have permission of a member of staff to do so. I will act as I expect others to act toward me: • I will respect others’ work and property and will not access, copy, remove or otherwise alter any other user’s files, without the owner’s knowledge and permission. • I will be polite and responsible when I communicate with others, I will not use strong, aggressive or inappropriate language and I appreciate that others may have different opinions. • I will not take or distribute images of anyone without their permission. I recognise that the school has a responsibility to maintain the security and integrity of the technology it offers me and to ensure the smooth running of the school: • I will only use my personal hand held / external devices (mobile phones / USB devices etc) in school if I have permission. I understand that, if I do use my own devices in school, I will follow the rules set out in this agreement, in the same way as if I was using school equipment. • I understand the risks and will not try to upload, download or access any materials which are illegal or inappropriate or may cause harm or distress to others, nor will I try to use any programmes or software that might allow me to bypass the filtering / security systems in place to prevent access to such materials.

• Assignment Amendments Waiver and Contract Complete 8.1 The Contractor may neither assign nor transfer any rights or obligations under this Agreement without the prior consent of the Authority and a fully executed Assignment Agreement, executed and approved by the same parties who executed and approved this Agreement, or their successors in office. Any attempted assignment without said consent shall be void and of no effect. The Authority may assign or otherwise transfer or dispose of all or a portion of this Agreement in its sole discretion and without the consent of the Contractor. The Contractor shall execute all consents reasonably required to facilitate such assignment or other transfer.

• Client Agreements Supplier will have a direct contract with, or provide its standard Product or Service terms directly to, Client, which will be enforceable solely between Client and Supplier, for all terms related to Client’s receipt and use of Products and Services (each a “Client Agreement”), other than the payment, risk of loss, and delivery terms that are contracted directly with Accenture.

• Service Level Agreements If a Service or a Plan includes a Service Level Agreement (SLA):

• Changes to Privacy Policy Agreement The Tintstitute reserves the right to update and/or change the terms of our privacy policy, and as such we will post those change to our website homepage at xxxx://xxx.xxxxxxxxxxxxxx.xxx, so that our users and/or visitors are always aware of the type of information we collect, how it will be used, and under what circumstances, if any, we may disclose such information. If at any point in time The Tintstitute decides to make use of any personally identifiable information on file, in a manner vastly different from that which was stated when this information was initially collected, the user or users shall be promptly notified by email. Users at that time shall have the option as to whether or not to permit the use of their information in this separate manner.

• Agreements with Subcontractors Business Associate shall enter into a Business Associate Agreement with any Subcontractor to whom it provides PHI received from Covered Entity or created or received by Business Associate on behalf of Covered Entity in which the Subcontractor agrees to the same restrictions and conditions that apply through this Agreement to Business Associate with respect to such PHI. Business Associate must enter into this Business Associate Agreement before any use by or disclosure of PHI to such agent. The written agreement must identify Covered Entity as a direct and intended third party beneficiary with the right to enforce any breach of the agreement concerning the use or disclosure of PHI. Business Associate shall provide a copy of the Business Associate Agreement it enters into with a subcontractor to Covered Entity upon request. Business associate may not make any disclosure of PHI to any Subcontractor without prior written consent of Covered Entity.

• END USER AGREEMENTS (“EUA H-GAC acknowledges that the END USER may choose to enter into an End User Agreement (“EUA) with the Contractor through this Agreement, and that the term of the EUA may exceed the term of the current H-GAC Agreement. H-GAC’s acknowledgement is not an endorsement or approval of the End User Agreement’s terms and conditions. Contractor agrees not to offer, agree to or accept from the END USER, any terms or conditions that conflict with those in Contractor’s Agreement with H-GAC. Contractor affirms that termination of its Agreement with H-GAC for any reason shall not result in the termination of any underlying EUA, which shall in each instance, continue pursuant to the EUA’s stated terms and duration. Pursuant to the terms of this Agreement, termination of this Agreement will disallow the Contractor from entering into any new EUA with END USERS. Applicable H-GAC order processing charges will be due and payable to H-GAC

• Vendor Agreement 230105 Vendor Agreement pdf The Vendor Agreement must be downloaded from the “Attachments” section of the IonWave eBid System, reviewed, Vendor Name placed in the line provided at the top, and uploaded to this location. If Vendor has proposed deviations to the Vendor Agreement, Vendor may assert so in the Attribute Questions and those shall be addressed during evaluation.