Processing of Customer Personal Data 3.1 UKG will:
Xxxxxxxx Custodians The Custodian of your IRA must be a bank, savings and loan association, credit union, or a person or entity approved by the Secretary of the Treasury.
Billing and Collection Customers BellSouth currently has in effect numerous billing and collection agreements with various interexchange carriers and billing clearing houses and as such these billing and collection customers (“B&C Customers”) query BellSouth’s LIDB to determine whether to accept various billing options from End Users. Until such time as BellSouth implements in its LIDB and its supporting systems the means to differentiate Comm South’s data from BellSouth’s data, the following shall apply:
Instructions from Customer Processing on Legal Requirement. 28(3) (b) 3.3 Personnel. 28(3) (c) and 32 2 and Appendix 2 Security of Processing and Appendix 2, Technical and Organizational Measures. 28(3) (e) 3.4 Cooperation. 28(3) (f) and 32-36 2 and Appendix 2, 3.5, 3.6 Security of Processing and Appendix 2, Technical and Organizational Measures. Personal Data Breach Notification. Data Protection Impact Assessment. 28(3) (g) 4 Data export and Deletion 28(3) (h) 5 CERTIFICATIONS AND AUDITS
Procurement of Recovered Materials (1) In the performance of this contract, the Contractor shall make maximum use of products containing recovered materials that are EPA-designated items unless the product cannot be acquired
PROCUREMENT OF RECOVERED MATERIAL H-GAC and the Respondent must comply with section 6002 of the Solid Waste Disposal Act, as amended by the Resource Conservation and Recovery Act. The requirements of Section 6002 include: (1) procuring only items designated in guidelines of the Environmental Protection Agency (EPA) at 40 CFR part 247 that contain the highest percentage of recovered materials practicable, consistent with maintaining a satisfactory level of competition, where the purchase price of the item exceeds $10,000 or the value of the quantity acquired during the preceding fiscal year exceeded $10,000; (2) procuring solid waste management services in a manner that maximizes energy and resource recovery; and (3) establishing an affirmative procurement program for procurement of recovered materials identified in the EPA guidelines. Pursuant to the Federal Rule above, as required by the Resource Conservation and Recovery Act of 1976 (42 U.S.C. § 6962(c)(3)(A)(i)), Respondent certifies that the percentage of recovered materials content for EPA-designated items to be delivered or used in the performance of the Contract will be at least the amount required by the applicable contract specifications or other contractual requirements. A RTICLE 40: XXXXXXXX “ANTI-KICKBACK” ACT Contractor shall comply with 18 U.S.C. § 874, 40 U.S.C. § 3145, and the requirements of 29 C.F.R. pt. 3 as may be applicable, which are incorporated by reference into the contract. The contractor or subcontractor shall insert in any subcontracts the clause above and such other clauses as appropriate agency instructions require, and also a clause requiring the subcontractors to include these clauses in any lower tier subcontracts. The prime contractor shall be responsible for the compliance by any subcontractor or lower tier subcontractor with all of these contract clauses. A breach of the contract clauses above may be grounds for termination of the Contract, and for debarment as a contractor and subcontractor as provided in 29 C.F.R. § 5.12.
Client Money Handling Rules 16.1. The Company will promptly place any Client money it receives into one or more segregated account(s) with reliable financial institutions (i.e. an affiliate, a bank, a market, a settlement agent, a clearing house or OTC counterparty) and the Client funds will be segregated from the Company’s own money and cannot be used in the course of its business. The Client money shall be treated, at all times, in accordance with the applicable ‘Client Money’ rules, as amended from time to time.
CONTRACTOR CUSTOMER SERVICE REPRESENTATIVE Contractor shall designate a customer service representative (and inform Enterprise Services of the same) who shall be responsible for addressing Purchaser issues pertaining to this Master Contract.
END USER AGREEMENTS (“EUA H-GAC acknowledges that the END USER may choose to enter into an End User Agreement (“EUA) with the Contractor through this Agreement, and that the term of the EUA may exceed the term of the current H-GAC Agreement. H-GAC’s acknowledgement is not an endorsement or approval of the End User Agreement’s terms and conditions. Contractor agrees not to offer, agree to or accept from the END USER, any terms or conditions that conflict with those in Contractor’s Agreement with H-GAC. Contractor affirms that termination of its Agreement with H-GAC for any reason shall not result in the termination of any underlying EUA, which shall in each instance, continue pursuant to the EUA’s stated terms and duration. Pursuant to the terms of this Agreement, termination of this Agreement will disallow the Contractor from entering into any new EUA with END USERS. Applicable H-GAC order processing charges will be due and payable to H-GAC
Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.
