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.
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.
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.
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.
FCPA Compliance The Company has not and, to the Company’s actual knowledge, none of its employees or agents at any time during the last five years have (i) made any unlawful contribution to any candidate for foreign office, or failed to disclose fully any contribution in violation of law, or (ii) made any payment to any federal or state governmental officer or official, or other person charged with similar public or quasi-public duties, other than payments required or permitted by the laws of the United States or any jurisdiction thereof.
SOX Compliance The Company has taken all actions it deems reasonably necessary or advisable to take on or prior to the date of this Agreement to assure that, upon and at all times after the Effective Date, it will be in compliance in all material respects with all applicable provisions of the Sxxxxxxx-Xxxxx Act of 2002 and all rules and regulations promulgated thereunder or implementing the provisions thereof. (the “Sxxxxxxx-Xxxxx Act”) that are then in effect and will take all action it deems reasonably necessary or advisable to assure that it will be in compliance in all material respects with other applicable provisions of the Sxxxxxxx-Xxxxx Act not currently in effect upon it and at all times after the effectiveness of such provisions.
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:
CRA Compliance Neither Buyer nor any Buyer Subsidiary has received any notice of non-compliance with the applicable provisions of the CRA and the regulations promulgated thereunder. As of the date hereof, Buyer’s and each Buyer Subsidiary’s most recent examination rating under the CRA was “satisfactory” or better. Buyer knows of no fact or circumstance or set of facts or circumstances which would be reasonably likely to cause Buyer or any Buyer Subsidiary to receive any notice of non-compliance with such provisions of the CRA or cause the CRA rating of Buyer or any Buyer Subsidiary to decrease below the “satisfactory” level.
DBE/HUB Compliance The Engineer’s subcontracting program shall comply with the requirements of Attachment H of the contract (DBE/HUB Requirements).
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”).
