Page last updated with slight tweaks 17/8/19; author CST/CE, incorporating material from WordPress.org, licence: Attribution 4.0 International (CC BY 4.0) .
Who we are
Our website address is: https://www.coresystemtrust.org.uk. To find out more about us if you don’t know it already, see about CST. In data protection, privacy, GPDR terms we are a not for profit, zero income, informal association operating, we believe in the public interest, but only holding personal data by consent.
We, either individually in relation to other roles we have, or occasionally on behalf of CST, process data to create information in the public interest about the CORE instruments. Such data comes to us either collected with consent, or under the GPDR principle of public interest. Regardless of whether it was collected with consent or under a public interest logic, we only receive it after it has been completely anonymised and is no longer personal data.
What personal data we collect and why we collect it
Posts and comments
If someone with author rights uploads images to the website, they are warned to avoid uploading images with embedded location data (EXIF GPS). Visitors to the website can download and extract any location data from images on the website.
If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.
If you have an account and you log in to this site, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.
Embedded content from other websites
Articles on this site may include embedded content (e.g. videos, images, articles, etc.) Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
With whom do we share data?
How long we retain your data
If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognise and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website, and as far as I can see that is only possible if I create a registration for you, which I would only do with your explicit permission and because you and we need your input to the site, then we store your Email address and any personal information you provide in your user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username and I don’t think they can not have an Email address saved). Website administrators can also see and edit that information, in theory that’s all three of the CST trustees but I am not sure that Michael or Frank will remember how to log in … which is probably something I should change in case I die! I suspect that it’s not insuperably difficult for administrators at the ISP we use to host the site to see that data but I trust them that they won’t (and their contract with us promises that they won’t). The are Mythic Beasts and, though I can’t yet (23.v.18) see a privacy statement on their site, I know from conversations with them that they take privacy extremely seriously.
As noted, the only other data we have that can be personal data when you are the only person using an IP address is that address in the visit logging and tracking services. I have set the Google Analytics retention period for that data to 50 months, I don’t know what MonsterInsights does with its IP address data.
What rights you have over your data
If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Where we send your data
Visitor comments may be checked through an automated spam detection service.
Our contact information
The best way to contact me (CE)/us is via the Contact Us form here but snailmail can be sent to:
Prof. Chris Evans, c.o. Prof. Michael Barkham,
University of Sheffield,
1 Vicar Lane,
How we protect your data
Mythic Beasts have a 31 day backup retention programme for our data and excellent layers of protection and I keep a backup copy of the site, including all its data, on an encrypted drive.
What data breach procedures we have in place
To the best of my knowledge we have never had any and we store so little data of any interest to anyone that I’d be surprised if we ever do but if we do, the three trustees would confer and take advice to do everything legally necessary and everything technically wise in the light of the breach.
What third parties we receive data from
The only situation I can see in which I ever receive personal data about others from third parties is when someone writes to me recommending I contact another person. Very occasionally I might decide the introduction so clearly has permission that I would act on that and make contact with the other person, mostly I would just invite the third party to make an (E)introduction between us. I believe I can confidently say that for CST I have no personal information, beyond those IP addresses of people visiting the site, on anyone that they didn’t know I had.
What automated decision making and/or profiling we do with user data
None at the level of individuals.
Industry regulatory disclosure requirements
I am not aware of any that apply.
Content checker target (not for humans!): pW6QTTHWk@UHY