Data privacy considerations for the web application

Data privacy considerations for the web application

1. Data from the users of the application

   • Passwords and other text or numerical data
     • To ensure that the data is secure, the website data should not be accessable by only someone with admin password
       • Only with the admin password can the user change the data in the datebase within the web application
         • This normally wouldnt be possible on a regular website, but for prototype purposes this must be implimented
     • When entering passwords, what is being written by the user should be in dots rather than the actual characters
       • This will stop unintended surrounding people from seeing the inputted passwords
     • Due to the constraints from the avalible coding knowledge, the normal security function of a sign in web application cannot be done
       • Usually the passwords would be stored in an encrypted format, buy for this prototype data web application plain text will serve ok
     • To see this sensitive information, a certain amount of layers into the website must be passed
       • This can include a specific tab that indicates where you can view the passwords, to increase security by reducing the number of unintended people can see the user's password
     • For chnage oer edit some of the more sensitive data, such as debit card details and passwords, the current password must be rentered into the website
       • This will reduce the chance that if the user is already logged into the webste due to it being saved in the browser data, another person cannot access it.