Originally Posted by
bengl3rt
I definitely considered that and figured the best way to solve that problem is to have the app never remember your mileage account password - so, every time you updated the app's local cache of your status information, you would have to enter the password. It would be tedious but it would certainly make me sleep easier knowing I wasn't liable for a ton of passwords if my server got broken into.
Yes that sounds like a good idea. The issue is you will have to make the source open to vet this out by other developers / hackers. If the software is closed source then it would be impossible to vet this independently.