Press "Enter" to skip to content

Google Confesses To Placing Old UIDAI Helpline Number On Your Contact List

Google has confessed that it is to blame for the strange appearance of an out-of-date helpline number of Aadhaar in the contact lists of handsets. The firm clarified that it was not an unauthorized violation of the Android machines. The U.S. Internet behemoth claimed that the problem will be solved over the weeks to come.

“Our internal evaluation has unveiled that in 2014, the 112 distress helpline number and the then helpline number of UIDAI (Unique Identification Authority of India) were unintentionally coded into the Android release’s SetUp wizard offered to OEMs for utilization in India. It has stayed there since then. Since the numbers comes on the contact list of the users, these get transferred accordingly on any new device to the contacts,” a spokesperson of Google claimed to the media.

“We are regretful for any concern that this may have caused, and will like to guarantee everybody that this is not a case of an illegal access to their Android machines,” the firm claimed. It claimed that consumers can manually remove the number from their handsets. “We will operate towards fixing this in a forthcoming SetUp wizard’s release, which will be made accessible to OEMs over the weeks to come,” Google claimed.

Previously in the day, telecom operators, the UIDAI, and handset merchants claimed that they had no job in the strange appearance of the helpline number for Aadhaar. They were answering to a social media storm this week over the appearance of the helpline number 1800-300-1947 for Aadhaar on some iOS and Android handsets. Many people feared of a breach of privacy in the middle of the current debate all over the Aadhaar system’s security. UIDAI, which controls the Aadhaar project of the country, claimed to the media that it has not asked telecom service providers and handset manufacturers to add its toll-free number on mobile handsets.

Be First to Comment

Leave a Reply

Your email address will not be published. Required fields are marked *