What kind of information do we collect?
Sign-up details: If you register or sign up for events, newsletters or projects with the Oxford Hub, we will ask you for personal information such as your name, email address, and other contact details such as a contact phone number.
Job application details: If you apply online for a job at Oxford Hub, we will collect information about you and your experience through that application process.
Referral details: We hold contact details and personal information on people who have been referred to our programmes e.g. Branch Up, Big Brothers Big Sisters and LinkAges Connect.
We take steps to protect your personal information and follow procedures designed to minimise unauthorised access or disclosure of your information.
Oxford Hub shall ensure that personal data is stored securely using software that is kept-up-to-date.
Access to personal data shall be limited to personnel who need access and appropriate security should be in place to avoid unauthorised sharing of information.
When personal data is deleted this should be done safely such that the data is irrecoverable.
Appropriate back-up and disaster recovery solutions shall be in place.
Archiving / removal
We will only keep any personal information that you provide to us for as long as is necessary to fulfil the purpose for which you gave us the information and we will securely delete information when it is no longer needed for that purpose, as explained in more detail below.
To ensure that personal data is kept for no longer than necessary, the Charity shall put in place an archiving policy for each area in which personal data is processed and review this process annually.
The archiving policy shall consider what data should/must be retained, for how long, and why.
In the event of a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data, Oxford Hub shall promptly assess the risk to people’s rights and freedoms and if appropriate report this breach to the ICO (more information on the ICO website).