Operational Data; Compliance Sample Clauses

Operational Data; Compliance. The Programs may collect certain operational data that may be used by Kubermatic for various business purposes that may include customer support, verifying the need for and providing Updates to the Programs, market research, product development and planning, verifying Customer’s compliance with the terms and conditions of the Agreement, and protecting Kubermatic’s intellectual property. Such operational data may be transmitted to Kubermatic automatically by the respective Program, if any inasmuch as documented in the Documentation. Operational data that is not collected and transmitted automatically through the Program, shall be provided by Customer upon Kubermatic’s request.
Sample 1
AutoNDA by SimpleDocs
Operational Data; Compliance. The Programs may collect certain operational data (non-personal data), which may be used by Kubermatic for various business purposes that may include customer support (on behalf of the Partner), verifying the need for and providing Updates to the Programs, (also on behalf of the Partner) market research, product development and planning, verifying Your compliance with the terms and conditions of this XXXX, and protecting Kubermatic’s intellectual property. Such operational data may be transmitted to Kubermatic automatically by the respective Program, if any inasmuch as documented in the Documentation.
Sample 1

Related to Operational Data; Compliance

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

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

  • PCI-DSS Compliance Merchant shall be in full compliance with rules, regulations, guidelines and procedures adopted by any Card Association or Payment Network relating to the privacy and security of Cardholder and Card transaction data, including without limitation the most up-to-date version of the Payment Card Industry Data Security Standard (PCI-DSS), as amended from time to time by the Payment Card Industry Security Standards Council. Detailed information pertaining to aforementioned requirements may be found at xxxxx://xxx.xxxxxxxxxxxxxxxxxxxx.xxx. Additional information regarding security requirements may be found on the Card Association’s respective web sites.

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

  • OSHA Compliance To the extent applicable to the services to be performed under this Agreement, Contractor represents and warrants, that all articles and services furnished under this Agreement meet or exceed the safety standards established and promulgated under the Federal Occupational Safety and Health Law (Public Law 91-596) and its regulations in effect or proposed as of the date of this Agreement.

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

  • PCI Compliance A. The Acquiring Bank will provide The Merchant with appropriate training on PCI PED and/or DSS rules and regulations in respect of The Merchants obligations. Initial training will be provided and at appropriate intervals as and when relevant changes are made to such rules and regulations.

  • Labor Compliance Program The City has its own Labor Compliance Program authorized in August 2011 by the DIR. The City will withhold contract payments when payroll records are delinquent or deemed inadequate by the City or other governmental entity, or it has been established after an investigation by the City or other governmental entity that underpayment(s) have occurred. For questions or assistance, please contact the City of San Diego’s Equal Opportunity Contracting Department at 000-000-0000.

  • Standards Compliance DNS. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).

  • REGULATORY FILINGS AND CAISO TARIFF COMPLIANCE 3.1 Filing

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