Permitted User Compliance Clause Samples
Permitted User Compliance. Client is responsible and liable for damages for any failure by a Permitted User to comply with this Schedule A. (PID # 224877) Page 3 of 34
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.
DBE/HUB Compliance The Engineer’s subcontracting program shall comply with the requirements of Attachment H of the contract (DBE/HUB Requirements).
Monitoring Compliance Upon the request of the Lender, but without incurring any liability beyond the Guaranteed Obligations, from time to time, Guarantor shall promptly provide to the Lender such documents, certificates and other information as may be deemed reasonably necessary to enable the Lender to perform its functions under the Servicing Agreement as the same relates to the Guarantor.
Standards Compliance 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.