Absolutely not, this is a violation of Google's terms of service. You're probably going to get your google authentication API privileges yanked for printing that both here and on your website.
Thanks for raising your concerns. As far as we know, it is not in violation with Google's terms of service. Please point us to the clause in question if you think it is, and we will look into it.
Google also reserves the right to lock your account and require a working SMS-receiving cell phone number to identify you before unlocking it (even if you never gave them your phone number in the first place). They claim this is some sort of anti-spammer thing.
This has never been a problem with any Predictious user so far. We will work with any user who finds themselves in that situation to make sure they can access their funds some other way.
I am not going to trust my coins to an organization that (a) will let google lock me out of my deposits and (b) can't figure out how to use a standard like
OpenID. This is extra surprising since google's authentication APIs are basically just a proprietization of OpenID.
By only allowing Google, we ensure every user gets a consistent level of security we are comfortable with. If the question of authentication becomes a recurring issue brought up by users, we will definitely look at offering alternatives.
Sad, really. You've got a nice little site but clearly the security is not thought through well at all. You have major technological counterparty risk and seem to be unaware of it.
There is actually no counterparty risk. From the point of view of Predictious, users are identified by their email addresses. Should there be a problem with Google, we could easily swap it out for a different mechanism.
We hope our answers will help, happy to follow up if you have more things to raise.
