CONTROLLER AND PROCESSOR OBLIGATIONS Sample Clauses

CONTROLLER AND PROCESSOR OBLIGATIONS. 2.1 This paragraph 2 relates to the following processing activities, in relation to which Pebble is deemed a Data Processor, and the Provider is deemed a Data Controller, pursuant to Data Protection Laws: Subject matter and duration of the Processing of Personal Data: The subject matter and duration of the Processing of Personal Data are set out in the Agreement. The nature and purpose of the Processing of Personal Data: To enable Pebble to provide the Pebble Services under the Agreement. The types of Personal Data to be Processed: ● Full name ● Date of birth 15 ● Contact information (email address, home address, business address and telephone number) ● Role of Provider Personnel ● Name(s) of child/children The categories of Data Subject to whom Personal Data relates: Provider Personnel, Care Seekers and Children. The obligations and rights of the Provider: The obligations and rights of the Provider are set out in the Agreement.
Sample 1
AutoNDA by SimpleDocs
CONTROLLER AND PROCESSOR OBLIGATIONS. 2.1 To the extent that Data Protection Laws apply to the processing of Customer Personal Data, the parties acknowledge and agree that: (a) MinervaDB Inc. is a Processor, and Customer is a Controller or Processor (as applicable) with regard to the processing of Customer Personal Data; and (b) each party shall comply with its obligations under Data Protection Laws, and this DPA, when processing Personal Data.
Sample 1
CONTROLLER AND PROCESSOR OBLIGATIONS. 4.1 As between the Parties, Customer shall be liable and responsible as the Controller and Palantir shall be liable and responsible as the Processor, in respect of Customer Personal Data. The subject matter and details of Processing are as described in the Agreement and this DPA, including Exhibit B (Subject Matter and Details of Customer Personal Data Processing). In the event that Customer acts as a Processor (or Subprocessor) in respect of Customer Personal Data, Customer represents and warrants to Palantir that it is validly authorized by the relevant Controller to enter into this DPA and to provide Customer Instructions (as defined below) on behalf of the Controller in relation to Customer Personal Data. The Products and Services provide Customer with a number of controls, including security features and functionalities, that Customer may use to retrieve, correct, delete or restrict Content (including Customer Personal Data) as described in the Documentation. Customer may use these controls as technical and organisational measures to assist it in connection with its obligations under Data Protection Laws, including its obligations relating to responding to requests from Data Subjects.
Sample 1

Related to CONTROLLER AND PROCESSOR OBLIGATIONS

  • Processor Obligations 4.1 The Processor may collect, process or use Personal Data only within the scope of this DPA.

  • Sub-processor Obligations MailChimp shall: (i) enter into a written agreement with the Sub-processor imposing data protection terms that require the Sub-processor to protect the Customer Data to the standard required by Data Protection Laws; and (ii) remain responsible for its compliance with the obligations of this DPA and for any acts or omissions of the Sub-processor that cause MailChimp to breach any of its obligations under this DPA.

  • Contractor Obligations The Contractor is responsible for fully meeting all Contract obligations set forth in the OGS Centralized Contract and for providing services in accordance with the Contract and any Authorized User Agreement, Statement of Work or Purchase Order.

  • Operator Obligations 2.01 The Operator shall:

  • Developer Obligations In accordance with applicable NYISO requirements, Developer shall maintain satisfactory operating communications with Connecting Transmission Owner and NYISO. Developer shall provide standard voice line, dedicated voice line and facsimile communications at its Large Generating Facility control room or central dispatch facility through use of either the public telephone system, or a voice communications system that does not rely on the public telephone system. Developer shall also provide the dedicated data circuit(s) necessary to provide Developer data to Connecting Transmission Owner and NYISO as set forth in Appendix D hereto. The data circuit(s) shall extend from the Large Generating Facility to the location(s) specified by Connecting Transmission Owner and NYISO. Any required maintenance of such communications equipment shall be performed by Developer. Operational communications shall be activated and maintained under, but not be limited to, the following events: system paralleling or separation, scheduled and unscheduled shutdowns, equipment clearances, and hourly and daily load data.

  • Parties to Perform Obligations 16.4.1 Notwithstanding the existence of any Dispute and difference referred to the Appropriate Commission and save as the Appropriate Commission may otherwise direct by a final or interim order, the Parties hereto shall continue to perform their respective obligations (which are not in dispute) under this Agreement.

  • Contractor Guaranties Contractor shall:

  • Supplier Obligations At all times during the Term, the Supplier is required to:

  • OBLIGATIONS OF THE CONTRACTOR AND SURETY The Contractor and the Surety, in consideration of the award of this Contract to the Contractor, jointly and severally for themselves, their heirs, executors, administrators, and successors or assigns, hereby guarantee, covenant and agree to and with the Owner that:

  • On-Site Obligations If Red Hat personnel are working on Client’s premises (a) Client will provide a safe and secure working environment for Red Hat personnel, and (b) Red Hat will comply with all reasonable workplace safety and security standards and policies, applicable to Client’s employees, of which Red Hat is notified in writing by Client in advance.

Time is Money Join Law Insider Premium to draft better contracts faster.