Quick answer
Rule 23 of the DPDP Rules, 2025 lets the Central Government, through authorised persons named in the Seventh Schedule, require any Data Fiduciary or intermediary to furnish information for three purposes: sovereignty, integrity and security of India; State functions or legal disclosure obligations; and assessing whether to notify a Significant Data Fiduciary. It applies from 13 May 2027 and can include a non-disclosure direction.
- Rule 23 applies to both Data Fiduciaries and intermediaries as defined in the IT Act, 2000.
- The Seventh Schedule lists three purposes and, for each, who is the authorised person entitled to call for information.
- Information must be furnished within the period specified in the request itself.
- Under Rule 23(2), the government can bar you from telling the affected Data Principal where disclosure would prejudice sovereignty, integrity or State security.
- The same Seventh Schedule purposes drive the one-year retention of personal data, traffic data and logs under Rule 8(3).
Who this is for: Data Fiduciaries of all sizes, Intermediaries, including social media and cloud platforms, Law enforcement response and trust and safety teams, General counsel and Data Protection Officers, Platform and data engineering teams
What does DPDP Rule 23 allow the government to do?
Rule 23(1) provides that the Central Government may, for the purposes of the Act specified in the Seventh Schedule, acting through the corresponding authorised person named in that Schedule, require any Data Fiduciary or intermediary "to furnish such information as may be called for, within the specified period as may be given in such" request.
Four elements define the power:
- Who asks: the Central Government, but only through the authorised person listed for the relevant purpose.
- Who must answer: any Data Fiduciary, and any intermediary within the meaning of the Information Technology Act, 2000 (Rule 23(3)). An intermediary need not itself be a Data Fiduciary for the data in question.
- Why: only for a purpose listed in the Seventh Schedule.
- When: within the period stated in the request.
Rule 23(2) adds a confidentiality power. Where disclosure that information has been furnished "is likely to prejudicially affect the sovereignty and integrity of India or security of the State", the government may require the fiduciary or intermediary not to disclose it to the affected Data Principal "or any other person" except with the previous written permission of the authorised person.
Rule 23 is among the rules that come into force on 13 May 2027, eighteen months after the Rules were published. It operationalises the Act's power for the Central Government to call for information, which is a separate track from the Data Protection Board's inquiry powers.
The three Seventh Schedule purposes and authorised persons
The Seventh Schedule is a three-row table. Each purpose has a specific authorised person.
| S. no. | Purpose | Authorised person |
|---|---|---|
| 1 | Use, by the State or any of its instrumentalities, of personal data of a Data Principal in the interest of sovereignty and integrity of India or security of the State | Such officer of the State or of any of its instrumentalities notified under section 17(2)(a) of the Act, as the Central Government or the head of that instrumentality may designate |
| 2 | Use, by the State or any of its instrumentalities, of personal data for (i) performance of any function under any law in force in India, or (ii) disclosure of information for fulfilling any obligation under any law in force in India | Person authorised under applicable law |
| 3 | Carrying out assessment for notifying any Data Fiduciary or class of Data Fiduciaries as a Significant Data Fiduciary | Such officer of the Central Government in MeitY as the Secretary in charge of MeitY may designate |
Reading the table:
- Purpose 1 is tied to instrumentalities notified under section 17(2)(a), which are exempt from the Act for those purposes. The request must come from an officer designated in respect of such an instrumentality.
- Purpose 2 is the broadest. It covers State use of personal data for any legal function or disclosure obligation, and routes the request through whoever applicable law authorises.
- Purpose 3 is narrow and regulatory: MeitY may collect information to decide whether a fiduciary should be designated a Significant Data Fiduciary. See SDF criteria.
Why Rule 23 drives the one-year retention rule
The Seventh Schedule heading cites both Rule 23(1) and Rule 8(3). That cross-reference has large engineering consequences.
Rule 8(3) requires every Data Fiduciary to retain, for processing by it or on its behalf by a Data Processor, "such personal data, associated traffic data and other logs of the processing for a minimum period of one year from the date of such processing, for the purposes as specified in the Seventh Schedule", and then erase them unless another law requires longer retention.
In other words, the purposes for which the government may call for information are the same purposes for which you must keep data and logs for at least a year — even if the user deletes her account. The Rules illustrate this with an e-book platform that must keep order, payment and delivery records and logs for a year after the transaction, and a company whose cloud provider must also retain hosted data and logs for a year.
Practical implications:
- Erasure is delayed, not abolished. A user's erasure request removes data from active use, but the Rule 8(3) copy must survive for the minimum period, then be erased.
- Logs must be complete. Traffic data and processing logs must be good enough to answer a Rule 23 request about who processed what and when.
- Processors count. You must make sure processors retain their copies too.
See one-year log retention and retention and erasure under Rule 8.
The non-disclosure direction in Rule 23(2)
Most DPDP obligations push towards transparency. Rule 23(2) is a deliberate exception.
When it can be used
Only where disclosure of the fact that information was furnished is "likely to prejudicially affect the sovereignty and integrity of India or security of the State". It is not available for ordinary regulatory or administrative requests.
What it bars
The fiduciary or intermediary may be required not to disclose the furnishing to the affected Data Principal or any other person, except with the previous permission, in writing, of the authorised person.
Operational consequences
- Rights responses. If a Data Principal later asks under section 11 for the identities of others her data was shared with, a live Rule 23(2) direction may restrict what you can say. Route such requests through legal before answering.
- Transparency reports. If you publish aggregate government request statistics, check whether a non-disclosure direction restricts even aggregate reporting, and seek written permission where needed.
- Internal access. Limit knowledge of the request to a small, named group. "Any other person" can include vendors and parts of your own organisation that do not need to know.
- Record-keeping. Keep a confidential register of requests, the authorised person, the purpose cited, the deadline, what was furnished and any non-disclosure direction.
Because the direction overrides normal transparency, verify that it is issued in writing by the correct authorised person before complying with the gag.
How to build a Rule 23 request-handling process
Treat Rule 23 requests like any lawful-access request: verify, scope, respond, record.
- Single intake point. Publish an internal channel (and if appropriate a law enforcement contact) so requests do not land in a support inbox.
- Verify the requester. Check that the request identifies a Seventh Schedule purpose and comes from the corresponding authorised person — for example, a MeitY officer designated by the Secretary for SDF assessments.
- Check scope. Confirm the information requested is linked to the cited purpose. Narrow over-broad requests through dialogue where possible.
- Note the deadline. Rule 23(1) requires response within the period specified in the request. Diary it immediately.
- Extract minimally. Pull only what is asked, from systems with access logs, and have a second person review before release.
- Apply any gag. If there is a Rule 23(2) direction, restrict disclosure and flag the affected accounts so support and rights teams do not inadvertently notify users.
- Transmit securely. Use encrypted channels and record what was sent, when and to whom.
- Record everything. Maintain a confidential register for audits and, if you are or become a Significant Data Fiduciary, for your annual DPIA and audit under Rule 13.
Intermediaries should align this with existing IT Act processes and the CERT-In Directions of 28 April 2022, which already require a designated point of contact and 180-day log retention within India. See CERT-In rules for AI systems.
Common mistakes with government information requests
Responding to anyone who cites the DPDP Act. Rule 23 is purpose-specific and person-specific. A request that does not map to a Seventh Schedule purpose and authorised person should be escalated before data leaves your systems.
Over-producing. Sending entire tables or full account exports when a narrow answer would do increases risk and may itself breach your security and minimisation duties for the data you do not need to disclose.
Breaking a gag by automation. Automated "your data was accessed" emails, rights-request portals that show third-party disclosures, or vendor ticketing systems can leak a confidential request. Build a suppression flag.
Ignoring intermediary status. Platforms that host content for others may receive requests as intermediaries even where they are not the Data Fiduciary for the underlying data. Rule 23 covers both roles.
Deleting too early. If Rule 8(3) retention is not implemented, you may be unable to answer a lawful request and may also be in breach of the retention rule itself.
No audit trail. Without a register of requests and responses, you cannot demonstrate compliance to auditors, the Board or a court, and you cannot spot patterns of overreach.
Treating it as a security incident. A lawful Rule 23 disclosure is not a personal data breach. But an unverified or spoofed "government request" that leads to disclosure may well be — verify first.
What to do before Rule 23 commences on 13 May 2027
Rule 23 and Rule 8(3) both start on 13 May 2027. Use the next six months to build the plumbing:
- Write a government request policy covering intake, verification against the Seventh Schedule, scoping, approvals, deadlines and non-disclosure handling.
- Implement Rule 8(3) retention for personal data, traffic data and processing logs, including at processors, with erasure after the minimum period unless another law requires longer.
- Make logs queryable by user identifier, system and time window so a response can be assembled quickly.
- Add a suppression flag to user records that stops automated notifications and rights-portal disclosures when a Rule 23(2) direction applies.
- Update processor contracts to require processors to retain data and logs for the minimum period and to cooperate with lawful requests. See DPA template.
- Train a small response team across legal, security and engineering.
- Prepare for SDF assessment requests. Larger fiduciaries should expect MeitY requests under purpose 3 and keep data-volume and risk metrics ready.
For the full schedule of obligations, see the DPDP compliance roadmap.
Further reading on suhasbhairav.com
- BlogData Minimization vs Data Retention: Practical Guidelines
- BlogAudit Logs for AI Agents: Traceable Actions in Production
- BlogZero-Trust for Agentic Enterprises and AI Workflows
- AI AutomationAI Automation for Security Compliance: Uses + Example
- AI SkillsAGENTS.md Template for Cloud Security Posture Reviews
Before 13 May 2027
Compliance checklist
Create a single intake channel for government requests
Route all Rule 23 requests to a named legal and security team rather than general support.
Rule 23(1)
Verify purpose and authorised person
Match each request to a Seventh Schedule purpose and its authorised person before releasing any data.
Seventh Schedule
Diary the response period
Record the deadline stated in the request and track it to completion.
Rule 23(1)
Build a non-disclosure suppression flag
Stop automated notices and rights-portal disclosures for accounts covered by a non-disclosure direction.
Rule 23(2)
Retain data, traffic data and logs for one year
Keep the Rule 8(3) minimum retention across your systems and processors, then erase unless another law requires more.
Rule 8(3)
Keep a confidential request register
Log each request, purpose, requester, deadline, data furnished and any gag, with restricted access.
Rule 23
Key dates
DPDP Rules, 2025 published, including Rule 23 and the Seventh Schedule
Rule 23 and Rule 8(3) come into force
Answers
Frequently asked questions
Can the Indian government ask a company for personal data under the DPDP Rules?
Can the Indian government ask a company for personal data under the DPDP Rules?
Yes. From 13 May 2027, Rule 23 lets the Central Government, through authorised persons listed in the Seventh Schedule, require any Data Fiduciary or intermediary to furnish information for three purposes: sovereignty, integrity and security of India; State functions or legal disclosure obligations; and assessment for notifying a Significant Data Fiduciary.
What is the Seventh Schedule of the DPDP Rules?
What is the Seventh Schedule of the DPDP Rules?
The Seventh Schedule is a table of three purposes and the authorised person for each: State use in the interest of sovereignty, integrity or State security; State use for legal functions or disclosure obligations; and MeitY's assessment for notifying Significant Data Fiduciaries. It governs Rule 23 requests and the one-year retention under Rule 8(3).
Do I have to tell users when I share their data with the government under Rule 23?
Do I have to tell users when I share their data with the government under Rule 23?
Not always. Under Rule 23(2), where disclosure is likely to prejudicially affect the sovereignty and integrity of India or State security, the government may require you not to tell the affected Data Principal or anyone else without the authorised person's prior written permission. Otherwise, normal transparency obligations continue to apply.
How quickly must a company respond to a Rule 23 request?
How quickly must a company respond to a Rule 23 request?
Rule 23(1) requires the information to be furnished within the period specified in the request itself. The Rules do not set a fixed number of days, so record the deadline stated in each request, verify the requester and scope promptly, and escalate early if the timeline is not achievable.
Does Rule 23 apply to intermediaries that are not Data Fiduciaries?
Does Rule 23 apply to intermediaries that are not Data Fiduciaries?
Yes. Rule 23 covers any Data Fiduciary or intermediary, and Rule 23(3) adopts the Information Technology Act, 2000 definition of intermediary. A platform hosting content for others can receive a request as an intermediary even where it does not decide the purpose and means of processing the data concerned.
How is Rule 23 connected to the one-year log retention rule?
How is Rule 23 connected to the one-year log retention rule?
Rule 8(3) requires every Data Fiduciary to keep personal data, associated traffic data and processing logs for at least one year for the purposes specified in the Seventh Schedule. Those are the same purposes for which the government may call for information under Rule 23, so the retention rule ensures the data is available.
Legal references and sources
- Digital Personal Data Protection Rules, 2025 — Rule 23 (official text)
- Digital Personal Data Protection Rules, 2025 — Seventh Schedule (official text)
- Digital Personal Data Protection Rules, 2025 — Rule 8(3) (official text)
- Digital Personal Data Protection Act, 2023 — Section 17(2)(a) (official text)
This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.
About the author

Suhas Bhairav
Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.
Related guides
- DPDP Rules 2025DPDP One-Year Log Retention: What to Keep and for How LongTwo DPDP rules require one year of retention: Rule 6(1)(e) for security logs and Rule 8(3) for personal data, traffic data and processing logs. What to keep, where, and how to protect it.
- DPDP Rules 2025DPDP Data Retention and Erasure Under Rule 8 and the Third ScheduleRule 8 sets when personal data must be erased: three-year dormancy erasure for large e-commerce, gaming and social media platforms, a 48-hour warning, and a one-year retention floor for everyone.
- DPDP Act 2023How the Government Decides a Significant Data FiduciaryThe Central Government designates Significant Data Fiduciaries by notification under section 10, weighing data volume, sensitivity, risk to rights and national interest factors.
- DPDP Act 2023DPDP Section 17 Exemptions ExplainedSection 17 switches off parts of the DPDP Act for legal claims, courts, crime, offshore outsourcing, mergers, loan defaults, notified State bodies, research and notified startups.
- India AI & sector rulesCERT-In Rules for AI Systems: Incident Reporting & LogsHow CERT-In's April 2022 directions on 6-hour incident reporting, 180-day logs in India and clock sync apply to LLM gateways, model APIs and AI agents, and how they meet DPDP.
- DPDP Rules 2025Algorithmic Due Diligence for Significant Data FiduciariesRule 13(3) requires Significant Data Fiduciaries to verify that technical measures, including algorithmic software, are not likely to pose a risk to Data Principals' rights. Here is what that means in practice.