Google’s Authentication Process… Doubtful?
The 2-factor authentication process has just been introduced by Google. To log in, the user has to provide his or her cell or landline telephone number. Google then sends a one-time authentication code that is used to log in to his or her account. At first glance, this new technology seemed good, but later, questions as to its real purpose have been raised.
This new tool would not allow the user to log in without first giving his or her number. Using the number provided, Google would send the “key” to open the account. A prompt box is provided where the sent code would be entered. That’s the only time when the user can continue with the log in process. It is as simple as that, but those who know about data collection have some doubts.
Phone numbers are the user’s private “property”. Mindless uploading of cellular or landline phone numbers in the internet could be dangerous. Google’s 2-factor authentication is not an exception. Collecting such important data from users just for verification is not good enough reason. The millions of numbers provided by millions of users contain lots of information which could be abused. What about the storage of these data? Would these be deleted right after authentication? Would it not be stored for future use?
