I understand your concerns. But let me clarify that this is a secure service. All sensitive information is stored encrypted, all traffic runs entirely over encrypted SSL and all goes through Plaid Technologies, one of the most prominent service provider of banking data. If you would like some more info, you should check: https://plaid.com/security/
That right there is why I won't use it regardless. No offense to you or Plaid's security. Just the idea I'm going to hand over the same credentials that let me transfer money out of my institution isn't an acceptable solution.
Zach here from Plaid (a bit late in responding). I understand the hesitations around privacy here; however, there's a difference between sharing credentials and account/routing number. SSSaving is using a read-only data feed that is authenticated by username and password. The app has no access to your account/routing data and cannot debit your account.
Your account and routing number are all that's needed to move money in or out of your account. SSSavings does not get these, nor should any application you don't want to debit you. Unfortunately, these numbers cannot be changed without shutting down the account (whereas credentials can be changed quickly).
Account numbers are usually hidden when logging in but are almost always available by downloading a statement or looking for any recently posted check images.
Same with routing numbers, though finding the routing number of a Bank of America account opened in CA, for instance, is just one google search away.
That said, I'm stoked about checking out Plaid sometime soon especially after reading the Yodlee docs (yikes!)
I don't agree with this mindset at all. People should build things they want to build. I agree—I wouldn't hand my bank credentials over to this service (or really any unknown third party), but I don't think we should say that the OP should have spent their time on something else.
