5 mins
RBI KYC 5-Year Retention vs DPDP Section 8 10-Year Example
Clarifying the conflict between RBI KYC 5-year data retention rules and the 10-year illustration in DPDP Act Section 8 for BFSI compliance teams.
Last updated:
Direct Answer for Compliance Teams
The ten-year retention period mentioned in Section 8 Illustration II of the Digital Personal Data Protection Act, 2023 is merely an example. It does not create a new statutory mandate for banks or NBFCs. Financial institutions must follow the actual data retention timelines prescribed by their sector regulators. The Prevention of Money Laundering (Maintenance of Records) Rules, 2005 govern the retention of KYC data in India. These rules require banking companies to maintain records of the identity of clients for a period of five years after the business relationship ends or the account is closed.
Section 8(7) of the DPDP Act mandates that a Data Fiduciary must erase personal data when the specified purpose is no longer served. This section provides an explicit exception if retention is necessary for compliance with any law. Because the PML Rules mandate a five-year retention window, compliance teams must configure their data lifecycle systems to execute deletion after five years. The Head of Compliance should instruct IT teams to ignore the ten-year illustration when configuring retention logic. Regulators will audit banks against the five-year PML rule combined with the DPDP Rules, 2025 erasure mandates.
Handling Legacy Core Banking Systems
Large financial institutions store KYC data across core banking systems and lending platforms. The Chief Compliance Officer must decide which systems act as the single source of truth for retention schedules. Existing governance software usually tracks policies and records the RoPA. These policy tools do not execute data erasure at the end of the five-year RBI window. Legacy banking systems were built to retain records indefinitely to support financial audits and dispute resolution. Banks need to procure an orchestration layer that connects the RoPA to runtime enforcement.
This layer monitors account closure dates in the core banking system. On day 1826 after account closure, the system triggers an automated deletion workflow across all connected databases. Relying on manual deletion scripts for millions of accounts exposes the institution to high penalty risks under the DPDP Act. The Board requires demonstrable proof that the bank destroys old data systematically. Manual interventions fail at enterprise scale.
DPBI Inquiry into Retention Practices
When the Data Protection Board of India investigates a banking entity, the inquiry will focus on technical proof of erasure. The DPDP Rules, 2025 require data fiduciaries to establish clear mechanisms for data lifecycle management. An auditor will request the retention logs for a sample of accounts closed five years ago. If the core banking system still holds the PAN or Aadhaar details of these individuals in an active table, the bank is in breach of Section 8. The Head of Compliance cannot use the ten-year illustration from the Act as a defense.
Illustrations in Indian statutes explain principles. They do not override specific sectoral laws like the PML Rules. The control owner must produce an audit trail showing that the system identified the five-year maturity date and successfully purged the identifiers. Failing this technical audit triggers immediate regulatory scrutiny and potential penalty proceedings.
What to Keep vs What to Build
Enterprises must distinguish between policy mapping and operational execution. Mapping data flows and assigning retention labels is a governance task. The legal team establishes the five-year rule for KYC data and shorter rules for session logs. Implementing these rules requires a technical engine capable of discovering personal data across on-premises databases and cloud instances. Building this engine in-house requires heavy backend engineering and infrastructure oversight. It pulls resources away from core banking upgrades.
Procurement teams evaluate external DPDP platforms to fill this execution gap. A credible solution reads the five-year rule from the policy layer and translates it into API calls that soft-delete or hard-delete specific database rows. The platform must isolate the customer identifier and erase the personal data while leaving anonymized transaction amounts intact for financial reporting. This technical separation satisfies both the DPDP Act and the Reserve Bank of India.
Acceptance Tests for Procurement Teams
Procurement teams evaluating data protection solutions must test how the software handles conflicting regulatory rules. The primary acceptance test is checking if the platform allows granular retention schedules based on specific lawful purposes. Evaluators should configure a test where marketing data deletes after six months of inactivity while KYC data waits for the five-year PML mark. The system must prove it can execute both rules independently for the same Data Principal.
Evaluators must demand an evidence pack that verifies deletion occurred across the primary database and its active backups. The platform must generate a verifiable audit trail for the Data Protection Board of India. This log needs to show the exact date of account closure, the statutory rule applied, and the timestamp of actual erasure. A viable system provides clear reports for control owners to present to the Board without requiring continuous IT intervention.
Common Mistake Treating Withdrawal as Global Delete
A major risk during DPDP implementation is confusing consent withdrawal with a mandate for total erasure. Section 4 states that a fiduciary may process data where the Data Principal has given her consent or for certain legitimate uses. If a retail banking customer withdraws consent for promotional offers, the bank must stop marketing communications. The bank must not delete the underlying KYC or transaction records. The five-year statutory retention obligation supersedes the marketing consent withdrawal.
Compliance teams must map data elements to their specific processing basis in the RoPA. Erasing financial records prematurely violates RBI mandates. Keeping marketing data after withdrawal violates the DPDP Act. Institutions require a purpose-level consent architecture to manage these distinct duties. The system must record the consent withdrawal and suppress marketing emails without touching the core banking profile.
Preparing for the Compliance Deadline
With 178 days remaining until the DPDP hard compliance deadline of 13 May 2027, banks face strict timelines to implement purpose-level enforcement. The DPDP Rules, 2025 require fiduciaries to maintain verifiable records of consent and erasure. A control owner cannot defend a data breach by pointing to a manual spreadsheet of deletion requests. Regulators expect automated pipelines that track data from ingestion through its five-year lifecycle to eventual destruction.
The penalty ceiling reaches up to 250 crore rupees for failing to secure personal data. Non-compliance with erasure mandates carries a maximum penalty of 50 crore rupees. Financial institutions must transition from tracking policies to demonstrating technical erasure. Preview an audit-ready architecture for your legacy systems at https://www.complydp.com/audit-preview.
Sources
Frequently asked questions
Does the DPDP Act require banks to keep customer data for 10 years?
No. The ten-year period in Section 8 Illustration II is only an example. Banks must follow the five-year retention mandate for KYC records set by the Prevention of Money Laundering (Maintenance of Records) Rules, 2005.
How do we manage consent withdrawal if RBI requires us to keep KYC data?
The bank must implement purpose-level consent tracking. If a customer withdraws marketing consent, the bank stops promotional communications. The underlying KYC data remains untouched until the five-year statutory retention period expires.
Can our existing core banking system handle DPDP data erasure?
Legacy core banking systems are designed to retain financial records indefinitely. Banks typically require a separate orchestration layer to monitor account closure dates and trigger API-based erasure after five years.
What evidence will the DPBI demand for data deletion compliance?
The Data Protection Board will require a verifiable audit trail proving that data was purged. This evidence pack must show the account closure date, the applied statutory rule, and the timestamp of successful deletion across databases.
What is the penalty for failing to delete data under the DPDP Act?
Retaining personal data beyond the specified purpose or statutory requirement violates Section 8. General non-compliance penalties under the Act can reach up to 50 crore rupees, while failure to secure data carries a maximum penalty of 250 crore rupees.
ComplyDP