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.
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.
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:
OFAC Compliance (a) Tenant represents and warrants that (a) Tenant and each person or entity owning an interest in Tenant is (i) not currently identified on the Specially Designated Nationals and Blocked Persons List maintained by the Office of Foreign Assets Control, Department of the Treasury (“OFAC”) and/or on any other similar list maintained by OFAC pursuant to any authorizing statute, executive order or regulation (collectively, the “List”), and (ii) not a person or entity with whom a citizen of the United States is prohibited to engage in transactions by any trade embargo, economic sanction, or other prohibition of United States law, regulation, or Executive Order of the President of the United States, (b) none of the funds or other assets of Tenant constitute property of, or are beneficially owned, directly or indirectly, by any Embargoed Person (as hereinafter defined), (c) no Embargoed Person has any interest of any nature whatsoever in Tenant (whether directly or indirectly), (d) none of the funds of Tenant have been derived from any unlawful activity with the result that the investment in Tenant is prohibited by law or that the Lease is in violation of law, and (e) Tenant has implemented procedures, and will consistently apply those procedures, to ensure the foregoing representations and warranties remain true and correct at all times. The term “
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.
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”).
Xxxxxx Compliance The Union shall comply with the requirements set forth in Chicago Teachers Union x. Xxxxxx, 475 U.S. 292 (1986) for the deduction of agency shop fees. Annually, the Union shall certify in writing to the City that the Union has complied with the requirements set forth in this section and in Xxxxxx, 475 U.S. 292.
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.
