Data Processor Agreement Sample Clauses

Data Processor Agreement. When you provide content in the form of data and information, of any kind, to the Dropboy Platform, website or other Dropboy managed media, including via email, this data can contain personal data pertaining to private as well as business persons. In respect of such personal data, and in accordance with EU’s GDPR regulations, Dropboy take up the role as Data Processor for the User’s data as well as the User’s customer data. By accepting the terms of this user agreement the User also accepts a Data Processor Agreement (DPA) between Dropboy and the User. Dropboy provides all customers access to historical order data 6 month back in time from the date when an order was created/uploaded. Should a customer wish access to older order data this must be separately agreed with Dropboy.
AutoNDA by SimpleDocs
Data Processor Agreement. Any processing of personal data by a processor must be governed by a Data Processor Agreement as required under Article 28(3). The General Data Protection Regulation sets out the specific requirements of such an agreement (see checklist in Appendix A). A Data Processor Agreement may be provided by the processor, or the University. The Data Protection Officer should be engaged to review the agreement to ensure it is compliant with the requirements of the regulation.
Data Processor Agreement. 1. The contact details of the HLO’s and each Partner’s Data Protection Officer (DPO) are: HLO’s DPO Name and address: Xxxx Xxxxx, Xxxxx Xxxxx, Xxxxxx Xxxx Xxxx, Xxxxxx BL1 1RU Tel: 00000 000000 Email: xxxx.xxxxx@xxxxxx.xxx.xx Bury Music Service DPO Name and address: Tel: Email: One Education DPO Name and address: Tel: Email: Oldham Borough Council DPO Name and address: Xxxxxx Xxxxx, Xxxxx Xxxxxx Xxxx Xxxxxx Xxxxxx, XX0 0XX Tel: 0000 000 0000 Email: XXX@xxxxxx.xxx.xx Rochdale Borough Council DPO Name and address: Tel: Email: Salford City Council DPO Name and address: Tel: Email: Stockport Metropolitan Borough Council DPO Name and address: Tel: Email: Tameside Borough Council DPO Name and address: Tel: Email: Trafford Borough Council DPO Name and address: Tel: Email: Wigan Borough Name and address: Council DPO Tel: Email: Description Details Identity of the Controller and Processor The Parties acknowledge that for the purposes of the Data Protection Legislation, the HLO is the Controller and each Partner is a Processor in accordance with paragraph 2.1 of the amin body of the Data Protection Schedule. Subject matter of the processing The processing is needed to (a) provide parents/carers with information about the musical activity (start and finishes times, venues, what students need to bring with them) and (b) ensure that the GMBD Music Hub appropriately safeguard all children involved in its activities. Whilst the HLO will need to collect Personal Data of Staff working for the GMBD Music Hub Personal Data will also need to be collected for individual Staff employed by the Partners. Duration of the processing Personal Data is only kept by the GMBD Music Hub whilst the children and young people are engaging with the activity as students. The HLO ask that the parents of the children and young people re-register the child every year to ensure that Personal Data is not retained for longer than required. Personal Data relating to Staff will only be kept during their involvement in the GMBD Music Hub. Nature and purposes of the processing The HLO will carry out its duties as the lead organisation which will involve leading new musical activities which bring together young people from across the region. Therefore, the HLO will need to collect data from young people and their families from other boroughs in the regional GMBD Music Hub. The HLO’s role is to create new regional music programmes and communicate with young people and their families in relation to these ...
Data Processor Agreement. All processing of Customer data shall be governed by the Data Processor Agreement and will take precedence over any corresponding provision in this or other agreements.
Data Processor Agreement. Maestro Xxxx xxxxx purposefully to ensure that the Software complies with applicable privacy laws and regulations. The Customer can request additional, non-public information about data processing from Maestro Soft. Please note that such requests may require a non-disclosure agreement. Maestro Soft reserves the right to bill its standard rates for such requests. The Customer can contact Maestro Soft's Data Protection Officer at: xxxxxxxxxx@xxxxxxx.xx In connection with the delivery of Software and lookup, transfer/sharing services and other online services that the Software uses in accordance with Maestro Software Agreement, Maestro Soft processes personal data on behalf of the Customer in accordance with these Terms. The Customer is responsible for the processing of Customer data, and is solely responsible for ensuring that the processing of personal data takes place in accordance with the Personal Data Protection Regulation (see Personal Data Protection Regulation Article 24), the applicable personal data protection provisions in Union law or the Member States' national law and these Terms and Conditions.
Data Processor Agreement. The Issuer shall instruct the Servicer, where the Servicer Processes Personal Data (as defined in the Data Protection Legislation) as a Data Processor on behalf of the Issuer, to take such steps in the processing of such personal data as:
Data Processor Agreement. This Data Processing Agreement (the “DPA”) details the parties’ obligations on the protection of Personal Data associated with Our Processing of Your Personal Data within the scope of the applicable Order or any agreement between You and Us for providing Services (hereinafter, the “Agreement”).
AutoNDA by SimpleDocs
Data Processor Agreement. When you provide content in the form of data and information, of any kind, to the Dropboy Platform, website or other Dropboy managed media, including via email, this data can contain personal data pertaining to private as well as business persons. In respect of such personal data, and in accordance with EU’s GDPR regulations, Dropboy take up the role as Data Processor for the User’s data as well as the User’s customer data. By accepting the terms of this user agreement the User also accepts a Data Processor Agreement (DPA) between Dropboy and the User.
Data Processor Agreement. 13.1 The Licensee warrants and represents that it will always comply with the terms of the Data Processor Agreement set out in Schedule 4.

Related to Data Processor Agreement

  • Data Processing Agreement The Data Processing Agreement, including the Approved Data Transfer Mechanisms (as defined in the Data Processing Agreement) that apply to your use of the Services and transfer of Personal Data, is incorporated into this Agreement by this reference. Each party will comply with the terms of the Data Processing Agreement and will train its employees on DP Law.

  • Vendor Agreement (Part 1)

  • Vendor Agreement 230105 Vendor Agreement pdf The Vendor Agreement must be downloaded from the “Attachments” section of the IonWave eBid System, reviewed, Vendor Name placed in the line provided at the top, and uploaded to this location. If Vendor has proposed deviations to the Vendor Agreement, Vendor may assert so in the Attribute Questions and those shall be addressed during evaluation.

  • Data Processing Addendum The parties’ agreement with respect to the processing of personal information submitted to the Subscription Service is described in the Data Processing Addendum attached to this Subscription Service Guide as Exhibit A.4 and incorporated herein by reference. The Data Processing Addendum may be updated periodically.

  • Our Agreement You, the Insured/ Insured Person, and We, the Company, agree

  • Client Agreement 2.1. The Company may unilaterally change any terms of this Client Agreement for any of the following reasons:

  • 230104 Vendor Agreement (Part 1).pdf If responding to Part 1, the Vendor Agreement must be downloaded from the “Attachments” section of the IonWave eBid System, reviewed, Vendor Name placed in the line provided at the top, and uploaded to this location. If Vendor has proposed deviations to the Vendor Agreement (Part 1), Vendor may assert so in the Attribute Questions and those shall be addressed during evaluation. Vendor Agreement Signature Form (Part 1) 230104 Vendor Agreement Signature Form (Part 1).pdf If responding to Part 1 the Vendor Agreement Signature Form (Part 1) must be downloaded from the “Attachments” section of the IonWave eBid System, reviewed, properly completed, and uploaded to this location. If Vendor has proposed deviations to the Vendor Agreement (Part 1), Vendor may leave the signature line of this page blank and assert so in the Attribute Questions and those shall be addressed during evaluation.

  • Service Agreement Refers to the Contract, Purchase Order or Terms of Service or Terms of Use. Student Data: Student Data includes any data, whether gathered by Provider or provided by LEA or its users, students, or students’ parents/guardians, that is descriptive of the student including, but not limited to, information in the student’s educational record or email, first and last name, birthdate, home or other physical address, telephone number, email address, or other information allowing physical or online contact, discipline records, videos, test results, special education data, juvenile dependency records, grades, evaluations, criminal records, medical records, health records, social security numbers, biometric information, disabilities, socioeconomic information, individual purchasing behavior or preferences, food purchases, political affiliations, religious information, text messages, documents, student identifiers, search activity, photos, voice recordings, geolocation information, parents’ names, or any other information or identification number that would provide information about a specific student. Student Data includes Meta Data. Student Data further includes “Personally Identifiable Information (PII),” as defined in 34 C.F.R. § 99.3 and as defined under any applicable state law. Student Data shall constitute Education Records for the purposes of this DPA, and for the purposes of federal, state, and local laws and regulations. Student Data as specified in Exhibit “B” is confirmed to be collected or processed by the Provider pursuant to the Services. Student Data shall not constitute that information that has been anonymized or De-Identified, or anonymous usage data regarding a student’s use of Provider’s services.

  • COMMENCEMENT OF WORK UNDER A SOW AGREEMENT Commencement of work as a result of the SOW-RFP process shall be initiated only upon issuance of a fully executed SOW Agreement and Purchase Order.

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