TRAI routes spam reports from caller-ID apps into the telcos' blockchain platform

A user taps "spam" on an unknown number in a caller-ID app. The tap records a fact about a phone number, and it also adds a row to the asset that makes the app worth installing. Those are not the same object, and which one has to travel is unsettled. Kazim Rizvi, founding director of the New Delhi think tank The Dialogue, drew the distinction for TechCrunch. Requiring an app to transmit a specific user report, he said, is materially different from requiring it to share the broader datasets, reputation signals or analytical systems it uses to identify suspicious calls ^[17]. Transmitting the one report is an integration ticket; the datasets and the signals are most of what Truecaller sells ^[6].

Sumeysh Srivastava, a partner at the New Delhi consulting firm The Quantum Hub, said the amendment bridges two layers: operators provide the network and run the blockchain-based anti-spam system. Caller-ID apps sit on top of that network, identifying and filtering calls ^[14]. He told TechCrunch the arrangement raises technical and jurisdictional questions: what reporting standards apps will have to follow, and how the requirement is enforced against companies that are not telecom operators ^[15]. A March draft proposed using India's IT laws for that enforcement, and Srivastava said the new announcement did not say whether that mechanism was retained ^[16]. TRAI did not respond to TechCrunch's questions about what information apps must share, or about whether the rule also covers spam-reporting features built into Android and iOS ^[19].

Scale is the regulator's case. Truecaller said in a February report that its users in India encountered around 42 billion spam calls in 2025, counting blocked, labeled or ignored calls, and that it blocked nearly 12 billion ^[7][8]. Subtract, and about 30 billion were labeled or ignored; the blocked share is roughly 29% ^[9]. India holds well over 350 million of Truecaller's more than 500 million monthly active users ^[5], so at least 70% of the global user base sits under one regulator ^[10].

Truecaller had objected to the designated-number carve-out well before Friday, arguing the exemption could let unwanted calls escape its filters ^[11]. "While our data and user sentiment clearly show that spam has skyrocketed due to this free pass to spammers, we have been compliant with this since late last year," a Truecaller spokesperson said ^[13].

What sorts the exposure for a product whose value sits in user-submitted signal is the nature of the signal. Does it record a fact about shared infrastructure, or something the product computed? A report that a given number sent spam is a fact about the phone network, and facts about regulated infrastructure are the cheap thing for a regulator to route; a reputation score is an inference the product made. It also matters whether the owner of the layer underneath enforces the rules on that layer. In India the operators run the anti-spam platform, so an app's users now file their reports into a competitor's system ^[14][1].

The low-cost path is to ship the minimum defined report and keep the scoring private. The trouble with that plan is that the minimum is not written yet. Rizvi said the rules will need clarity on what information must be transmitted, how users are notified or asked for consent, and how that data can be retained and used ^[18]. Teams that already keep the raw report and the derived score as separate objects have an integration to do. Teams that keep them blended will be arguing scope with TRAI after the rule is in force ^[1].