confluence-users, domain admins, domain users, jira-users, producers, stash-users, virtual vision mixer, vision mixer (obs)
9
edits
YSTV Constitution: Difference between revisions
From YSTV Documentation Wiki
no edit summary
Caroline.pv (talk | contribs) m (formatting error) |
Alize.akturk (talk | contribs) No edit summary |
||
| Line 220: | Line 220: | ||
##To organise social events for members of YSTV to facilitate the above; | ##To organise social events for members of YSTV to facilitate the above; | ||
##To encourage people to get involved with YSTV through socials. | ##To encourage people to get involved with YSTV through socials. | ||
Data Protection | |||
* All membership personal data is subject to General Data Protection Regulations (GDPR), law and YUSU procedures. | |||
* The Lead Signatory is responsible for the safety and security of all membership personal data held outside of YUSU software and systems and must take all reasonable steps to ensure access to YUSU software and systems is not shared without YUSU consent. | |||
* The Lead Signatory is required to successfully undertake GDPR online awareness and compliance training supplied by YUSU. | |||
* The Lead Signatory must advise YUSU of any breaches of data protection as soon as they are made aware of any such breach. | |||
* The Lead Signatory can formally nominate a Data Protection Officer from the Lead Signatory who is responsible for overseeing the society’s compliance to GDPR and YUSU procedures. | |||
Key responsibilities include: | |||
#Membership personal data including email addresses are private and confidential and should only be used for society membership purposes and contact that would be reasonably expected as part of the membership offer. | |||
#Bulk or multiple emailing must only be done as “bcc”. | |||
#The Lead Signatory is responsible for obtaining the necessary consents from members to hold and process personal data in relation to membership. | |||
#The Lead Signatory must not share membership personal data with any other society, university department or external organisation without the prior written consent of the data subject or YUSU. | |||
#The Lead Signatory must advise YUSU of any breaches of data protection as soon as they are made aware of the breach. | |||
#Failure to follow YUSU’s data protection guidance and procedures will constitute grounds for de-ratification and/or disciplinary procedures. | |||
==Representation in YUSU Media Comittee== | ==Representation in YUSU Media Comittee== | ||
