Scholendar privacy policy

This is the Scholendar privacy policy. It is in place to inform you about the data we collect, process, store, and distribute, and how we do it to protect you as a consumer.

Small disclaimer.
It's incredibly important to understand that there exists no 100% safe way of transferring and storing data on the internet. Exploits and bugs happen all the time, and due to that we stress that the consumer takes on some responsibility to keep their own data safe by using safe passwords and transferring methods.

How do we protect your data?
We are constantly working to keep ourselves up to date with data protection. We do our best to lock down our servers, and to plug any security holes in our algorithms. Your data is protected with the most recent of protection standards. Your passwords are hashed in such a way that the result cannot, with modern day computers, be reversed back to your clear text password before the end of the human civilization. We also provide our service through the “Hypertext Transfer Protocol Secure” or HTTPS to further encrypt and secure data and data transfer.

What data do we store on our servers?
Most of the data we store is the data that you provide for us willingly. In this case it’s your email, a heavily encrypted version of your password, the notes you choose to write down and save in our note editor, your classes, and your event information, along with other data you choose to provide. At the moment we do in fact store no data behind your back, but we are going to implement features in the future that will help make logins and the similar far more secure, as well as to give us an overview of how you use our application.

What data is stored in the form of cookies, and why?
Currently we store only the most essential information for the operation of our application in the form of cookies. The cookies are set once you perform a willing action, which means we use no cookies to keep track of you across the internet. We only use cookies to make our application work as it’s supposed to. Examples of these cookies are your login token (the token your browser is given to identify you once you click on the “remember me” button), and application settings (such as the application theme).