Sector guidesUpdated 22 November 20269 min read

DPDP for Banks, NBFCs and Fintechs

How banks, NBFCs, payment companies and fintechs layer DPDP obligations on top of RBI rules: consent, retention, breach, cross-border, AI credit models and Consent Managers.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Core DPDP rules apply
13 May 2027
Stricter sectoral law
Continues to apply (s. 16(2) for transfers)
RBI payment data storage
Circular of 6 April 2018
Board detailed breach report
Within 72 hours (Rule 7(2)(b))
CERT-In incident report
Within 6 hours of noticing
Security penalty
Up to ₹250 crore

Quick answer

Banks, NBFCs and fintechs are Data Fiduciaries under DPDP from 13 May 2027 and must meet notice, Rule 6 security, 72-hour breach, one-year log retention and rights obligations. DPDP does not displace RBI rules: section 16(2) preserves stricter transfer restrictions, so RBI payment data storage continues, and sectoral record-keeping that requires longer retention continues to prevail.

  • DPDP adds a horizontal privacy layer; stricter RBI and other sectoral requirements continue to apply.
  • Section 16(2) preserves laws with a higher degree of protection or restriction on cross-border transfer, such as RBI payment data storage.
  • Every personal data breach is reportable to customers and the Board, alongside existing RBI and CERT-In incident reporting.
  • The RBI FREE-AI report recommends board-approved AI policies, AI inventories and customer disclosure; it binds only through RBI directions.
  • Consent Manager registration has been possible since 13 November 2026; the Rules' own illustration uses two banks.

Who this is for: Banks and small finance banks, NBFCs and digital lenders, Payment aggregators and PPI issuers, Fintech startups and lending service providers, Compliance, CISO and DPO teams

How does DPDP interact with RBI regulation?

Banks and regulated financial entities already operate under detailed RBI directions on KYC, outsourcing, IT governance, cyber security, digital lending and customer service. The DPDP Act adds a horizontal privacy law on top. It does not repeal sectoral requirements.

Three principles govern the overlap:

  1. Stricter sectoral rules continue. Where an RBI direction or other law imposes a higher standard — longer retention, tighter localisation, faster reporting — it continues to apply. Section 16(2) of the DPDP Act says the transfer section does not restrict laws providing a higher degree of protection or restriction on transfer of personal data outside India.
  2. Legal retention prevails over erasure. Section 8(7) requires erasure when consent is withdrawn or the purpose is served "unless retention is necessary for compliance with any law". KYC and transaction record-keeping obligations therefore override a customer's erasure request for that data.
  3. DPDP fills gaps. Notices, consent quality, rights requests, grievance timelines, breach notice to every affected customer and the Board, and one-year log retention are DPDP obligations even where sectoral rules are silent.

The core Rules apply from 13 May 2027. Until then, section 43A of the IT Act and the SPDI Rules, 2011 continue to apply; section 44(2) of the DPDP Act omits section 43A from that date.

Account opening and servicing involve processing that is either required by law or voluntarily provided for a specified purpose:

  • Legal obligations. KYC and regulatory reporting follow from law; erasure requests do not reach data that law requires you to keep.
  • Section 7(a). Data a customer voluntarily provides to open an account or take a loan, used for that purpose, fits the voluntary-provision legitimate use where she has not indicated non-consent.
  • Consent (section 6). Marketing, cross-selling third-party products, sharing with partners for their own purposes, and alternative-data credit models that go beyond what the customer provided for the loan.

Rule 3 notices must itemise data and specify purposes. For lending apps, that means listing device data, SMS or contacts access if any, bureau pulls and any alternative data sources, with specific uses.

Exemption to note. Section 17(1) disapplies parts of the Act for processing to ascertain the financial information and assets and liabilities of a person who has defaulted on a loan or advance, where done under law. It is narrow and does not cover general collections practices.

Consent Managers. Rule 4 has been in force since 13 November 2026. The First Schedule's illustration describes a user on a Consent Manager platform giving consent to bank B1, either directly or routed through bank B2 that holds her statement. Banks should plan how they will accept consents via registered Consent Managers. See Consent Managers explained.

Data localisation and cross-border transfers

DPDP itself does not impose general localisation. Section 16 lets the Central Government restrict transfers to notified countries, and Rule 15 lets it specify requirements on making data available to foreign States. Rule 13(4) can require Significant Data Fiduciaries to keep specified data in India, once notified.

Sectoral rules are stricter:

RequirementSourceWhat it means
Entire payment system data stored only in IndiaRBI circular, 6 April 2018Applies to payment system providers and their service providers
Foreign-leg processingRBI FAQs, June 2019Data may be processed abroad but must be stored in India; delete abroad within one business day or 24 hours, whichever is earlier
Other localisation and outsourcing conditionsRBI directionsCheck the current master directions for your entity type

For AI workloads, this means payment data cannot be sent to an offshore LLM or analytics service for storage, and any foreign processing must meet the return-and-delete rule. Use India-region hosting for models that touch payment data, or mask it before it leaves.

See RBI payment data localisation and AI and DPDP cross-border transfers.

Security safeguards and breach reporting

Banks already run mature security programmes, but DPDP changes breach notification in one important way: every personal data breach must be notified to each affected customer and to the Board, with no materiality threshold.

Under Rule 7:

  • Customers: without delay, through their account or registered contact — description, likely consequences, mitigation, steps they can take, and a contact.
  • Board: without delay, a description including nature, extent, timing, location and likely impact; within 72 hours, a detailed report covering circumstances, mitigation, findings on who caused it, remediation and a report on customer notices.

This runs in parallel with CERT-In's 6-hour reporting for specified incidents and any RBI incident reporting requirements. Build one incident workflow that produces all three outputs from the same facts.

Rule 6 safeguards map onto existing controls — encryption and tokenisation, privileged access management, SOC monitoring, backups and DR — with two additions to check:

  • Rule 6(1)(e) and 8(3): retain relevant logs and personal data for one year, then erase unless law requires longer. Banking record-keeping often requires longer for transaction data; logs should still have a defined end.
  • Rule 6(1)(f): security clauses in every processor contract — core banking vendors, BCs, collection agencies, cloud and AI providers.

Penalties reach ₹250 crore for security failures and ₹200 crore for failing to notify.

AI credit models, fraud analytics and FREE-AI

Fintech AI raises DPDP questions in three places:

  • Credit scoring. Section 8(3) requires completeness, accuracy and consistency of personal data used to make decisions affecting the Data Principal. Credit decisions are the clearest case. Keep data quality controls, explainability for adverse decisions and a correction route.
  • Alternative data. Device, SMS, location or contacts data used for underwriting needs a specific Rule 3 notice and consent; it is rarely "voluntarily provided" for that purpose in the section 7(a) sense.
  • Fraud and AML analytics. Usually tied to legal obligations; document the basis and keep models' input data minimised.

The RBI FREE-AI committee report (August 2025, chaired by Prof. Pushpak Bhattacharyya) sets out 7 sutras and 26 recommendations across six pillars. Its asks for regulated entities include a board-approved AI policy, an AI inventory of models and use cases, risk-based classification, disclosure to customers when they interact with AI, grievance mechanisms with human escalation, AI incident reporting, audits and model validation, and AI cybersecurity. It becomes binding only when RBI issues directions or circulars — check the latest position.

If you score EU residents' creditworthiness, the EU AI Act treats credit scoring of natural persons (except fraud detection) as Annex III high-risk. See RBI FREE-AI and the board AI policy template.

Partners, lending service providers and fintech stacks

Financial products are increasingly delivered through partnerships — bank with fintech front-end, NBFC with lending service provider, PA with merchant platforms. DPDP requires clarity on roles:

  • Who is fiduciary? The entity deciding purpose and means. Co-lending and embedded-finance arrangements may create joint or separate fiduciaries for different purposes. Document it per data flow.
  • Processors. Sourcing agents, collection agencies, KYC vendors, cloud and AI providers acting on instructions need a valid contract under section 8(2) with Rule 6(1)(f) safeguards.
  • Rights requests across partners. Section 11 gives the customer a right to know the identities of other fiduciaries and processors her data was shared with. Keep a sharing register per customer.
  • Rule 8(3) for processors. The Rule's cloud illustration requires you to ensure processors also retain data and logs for at least one year before erasure.
  • Grievances. Publish one route with a response period of at most 90 days, and coordinate with partners so the customer is not bounced between them.

Fintechs selling to banks should expect DPDP-mapped vendor due diligence on top of RBI outsourcing requirements. See the AI vendor due diligence checklist.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Map each data flow to its basis

    Separate legal-obligation processing, s. 7(a) servicing and consent-based marketing or alternative-data use.

    DPDP Act ss. 6–7

  2. Reconcile retention with sectoral law

    Document where RBI or other laws require longer retention and erase other data on purpose completion.

    DPDP Act s. 8(7); Rule 8(3)

  3. Keep payment data in India

    Ensure payment system data, including in AI and analytics workloads, is stored only in India and foreign copies deleted on time.

    RBI circular, 6 April 2018

  4. Unify incident reporting

    Produce customer notices, the 72-hour Board report, CERT-In and RBI reports from one workflow.

    Rule 7

  5. Add DPDP clauses to processor contracts

    Cover safeguards, breach notice, one-year retention and erasure for BCs, agencies, cloud and AI vendors.

    Rule 6(1)(f); s. 8(2)

  6. Control credit-model data quality

    Ensure accuracy and correction routes for data used in credit decisions.

    DPDP Act s. 8(3)

  7. Itemise alternative-data use in notices

    List device, SMS, location or bureau data and their specific uses in Rule 3 notices.

    Rule 3(b)

  8. Prepare to accept Consent Manager consents

    Design integration with registered Consent Managers for consent capture and withdrawal.

    Rule 4; First Schedule

  9. Maintain an AI inventory

    List models and use cases with risk classification, ahead of any RBI directions on FREE-AI.

    RBI FREE-AI (recommendation)

  10. Keep a per-customer sharing register

    Record fiduciaries and processors each customer's data is shared with, for access requests.

    DPDP Act s. 11

Key dates

  1. RBI circular on storage of payment system data

  2. DPDP Rules notified

  3. Consent Manager registration (Rule 4) in force

  4. Core DPDP obligations apply; IT Act s. 43A omitted

Answers

Frequently asked questions

Does DPDP override RBI data rules?

No. DPDP adds a general privacy layer and stricter sectoral rules continue to apply. Section 16(2) preserves laws that provide a higher degree of protection or restriction on cross-border transfers, so RBI's payment data storage requirements continue, and record-keeping laws requiring retention prevail over erasure requests.

Can a bank customer ask for her KYC data to be deleted under DPDP?

She can make an erasure request, but section 8(7) allows retention where it is necessary to comply with any law. KYC and transaction records that banking and anti-money-laundering laws require the bank to keep will not be erased until those periods end. The bank should explain this in its response.

Do banks have to report every data breach under DPDP?

Yes. From 13 May 2027, Rule 7 requires notice of every personal data breach, with no materiality threshold, to each affected customer without delay and to the Data Protection Board, followed by a detailed report within 72 hours. CERT-In's 6-hour reporting and RBI reporting requirements continue alongside.

Is the RBI FREE-AI framework mandatory?

Not by itself. FREE-AI is a committee report released in August 2025 with 26 recommendations, including board-approved AI policies, AI inventories and customer disclosure. Its recommendations become binding only when RBI issues directions or circulars, so check the latest RBI communications.

Can a fintech use SMS or contact data for credit scoring under DPDP?

Only with a specific, informed consent and a Rule 3 notice that itemises the data and the use, and subject to any RBI digital lending rules that restrict such access. This data is rarely voluntarily provided for underwriting in the section 7(a) sense, and section 8(3) accuracy duties apply to credit decisions.

What do Consent Managers mean for banks?

Since 13 November 2026, entities meeting First Schedule conditions, including ₹2 crore net worth, can register with the Board as Consent Managers. The Rules' illustration shows a user giving a bank consent through such a platform, directly or routed through another bank. Banks should plan integration for consent capture and withdrawal.

Legal references and sources

  • Digital Personal Data Protection Act, 2023 — Sections 8, 16 and 17(1) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rules 6, 7 and 8(3) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 4 and First Schedule (official text)
  • RBI circular on storage of payment system data — 6 April 2018 and FAQs (June 2019) (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

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.