What a Grievance System May Retain Under DPDP

Executive Summary

A department that adds a voice layer to its grievance portal creates three new kinds of record: call audio, transcripts and callback outcomes. The vendor's template says "delete the audio after 30 days, the transcript on closure". That advice is borrowed from private-sector privacy practice, and for a State body it is the wrong starting point. Section 17(4) of the Digital Personal Data Protection Act switches off the general erasure duties for processing by the State, and the retention period is then set by other rules, some of which set a floor rather than a ceiling.

This article is for the nodal grievance officer, the district grievance cell or the state IT department that has to put a retention schedule into a vendor contract.

Executive Callout The DPDP Act's erasure duty (section 8(7)) and erasure-on-request right (section 12(3)) do not apply to processing by the State or its instrumentalities (section 17(4)). What does apply: the DPDP Rules' one-year minimum for logs and for personal data processed in the State's functions under law (rules 6 and 8(3)), the Second Schedule standard of retaining data only "till required" for the use, and the department's own record retention schedule. None of these is a number a vendor can choose for you. (DPDP Act 2023 ss. 8(7), 12(3), 17(4); DPDP Rules 2025, G.S.R. 846(E), 13 November 2025)

Introduction: What the Grievance Cell Actually Decides

Today a grievance sits in one place: the portal, whether CPGRAMS or a state system. Its retention follows the department's record schedule, and nobody asks the portal when it will forget a complaint. A voice layer changes that. A call produces audio, a transcript, telephony metadata, a record of what the citizen was told about the call, and, if the department runs closure callbacks, a second set of all four. These sit in the vendor's systems unless the contract says otherwise.

The buyer here is the public body that owns the grievance and answers for it: the nodal PG officer or the grievance cell. The workflow it runs today has one record and one schedule. The change is that it must now set a schedule for each new artefact, state when each clock starts, and make the vendor delete on instruction.

Timing first. The DPDP Act is only partly in force. Its consent and penalty sections commence on 13 May 2027, and under rule 1(4) of the DPDP Rules, rules 3 and 5 to 16 (including the retention rule, rule 8) come into force eighteen months after the Rules' publication on 13 November 2025. Rule 6, on security safeguards, falls in the same tranche. Nothing below is enforceable today, which makes this the time to design it.

The Rules That Govern a Department's Grievance Records

Five layers bear on the question. They do not all apply to every record, and a department's legal adviser should confirm which do.

Layer	What it says	Does it bind a State grievance cell?
DPDP Act s. 8(7) and s. 12(3)	Erase personal data when the purpose is no longer served, or on the citizen's request, unless retention is necessary for compliance with a law	No. Section 17(4): "In respect of processing by the State or any instrumentality of the State, the provisions of sub-section (7) of section 8 and sub-section (3) of section 12... shall not apply"
Second Schedule to the Rules, via rule 5	Where the State processes data to provide a subsidy, benefit or service, personal data is "retained till required for such uses... or for compliance with any law", and processing is limited to what is necessary	Yes, where the grievance is processed under section 7(b). Whether a free-standing complaint line counts as a "service" is a question for counsel
Rule 8(3)	A Data Fiduciary retains personal data, associated traffic data and logs of processing for a minimum of one year from the date of processing, for Seventh Schedule purposes, then erases unless another law requires longer. This extends to processing done by a Data Processor on its behalf	Yes, if the work is "performance of any function under any law" (Seventh Schedule, item 2). Whether an executive office memorandum is a "law" is the open point
Rule 6(1)(e)	Retain logs and personal data for one year so unauthorised access can be detected and investigated, unless another law requires otherwise	Yes. Section 17(4) does not touch it
Record schedule under the Public Records Act, 1993	Files are kept for the period in the department's retention schedule	Yes, for central departments; a state department should check the record rules that apply to it

Read the first row and the third row together and the vendor template's problem becomes clear. A 30-day audio deletion default can sit below a one-year floor. If your grievance handling falls within the Seventh Schedule, deleting at 30 days would breach rule 8(3) once it commences. If it does not, the vendor's default is a policy choice, not a legal requirement either way. The department must know which case it is in before it configures anything.

What Section 17(4) Does Not Excuse

The exemption is narrow. It names two provisions, and one conditional carve-out of section 12(2), and nothing else. Everything else the Act and Rules ask of a fiduciary still applies to a State body:

Security safeguards and breach intimation (section 8(5) and 8(6), rule 6).
Accuracy and completeness where data feeds a decision about the citizen (section 8(3)).
Purpose limitation and data minimisation under the Second Schedule, where that Schedule applies.
Accountability of whoever determines the purposes and means of processing (Second Schedule, item (h)).
A grievance route for data complaints (section 13). A grievance cell must itself offer citizens a way to complain about how it handled their data.

The exemption is also written for processing "by the State or any instrumentality of the State". A voice agent the department operates as its processor sits inside that processing. A vendor that decides its own purposes, such as keeping recordings to improve its models, should not assume the shelter extends to it. The contract should forbid any such use.

When the Retention Clock Starts

Most schedules say "X months after closure". Under CPGRAMS, closure is not a single event. DARPG's office memorandum of 23 August 2024 sets these points:

Grievances are ordinarily resolved in 21 days (para 3.1.1).
A disposed grievance is treated as closed "unless the citizen has filed the appeal", and if an appeal is filed, "closed only after disposal of appeal" (para 7.5).
Appeals are ordinarily closed within 30 days (para 4.2).
Every disposed grievance is dialled by DARPG's feedback call centre (para 8.1).

A retention clock that starts at disposal will tick during an appeal and may expire on a file the appellate authority is reading. Define final closure as the latest of: disposal, the decision on any appeal, and the recording of the closure-callback outcome. The escalation ladder and the reference-number and status-call design both generate events that belong inside this definition.

One dated source is worth knowing. The 13th edition of the Central Secretariat Manual of Office Procedure (September 2010) says, at para 122(15), that "the record of grievances will be retained in the computer for one year after the date of final disposal of the grievances." That sentence predates the 2024 appeal and feedback process, and it was written for an earlier version of CPGRAMS. Para 111 of the same Manual tells each department to issue its own retention schedule, in consultation with the National Archives of India, for records tied to its substantive functions. Check the edition your department currently follows, and treat the schedule it has issued as the controlling text.

A Working Schedule by Artefact

The table gives a starting position for each artefact. It names no period that no source supports. Where the sources set a floor, it says so. Where they do not, the department chooses and writes the choice down.

Artefact	Treatment	Anchor
Case record in the portal	Stays in the system of record under the department's schedule. The voice layer holds no second copy	CSMoP para 111; Public Records Act
Call audio	Keep only as long as needed for dispute and audit. The period is a written contract term, not shorter than any floor that applies	Rule 8(3) if Seventh Schedule applies; Second Schedule item (e)
Transcript	If it informs a decision or is attached to a disputed closure, it is part of the case file and follows its schedule. Otherwise treat as audio	Section 8(3); Second Schedule
Closure-callback outcome	Yes, no or partly, plus the citizen's words. Written into the case record, never kept only by the vendor	DARPG OM, paras 7.5, 8.1
Access logs and telephony metadata	Minimum one year	Rule 6(1)(e); rule 8(3)
Record of the notice given on the call	Keep with the case; it shows what the citizen was told	Second Schedule item (g)
Anything for vendor analytics or model training	Not retained. Aggregate, de-identified counts are the limit	Purpose limitation

Telecom call detail records sit outside the vendor's perimeter, held by the telecom operator. Ask the operator for its period and put it in the same schedule so the department knows the full picture.

Contract Clauses That Make the Schedule Real

Section 8(7)(b), the duty to make a processor erase data, is among the provisions section 17(4) disapplies for the State. That means the statute will not require the vendor to delete. The contract must.

An annexed schedule by artefact, with period, clock-start and deletion method.
A defined "final closure" as set out above, so the vendor does not apply its own.
Deletion on written instruction within a stated number of days, with a certificate listing what was erased.
A legal-hold clause that suspends deletion for any record tied to a pending appeal, audit, court case or inquiry.
End-of-contract return and erasure of every artefact, including backups, with the department's copy confirmed first.
No secondary use, including training, benchmarking or product analytics.
One-year log retention and breach notification to the department within a stated window.
A review trigger on 13 May 2027 and on any new edition of the CSMoP or amended schedule.

Risks and Mitigation

Deleting too early. A one-month audio default can destroy the only evidence of what a citizen was told while an appeal runs. Mitigation: the legal-hold clause and a clock that starts at final closure.

Keeping too long. Every old recording is exposure in a breach. Mitigation: a written period per artefact, with a quarterly deletion certificate and a sample of closed cases checked against it.

Relying on the exemption alone. Section 17(4) removes two duties, not the rest of the Act.

A confident legal reading nobody owns. Whether a grievance line is a "service" under section 7(b) or a "function under law" under the Seventh Schedule changes the answer. Get the department's legal adviser to record a view and attach it to the contract file.

Key Takeaways

Section 17(4) removes the general erasure duties for State processing. It does not remove the Rules' one-year floors or the department's record schedule.
A 30-day audio default may be below a floor; check before configuring it.
Start the clock at final closure, after any appeal and callback, not at disposal.
Write the schedule into the contract, because the statute will not make the vendor delete.

Conclusion

A grievance cell's retention question looks like a privacy question and is mostly a records question. The department already has a schedule, a system of record and an appeals process. The voice layer adds artefacts that must inherit the same discipline, with the contract doing the work the statute leaves undone.

The grievance redressal system overview shows where intake, status calls and closure verification sit relative to the portal, and the disposal versus resolution piece explains why closure callbacks produce records worth keeping.

Government leaders exploring AI-powered citizen engagement can begin with a focused pilot in one department or constituency to validate impact before scaling statewide. Aisewak helps public institutions deploy multilingual Voice AI solutions designed specifically for Indian governance.

FAQ

Does the DPDP Act require a government department to delete grievance records once a case is closed? Not under the general erasure provisions. Section 17(4) says section 8(7) and section 12(3) do not apply to processing by the State or its instrumentalities. Retention is then governed by the Rules' floors, the Second Schedule standard and the department's record schedule.

Is there a minimum retention period for grievance data? Rule 8(3) sets a minimum of one year from the date of processing for personal data, traffic data and logs processed for Seventh Schedule purposes, and rule 6(1)(e) sets one year for logs and data needed to investigate unauthorised access. Whether a particular grievance line falls under rule 8(3) is for the department's legal adviser to decide.

Can a vendor delete call recordings after 30 days? Only after confirming no floor applies. If the work is a State function under law, rule 8(3) would make 30 days too short once it commences on 13 May 2027. If it is not, the period is a contractual choice.

When do these retention rules come into force? The DPDP Act is only partly in force; its consent and penalty sections commence on 13 May 2027. Rule 1(4) brings rules 3 and 5 to 16, including rules 6 and 8, into force eighteen months after the Rules' 13 November 2025 publication.

Can a citizen demand that their grievance data be erased? Section 12(3) gives that right, but section 17(4) disapplies it for State processing. A citizen can still use the grievance route under section 13 to complain about how their data was handled.

How long does the Central Secretariat Manual say grievance records are kept? The 13th edition (September 2010), at para 122(15), says one year after final disposal for the record held in the computer. That predates DARPG's 2024 appeal and feedback process, so confirm the edition your department follows.

Who deletes data held by the voice vendor? The vendor, on the contract's terms. The statutory duty to cause a processor to erase data sits in section 8(7)(b), which section 17(4) disapplies for the State, so the department must write the obligation into the contract.

Does the exemption cover a vendor that reuses recordings to train models? It should not be assumed to. The exemption is written for processing by the State or its instrumentalities. The contract should prohibit secondary use outright.

Schema Markup Suggestions

TechArticle — @type: TechArticle, headline, description, datePublished, dateModified, author (Organization: AiSewak Editorial), publisher
FAQPage — each Q/A above as Question + acceptedAnswer
GovernmentService — on the linked /ai-grievance-redressal-system landing: @type: GovernmentService, serviceType: Citizen Grievance Redressal, areaServed: India

Suggested External References

Digital Personal Data Protection Act, 2023 — sections 7, 8(7), 12(3), 13 and 17(4)
Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E), 13 November 2025) — rules 1(4), 5, 6(1)(e), 8(3); Second and Seventh Schedules
DARPG office memorandum on handling public grievances, 23 August 2024 — paras 3.1.1, 4.2, 7.5, 8.1
Central Secretariat Manual of Office Procedure, 13th edition (September 2010) — paras 111 and 122(15)

The DPDP Act's erasure duty does not apply to State processing (section 17(4)), so a vendor's "delete audio after 30 days" default is not the legal answer for a grievance cell. The Rules set one-year floors, the department's record schedule governs, and the contract has to do what the statute does not. A retention guide for grievance officers.

LinkedIn Executive Summary

A department adding a voice line to its grievance portal will be handed a retention template: delete audio at 30 days, transcripts at closure. It borrows from private-sector privacy practice.

For a State body the starting point differs. Section 17(4) of the DPDP Act disapplies the general erasure duty (section 8(7)) and the erasure-on-request right (section 12(3)) for State processing. The 2025 Rules then add one-year minimums: rule 8(3) for personal data and logs processed in State functions under law, and rule 6(1)(e) for logs needed to detect unauthorised access. Whether a grievance line is a function under law is a question for counsel. A 30-day audio default may sit below the floor.

Two practical points. Start the retention clock at final closure, after any appeal and the closure callback, since DARPG's 2024 memorandum keeps a disposed case open until its appeal is decided. And write the schedule into the vendor contract, because the statute that would have required the processor to erase is the one the exemption removes.

Rules 5 to 16 commence on 13 May 2027, so the design window is open.

AI Search Optimization Summary

Entities: DPDP Act 2023, DPDP Rules 2025, Data Protection Board of India, MeitY, DARPG, CPGRAMS, Central Secretariat Manual of Office Procedure, Public Records Act 1993, National Archives of India, Aisewak

Topics: government grievance data retention, DPDP section 17(4) State exemption, call recording retention government helpline, DPDP rule 8(3) one-year retention, grievance record retention schedule, voice vendor data processing contract

Semantic keywords: how long can a government department keep grievance records, DPDP Act erasure exemption State, rule 8 DPDP Rules retention minimum, CPGRAMS appeal and record retention, call audio deletion government voice AI, final closure retention clock, processor erasure clause government contract