Security Compliance Apple will take appropriate steps to ensure compliance with security procedures by its employees, contractors and sub processors and Apple shall ensure that any persons authorized to process Personal Data comply with applicable laws regarding the confidentiality and security of Personal Data with regards to the Service.
Compliance by other operators Except where XXX has directed otherwise in the exercise of its powers under the Act or the Network Code, and except in relation to London Underground Limited and Heathrow Express Operating Company Limited to the extent that such persons are not party to the Network Code, Network Rail shall ensure that all operators of trains having permission to use any track comprised in the Network agree to comply with the Network Code.
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.
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.
Compliance Monitoring Grantee must be subject to compliance monitoring during the period of performance in which funds are Expended and up to three years following the closeout of all funds. In order to assure that the program can be adequately monitored, the following is required of Grantee:
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”).
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.
Monitoring and Compliance Every year during the term of this Agreement on the anniversary date of the effective date of the Agreement, the Restaurant shall provide to the United States a narrative report of the actions taken during the reporting period to remove any barriers to access and otherwise enhance accessibility for individuals with disabilities at the Restaurant and any plans for action concerning ADA compliance in the coming year. The report shall include as an exhibit copies of any complaint, whether formal or informal, received during the reporting period alleging that the Restaurant was not being operated in compliance with the ADA or otherwise discriminated against any person on account of disability. The Owner and Operator of the Restaurant shall cooperate in good faith with any and all reasonable requests by the United States for access to the Restaurant and for information and documents concerning the Restaurant's compliance with this Agreement and the ADA. The United States shall have the right to verify compliance with this Agreement and the ADA, both as set forth in this Agreement and through any means available to the general public, including visits to the public areas of the Restaurant and communications with Restaurant staff. The United States shall have the right to inspect the facility at any time, and counsel for the United States need not identify themselves in the course of visits to the public areas.
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.
Legal Compliance Contractor represents and warrants that it shall secure all notices and comply with all applicable laws, ordinances, rules and regulations of any governmental entity in conjunction with the performance of obligations under the Contract. Prior to award and during the Contract term and any renewals thereof, Contractor must establish to the satisfaction of the Commissioner that it meets or exceeds all requirements of the Bid and Contract and any applicable laws, including but not limited to, permits, licensing, and shall provide such proof as required by the Commissioner. Failure to comply or failure to provide proof may constitute grounds for the Commissioner to terminate or suspend the Contract, in whole or in part, or to take any other action deemed necessary by the Commissioner. Contractor also agrees to disclose information and provide affirmations and certifications to comply with Sections 139-j and 139-k of the State Finance Law.
