DPDP Workspace
Menu

DPDP for banks, from the branch to the app

Keep one record of what each customer agreed to, across branch, app and call centre, and answer every request and breach on time.

An illustration of the Banking pack's tasks in the platform.

This is general information, not legal advice. For your own situation, speak to a lawyer.

Where DPDP bites in Banking

  • Consent across every channel

    A customer who agrees in the app and withdraws at a branch must be heard in both; withdrawing is as easy as consenting, and you prove each consent.Source: s.6(4) · s.6(10)
  • Keeping versus erasing

    DPDP erases data once its purpose is served unless a law needs it kept; RBI's rules for banks set their own record periods, which come first.Source: s.8(7)
  • Two breach clocks at least

    CERT-In wants listed cyber incidents within 6 hours; the Board a detailed report within 72 hours of a personal data breach, on top of RBI's own reporting rules.Source: direction (ii) · R.7(2)(b)
  • A likely Significant Data Fiduciary

    The government may notify a Data Fiduciary that processes large volumes or sensitive personal data as a Significant Data Fiduciary, with a Data Protection Officer in India, audits and impact assessments.Source: s.10(1) · R.13

The Banking pack

Added to the DPDP tasks every client gets, and kept up to date as data.

  • Obligations by channelDPDP tasks for branch, app, call centre and agents, each with its section.
  • Retention rulesRecord periods you set from RBI's rules, held before erasure.
  • Breach clocksCERT-In's 6 hours and the Board's 72 hours on every incident.
  • Banking data categoriesAccount, KYC, card, transaction and nominee records.
  • Readiness questionsQuestions for banks, added to your readiness assessment.

Key modules

  • Consent & preferences

    Collect, check and withdraw consent on web, apps and your own systems
  • Rights requests

    Every request from intake to reply, on its deadline clock, with proof
  • Breach response

    Every breach recorded, with the 6-hour and 72-hour clocks and the Board report
  • Governance & evidence

    A tamper-evident trail of every action and an evidence pack in one click

Questions

Does every use of customer data need consent?

Not always. Data a customer gives you for a specified purpose can be used for it unless they object, and data a law needs kept is kept as that law requires. Marketing usually rests on consent, withdrawable at any time.

Source: s.7(a) · s.8(7) · s.6(4)

Does CERT-In's 6-hour rule apply to banks?

Yes. CERT-In's directions of 28 April 2022 apply to any body corporate, and listed cyber incidents are reported within 6 hours of noticing them, beside the Board's report.

Source: direction (ii) · R.7

How long do we have to answer a customer's grievance?

Within the period you publish, which can be no longer than 90 days. The platform puts each request on its own clock from the day it arrives.

Source: R.14(3)

Do RBI's rules still apply alongside DPDP?

Yes. The Act applies in addition to other laws, and its erasure duty yields to a law that needs data kept. Your compliance team sets the periods from RBI's rules in the platform.

Source: s.38(1) · s.8(7)

Official texts: MeitY's data protection page, the Gazette of India, CERT-In.

See the platform with Banking data

We show you the platform with sample data from your sector and talk through how your team would use it.