Skip to content

Bananaflow MCP is live.

Read the docs

DPDP Rules 2025 for Call Centers: Consent

Jaseem Abbas, founder of Bananaflow, in glasses and a dark top against a pale background.Jaseem Abbas

Published
Updated
Cover for "DPDP Rules 2025 for Call Centers: Consent": a white line diagram of one call's data trail, five glass panels in a row labelled Call, Notice, Consent, Recording and Erase, with a dashed arrow from Recording up to a pill reading Breach: Board, 72 hours, and an arc under the row from Consent to Erase labelled Withdraw, drawn over a soft, out-of-focus delphinium in muted sky blue, with a sage mint haze at the far left and a dusty rose glow at the far right.

Picture a home-loan helpline in Pune. It takes 3,000 calls a day, records every one, and keeps the audio on a shared drive "just in case". A caller named Meera asks the agent to stop calling her about a loan offer. Six months later, she finds out the recording of that call is still there, and nobody can tell her who listened to it.

Until now, that was a service problem. Under the Digital Personal Data Protection Act, 2023 (the DPDP Act) and the DPDP Rules, 2025, it becomes a legal one. A caller's voice, phone number and words are personal data. This guide explains what the law asks of a call center, with the dates and the official sources.

What are the DPDP Act and the DPDP Rules 2025?

The DPDP Act, 2023 is India's data protection law. Parliament enacted it on 11 August 2023. The DPDP Rules, 2025 are the detailed rules under it. They were published in the Gazette of India on 13 November 2025 as G.S.R. 846(E). Together they set how a business collects, uses, keeps and protects personal data.

The Press Information Bureau announced the Rules on 14 November 2025. The Act also creates the Data Protection Board of India, a digital body that takes complaints. Appeals against its decisions go to the Telecom Disputes Settlement and Appellate Tribunal (TDSAT).

Three words matter in the Act, and they come up all through this guide:

  • Data Principal: the person the data is about. On a call, that is the caller.
  • Data Fiduciary: the business that decides why and how the data is used.
  • Data Processor: anyone who handles the data on the fiduciary's behalf.

Read the full DPDP Act, 2023 and DPDP Rules, 2025 on the Ministry of Electronics and IT (MeitY) site.

When do the DPDP Rules start applying to a call center?

The Rules start in three steps. Rules 1, 2 and 17 to 21 began on 13 November 2025. Rule 4, on consent managers, starts one year after publication, on 13 November 2026. Rules 3, 5 to 16, 22 and 23 start eighteen months after publication, in May 2027. Those hold your day-to-day duties.

The dates come from rule 1. The Act's own sections switched on in the same three steps (AZB & Partners table).

  • Date: 13 November 2025

    What starts
    Rules 1, 2 and 17 to 21
    What it means for a call center
    Definitions and the Data Protection Board. No new duty on your calls yet.
  • Date: 13 November 2026

    What starts
    Rule 4
    What it means for a call center
    How consent managers register. Matters only if your customers use one.
  • Date: May 2027

    What starts
    Rules 3, 5 to 16, 22 and 23
    What it means for a call center
    Notice, security, breach reporting, erasure, rights and children's data.

A word on a possible shorter timeline. In January 2026, MeitY reportedly asked industry for views on cutting the 18 months to 12, including for large "significant data fiduciaries" (see the S.S. Rana & Co. note on the proposal). As of 11 November 2026, we found no notified amendment that changes the dates above. Check the Gazette on meity.gov.in before you rely on any date.

Is a call center a data fiduciary or a data processor?

It depends on who decides why and how the data is used. A business that chooses to call its customers is the data fiduciary. A call center that places those calls on its behalf is usually a data processor. The fiduciary stays responsible for what the processor does, and must hire it under a valid contract.

The Act says this in section 2: a Data Fiduciary is anyone who "determines the purpose and means of processing", and a Data Processor is anyone who processes data "on behalf of a Data Fiduciary". Section 8(1) then says the fiduciary is responsible "irrespective of any agreement to the contrary", and section 8(2) allows a processor only "under a valid contract".

What this means in practice:

  • If you are a BPO, expect your clients to rewrite your contracts. They will ask how you secure data, how fast you report a breach and how you delete data.
  • If you run your own call center, you are the fiduciary. Your vendors (dialer, recording, cloud) are processors, and a breach at one of them is still yours to report.

Is the caller's voice really "personal data"? Section 2(t) defines personal data as "any data about an individual who is identifiable by or in relation to such data". A recording of a named customer talking about her loan fits. Section 2(x) lists "recording" and "storage" as forms of processing. For more, read is call recording legal in India.

Consent must be free, specific, informed, unconditional and unambiguous, with a clear action by the caller. It must cover only the data needed for the stated purpose. Before you ask for it, you must give a notice that names the data and the purpose, and tells the caller how to withdraw consent and complain.

The Act's section 6(1) sets the standard for consent. Section 5 and rule 3 set the notice. Under rule 3, the notice must:

  • be understandable on its own, separate from other information;
  • be in clear and plain language;
  • give an itemised description of the personal data;
  • state each specific purpose and the goods or services or uses it enables; and
  • give a link to your website or app, and describe other ways the person can withdraw consent (as easily as it was given), use their rights and complain to the Board.

Section 5(3) adds that the notice must be available in English or any language in the Eighth Schedule to the Constitution, which includes Hindi, Tamil, Telugu, Marathi and the other major Indian languages. A notice read only in English does not serve a caller who speaks Tamil.

Section 6(10) puts the burden on you. If a dispute arises, the fiduciary must prove it gave the notice and got consent. A call recording of the consent moment can be that proof, which is one reason many teams keep recordings.

Here is an example opening line for a recorded call. It shows the shape of the wording, not approved legal text.

Hindi: नमस्ते, यह [कंपनी का नाम] की ओर से कॉल है। आपकी सेवा के लिए यह कॉल रिकॉर्ड की जा रही है। रिकॉर्डिंग कैसे इस्तेमाल होती है, और उसे हटवाने या शिकायत करने का तरीका हमारी वेबसाइट पर लिखा है। क्या हम आगे बढ़ें?

Hinglish: Namaste, yeh [company ka naam] ki taraf se call hai. Aapki service ke liye yeh call record ki ja rahi hai. Recording kaise use hoti hai, aur use hatwane ya shikayat karne ka tareeka hamari website par likha hai. Kya hum aage badhein?

The Rules assume a link on a website or app. How a notice should be "presented" on a live call is not spelled out, and we found no official guidance for calls. Ask your lawyer how to pair a short spoken line with a written notice, such as an SMS link.

Consent on one call: a short spoken notice, a link to the full one, then the caller's choice. Withdrawing later must be as easy as saying yes.

Sometimes. Section 7 lists "legitimate uses" where consent is not needed. The most relevant one for call centers covers data a person gave you voluntarily for a stated purpose, where she has not said she does not consent. It does not cover unrelated marketing. When in doubt, ask for consent.

Section 7(a) is the clause call centers lean on. Its own example is a person who messages a real estate broker to find a rented flat, so the broker may use her data to send matching listings. If she later says she no longer needs help, the broker must stop.

Two limits to remember:

  1. A legitimate use is tied to the purpose. A caller who asked about a loan did not agree to be called about insurance.
  2. The DPDP Act does not replace telecom rules. Calling someone who has registered not to be called is still a telecom matter. Read what a DND list is, the TRAI rules for AI calls and our guide to TRAI's new rules for business calls. Call centers that serve clients may also need to follow DoT's OSP guidelines.

How long can you keep call recordings and data?

You must erase personal data when the caller withdraws consent or when it is reasonable to assume the purpose is over, whichever comes first. The exception is a law that requires you to keep it. The Rules also require you to keep certain logs for at least one year. Both can be true at once.

Section 8(7) of the Act sets the erasure duty and the "unless retention is necessary for compliance with any law" exception. Two rules sit alongside it:

  • Rule 6(1)(e) asks for logs and personal data to be kept for one year, to help detect and investigate unauthorised access, unless another law requires longer.
  • Rule 8(3) requires a fiduciary to keep personal data, associated traffic data and other logs of processing for at least one year from the date of processing, for the purposes in the Seventh Schedule, and then erase them unless another law requires longer.

Rule 8(1) and (2) add a three-year countdown for large e-commerce, online gaming and social media platforms (the Third Schedule), with at least 48 hours' notice before erasure. Most call centers are not in these classes.

A worked example. From 1 January 2027, a lender's recovery call recordings must be kept for six months under RBI directions. That is a law requiring retention, so the erasure duty does not force deletion on day one. After six months, with no dispute open, the recording should go. Read the RBI rules for recovery agent calls.

What must a call center do after a data breach?

Report it. The business must tell each affected person without delay, in clear and plain language. It must tell the Data Protection Board without delay too, and send a detailed report within 72 hours of becoming aware, unless the Board allows longer in writing. Failing to report can cost up to Rs 200 crore.

Rule 7 spells out the content. The affected person gets: what happened, its likely consequences for her, what you are doing, what she can do to protect herself and a contact who can answer. The Board's 72-hour report adds the facts and reasons behind the breach, who caused it, the fixes to stop a repeat, and what you told affected people.

A "personal data breach" is wide. Section 2(u) covers unauthorised processing and accidental disclosure, use, alteration, destruction or loss of access. A call center employee emailing a list of customer numbers to the wrong address counts. So does a recording bucket left open.

To prevent that, rule 6 sets the minimum "reasonable security safeguards": encryption, masking or tokens; access controls; logs and monitoring; backups; one-year log retention; and security terms in processor contracts.

  • Breach of: Duty to take reasonable security safeguards (section 8(5))

    Maximum penalty
    Up to Rs 250 crore
  • Breach of: Duty to notify a personal data breach (section 8(6))

    Maximum penalty
    Up to Rs 200 crore
  • Breach of: Extra duties for children's data (section 9)

    Maximum penalty
    Up to Rs 200 crore
  • Breach of: Extra duties of a Significant Data Fiduciary (section 10)

    Maximum penalty
    Up to Rs 150 crore
  • Breach of: Any other provision of the Act or Rules

    Maximum penalty
    Up to Rs 50 crore

These are ceilings, not fixed fines. The Board decides the amount case by case.

What rights do callers have, and how fast must you reply?

Callers can ask to see their data, correct it, erase it and nominate someone to act for them. You must publish how to make these requests and a grievance system that replies within a set period of no more than 90 days. You must also show the contact details of a person who can answer questions.

Rule 14(3) sets the grievance window at a "reasonable period not exceeding ninety days", and the PIB release says requests must be answered within 90 days. Rule 9 requires you to publish the contact details of your Data Protection Officer, or another person who can answer, on your website or app. A caller must use your grievance process before going to the Board (section 13(3)).

For a call center, this means a front desk for privacy requests. Who receives "delete my recording", checks who is asking, finds the audio and confirms deletion? Decide before the first request arrives.

Children. If a caller is a child, rule 10 requires verifiable consent from a parent, with limited exemptions such as healthcare, education and real-time safety. This matters to teams that call about school admissions.

What should a call center do now? A checklist

You have until May 2027 on current dates. Use the time like this:

  1. Map your calls. List every call type, the data it captures, where it is stored and who can open it.
  2. Name your role for each client or process: fiduciary or processor.
  3. Write the notice in each language you serve: plain, itemised and specific to the purpose. Add a withdrawal path as easy as saying yes.
  4. Set retention per call type, with the legal reason and the delete date.
  5. Lock down access using the rule 6 list, and update vendor contracts with security, breach and deletion terms.
  6. Write a breach plan that names who tells the Board and the callers, and rehearse the 72-hour clock.
  7. Publish a named contact and a grievance route on your website, and train agents on a one-page rule sheet.

How Bananaflow fits

Consent, notices and DPDP compliance stay with your business. You write what the agent says, so the opening notice is yours to word and test. Call recordings on Bananaflow are stored in India (AWS S3, Mumbai region), and call data is not used to train models, ours or our providers'. That covers recordings, not every system your business runs.

For the call-quality side, see call QA and analytics.

This article is general information, not legal advice. For your own case, speak to a lawyer, and check the official text from the Ministry of Electronics and IT and the Press Information Bureau release on the DPDP Rules. Facts are as of 11 November 2026.

FAQ

Frequently asked questions

  • Is the DPDP Act in force in India today?

    In part. The Act and the Rules came into force in three steps from 13 November 2025. The Data Protection Board and the definitions are in place. The main duties on notice, consent, security, breach reporting and erasure start in May 2027, 18 months after the Rules were published in the Gazette.

  • Are call recordings personal data under the DPDP Act?

    Yes, if the caller can be identified from the recording or from the data around it, such as a name, number or account. The Act's definition of processing lists recording and storage by name. So a business that records calls must have a lawful ground, a notice and a retention plan.

  • Who is responsible if our outsourced call center has a breach?

    You are, if you are the data fiduciary. Section 8(1) of the Act makes the fiduciary responsible for processing done on its behalf by a processor, whatever the contract says. That is why you need a valid contract with security, breach reporting and deletion terms, and a way to check that the call center follows them.

  • How fast must a data breach be reported under the DPDP Rules?

    Tell each affected person without delay, and tell the Data Protection Board without delay too. Then send the Board a detailed report within 72 hours of becoming aware, or a longer period if the Board allows it in writing. Rule 7 lists what each message must contain.

  • What is the maximum penalty under the DPDP Act?

    Up to Rs 250 crore, for failing to take reasonable security safeguards to prevent a personal data breach. Failing to report a breach can cost up to Rs 200 crore. Breaking any other provision can cost up to Rs 50 crore. These are ceilings, and the Board decides the amount in each case.

Written by

  • Jaseem Abbas, founder of Bananaflow, in glasses and a dark top against a pale background.

    Jaseem Abbas

    Founder, Bananaflow

    Jaseem founded Bananaflow to build voice AI that understands how people in India really speak, including the switch between languages in the middle of a call.

Similar articles

Bring us one process. We'll pilot it on your real calls, with your team as the fallback.

Plan a pilot