By sector · Financial services

Customer data alongside sector regulation

Financial institutions already work under detailed regulation. ControlMap records what the DPDP framework adds, next to the security controls you already measure.

Your role under the Act

Institutions are usually Data Fiduciaries; outsourced providers are often Data Processors

A bank, lender, insurer or fintech company that decides why and how customer data is processed is a Data Fiduciary. A provider that processes data on its behalf under contract may be its Data Processor.

The Act is in addition to, and not in derogation of, any other law in force (Section 38). Requirements set by sector regulators continue to apply. This page does not describe them.

Guide: Data Fiduciary or Data Processor

Challenges

What makes this hard

  • Onboarding and identity data

    Identity verification collects detailed personal data from every customer, through several channels.

  • Retention set by other laws

    Records have to be kept for periods fixed elsewhere, which has to be reconciled with the duty to erase.

  • Extensive outsourcing

    Collections, customer support, cloud hosting and analytics all involve processors handling customer data.

  • Several legal bases at once

    Some processing rests on consent, some on a legal obligation, and the difference is rarely written down per activity.

  • High volumes of requests

    Large customer bases mean a steady stream of requests and grievances, each with a period for response.

  • Two kinds of assurance

    Technical security is measured by one team and privacy governance by another, with no shared view.

Relevant DPDP obligations

What the Act and the Rules say

These provisions are often relevant to financial services. They are summaries; the full list is on the DPDP Act page.

Section 5

Notice at the point of collection

A request for consent is accompanied or preceded by a notice. The Act illustrates this with a bank that collects personal data in a video-based customer identification process.

Section 7(d)

Disclosure required by law

Among the certain legitimate uses is fulfilling an obligation under any law in force in India to disclose information to the State or its instrumentalities.

Section 8(7)

Erasure, unless a law requires retention

Data is erased when consent is withdrawn or the purpose is no longer served, unless retention is necessary for compliance with a law. The Act illustrates this with a bank that must keep client identity records for a period set by the law that applies to banks.

Section 17(1)(f)

Loan defaults

Chapter II (other than Sections 8(1) and 8(5)), Chapter III and Section 16 do not apply to processing for ascertaining the financial information, assets and liabilities of a person who has defaulted on a loan or advance from a financial institution, subject to other law on disclosure.

Section 8(5), 8(6) · Rules 6 and 7

Safeguards and breach intimation

Reasonable security safeguards are required, and on a personal data breach the Board and each affected Data Principal are intimated.

Section 16 · Rule 15

Transfers outside India

The Central Government may restrict transfers by notification. Any other law that provides a higher degree of protection or restriction on transfer continues to apply.

These are summaries for orientation, not legal advice. Whether a provision applies to you depends on your facts. The DPDP Act page sets out the provisions more fully, says when each comes into force and links to the official text.

Typical workflow

How the work usually runs

A sequence that sits beside existing risk and audit processes.

  1. Inventory customer data by product

    Record datasets for each product line and channel, with owner, purpose and retention period.

  2. Record the basis for each activity

    Note whether processing rests on consent or on a certain legitimate use, and keep the reasoning.

  3. Review processors and transfers

    List each processor with its contract reference, and review flows that leave India.

  4. Assess the controls

    Score implementation and evidence separately for each control, with an owner and reviewer.

  5. View governance beside technical readiness

    Read control readiness next to technical control alignment from configuration checks, in one view.

The form for recording a data flow and, below it, the register of flows with source and destination, data category, purpose, basis, owner, country and any finding such as a cross-border flow that requires review.
Product screenshot. The organisation and records shown are sample data that ships with ControlMap.

Implementation approach

Three phases, in your own time

The order matters more than the pace. How long each phase takes depends on how many systems you have and who is available to do the work.

  1. First

    Scope by product line

    Start with the products that hold the most customer data, and record the inventory and basis for each.

  2. Next

    Processors, transfers and evidence

    Review outsourcing arrangements and cross-border flows, and attach evidence to the assessed controls.

  3. Ongoing

    Operate with existing governance

    Fold the review cycle into existing risk and audit calendars, and report from the live record.

Benefits

What you have at the end

ControlMap supports the work of governance. Meeting the Act's requirements remains the responsibility of your organisation.

  • The basis for each processing activity is recorded and reviewable.
  • Retention periods sit beside the reason for them.
  • Governance readiness and technical readiness are shown side by side, with the weighting between them visible.
  • An append-only audit log of who changed what.

See ControlMap beside your existing governance.

We will walk through the modules on this page with the product's sample data and answer what they do and do not cover.