uzh / marugoto

Marugoto: eLearning Framework for Story Telling
GNU General Public License v2.0
8 stars 6 forks source link

Data protection clarity (and text for frontpage) #45

Closed martindusinberre closed 4 years ago

martindusinberre commented 5 years ago

Can we have absolute clarity on what text we need to include on the frontpage for data protection (and whether we need to be more explicit about email storage protections, pseudonyms etc)?

martindusinberre commented 5 years ago

Leyla will talk to her colleagues at DLF about this with particular reference to whether student input in MOOCs (or Adfontes) count as "private data". Ideally, she would be able to come back to us with a draft text that could go on the game's frontpage (in one of the tabs)

lfeine commented 5 years ago

I asked about the data privacy and Anita said the deciding factor is where our data is stored. If it's all within the university/switzerland, it shouldn't be a problem, but we should probably include some sort of user agreement that specifies how long the data is stored and what it's used for. If the data is stored with a third party outside of switzerland, we'd have to make a contract with them. Anita could help with that though.

martindusinberre commented 5 years ago

Pim, can you please check where our data will be stored so that Leyla can get back to DLF? Thanks, Martin

witlox commented 5 years ago

data will only be stored in system, as long as the system is hosted in Switzerland, the data will reside in Switzerland.

martindusinberre commented 5 years ago

Now that we're clear from Pim that the data is stored in Switzerland, then it's time to deal with this from your previous comment: "we should probably include some sort of user agreement that specifies how long the data is stored and what it's used for". @witlox can you let Leyla know this, and then @lfeine can you please go to Anita in DLF and see if they have some kind of template text we can use for the LiT frontpage? Thanks

lfeine commented 5 years ago

Will do.

However, if we want to be very correct about it, the website does use google fonts, which allows google to skim some data from our users. It is a small amount of potential data and google says they do not use it, but technically we are subject to their API agreement (FAQ ). The fonts could be hosted directly on our servers as well, but I'm not sure if this is enough of a priority to make an issue for it. It's just a technicality to be aware of.

martindusinberre commented 5 years ago

Great, thanks Leyla. Does that mean that we don't need any data protection text on the frontpage? Or some kind of general text similar to what DLF has for its own projects?

lfeine commented 5 years ago

We will definitely need some sort of disclaimer. I will ask Anita for more information.

interrogator commented 4 years ago

@lfeine I can add it, but don't know what the text is. Please add it here, ideally as HTML but plain text with links at bottom OK too

lfeine commented 4 years ago

Sorry, I've sent it directly to Pim! Here's the text (it's a txt file but contained within should be valid HTML I've written up) TOS.txt

interrogator commented 4 years ago

OK, these terms have been added to the site, so closing