Authorized User Conduct; Compliance Sample Clauses

Authorized User Conduct; Compliance. Customer is responsible for use of the Services by its Authorized Users and for their compliance with the Terms of Service. Customer is also responsible for providing any notice and obtaining any consents and authorizations necessary: (a) to allow the Authenticated Creator to access, monitor, use and disclose the Customer Content posted by Authorized Users on the Services; and (b) to allow Visual Vocal to provide the Authenticated Creator with access to such Customer Content. The Services are not authorized for use by persons under the age of 13 and Customer will ensure that it does not allow any person under 13 to use the Services.
AutoNDA by SimpleDocs

Related to Authorized User Conduct; Compliance

  • Software compliance Unless explicitly agreed, software being used and developed to provide the service should: ● Be licensed under an open source and permissive license (like MIT, BSD, Apache 2.0,...). ● The license should provide unlimited access rights to the EGI community. ● Have source code publicly available via a public source code repository (if needed a mirror can be put in place under the EGI organisation in GitHub13.) All releases should be appropriately tagged. ● Adopt best practices: ○ Defining and enforcing code style guidelines. ○ Using Semantic Versioning. ○ Using a Configuration Management frameworks such as Ansible. ○ Taking security aspects into consideration through at every point in time. ○ Having automated testing in place. ○ Using code reviewing. 9 xxxxx://xxx.xxx.xx/about/policy/policies_procedures.html 10 xxxxx://xxxx.xxx.xx/wiki/OMB 11 xxxx://xxx.xxx.xx/ 12 xxxxx://xxx.xxx.xx/portal/index.php?Page_Type=NGI&id=4 13 xxxxx://xxxxxx.xxx/EGI-Foundation ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, and end users.

  • Information Technology Accessibility Standards Any information technology related products or services purchased, used or maintained through this Grant must be compatible with the principles and goals contained in the Electronic and Information Technology Accessibility Standards adopted by the Architectural and Transportation Barriers Compliance Board under Section 508 of the federal Rehabilitation Act of 1973 (29 U.S.C. §794d), as amended. The federal Electronic and Information Technology Accessibility Standards can be found at: xxxx://xxx.xxxxxx-xxxxx.xxx/508.htm.

  • Program Compliance The School Board shall be responsible for monitoring the program to provide technical assistance and to ensure program compliance.

  • Export Control Compliance User acknowledges that Center is an open laboratory for fundamental research that has many foreign persons as its employees and students. User understands and agrees that under no circumstances will User bring export control-listed items, or unpublished software source code or technical information in the form of defense articles or technical data regulated by the International Traffic in Arms Regulations (ITAR), to Center. Use of Center or facilities for activity subject to the ITAR, including the development, assembly or fabrication of defense articles identified on the US Munitions List, is prohibited.

  • Privacy Compliance The Provider shall comply with all applicable federal, state, and local laws, rules, and regulations pertaining to Student Data privacy and security, all as may be amended from time to time.

  • REGULATORY FILINGS AND CAISO TARIFF COMPLIANCE 3.1 Filing

  • HIPAA Compliance If this Contract involves services, activities or products subject to the Health Insurance Portability and Accountability Act of 1996 (HIPAA), the Contractor covenants that it will appropriately safeguard Protected Health Information (defined in 45 CFR 160.103), and agrees that it is subject to, and shall comply with, the provisions of 45 CFR 164 Subpart E regarding use and disclosure of Protected Health Information.

  • CEQA Compliance The District has complied with all assessment requirements imposed upon it by the California Environmental Quality Act (Public Resource Code Section 21000 et seq. (“CEQA”) in connection with the Project, and no further environmental review of the Project is necessary pursuant to CEQA before the construction of the Project may commence.

  • Regulatory Compliance a. Monitor compliance with the 1940 Act requirements, including:

  • FERPA Compliance In connection with all FERPA Records that Contractor may create, receive or maintain on behalf of University pursuant to the Underlying Agreement, Contractor is designated as a University Official with a legitimate educational interest in and with respect to such FERPA Records, only to the extent to which Contractor (a) is required to create, receive or maintain FERPA Records to carry out the Underlying Agreement, and (b) understands and agrees to all of the following terms and conditions without reservation:

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