DPDP for banks and NBFCs

DPDP compliance for banks and NBFCs

Customer, loan and KYC data spread across core systems, apps, branches and lending partners. We map it, then build consent, rights, retention and breach workflows into the stack you already run.

Core systems and partnersLaw firm sign-off
Banks and NBFCs

What changes, with evidence

Notice and consentVersioned notices and a consent log
Rights requestsRequest log with each step and its date
Retention and erasureRetention schedule and deletion logs
Partners and vendorsPartner register; contracts flagged for the law firm
Breach notificationTested runbook and incident records
Security safeguardsAccess reviews, logs and a control register
Six duties for lendersCore duties: 13 May 2027
One breach runbook

Where personal data sits in a bank or NBFC.

Lenders hold more personal data, in more places, than most companies. A DPDP gap assessment for a bank or NBFC starts here.

Core banking and loan management

Accounts, loans, repayments and the customer records behind them.

Onboarding and KYC

Identity documents, video KYC, bureau pulls and underwriting data.

Mobile and internet banking

App and web journeys, device data and in-app consent.

CRM, call centre and branches

Leads, service tickets, call recordings and paper forms that get scanned.

Collections

Contact details and repayment history shared with agencies and field staff.

Partners

DSAs, co-lending partners, fintechs and other vendors that receive customer data.

Data warehouse and analytics

Copies of customer data used for reporting, risk and marketing.

Employee data

HRMS, payroll and access records for your own staff.

What DPDP changes for banks and NBFCs.

Most duties start on 13 May 2027. Each one needs a system change and evidence that it works.

Notice and consent

What changesA clear notice and consent per purpose in onboarding and lending journeys, kept separate from marketing.

EvidenceVersioned notices and a consent log

Rights requests

What changesOne intake for access, correction, erasure and grievances, routed to every system and partner that holds the data.

EvidenceRequest log with each step and its date

Retention and erasure

What changesA retention period for each system. Records you must keep under other laws are listed with their reason, and confirmed by our partner law firm.

EvidenceRetention schedule and deletion logs

Partners and vendors

What changesA map of what each DSA, collection agency, co-lending partner and vendor receives, with controls on what they get.

EvidencePartner register; contracts flagged for the law firm

Breach notification

What changesOne runbook: CERT-In within 6 hours; affected people and the Data Protection Board without delay, with a detailed report to the Board within 72 hours.

EvidenceTested runbook and incident records

Security safeguards

What changesAccess control, encryption, logging and monitoring on every system that holds customer data.

EvidenceAccess reviews, logs and a control register

DPDP alongside your sector rules.

Banks and NBFCs already follow sector rules on records, outsourcing and cyber security. We build one set of controls and evidence, and our partner law firm confirms where those rules and DPDP overlap.

  1. Step 1

    Map

    Find customer, loan and KYC data across systems, branches and partners.

  2. Step 2

    Assess

    Compare each system against the Act and Rules, and flag sector rules for the law firm.

  3. Step 3

    Build

    Consent, rights requests, retention jobs and the breach runbook, in your stack.

  4. Step 4

    Evidence

    Logs and records your compliance and audit teams can check.

Fintechs, NBFCs and digital lending.

The same customer data, seen from three seats. What each one has to build for DPDP and the RBI’s rules. Our guide to DPDP for digital lending apps goes through each rule with its paragraph number.

Fintechs and lending service providers

  • The lender stays responsible for its LSPs and their apps under the RBI’s digital lending rules
  • An LSP working only for the lender usually acts as its processor under DPDP
  • An LSP that uses borrower data for its own marketing or models may be a fiduciary for that use
  • An LSP may store only basic minimal data, such as name, address and contact details

NBFCs

  • KYC records kept for at least five years under the KYC Directions, then erased
  • One retention schedule that names the law behind every record you keep
  • Account Aggregator data used only as the consent artefact allows
  • A board-approved AI policy, as the RBI’s FREE-AI committee recommends

Digital lending apps

  • No access to files, media, contacts, call logs or telephony, SDKs included
  • Camera, microphone and location once only, for onboarding or KYC, with explicit consent
  • Need-based collection, with consent per purpose and an audit trail
  • Borrower data stored only on servers in India

RBI and DPDP: one control map.

The DPDP Act applies alongside other laws, and where the RBI’s rule is stricter you build to it. One control can then serve both, with one set of evidence. Using Account Aggregator data? Read where AA consent and DPDP consent meet. Our partner law firm confirms which Directions apply to you.

Notice and consent

DPDP Act and RulesA standalone notice with an itemised list of the data and purposes (Rule 3). Consent that is free, specific, informed and limited to the data needed (Section 6(1)).

RBI rulesNeed-based collection with prior, explicit consent and an audit trail (Digital Lending, para 13(1)).

Sharing with partners

DPDP Act and RulesConsent or a legitimate use, and processors only under a valid contract (Sections 4, 7 and 8(2)).

RBI rulesExplicit consent before sharing with any third party, unless a statute or regulation requires it (Digital Lending, para 13(4)).

Account Aggregator data

DPDP Act and RulesYour own processing of the data still needs a DPDP ground, a notice and the Section 8 duties.

RBI rulesNo use or disclosure beyond the consent artefact; consent can be revoked in full or in part (AA Directions 2025, paras 20 and 28).

Retention and erasure

DPDP Act and RulesErase when consent is withdrawn or the purpose ends, unless a law requires retention (Sections 8(7) and 12(3)). Keep logs for at least one year (Rule 8(3)).

RBI rulesKYC identification records kept for at least five years after the relationship ends, and transaction records for at least five years from each transaction (KYC Directions, para 47).

Where data is stored

DPDP Act and RulesTransfers abroad are allowed unless the Government restricts a country, and stricter laws still apply (Section 16).

RBI rulesPayment system data stored only in India (RBI/2017-18/153). Digital lending data stored only on servers in India (para 14(4)).

Breach and incidents

DPDP Act and RulesTell each affected person and the Board without delay, with a detailed report to the Board within 72 hours (Rule 7). CERT-In: 6 hours.

RBI rulesReport to the RBI where your Directions require it. Payment aggregators also send monthly cyber security incident reports.

AI and models

DPDP Act and RulesNo AI-specific duty, but every DPDP duty applies to data used in AI. Algorithmic due diligence applies to Significant Data Fiduciaries, if designated (Rule 13(3)).

RBI rulesFREE-AI recommends a board-approved AI policy; it is not a direction. The June 2026 model risk guidance is still a draft.

Building AI into lending or support? See our board-approved AI policy guide for NBFCs. Regulated by SEBI as well? Read SEBI’s AI/ML rules for intermediaries.

Payment aggregators and gateways: a processor checklist.

For teams that build or run payment aggregator and gateway systems, or process data for them. Taken from the RBI’s Payment Aggregator Directions, 2025 (updated as on 11 November 2026) and the DPDP Act and Rules. This is not legal advice.

Payment data in India

Payment system data is stored only in India. If it is processed abroad, it is deleted there and brought back within one business day or 24 hours, whichever is earlier.

No stored card credentials

Customer card credentials are not stored in any database or server the merchant can access.

PCI-DSS and PCI-SSF

Your own systems and your merchants’ infrastructure meet PCI-DSS and PCI-SSF, as applicable.

Security policy and audit

A board-approved information security policy, and an annual system and cyber security audit by a CERT-In empanelled auditor.

One incident runbook

Security incidents and card holder data breaches reported to the RBI, CERT-In within 6 hours, and DPDP breach notices under Rule 7.

Merchant KYC

Merchant due diligence under the KYC Directions, with KYC records pulled from CKYCR with the merchant’s consent. A sole proprietor’s KYC record is personal data too.

Processor duties

Where you process data for a merchant or bank, a contract with security terms (Section 8(2), Rule 6(1)(f)), and erasure when the fiduciary asks (Section 8(7)(b)).

Payment gateways

A gateway that never handles funds is outside the Directions, but the RBI encourages it to adopt the same baseline technology recommendations.

DPDP for banks and NBFCs: FAQs.

Can a customer ask us to erase data we are required to keep?

Banks and NBFCs must keep some records under other laws. We list each one with its reason and retention period, and our partner law firm confirms which rules apply. Everything else follows your DPDP retention schedule.

Do DSAs, collection agencies and co-lending partners count?

They often receive your customers' personal data, so they are in scope. We map what each partner receives and how. Our partner law firm confirms which act on your behalf and which are responsible for the data in their own right, and reviews the contracts.

How do CERT-In and DPDP breach reporting fit together?

CERT-In requires cyber incidents to be reported within 6 hours. Under the DPDP Rules you must tell affected people and the Data Protection Board without delay, and send the Board a detailed report within 72 hours. We build one runbook that covers both.

What are the penalties under the DPDP Act?

Up to ₹250 crore for failing to take reasonable security safeguards to prevent a breach. Up to ₹200 crore for failing to report a breach or for breaching the duties on children's data. Other failures carry lower limits set out in the Act's Schedule.

Do you give legal advice?

No. Our engineers do the technical work. Our partner law firm reviews it and gives you signed, written legal documentation.

Find out what DPDP changes for your lending business.