A good example of what may happen when we don't read the ToS? I suppose that the collection of passwords was clearly referred to in the EULA. Further on down/up there may have been wording that any information gathered by the app could be used for whatever purposes deemed fit by the developer. I'm not implying that anyone was trying to do anything wrong; rather, I was somewhat amazed with some of the things that appear to have become possible via EULAs.

http://www.tuaw.com/2011/06/15/passc...nned-by-apple/

It's a little skeezy, for sure. In this case, though, the irony is that the gigantic EULA is AMBIGUOUS when it comes to whether the developer can take your password or not. In a strictest sense, no, your password can't possibly be used to identify you, so they ought to be allowed to take it.

Good on Apple for letting common sense prevail, but it's a little spooky, nevertheless.

Originally Posted by antonio107

It's a little skeezy, for sure. In this case, though, the irony is that the gigantic EULA is AMBIGUOUS when it comes to whether the developer can take your password or not. In a strictest sense, no, your password can't possibly be used to identify you, so they ought to be allowed to take it.

Good on Apple for letting common sense prevail, but it's a little spooky, nevertheless.

Definitely spooky. We are being conditioned into just OKing EULAs because it's just not possible for *anyone* to process the length and the overwhelming number of them that we run into on an almost daily basis.