That is naive. Say the company (any company) grows and eventually multiple people will have access to the password list. If it is hashed that provides a level of security against internal theft/abuse. If it isn't then an employee steals your login credentials, goes home, logs in as you with your unique secure password and withdraws all your coins.
There is a reason hashed passwords is a security standard. Password resuse is on vulnerability but it isn't the only one.
No such threat exists currently because only one person has access to any such data (myself). Employees of any company are expected to treat data in a secure fashion. My bank for instance knows my password and all security questions. Any employee I call has access to that data. More factors of authentication is always good and helps restrict what employees can do though, which I've added in the next update.
I think the biggest weakness with any of these systems is the human element which is why I reduced the need for them to the bare essentials. Handling 10 minutes of support a day for over 7000 accounts isn't too hard for me atm but thinking longer term if the site is very successful then new arrangements will have to be made because I always want to restrict that human element, the biggest weakness.
