The Shared Personal Data Clause Samples

The Shared Personal Data. Categories of data to be shared Staff Member - first and last name, address, including postcode, date of birth, gender, mobile phone number, school, employee/payroll number, e- mail, saliva test results. Pupil - first and last name, address, including postcode, date of birth, gender, mobile phone number, e-mail, Unique Pupil Number, school, class and for secondary school tutor and year group, saliva test results. Parent or Guardian of Pupil - first and last name, address, including postcode, mobile phone number, e-mail. School contractor – first and last name, address, including postcode, date of birth, gender, mobile phone number, school, e-mail, saliva test results.
View SourceView Similar (2)
The Shared Personal Data. 4.1 The Shared Personal Data, including any applicable restrictions relating to it agreed by the Parties is described fully in Schedule 1. 4.3 The Disclosing Party shall ensure that the Shared Personal Data is accurate and up- todate prior to its disclosure to the Receiving Party. 4.4 The Parties shall use compatible technology for the processing of the Shared Personal Data in order to preserve accuracy.
View Source
The Shared Personal Data. Categories of data to be shared Staff Member - first and last name, address, including postcode, date of birth, gender, mobile phone number, school, e-mail Pupil - first and last name, address, including postcode, date of birth, gender, mobile phone number, school, class and for secondary school tutor and year group Parent or Guardian of Pupil - first and last name, address, including postcode, mobile phone number, e-mail. Categories of Data Subject Participants drawn from a. School staff, b. School pupils. Who in Schools shares the data? ▇▇▇▇▇ ▇▇▇▇▇▇▇▇, Admin Officer Date planned for sharing Between week commencing 7 September 2020 and 31 October 2020 How will it be shared? By encrypted Excel spreadsheet by zip file which is password protected with password being supplied separately to UHS to a nominated person. Who in UHS receives the data? Overall supervision of Systems Team is responsibility of Professor ▇▇▇▇▇ ▇▇▇▇▇▇▇▇▇, Systems Lead Programme. ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇@▇▇▇.▇▇▇.▇▇ What happens with the data when it is received? Used for the Permitted Purpose. For the avoidance of doubt the Shared Personal Data will not be used for communications from the Receiving Party to those data subjects who have not consented to participation in the Programme by submitting samples for testing without the agreement of the head teacher of the School. What retention period shall be applied to that data? The information processed by the NHS is kept for as long as it is required to provide the participant with direct care and to support NHS initiatives to fight COVID-19. Information held for direct care purposes are stored in line with the Records Management Code of Practice for Health and Social Care 2016. This means such information will be held for up to 8 years before it is deleted. Any personal data gathered as part of this Feasibility Study for other purposes will be deleted at the end of the Feasibility Study. For the avoidance of doubt, the encrypted Excel spreadsheet providing the data will be destroyed at the end of the schools testing programme and the Shared Personal Data of any person who does not or whose child does not participate in the provision of saliva samples will be deleted from the UHS database at the end of the Feasibility Study in both cases on or before 31 October 2020.
View Source
The Shared Personal Data. 3.1 The Shared Personal Data, includes any data shared under the ▇▇▇▇ between the parties. 3.2 No special category personal data is to be shared between the parties. 3.3 The Disclosing Party shall ensure that the Shared Personal Data is accurate and up-to- date prior to its disclosure to the Receiving Party. 3.4 The parties shall use compatible technology for the processing of the Shared Personal Data in order to preserve accuracy.
View Source
The Shared Personal Data must not be irrelevant or excessive with regard to the Purpose.
View Source

Related to The Shared Personal Data

  • Shared Personal Data This clause sets out the framework for the sharing of personal data between the parties as data controllers. Each party acknowledges that one party (the Data Discloser) will regularly disclose to the other party (the Data Recipient) Shared Personal Data collected by the Data Discloser for the Agreed Purposes.

  • 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.

  • 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.

  • Your Personal Data If you determine that you will be supplying us with your Personal Data (as defined in the Data Processing Addendum referenced below) for us to process on your behalf, in the provision of maintenance and support services or hosting services (if the Product licensed to you is a Hosted Service) or during the course of any audits we conduct pursuant to section 1.14 (Audit), you may submit a written request at ▇▇▇▇▇▇▇@▇▇▇▇▇▇▇▇.▇▇▇ for the mutual execution of a Data Processing Addendum substantially in the form we make available at ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/docs/default-source/progress-software/data-processing-addendum.pdf and we will enter into such Data Processing Addendum with you. To the extent there is any conflict between this ▇▇▇▇ and such Data Processing Addendum, the Data Processing Addendum will prevail with respect to our handling and processing of your Personal Data.

  • 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.