On 17 August 2026, the Department of Telecommunications (DoT) sent operators a circular about subscribers who hold too many mobile connections. From 23 August, its Digital Intelligence Platform would carry a photo of each subscriber already at the limit. Operators must download those images every day and use them to refuse a further connection. They have until 30 November 2026 to build that check into enrolment.
Read the circular as a Data Protection Officer and different questions appear. Where do the daily downloads land? Who can open them? How many copies exist by Friday, and when does each one go? A telecom DPO who can answer in an hour has working data discovery. One who needs a fortnight has a gap that the DPDP Rules will expose.
TRAI counted 134.8 crore telephone subscriptions at the end of June 2026. Each one sits on a stack of records that other laws require operators to keep. The Digital Personal Data Protection Act, 2023 leaves those duties in place. It asks operators to show that every copy has a lawful basis and an end date.
The Act even uses a telco to explain itself. Its illustration to Section 6(6) has a telecom provider whose billing vendor must stop emailing bills once a customer moves to the app. That instruction only works if the operator knows which vendor holds which customer's email address.
Where things stand on 10 November 2026
MeitY notified the DPDP Rules on 13 November 2025 as G.S.R. 846(E). Rule 1 sets three start points. Rules 1, 2 and 17 to 21 applied at once, mostly to set up the Data Protection Board. Rule 4 on Consent Managers starts one year after publication. Rules 3, 5 to 16, 22 and 23 start eighteen months after publication. Most advisers count that to 13 May 2027.
Those later rules carry the daily work. They cover notice in Rule 3, security in Rule 6, breach intimation in Rule 7, retention in Rule 8 and rights in Rule 14.
In January 2026, Business Standard reported that MeitY had proposed a 12-month window for Significant Data Fiduciaries. The report relied on unnamed sources, and the ministry did not respond before press time. As of 10 November 2026, we have not found any notified change to Rule 1.
Plan to 13 May 2027, and treat any shorter date as a reason to start sooner. Our plan that works back from 13 May 2027 sets out the full sequence. For an operator, discovery sits at the front of it.
Why every DPDP obligation starts with an inventory
Rule 3 says a notice must give "an itemised description of such personal data". You cannot itemise data you have not found.
Section 11(1)(b) goes further. A subscriber can ask for the identities of every Data Fiduciary and Data Processor that received her data. She can also ask for a description of what each one received.
For an operator, that list runs long. It covers billing and print vendors, collection agencies, retail distributors, call-centre partners and cloud hosts. A rights request portal can receive the request. Only an inventory can answer it.
Section 8(7) adds a further demand. Personal data must be erased once the purpose is served, unless another law requires the operator to keep it. In telecom, "another law" covers a large part of the estate.
So discovery has two jobs here. It must find each copy. It must also tie each store to the instrument that lets the operator keep it.
What a telecom data estate actually holds
A bank's customer data clusters around core banking. A telco's is spread across dozens of systems, each holding part of the subscriber.
| Data | Where it usually sits | Why it matters |
|---|---|---|
| Customer Application Form and Subscriber Data Records | CRM, provisioning, retail apps | Uploaded to DoT's platform the day after activation |
| e-KYC and biometric captures | Enrolment apps, KYC middleware | Retail devices must not store them |
| CDR, EDR and IPDR | Mediation, billing, archives | Licence retention of two years |
| Location and roaming data | HLR, VLR, network analytics | Shows where a person goes |
| Porting records | MNP systems, CRM | Move between operators |
| Commercial communication consents | TRAI consent registrar, CRM | A second consent regime |
| M2M SIM records | IoT platforms | Some link to an individual |
Scale makes the hidden corners large. TRAI recorded 13.47 crore M2M connections and about 1.48 crore porting requests in June 2026. Not every M2M SIM carries personal data. Discovery is how you find out which ones do.
TRAI's own counting method points to another corner. It deducts IMSIs whose "subscriber retention period" has expired from the total registered in the HLR. Those records are still in the HLR when the count is taken. Discovery should establish what happens to them next, and on whose authority.
The August 2026 circular adds a daily flow. Operators share Subscriber Data Records, including additions, port-ins, deletions and port-outs, the day after activation. They then pull photos back from the platform. Each step leaves a copy that your inventory must show.
Retention clocks that run on the same record
One mobile data session can fall under several retention rules at once. They rarely conflict. They do end on different days.
DoT amended clause 39.20 of the Unified Licence on 21 December 2021, doubling the archive period. The table sets that amendment beside the DPDP Rules and CERT-In's directions.
| Instrument | What it covers | Minimum period |
|---|---|---|
| Unified Licence, clause 39.20 | Commercial records, CDR, EDR, IPDR | Two years |
| Unified Licence, Part II, Chapter IX, clause 7.2 | Internet login and logout details | Two years |
| DPDP Rule 8(3) | Personal data, traffic data, processing logs | One year from processing |
| DPDP Rule 6(1)(e) | Logs and personal data for breach detection | One year, unless law requires otherwise |
| CERT-In directions, 28 April 2022 | Logs of all ICT systems | 180 days, rolling |
The licence clause says such records "may be destroyed thereafter unless directed otherwise". Rule 8(3) tells the operator to erase after the minimum, unless another law requires more. Read together, a CDR older than two years needs some other legal basis to stay. Discovery is how you find the records that have none.
The Third Schedule adds a three-year inactivity clock for large e-commerce, online gaming and social media platforms. Telecom operators are not on that list. So each operator must decide when a purpose is no longer being served under Section 8(7). Write that decision down for each system, with the evidence behind it.
The licence is becoming an authorisation
In June 2026, DoT notified rules that move telecom services from licences to authorisations under the Telecommunications Act, 2023. JSA's summary of the new framework notes that existing licences continue for their term unless migrated earlier. Where no term is fixed, they continue for five years.
Migration doesn't wipe the slate. The rules preserve existing obligations, liabilities and approvals.
The new Principal Services Rules carry their own conditions on subscriber records and on keeping data and logs in India. That has a plain consequence for your inventory. The citation behind a retention period can change when a service area migrates.
Record the instrument and the clause beside every retention period. A number of years with no source won't survive the move. Check each clause against the Gazette text of your own authorisation.
New flows from 2026 that inventories miss
DoT notified the Telecommunications (User Identification) Rules, 2026 on 21 August 2026. AZB & Partners' note on the rules explains that they cover enrolment, disconnection, updates and reverification. Aadhaar holders verify through e-KYC, and others through a digital KYC process.
One condition doubles as a discovery test. Point of Sale locations may not store user or biometric data, and must send it securely to the operator.
Run that test now. Pick ten retail devices across two service areas. Check local storage, app caches and photo folders for identity images. If you find any, the retail estate belongs inside your inventory.
Porting is a second flow. A port-out ends the commercial relationship with that subscriber. It doesn't end the records the donor operator holds about her.
Consent is the third. Under TRAI's commercial communication rules, explicit consent for promotional messages sits in a consent registrar. Khaitan & Co's summary of the February 2025 amendment notes that inferred consent now lasts only for the contractual relationship. When a subscriber ports out, any inferred consent to market to her ends with the contract.
DPDP consent will live in your own consent records. Discovery must reconcile both registers, or your marketing lists will drift from both rule books.
Section 5(2) adds a duty for the existing base. Where consent predates commencement, the operator must give notice as soon as reasonably practicable. That notice must describe the personal data processed, so it draws on the same inventory.
Breach clocks depend on knowing who is affected
Three breach regimes apply to an operator. The Telecom Cyber Security Rules, 2024 require a report to the Central Government within six hours of becoming aware. SCC Online's summary of the rules notes that within 24 hours the operator must state the number of users affected.
CERT-In's 2022 directions set a six-hour window for cyber incidents. The Internet Society's brief on those directions lists telecom service providers among the entities covered.
Then Rule 7 of the DPDP Rules applies. Each affected Data Principal must be told without delay. The Board gets a first intimation without delay and a detailed report within 72 hours.
Every one of these clocks asks the same question. Whose data was in the system that failed? If that store was never classified, you'll be counting under pressure, from backups, with incomplete logs.
The Schedule to the Act sets the stakes. Failing to take reasonable security safeguards can draw a penalty of up to ₹250 crore. Failing to notify a breach can draw up to ₹200 crore. Section 33(2) asks the Board to weigh the type of data affected and how quickly the operator acted.
An independent cybersecurity assessment can test whether your incident team can produce that count in hours.
A 90-day discovery plan for an operator
Ninety days is enough to build a baseline you can defend. It isn't enough to fix everything you find. This is the order we recommend.
| Days | Work | Output |
|---|---|---|
| 1 to 15 | List every system and vendor that touches subscriber data | System register with named owners |
| 16 to 35 | Scan structured and unstructured stores, including archives | Classified inventory by data type |
| 36 to 50 | Trace flows to DoT, TRAI, vendors and partners | Data map with every recipient |
| 51 to 65 | Attach instrument and clause to each retention period | Retention schedule with citations |
| 66 to 80 | Test retail devices, backups and vendor copies | Remediation list with deadlines |
| 81 to 90 | Present findings to the Board | Approved baseline and owners |
Give the CISO the scanning and the DPO the classification rules. Give legal the retention citations, because they will change with migration.
Build the data map around recipients. Section 11 requests will ask for exactly that. If you want an outside view first, a DPDP gap assessment gives you a baseline to measure against.
The one thing to remember
In telecom, other laws decide how long most subscriber data stays. The DPDP Act asks you to prove it. Every copy should point to the rule that keeps it.
Find the copies that point nowhere before 13 May 2027, and you'll have done the hardest part of compliance.
This article is general information. It is not legal advice for a specific situation.
Sources
- Ministry of Electronics and Information Technology, "Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E)), Gazette of India text", 13 November 2025. Link
- India Code, "The Digital Personal Data Protection Act, 2023 (Act No. 22 of 2023)", as on 19 November 2025. Link
- Business Standard, "Meity may cut compliance timeline for key DPDP rules to 12 months", 22 January 2026. Link
- Telecom Regulatory Authority of India, "Highlights of Telecom Subscription Data at the end of June 2026 (Press Release No. 104/2026)", 28 July 2026. Link
- Department of Telecommunications, "Circular no. 3/User Identification/2026: Instructions for reverification of existing mobile connections", 17 August 2026. Link
- Department of Telecommunications, "Amendment in Unified License (UL) Agreement for change in time period of storage of CDR/EDR/IPDR", 21 December 2021. Link
- JSA Advocates & Solicitors, "Telecommunications authorisation regime, 2026: Key features of the new authorisation based framework", June 2026. Link
- AZB & Partners, "Telecommunications (User Identification) Rules, 2026", 27 October 2026. Link
- Khaitan & Co, "Efforts to curb spam continue: TRAI releases Second Amendment to the TCCCPR 2018", 2 April 2025. Link
- SCC Online, "Govt. notifies Telecom Cyber Security Rules to enhance safety of telecommunication infrastructure", 22 November 2024. Link
- Internet Society, "Internet Impact Brief: India CERT-In Cybersecurity Directions 2022", 1 June 2022. Link