A few ethical issues would be keeping the privacy of someone secure, knowing there could possibly be a security breach thus exposing someone’s personal information, the possibility of having inaccurate information, and who ultimately is given access to the information. I feel like the first point I am trying to make is obvious, but, if someone gives you private information it is then your responsibility to keep it that way. Somebody is trusting you by giving you some sort of information that they do not want to be made public, and by potentially ruining that, you will most likely lose their trust. Next, I think another obvious issue is preventing a security breach on your system. If someone unauthorized to access your system got into it, they could have all the information you told your customers would be kept private. A security breach could also result in the loss of being able to serve your customers until the issue is resolved. When you are dealing with something that requires information you have stored, you risk have the inaccurate information. Let us say you needed to send someone their monthly bill. Should be easy, right? You have their address stored which they gave you just send it out to them. But what if they ended up moving and forgot to notify you about the move. Now you are sending sensitive information to a random person who might try and use it against your customer. Lastly, we need to really consider who we are giving access to this information. Like a previous point, once a customer puts their trust in you that you will keep their information secure, you are now obligated to do your best to keep it private. This means maybe doing a deeper background check on someone that is given access. No matter what type of information you are trying to keep secure, you need to trust who you appoint as much as you would trust a seatbelt to keep you safe in the event of a car crash.