DPDP Data Retention vs PMLA: Which Law Wins Before May 2027
DPDP Act Compliance

DPDP Data Retention vs PMLA: Which Law Wins Before May 2027

Ranu GuptaNovember 202612 min

The DPDP Act's own illustration on erasure assumes a bank must keep closed-account identity records for ten years, though PMLA has required five since 2013. That stale figure now sits in vendor material and internal policies, and it frames DPDP data retention as a fight between two laws. Our view is that the laws already fit and over-retention is the bigger risk, and this article sets out the controls that prove it.

Why 13 May 2027 Forces the Retention Question Now

The commencement notification of 13 November 2025 brought most of Sections 3 to 17 of the DPDP Act into force eighteen months later. That date is 13 May 2027. The erasure duty in Section 8(7), the rights in Sections 11 and 12 and the exemptions in Section 17 all start together. The DPDP Rules, 2025 follow the same calendar for Rules 3 and 5 to 16, which include Rule 8 on erasure.

The banking side has moved as well. The RBI consolidated its KYC rules for commercial banks in Directions dated 28 November 2025, reference RBI/DOR/2025-26/169. The text was last updated as on 1 October 2026. Paragraph 50 restates the PMLA retention periods and widens what counts as an identification record.

Less than six months remain, which is not long for this work. Retention touches every system at once. Core banking, the loan origination stack, the CRM, call recordings and the backup vendor all hold copies, and each runs its own release cycle. For banks, NBFCs and fintechs, retention design has to start this quarter if deletion is to run by May.

The Schedule to the Act sets the stakes. A failure of reasonable security safeguards can draw a penalty of up to ₹250 crore. A failure to erase falls under the residual entry, which goes up to ₹50 crore. Archived KYC data carries the first risk for as long as you hold it, and stale data carries the second.

Where DPDP Data Retention and PMLA Actually Collide

Start with the text. Section 8(7) requires erasure once consent is withdrawn or the purpose is spent, unless retention is necessary for compliance with any law. Section 6(6) lets processing continue after withdrawal where another law requires it. Section 12(3) carries the same exception into the customer's erasure right. Section 38(2) makes the DPDP Act prevail over other laws in a conflict, but on retention the Act has already stepped aside.

Many programmes import a European habit at this point. Teams tag KYC data as legal obligation processing and move on. The DPDP Act has no such ground. Section 4 allows processing on consent or for the legitimate uses in Section 7. Of those, Section 7(d) reaches only duties to disclose information to the State. In our reading, KYC collected at onboarding rests on notice and consent, or on voluntary provision under Section 7(a). The Act's own illustration under Section 5, a KYC done through video-based customer identification, assumes a notice. So the PMLA defence works as an exception to erasure. It gives no licence for fresh uses of the data.

The genuine collision is confidentiality. Section 11 entitles a customer to a summary of the personal data processed about her. PMLA Section 12(2) keeps every record maintained or furnished under it confidential. The RBI Directions bar disclosure of reporting to FIU-IND in paragraph 54 and of risk categorisation in paragraph 20(4). We read Section 17(1)(c) of the DPDP Act as the answer. It disapplies Chapter III rights where data is processed to prevent, detect or investigate an offence. Alert files, suspicious transaction report (STR) workings and AML risk scores sit inside that exemption. The customer's address and account balance do not.

Retention under PMLA does not take data outside the DPDP Act. Section 17(1) keeps the security duty in Section 8(5) alive even for exempt processing. Every archived KYC image still needs encryption, access control and breach readiness.

PMLA protects the record it names, for the period it names. It does not protect the copy sitting in a marketing data lake.

SARC DPDP Act Compliance Practice

The Two PMLA Clocks Behind Every DPDP Data Retention Schedule

PMLA runs two clocks. Section 12(3) keeps transaction records for five years from the date of each transaction. Section 12(4) keeps identity documents, account files and business correspondence for five years after the relationship ends or the account closes, whichever is later.

The ten-year figure is older law. Section 12 was substituted by Act 2 of 2013, and the version it replaced set ten years for both clocks. Illustration (II) to Section 8(7) still describes the old period. An illustration explains a provision. It cannot extend a retention period that PMLA itself has shortened.

The RBI Directions say "at least five years". That wording permits a longer period but does not require one. From 13 May 2027, any period beyond five years needs its own legal reason, written down against the data category.

What counts as an identification record has grown. The Explanation to paragraph 50 includes updated records, account files, business correspondence and the results of any analysis. The Second Amendment Rules of 4 September 2023, G.S.R. 652(E), added analysis results to Rule 10(3) of the PML Rules. Alert dispositions and enhanced due diligence (EDD) notes now run on the longer, relationship-based clock. We read updated records as keeping superseded KYC versions in the file, so periodic updation adds to the archive rather than refreshing it.

SEBI adds an open-ended hold for securities intermediaries. Its master circular of 6 June 2024 keeps records linked to an ongoing investigation or an STR until the case is confirmed closed. Investigating agencies may also ask intermediaries to retain records for longer. Banks receive the same agency requests, so the hold belongs in every reporting entity's design.

The schedule we recommend starts from these clocks:

Data categoryBasis for keepingClock startsMinimum period
Transaction recordsPMLA Section 12(3), RBI para 50(1)Date of transactionFive years
Identity documents, account files, correspondencePMLA Section 12(4), RBI para 50(2)Relationship ends or account closes, whichever is laterFive years
Alert reviews, EDD notes, analysis resultsPML Rules Rule 10(3) as amended in 2023Relationship ends or account closesFive years
Records under investigation or linked to an STRSEBI master circular para 52, agency requestsHold placedUntil case closure
Marketing, cross-sell and analytics dataConsentWithdrawal or purpose endsErase under Section 8(7)
Access and processing logsDPDP Rules 6(1)(e) and 8(3)Date of processingOne year

Two consequences follow. A long-standing customer's early transactions can age out while the account is still open, unless another law or a hold keeps them. And no KYC image can go at closure, however firmly the customer asks. Legal teams also need to settle what counts as an account file. Statements are the usual argument, and the answer sets the size of your archive.

Withdrawal, Erasure Requests and the Copies PMLA Does Not Cover

Under Section 6(6), withdrawal of consent stops processing within a reasonable time, except where another law requires it. In practice that means a use freeze. The core banking record stays. The marketing flag, the pre-approved offer engine and the propensity model lose that customer on the same day.

Copies are where most banks fail. Our PMLA compliance guide explains why a PAN image cached in a lending app or a CRM export sits outside the PMLA record. The fix is to find them. Data discovery across file shares, mailboxes and vendor portals often turns up KYC images in places nobody listed. Section 8(7)(b) then makes the bank answerable for erasure by its processors. Most onboarding vendor contracts we read say return or destroy on termination. They say nothing about a customer who leaves while the contract runs.

Minimisation applies inside the archive as well. Keep what Section 12 names, plus the details paragraph 50(5) needs to reconstruct a transaction. Nature, amount, currency, date and parties are enough. Device fingerprints, app behaviour scores and campaign tags do not belong there.

Access should narrow on the day an account closes. The Principal Officer's team, internal audit and staff answering competent authorities need it. Relationship managers and collections do not, unless a live claim exists. Enforce this through identity and access management rather than a policy note. Keep the access logs for at least one year under Rule 6(1)(e).

The flowchart below shows how an erasure request should route after 13 May 2027.

The reply matters as much as the routing. Tell the customer which categories you are keeping, under which law and until when. Never mention an alert, an STR or a risk rating. A rights request workflow should run that AML screen before release and log that it ran.

Retention Schedules, Deletion Jobs and Notices That Survive Inspection

Build the schedule from a field-level data map, not from the policy binder. Each row needs the data category, system, legal basis, trigger event, period, owner and a hold flag. That row set is the core of a record of processing activities, and it is the document an inspector is likely to ask for first.

Key the deletion job to the closure date in core banking, never the onboarding date. A nightly run reads closure and transaction dates, checks hold flags set by the Principal Officer's team, and queues deletion across systems and processors. Each run writes a log line with the record identifier, category, legal basis, system and date. No content goes into the log. Rule 8(3) requires processing logs to be kept for at least a year, so the deletion evidence outlives the data it describes. Backups age out on rotation. Document the rotation period and block restores of records already erased.

Notices then need to say plainly what the bank keeps. Wording that reads well with customers covers three points:

  • We keep your identity documents, account files and correspondence for five years after your relationship with us ends, as anti-money laundering law requires.
  • We keep records of each transaction for five years from the date of that transaction.
  • During that time we use these records only to meet legal duties, and we delete them when the period ends unless an investigation requires longer.

Before 13 May 2027, a reporting entity should be able to show:

  • A field-level data map across core banking, lending, CRM, contact centre and vendor systems, tagged by legal basis.
  • A retention schedule with separate transaction and identification clocks, approved by the Board or its delegate.
  • A legal hold register owned by the Principal Officer and wired into the deletion job.
  • An automated deletion job driven by closure and transaction dates, with run logs kept for at least one year.
  • Processor contracts that require erasure on instruction during the contract, not only at exit.
  • A rights request workflow with an AML screen before any reply.
  • Updated notices that state statutory retention in plain language.
  • A sized backlog of records already past both PMLA clocks, with an owner and a date to clear it.

The SARC Perspective

Start with the backlog. Accounts closed before May 2022 will be past both PMLA clocks by 13 May 2027, unless a hold or another law applies. In most banks those records sit untouched, because nobody has ever owned their deletion. Size the backlog now and test it against tax, banking and limitation rules with your legal team. Section 17(1)(a) exempts processing needed to enforce a live legal claim, such as a recovery suit. Everything else with no remaining basis should go before the Board has to explain why it did not.

Then settle ownership. Retention tends to fall between the Principal Officer, the DPO and the CIO, and each assumes another holds it. Give one executive the schedule and give the Principal Officer the hold flag. Our DPDP readiness assessment tests the schedule against live systems rather than policy. Alongside it, our anti-money laundering specialists check that nothing PMLA needs is lost in the clean-up. That pairing is why our DPDP Act compliance and risk teams take this problem on together.

Frequently Asked Questions

Does the DPDP Act's ten-year illustration override the PMLA period?

No. Illustrations explain a provision and do not create obligations. Section 12 of PMLA sets five years for both clocks. Keep records longer only where another law, a hold or a live legal claim requires it.

Can a customer insist that we delete KYC documents after closing the account?

Not within the PMLA period. Section 12(3) of the DPDP Act lets you keep data needed to comply with law. Delete the copies held outside the PMLA record, and tell the customer when the retained records will go.

Must we show a customer their alert history or risk rating in an access response?

No. We read Section 17(1)(c) as taking that processing outside the Chapter III rights. PMLA Section 12(2) and the RBI Directions separately require confidentiality. Answer the request with ordinary account data and record that the AML screen ran.

Can we keep loan files beyond five years for recovery litigation?

Yes, while the claim is live. Section 17(1)(a) exempts processing necessary to enforce a legal right or claim. Record the case reference against the file and release the hold when the matter ends.

Does the one-year log rule add to the PMLA periods?

It runs alongside them. Rule 8(3) requires personal data, traffic data and processing logs to be kept for at least one year from processing. For PMLA records, the five-year clocks are always longer. The rule matters most for deletion logs and for data held outside the PMLA record.

Talk to SARC's DPDP Act Compliance team about your PMLA retention schedule

Our advisory team is ready to help.

Contact Us
Ranu Gupta

Ranu Gupta

Co-founder & Chief Executive Officer