Dodona and your data
For the correct operation of Dodona, it is necessary to keep track of some data about our users. On this page, we explain what data we store, why we need that data, and who has access to the data. If you have any further questions, don’t hesitate to contact us.
When signing into Dodona, we exclusively use external authentication systems. Examples of these are Office 365, Google, Smartschool (for secondary education only) and SAML (for higher education only). This means that under no circumstances, Dodona gets access to your password. What we do get access to when signing in are your name, username and email address. We need these data to identify you correctly and to be able to contact you in case of any problems. Next to that, we also store the institution you used to sign in, your preferred language and your local timezone. Your timezone is needed to display any deadlines set by courses correctly.
You can check these data for yourself on your profile page. Your profile is also visible for the teachers of the courses you subscribed to.
By using Dodona, you also generate additional Dodona-specific data which we store for the correct operation of the platform. For example, we need to keep track of all the courses you’re subscribed to and which submissions you made. For each submission, in addition to your submitted code, we also store the result and time of submission.
An overview of all your submissions can be seen on this overview page. Teachers can also see all submissions for the exercises of their courses. For some exercises, part of the generated feedback is only visible to the teachers.
We have the ambition to transform Dodona into an intelligent platform that optimally supports students in acquiring programming skills. We could do this, for example, by offering dynamic learning paths and by recommending exercises about a specific topic or of a certain difficulty. At the same time, we wish to give teachers insight into the progress of their students to enable them to optimise their teaching.
To develop and eventually provide these functionalities, it is necessary to (automatically) process the available data, for example, using machine learning. When doing this, the data will always be pseudonymised and in many cases, aggregated. Your personal data will be decoupled from your submissions using this de-identification procedure and will not be processed. By doing this, the risk of unwanted identification of people within Dodona is minimised.
Insights acquired from using and developing these innovative educational technologies can be published as scientific research. Within this context, we will never share or publish data that would allow the identification of individual users unless explicit permission is given.
To safeguard the availability of Dodona, it is necessary to monitor the status of our servers. This means, for example, that we keep track of the load of individual machines, and that we use heavily aggregated data to keep an eye on the length of the submissions queue and the number of active users.
Individual servers also keep log files of all activity on those machines. These files are kept for a maximum of 7 days and are only accessible to the platform administrators. Platform administrators can also request specific data on Dodona itself. As with the log files, these data are only accessed in the event of problems or to make technical adjustments.