THUK Obligations when Processing Personal Data as a Processor Sample Clauses

THUK Obligations when Processing Personal Data as a Processor. 4.2.1 THUK is acting as a Processor on behalf of the Customer in respect of and to the extent that THUK receives any Personal Data directly from the Customer. THUK will Process such Personal Data in accordance with the terms set out in this section 4.2, and will not enhance or enrich such Personal Data.
AutoNDA by SimpleDocs

Related to THUK Obligations when Processing Personal Data as a Processor

  • Subprocessors Provider shall enter into written agreements with all Subprocessors performing functions for the Provider in order for the Provider to provide the Services pursuant to the Service Agreement, whereby the Subprocessors agree to protect Student Data in a manner no less stringent than the terms of this DPA.

  • Subprocessor For the purposes of this DPA, the term “Subprocessor” (sometimes referred to as the “Subcontractor”) means a party other than LEA or Provider, who Provider uses for data collection, analytics, storage, or other service to operate and/or improve its service, and who has access to Student Data.

  • Provider Employee Obligation Provider shall require all of Provider’s employees and agents who have access to Student Data to comply with all applicable provisions of this DPA with respect to the Student Data shared under the Service Agreement. Provider agrees to require and maintain an appropriate confidentiality agreement from each employee or agent with access to Student Data pursuant to the Service Agreement.

  • Data Storage Where required by applicable law, Student Data shall be stored within the United States. Upon request of the LEA, Provider will provide a list of the locations where Student Data is stored.

  • General Requirements The Contractor hereby agrees:

  • Provide Data in Compliance with Applicable Laws LEA shall provide Student Data for the purposes of obtaining the Services in compliance with all applicable federal, state, and local privacy laws, rules, and regulations, all as may be amended from time to time.

  • Subcontractors The Contractor will not subcontract any work under the Contract without prior written consent of the Department. The Contractor is fully responsible for satisfactory completion of all its subcontracted work. The Department supports diversity in its procurements and contracts, and requests that the Contractor offer subcontracting opportunities to certified woman-, veteran-, and minority-owned small businesses. The Contractor may contact the OSD at xxxxxxx@xxx.xxxxxxxxx.xxx for information on certified small business enterprises available for subcontracting opportunities.

  • Scope of Services The specific scope of work for each job shall be determined in advance and in writing between TIPS Member, Member’s design professionals and Vendor. It is permitted for the TIPS Member to provide a general scope description, but the awarded vendor should provide a written scope of work, and if applicable, according to the TIPS Member’s design Professional as part of the proposal. Once the scope of the job is agreed to, the TIPS Member will issue a PO and/or an Agreement or Contract with the Job Order Contract Proposal referenced or as an attachment along with bond and any other special provisions agreed by the TIPS Member. If special terms and conditions other than those covered within this solicitation and awarded Agreements are required, they will be attached to the PO and/or an Agreement or Contract and shall take precedence over those in this base TIPS Vendor Agreement.

  • Additional Services Registry Operator shall be entitled to provide the Registry Services described in clauses (a) and (b) of the first paragraph of Section 2.1 in the Specification 6 attached hereto (“Specification 6”) and such other Registry Services set forth on Exhibit A (collectively, the “Approved Services”). If Registry Operator desires to provide any Registry Service that is not an Approved Service or is a material modification to an Approved Service (each, an “Additional Service”), Registry Operator shall submit a request for approval of such Additional Service pursuant to the Registry Services Evaluation Policy at xxxx://xxx.xxxxx.xxx/en/registries/rsep/rsep.html, as such policy may be amended from time to time in accordance with the bylaws of ICANN (as amended from time to time, the “ICANN Bylaws”) applicable to Consensus Policies (the “RSEP”). Registry Operator may offer Additional Services only with the written approval of ICANN, and, upon any such approval, such Additional Services shall be deemed Registry Services under this Agreement. In its reasonable discretion, ICANN may require an amendment to this Agreement reflecting the provision of any Additional Service which is approved pursuant to the RSEP, which amendment shall be in a form reasonably acceptable to the parties.

  • Confidential Information “Confidential Information” shall mean (i) Highly Confidential Information (as defined below), (ii) any other technology, software development tools, methodologies, processes, algorithms, test data sets and test data cases and related documentation that CI Plus LLP provides to Licensee hereunder in order to facilitate Licensee’s exercise of its rights and performance of its obligations hereunder, and (iii) any other information of CI Plus LLP and information of Licensee, each of which is clearly marked as “Confidential” or a similar expression when disclosed in written or electronic form, or indicated as “Confidential” when disclosed orally and confirmed in writing within thirty (30) calendar days after such disclosure. “Confidential Information” shall not include information which: (a) was in the possession of, or was known by, the receiving party ("Recipient") prior to its receipt from the disclosing party (“Discloser), without an obligation owed to Discloser, or its licensors, to maintain its confidentiality; (b) is or becomes generally known to the public without violation of this Agreement by the “Recipient”; (c) is obtained by Recipient from a third party, without an obligation owed to such third party to keep such information confidential; or (d) is independently developed by Recipient without use of any Confidential Information of the other party. Recipient agrees that it shall use reasonable care to keep the Confidential Information of the other party strictly confidential and not disclose it to any other person except to its Affiliates and its and their respective employees, contractors, consultants, agents, customers and representatives (other than Members) who have a “need to know” for the purposes of this Agreement and are obligated by Licensee to be bound by the same confidentiality obligation which Recipient is bound by under this Exhibit H, provided however that Recipient may disclose Highly Confidential Information only in accordance with Section 2 of this Exhibit H. Recipient shall be responsible for any breach of such confidentiality obligation by such parties, including former employees, Affiliates, contractors, consultants, agents, customers (other than Members) and representatives. Recipient shall protect the Confidential Information of the other party with the same degree of care as it normally uses in the protection of its own similar confidential and proprietary information, but in no case with any less than reasonable care. Notwithstanding anything in this Exhibit H to the contrary, Confidential Information may be disclosed by Recipient pursuant to the order or requirements of a court or governmental administrative agency or other governmental body of competent jurisdiction, provided that (x) Discloser has been notified of such a disclosure request immediately after Recipient knows such order or requirements in order to afford Discloser reasonable opportunity to obtain a protective order or otherwise prevent or limit the scope of such disclosure to the extent permitted by law and (y) Recipient cooperates in good faith with such efforts by Discloser. The obligations under this Exhibit H shall terminate three years after the date of the last shipment of product using the Licensed Technology by Licensee or any other licensee of the Licensed Technology; provided that Sections 2.0(b), 2.0(c), and 3.0 in this Exhibit H shall cease to apply when the Recipient has returned all tangible embodiments of Licensed Technology in its possession to the Discloser.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!