Personal data to be processed Clause Samples

The 'Personal data to be processed' clause defines which specific types of personal data will be collected, used, or handled under the agreement. It typically lists categories such as names, contact details, identification numbers, or other information that can identify an individual, and may specify the purposes for which this data is processed. By clearly outlining the scope of personal data involved, this clause ensures transparency and compliance with data protection laws, helping both parties understand their responsibilities and reducing the risk of unauthorized or unintended data processing.
Personal data to be processed. The following classes of personal data may be processed under this joint data controller agreement: • personal details of the aggrieved/person affected (PA) • personal details of any representative making the complaint on behalf of the PA • family details of the PA • personal details of other people involved in the case • lifestyle and social circumstances • goods and servicesfinancial details • employment and education details • details of complaints, incidents and grievances • visual images, personal appearance and behaviour • responses to surveys We also process special categories of personal data, and other sensitive classes of information that may include: • physical or mental health details • racial or ethnic origin • religious or other beliefs • political opinions, sexual life • trade union membership offences (including alleged offences) • criminal and legal proceedings, outcomes and sentences
Personal data to be processed. The Company may only enter the personal details which A New Spring indicates by means of the Web Application and/or which are agreed separately. Company can freely choose the categories of data subjects and personal data and the associated forms of processing from within the Web Application. Parties therefore accept that a separate annex with this information is not useful. The Company will never enter special personal details (for example medical records, religious affiliation, criminal record, sexual preference, union membership, etc) or citizen service numbers in the Web Application or allow its users to do so without specific consent from A New Spring. Company recognizes that the A New Spring security measures are not focused on the processing of special personal data or citizen service numbers and does not need A New Spring to do so. By allowing the entry of personal data, the Company guarantees that it has permission or has other legal grounds for the processing via the A New Spring Platform. A New Spring cannot be held responsible for claims based on a breach of this warranty.
Personal data to be processed. 2.1. Account creation, account details and related information (first and last name, personal identification code, email address, phone number, hardware, role, subjects, study groups, user institution and class, invitation from another user + inviter details, service usage time, and the user’s IP address). 2.2. Stuudium key, social media key on Facebook and Google, E-kool account key, user name, and email address, HarID account key, user name, email address, personal identification code.
Personal data to be processed. The Data Processor will Process Personal Data related to individuals ("Data Subjects”) as described in Section 1 (Personal Data in BizView365) of Bizview365 Privacy Policy. Data Controller may after the written approval from the Data Processor submit Uncontrolled Personal Data to the Service which may include, but is not limited to the Data Controller’s contacts, employees, contractors, collaborators, customers, prospects, suppliers and subcontractors. Personal Data will be Processed for purposes of providing the Services set out, as further instructed by Data Controller in its use of the Services, and otherwise agreed to in this DPA.
Personal data to be processed. 2.1. Account creation, account details and related information (first and last name, personal identification code, email address, phone number, hardware, role, subjects, study groups, user institution and class, invitation from another user + inviter details, service usage time, and the user’s IP address). 2.2. Stuudium key, social media key on Facebook and Google, E-kool account key, user name, and email address, HarID account key, user name, email address, personal identification code. 2.3. Licence in OPIQ. 2.4. User logs in OPIQ. 2.5. User-added study material (file, text), answers to tasks solved in the study material, notes and comments added to the study material. 2.6. Information about the student’s performance (student’s answers to the task, automatically checked feedback, teacher feedback in the form of corrections, grades, or other form). 2.7. Created/modified records. 2.8. Information about the finished study material, tasks, and bookmarks in the study material. 2.9. First and last name, email address, place of work (publisher) of the CMS (content management system) author, editor, etc. with whom OPIQ has a contractual relationship. 2.10. Accounting data (invoices paid by private user by name, term of license). When using a payment service, the user’s bank account number. 2.11. Usage records, e.g. browsing history, usage history of interactive components.
Personal data to be processed. Klippa undertakes to Process the Personal Data, Processed in the context of the performance of the Agreement, on the terms and conditions of this DPA. The nature and the Purpose of the Processing, as well as the type of Personal Data and categories of Data Subjects processed by Klippa on behalf of Licensee, is set out in the Agreement, in the absence of which the processing is limited to those activities strictly necessary for the performance of the Agreement. Notwithstanding the aforementioned, Klippa is allowed to process the Personal Data to the extent that Klippa is required to do so by either Union or member state law to which Klippa is subject. In such a case, Klippa shall inform Licensee of that legal requirement before processing, unless that law prohibits providing such information on important grounds of public interest
Personal data to be processed. The Company may only enter the personal details which A New Spring indicates by means of the Web Application and/or which are agreed separately. Personal data that is processed by A New Spring in any case are the minimum data to create an account, these are name and email address. Company can freely choose the categories of data subjects and additional personal data and the associated forms of processing from within the Web Application. Parties therefore accept that a separate annex with this information is not useful. The Company will never enter special personal details (for example medical records, religious affiliation, criminal record, sexual preference, union membership, etc) or citizen service numbers and passport numbers in the Web Application or allow its users to do so without specific consent from A New Spring. Company recognizes that the A New Spring security measures are not focused on the processing of special personal data or citizen service numbers and passport numbers and does not need A New Spring to do so. By allowing the entry of personal data, the Company guarantees that it has permission or has other legal grounds for the processing via the A New Spring Platform. A New Spring cannot be held responsible for claims based on a breach of this warranty.
Personal data to be processed. 2.1 The Data Controller agrees to provide the Data Processor with the relevant data required for ‘the Purpose and Nature’ of this Agreement. 2.2 The information to be provided will relate to the following categories of data Subjects: • Occupants • Applicants 2.3 The personal data to be processed about the aforementioned categories of data subjects will include: • Name and Contact details • Finance details • Warning Flags • Data about Sexual Orientation • Risk History Information • Capacity assessment information • Previous addresses • Previous legal action details • Safeguarding details 2.4 The data transferred to the Data Processor under the Agreement at no time becomes the property of the Data Processor
Personal data to be processed. The following classes of personal data may be processed under this joint data controller agreement:  personal details of the aggrieved/person affected (PA)  personal details of any representative making the complaint on behalf of the PA  family details of the PA  personal details of other people involved in the case  lifestyle and social circumstances  goods and servicesfinancial details  employment and education details  details of complaints, incidents and grievances  visual images, personal appearance and behaviour  responses to surveys We also process sensitive classes of information that may include:  physical or mental health details  racial or ethnic origin  religious or other beliefs  political opinions, sexual life  trade union membership  offences (including alleged offences)  criminal and legal proceedings, outcomes and sentences

Related to Personal data to be processed

  • Personal Data Processing 2.1 The Processor shall process Personal Data only on the basis of corresponding recorded orders from the Controller. 2.2 By way of exception, in particular in urgent cases, processing orders from the Data Controller may also be made orally. In this case, the Data Controller shall confirm as soon as possible and in writing, by any appropriate means, the instructions given orally. 2.3 Where the processing concerns the transmission of Personal Data to a third country outside the European Union or to an international organization, the Data Processor shall also comply with the relevant instructions of the Data Controller, unless different legal requirements exist under European Union laws or the laws of the Member State to which the Data Processor is subject. In such a case, the Data Processor shall inform the Data Controller before processing of the legal requirement in question, unless the said law prohibits this kind of information for reasons of substantial public interest. 2.4 The transmission of Personal Data to a third country outside the European Union is prohibited unless the Data Controller has given prior explicit approval to that end, and one of the following conditions is met: • the European Commission has resolved that an adequate level of protection of personal data is ensured in the country the Personal Data is to be transmitted; • the transmission is to be made to the U.S.A.; and the recipient of the Personal Data has acceded to and abides by the Privacy Shield Framework; • the transmission will be governed by the standard data protection clauses issued by the European Commission. 2.5 The Data Processor shall inform the Data Controller immediately upon receipt of the order or as soon as possible if he / she determines that the content of a particular processing order violates the Regulation and / or national law and / or the law of another Member State of the European Union (EU), and / or other provisions of EU law on the protection of Personal Data. 2.6 The Data Processor acknowledges that the Data Controller has full control over her Personal Data and determines any particular feature of the processing to which the Personal Data will be submitted. If the Data Processor ignores the instructions of the Data Controller and determines alone the scope, the means and generally any other matter concerning the processing of Personal Data, she shall render herself the Data Controller for the purposes of implementing the Regulation and the legal framework on the protection of Personal Data. The practical consequence of this is that, in addition to the full responsibility of the Processor towards the Controller, she shall carry the same level of responsibility vis-à-vis the independent supervisory authority (and any other competent state authority) as well as the Natural Persons - Data Subjects of the data being processed.

  • Student Data to Be Provided In order to perform the Services described in this Article and Exhibit “A”, LEA shall provide the categories of data described in the Schedule of Data, attached hereto as Exhibit “B”.

  • Personal Data Registry Operator shall (i) notify each ICANN-­‐accredited registrar that is a party to the registry-­‐registrar agreement for the TLD of the purposes for which data about any identified or identifiable natural person (“Personal Data”) submitted to Registry Operator by such registrar is collected and used under this Agreement or otherwise and the intended recipients (or categories of recipients) of such Personal Data, and (ii) require such registrar to obtain the consent of each registrant in the TLD for such collection and use of Personal Data. Registry Operator shall take reasonable steps to protect Personal Data collected from such registrar from loss, misuse, unauthorized disclosure, alteration or destruction. Registry Operator shall not use or authorize the use of Personal Data in a way that is incompatible with the notice provided to registrars.

  • Processing Personal Data This ▇▇▇▇▇ shall be completed by the Controller, who may take account of the view of the Processors, however the final decision as to the content of this Annex shall be with the Buyer at its absolute discretion.

  • Data to Be Provided In order for the Operator to perform the Services described in the Service Agreement, LEA shall provide the categories of data described in the Schedule of Data, attached as Exhibit B.