New Delhi – Meta Platforms announced that WhatsApp is testing a feature that would let users hide their phone numbers from contacts by sharing a temporary or masked identifier. While Meta says the change is intended to bolster user privacy, India’s Ministry of Electronics and Information Technology (MeitY) has asked the company to postpone any rollout in the country until a full review of the proposal’s impact on data‑privacy and telecommunications law is completed.
What happened
Meta disclosed that the phone‑number masking option is in a limited trial phase in select markets and will be introduced gradually, with a global launch planned “in the coming months,” according to a company press release. The feature would allow a WhatsApp user to replace the personal mobile number that traditionally serves as the account’s primary identifier with a temporary or masked number that can be shared with contacts.
In response, MeitY issued a statement to the media requesting that Meta delay the introduction of the feature in India. The ministry said the proposal could “affect existing norms around user identification” and might conflict with the Telecom Regulatory Authority of India’s (TRAI) guidelines on user data protection. No official timeline for a possible postponement has been announced, and Meta has not confirmed whether it will comply with the request.
Why it matters
WhatsApp’s reliance on phone numbers for account creation and contact verification has long been a point of discussion among privacy advocates. A masking option could reduce the exposure of personal identifiers, potentially limiting unsolicited messages and phishing attempts that exploit known numbers. At the same time, the change raises questions about how users will authenticate contacts and how law‑enforcement agencies might trace communications when required by court order.
India, home to more than 400 million WhatsApp users, is a key market for Meta. The country’s regulatory environment has grown increasingly stringent after the 2021 Personal Data Protection Bill and ongoing enforcement of TRAI’s data‑protection guidelines. A delay could set a precedent for how global tech firms align new privacy‑enhancing tools with local legal frameworks.
Background and context
WhatsApp, owned by Meta Platforms, has historically used a phone number as the sole identifier for each account. The platform’s end‑to‑end encryption protects message content, but metadata such as the user’s phone number remains visible to contacts and, in some cases, to third‑party services that integrate with the app.
Meta’s announcement follows a broader industry trend toward “privacy‑by‑design” features, including Apple’s recent rollout of “Hide My Email” and Google’s “Phone Number Privacy” tools. In its press release, Meta framed the masking feature as a response to “user privacy concerns” and a measure to “protect personal data from unwanted contact.”
India’s MeitY, which oversees the nation’s electronic and information technology policies, cited potential conflicts with TRAI’s regulations. TRAI’s current guidelines require telecom operators and messaging services to maintain accurate user identification records, primarily to aid in crime prevention and national security. The ministry’s request for a pause reflects a cautious approach to any alteration that could obscure the link between a user’s account and their verified mobile number.
Competing claims and uncertainty
Meta maintains that the feature is optional and that users who choose to mask their number will still be able to verify contacts through alternative mechanisms, though the company has not detailed what those mechanisms will be. The firm reiterated its “commitment to user privacy” and indicated it will continue engaging with regulators worldwide.
MeitY, however, has not provided a detailed legal analysis, only noting that the feature “could affect existing norms” and may “conflict with TRAI’s guidelines.” The ministry has not indicated whether it expects Meta to modify the feature, conduct a joint impact assessment, or abandon the rollout entirely.
Legal experts caution that the lack of public documentation leaves several uncertainties:
* Authentication – If a masked number replaces the primary identifier, how will WhatsApp ensure that users can still confirm the authenticity of new contacts without exposing their real numbers?
* Law‑enforcement access – TRAI’s guidelines aim to preserve the ability of authorities to trace communications when required. A masked identifier could complicate lawful interception unless Meta retains a back‑end mapping of temporary numbers to real numbers, a detail not disclosed by the company.
* Cross‑border data flows – Meta’s global rollout may encounter divergent regulatory regimes. While the European Union’s GDPR permits pseudonymisation, India’s pending data‑protection legislation may impose stricter requirements on the retention of linking data.
Because the feature remains in testing, concrete data on its security architecture, user adoption rates, or potential misuse are not publicly available. Both Meta and MeitY have refrained from releasing technical documentation, leaving analysts to speculate on the practical implications.
What to watch next
* Official response from Meta – A formal statement confirming whether Meta will honor MeitY’s request, modify the feature, or seek a compromise could clarify the rollout timeline.
* Regulatory clarification – TRAI may issue a detailed advisory or amendment to its user‑identification guidelines, explicitly addressing masked identifiers and their compliance requirements.
* Legal challenges – Consumer‑rights groups in India have previously filed petitions against data‑privacy practices of tech firms. Any filing related to the masking feature could trigger judicial review.
* User feedback – Early testers in the limited markets may provide data on usability, security incidents, or privacy benefits, influencing both Meta’s product decisions and regulator assessments.
* International precedent – Actions taken by other jurisdictions, such as the European Union’s Digital Services Act assessments, could inform India’s stance and Meta’s global strategy.
Conclusion
WhatsApp’s proposed phone‑number masking tool reflects a growing industry push to give users more control over personal identifiers. Yet, in India—a market where regulatory scrutiny of digital services is intensifying—the feature collides with existing telecom identification norms. The Ministry of Electronics and Information Technology’s request for a delay underscores the tension between privacy innovation and the state’s mandate to maintain traceability for security and law‑enforcement purposes. How Meta navigates this regulatory impasse will likely influence not only the future of the feature in India but also set a benchmark for the deployment of similar privacy‑enhancing functionalities worldwide.
Sources
– “WhatsApp Wants to Hide Your Phone Number. India Wants It to Wait.” Sify.com, accessed via Google News India Technology RSS feed, https://news.google.com/rss/articles/CBMinAFBVV95cUxOS1NnMmo1dTlRNWR5R05jcEc4WThjcm43QXd6WjgtN0RuaXJsOXU2RFFRMGs0S3kyVTZBUVgzX2dGek5BVUV0V3B4aE9NMXNqcVF0UWhhTlZBRjBlbFdSeVV3LTZZdVdCWC1DelZJQUpjVEtqUmlJOVNuNklmQ2VWQnJjVnZNVWdibWMyei1RdVd4dGJ2QlBLaWtSUlQ?oc=5
—
Story synopsis gathered from: Google News India Technology — source
Corrections
If you believe this article contains an error, contact Herald Express with the source URL and supporting evidence.
