Content Use and Online Conduct
Content Use and Online Conduct Sample Clauses
Related to Content Use and Online Conduct
User Conduct You agree not to use Mobile Banking or the content or information delivered through Mobile Banking in any way that would: (a) infringe any third-party copyright, patent, trademark, trade secret or other proprietary rights or rights of privacy, including any rights in the Software; (b) be fraudulent or involve the sale of counterfeit or stolen items, including, but not limited to, use of Mobile Banking to impersonate another person or entity; (c) violate any law, statute, ordinance or regulation (including, but not limited to, those governing export control, consumer protection, unfair competition, anti-discrimination or false advertising); (d) be false, misleading or inaccurate; (e) create liability for us or our affiliates or service providers, or cause us to lose (in whole or in part) the services of any of our service providers; (f) be defamatory, trade libelous, unlawfully threatening or unlawfully harassing; (g) potentially be perceived as illegal, offensive or objectionable; (h) interfere with or disrupt computer networks connected to Mobile Banking; (i) interfere with or disrupt the use of Mobile Banking by any other user; or (j) use Mobile Banking in such a manner as to gain unauthorized entry or access to the computer systems of others.
Collocation Transfer of Responsibility Without Working Circuits The Collocation is not serving any End User Customers and does not have active service terminations (e.g., Interconnection trunks or UNE Loops) or 2) Collocation Transfer of Responsibility With Working Circuits – The Collocation has active service terminations, such as Interconnection trunks or is serving End User Customers.
Network Services Local Access Services In lieu of any other rates and discounts, Customer will pay fixed monthly recurring local loop charges ranging from $1,200 to $2,000 for TDM-based DS-3 Network Services Local Access Services at 2 CLLI codes mutually agreed upon by Customer and Company.
Verizon Operations Support Systems Verizon systems for pre- ordering, ordering, provisioning, maintenance and repair, and billing.
Requester and Approved User Responsibilities The Requester agrees through the submission of the DAR that the PI named has reviewed and understands the principles for responsible research use and data management of the genomic datasets as defined in the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. The Requester and Approved Users further acknowledge that they are responsible for ensuring that all uses of the data are consistent with national, tribal, and state laws and regulations, as appropriate, as well as relevant institutional policies and procedures for managing sensitive genomic and phenotypic data. The Requester certifies that the PI is in good standing (i.e., no known sanctions) with the institution, relevant funding agencies, and regulatory agencies and is eligible to conduct independent research (i.e., is not a postdoctoral fellow, student, or trainee). The Requester and any Approved Users may use the dataset(s) only in accordance with the parameters described on the study page and in the 1 If contractor services are to be utilized, PI requesting the data must provide a brief description of the services that the contractor will perform for the PI (e.g., data cleaning services) in the research use statement of the DAR. Additionally, the Key Personnel section of the DAR must include the name of the contractor’s employee(s) who will conduct the work. These requirements apply whether the contractor carries out the work at the PI’s facility or at the contractor’s facility. In addition, the PI is expected to include in any contract agreement requirements to ensure that any of the contractor’s employees who have access to the data adhere to the NIH GDS Policy, this Data Use Certification Agreement, and the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. Note that any scientific collaborators, including contractors, who are not at the Requester must submit their own DAR. Addendum to this Agreement for the appropriate research use, as well as any limitations on such use, of the dataset(s), as described in the DAR, and as required by law. Through the submission of this DAR, the Requester and Approved Users acknowledge receiving and reviewing a copy of the Addendum which includes Data Use Limitation(s) for each dataset requested. The Requester and Approved Users agree to comply with the terms listed in the Addendum. Through submission of the DAR, the PI and Requester agree to submit a Project Renewal or Project Close-out prior to the expiration date of the one (1) year data access period. The PI also agrees to submit an annual Progress Update prior to the one (1) year anniversary2 of the project, as described under Research Use Reporting (Term 10) below. By approving and submitting the attached DAR, the Institutional Signing Official provides assurance that relevant institutional policies and applicable local, state, tribal, and federal laws and regulations, as applicable, have been followed, including IRB approval, if required. Approved Users may be required to have IRB approval if they have access to personal identifying information for research participants in the original study at their institution, or through their collaborators. The Institutional Signing Official also assures, through the approval of the DAR, that other institutional departments with relevant authorities (e.g., those overseeing human subjects research, information technology, technology transfer) have reviewed the relevant sections of the NIH GDS Policy and the associated procedures and are in agreement with the principles defined. The Requester acknowledges that controlled-access datasets subject to the NIH GDS Policy may be updated to exclude or include additional information. Unless otherwise indicated, all statements herein are presumed to be true and applicable to the access and use of all versions of these datasets.
Restricted Use By Outsourcers / Facilities Management, Service Bureaus or Other Third Parties Outsourcers, facilities management or service bureaus retained by Licensee shall have the right to use the Product to maintain Licensee’s business operations, including data processing, for the time period that they are engaged in such activities, provided that: 1) Licensee gives notice to Contractor of such party, site of intended use of the Product, and means of access; and 2) such party has executed, or agrees to execute, the Product manufacturer’s standard nondisclosure or restricted use agreement which executed agreement shall be accepted by the Contractor (“Non-Disclosure Agreement”); and 3) if such party is engaged in the business of facility management, outsourcing, service bureau or other services, such third party will maintain a logical or physical partition within its computer system so as to restrict use and access to the program to that portion solely dedicated to beneficial use for Licensee. In no event shall Licensee assume any liability for third party’s compliance with the terms of the Non-Disclosure Agreement, nor shall the Non-Disclosure Agreement create or impose any liabilities on the State or Licensee. Any third party with whom a Licensee has a relationship for a state function or business operation, shall have the temporary right to use Product (e.g., JAVA Applets), provided that such use shall be limited to the time period during which the third party is using the Product for the function or business activity.
Service Level Agreement Subject to the terms and conditions of this Agreement, Bank agrees to perform the custody services provided for under this Agreement in a manner that meets or exceeds any service levels as may be agreed upon by the parties from time to time in a written document that is executed by both parties on or after the date of this Agreement, unless that written document specifically states that it is not contractually binding. For the avoidance of doubt, Bank’s Service Directory shall not be deemed to be such a written document.
Business Conduct Merger Sub was incorporated on November 5, 2020. Since its inception, Merger Sub has not engaged in any activity, other than such actions in connection with (a) its organization and (b) the preparation, negotiation and execution of this Agreement and the Transactions. Merger Sub has no operations, has not generated any revenues and has no assets or liabilities other than those incurred in connection with the foregoing and in association with the Merger as provided in this Agreement.
ACCESS TO OPERATIONS SUPPORT SYSTEMS 2.1 BellSouth shall provide Max-Tel access to operations support systems (“OSS”) functions for pre-ordering, ordering and provisioning, maintenance and repair, and billing. BellSouth shall provide access to the OSS through manual and/or electronic interfaces as described in this Attachment. It is the sole responsibility of Max-Tel to obtain the technical capability to access and utilize BellSouth’s OSS interfaces. Specifications for Max-Tel ’s access and use of BellSouth’s electronic Version R4Q01: 12/01/01 interfaces are set forth at xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx and are incorporated herein by reference.
