Ownership; Compliance Tools Sample Clauses

Ownership; Compliance Tools. The Parties understand and agree that all Software is licensed and not sold hereunder. The Parties agree that, as between the Parties, all Software and its Documentation, and all worldwide intellectual property rights therein or related thereto, are the exclusive property of Trend Micro, its Affiliates, and/or its or their licensors/suppliers. All rights in and to Software not expressly granted to Company in this Agreement are reserved by Trend Micro and Company will have no other or different rights (implied, by estoppel, or otherwise) or privileges with respect to any Software. Nothing in this Agreement will be deemed to grant, by implication, estoppel, or otherwise, a license under any of Trend Micro’s existing or future patents or other intellectual property rights. Trend Micro reserves the right to take any and all reasonable steps to prevent unauthorized access to, and use of, Software by any person. Company acknowledges and agrees that Trend Micro may utilize and deploy in connection with any or all Products: (a) registration or license keys or authorization codes that are required for activation and/or renewal of each or all copies or use of a Product; and/or (b) other compliance tools, processes, procedures, and /or controls to ensure that Company has purchased full entitlement for Products it has deployed.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Ownership; Compliance Tools. The Parties understand and agree that all Software is licensed and not sold hereunder. The Parties agree that, as between the Parties, all Software and its Documentation, and all worldwide intellectual property rights therein or related thereto, are the exclusive property of TXOne Networks, its Affiliates, and/or its or their licensors/suppliers. All rights in and to Software not expressly granted to Company in this Agreement are reserved by TXOne Networks and Company will have no other or different rights (implied, by estoppel, or otherwise) or privileges with respect to any Software. Nothing in this Agreement will be deemed to grant, by implication, estoppel, or otherwise, a license under any of TXOne Networks’ existing or future patents or other intellectual property rights. TXOne Networks reserves the right to take any and all reasonable steps to prevent unauthorized access to, and use of, Software by any person. Company acknowledges and agrees that TXOne Networks may utilize and deploy in connection with any or all Products: (a) registration or license keys or authorization codes that are required for activation and/or renewal of each or all copies or use of a Product; and/or (b) other compliance tools, processes, procedures, and /or controls to ensure that Company has purchased full entitlement for Products it has deployed.
Sample 1Sample 2Sample 3

Related to Ownership; Compliance Tools

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

  • Requirement to Utilize HUB Compliance Reporting System Pursuant to Texas Administrative Code, Title 34, Part 1, Sections 20.285(f) and 20.287(b), TFC administers monthly administration HSP-PAR compliance monitoring through its HUB Compliance Reporting System commonly known as B2G. PSP and PSP’s subcontractors/subconsultants shall submit required PAR information into the B2G system. Any delay in the timely submission of PAR information into the B2G system will be treated as an invoicing error subject to dispute under Texas Government Code Section 2251.042.

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

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

  • DBE/HUB Compliance The Engineer’s subcontracting program shall comply with the requirements of Attachment H of the contract (DBE/HUB Requirements).

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

  • Commodity Compliance and Compatibility It is the Contractor’s responsibility to ensure that the Commodities supplied are compliant with the Contract requirements, specifications, terms, and conditions. Additionally, the Contractor shall ensure that all Commodities ordered by the Customer are fully compatible with each other and with any associated pre-existing Commodity possessed by the Customer and disclosed to the Contractor by the Customer. The Contractor’s acceptance of the Customer’s order shall indicate that the Contractor agrees to deliver a Commodity that is fully compliant and compatible with the Customer’s order requirements, specifications, terms, and conditions. In the event any ordered Base Equipment, OEM and Non-OEM Option(s), Part(s), Accessory(ies), and Implement(s); and their respective features, equipment, and components are found by the Customer to be missing, incorrect, defective, damaged, non- compatible, or non-compliant, the Contractor shall, at the Customer’s discretion, be required to complete one of the following: • Install or repair the Base Equipment, OEM and Non-OEM Option(s), Part(s), Accessory(ies), and Implement(s), and their respective features, equipment, and components; • Replace the Base Equipment, OEM and Non-OEM Option(s), Part(s), Accessory(ies), and Implement(s); and their respective features, equipment, and components; • Refund the purchase price of the Base Equipment, OEM and Non-OEM Option(s), Part(s), Accessory(ies), and Implement(s); and their respective features, equipment, and components to the Customer. Any changes necessary after the delivery of the Customer’s order that are required to bring a Commodity into compliance or compatibility due to an incorrect order fulfillment by the Contractor shall be accomplished at the Contractor’s expense.

  • Year 2000 Compliance Each Party warrants that it has implemented a program the goal of which is to ensure that all software, hardware and related materials (collectively called “Systems”) delivered, connected with BellSouth or supplied in the furtherance of the terms and conditions specified in this Agreement: (i) will record, store, process and display calendar dates falling on or after January 1, 2000, in the same manner, and with the same functionality as such software records, stores, processes and calendar dates falling on or before December 31, 1999; and (ii) shall include without limitation date data century recognition, calculations that accommodate same century and multicentury formulas and date values, and date data interface values that reflect the century.

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

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

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!