NEWDPIIT startups: ₹5,000 free API creditsApply →Apply now →
Compliance · DPDP

The DPDP Act for KYC Teams: What Changes for Identity Verification

The DPDP Act does not stop KYC or override RBI record-keeping. It changes consent, retention, breach reporting and vendor contracts. A checklist for product teams.

ID

By idto.ai

Published · November 2026 · 10 min read

← Back to blog list

India's Digital Personal Data Protection (DPDP) Act doesn't stop you doing KYC, and it doesn't override the RBI's record-keeping rules. What it changes is how you do it: clear consent notices, collecting only what each check needs, defined retention periods, fast breach reporting, and proper contracts with every verification vendor you use.

This post is a practical guide for product and compliance teams. It isn't legal advice. Speak to your legal counsel about how the DPDP Act and Rules apply to your business.

KYC teams handle some of the most sensitive data any business collects: PAN, Aadhaar, selfies, video recordings, bank details. From 2027, every KYC journey has to answer two questions, not one: does this meet the RBI's rules, and does it meet the DPDP Act?

The DPDP Act in 60 seconds

The DPDP Act was passed in August 2023. The government notified the Digital Personal Data Protection Rules, 2025 in November 2025, and they come into force in phases. Here's who's who:

  • Data principal: the person the data is about. In KYC, that's your customer.
  • Data fiduciary: the business that decides why and how the data is processed. If you're a bank, NBFC or fintech running KYC, that's you.
  • Data processor: anyone processing data on your behalf. KYC APIs, Video KYC platforms, OCR and face-match providers, orchestration layers and cloud hosts all count.
  • Significant data fiduciary: a fiduciary the government designates because of the volume or sensitivity of the data it handles. They have extra duties, such as an India-based data protection officer and regular audits.
  • Data Protection Board of India: the body that enforces the Act. Penalties run up to ₹250 crore for failing to take reasonable security safeguards, and up to ₹200 crore for failing to report a breach.

The timeline matters, because the obligations KYC teams care about most aren't live yet.

Phase
When
What comes into force
Phase 1
On notification (November 2025)
Setting up the Data Protection Board and the Rules' administrative provisions
Phase 2
12 months after notification
Registration and duties of consent managers
Phase 3
18 months after notification (around May 2027)
Core obligations: notices, consent, security safeguards, breach reporting, retention and data principal rights

As of November 2026, that leaves roughly six months before the core rules apply. That's enough time to fix a KYC journey, but not enough to wait and see.

What changes for KYC under the DPDP Act

1. Consent notices

Under the Act, consent has to be free, specific, informed, unconditional and unambiguous, given through a clear affirmative action. The Rules add detail on the notice itself. It must stand on its own, be written in clear and plain language, and set out:

  • an itemized list of the personal data you are collecting;
  • the specific purpose for each item, and what service it enables;
  • how the customer can withdraw consent, which must be as easy as giving it;
  • how they can exercise their rights and complain to the Data Protection Board.

That rules out consent buried in the terms, pre-ticked boxes, and one blanket "I agree" covering everything from KYC to marketing. A DPDP-ready KYC screen says, in a sentence or two, what you're checking and why: for example, that you'll verify their PAN and take a selfie to confirm their identity as RBI rules require.

Two points to settle with your legal team: whether consent or one of the Act's narrower "legitimate uses" is your legal basis, and how you handle withdrawal. A customer can withdraw consent, but you may still have to keep their KYC records under RBI and anti-money laundering rules, so say so in the notice.

2. Collecting only the data you need

The Act limits consent to the personal data that's necessary for the stated purpose. In KYC, it's easy to collect more than you need without noticing. Common examples include:

  • Storing full Aadhaar numbers when a masked number would do. Aadhaar also has its own storage rules under UIDAI regulations, which still apply.
  • Pulling bank statements at onboarding when you only need to validate the account.
  • Saving complete raw responses from verification APIs, with far more fields than you'll ever use.
  • Keeping every liveness frame and selfie long after the face match is done.

List every field your KYC flow collects or stores, with its purpose next to it. Anything without a clear purpose should go, be masked, or be stored as a result ("PAN verified, name matched") rather than raw data.

3. How long to keep KYC data

This is where DPDP and RBI rules seem to pull in opposite directions. The DPDP Act says you should erase personal data once its purpose is served or consent is withdrawn, unless the law requires you to keep it. Under the Prevention of Money Laundering Act (PMLA) rules and the RBI's KYC Master Direction, regulated entities generally have to keep customer identification records for at least five years after the business relationship ends.

In practice, the conflict is smaller than it looks. The legal retention requirement wins, but only for the data the law actually requires, and only for as long as it requires. After that, the data should go. The Rules also expect you to keep processing logs for at least a year, which matters for audit trails.

Here's how that plays out across typical KYC data:

KYC data
What drives retention
What product teams should do
Identity records of onboarded customers
RBI and PMLA record-keeping (generally five years after the relationship ends)
Set a deletion trigger linked to account closure, not onboarding
Video KYC recordings
RBI V-CIP rules treat them as part of the KYC record
Tag each recording to the customer record so it follows the same schedule
Selfies and liveness frames beyond the KYC record
DPDP data minimisation
Keep only what forms part of the KYC record and delete the rest after the check
Rejected or abandoned applications
No ongoing relationship; agree a basis with legal
Define a short, documented retention window instead of keeping them indefinitely
Raw verification API responses
Debugging and dispute handling
Store only the fields you need, for a short, defined period
Access and processing logs
DPDP Rules (minimum one year)
Keep logs of who accessed KYC data and when, for at least a year

4. Breach reporting

If personal data is breached, the Rules require you to inform each affected customer without delay, in plain language: what happened, when, the likely consequences, what you're doing about it, and what they can do to protect themselves. You also have to inform the Data Protection Board without delay, followed by a detailed report within 72 hours of becoming aware of the breach.

This sits alongside, not instead of, your existing duties. Cyber incidents still have to be reported to CERT-In within six hours, and regulated entities have their own RBI reporting obligations.

Have a runbook ready that covers all three reporting routes, and make sure your vendors are contractually required to tell you about a breach quickly. As the data fiduciary, the reporting clock is yours.

5. Contracts with verification vendors

Under the DPDP Act, you remain responsible for personal data even when a vendor processes it on your behalf, and you can only engage a processor under a valid contract. Most KYC stacks involve several processors, so every one of them needs a contract that covers:

  • processing only for your specified purpose and on your instructions;
  • reasonable security safeguards, such as encryption, access controls and logging;
  • breach notification to you within a tight, defined window;
  • which sub-processors they use, and your right to know about changes;
  • deletion or return of data when the contract ends;
  • your right to audit, and where data is stored and processed.

If you use several KYC providers, how data flows between them matters too. An orchestration layer that sends each check only to the provider handling it, rather than copying data to every vendor, keeps your exposure smaller. We explain how that routing works in our guide to KYC orchestration.

DPDP checklist for KYC product teams

Use this to review your KYC journey before the core rules apply:

  • Map every personal data field your KYC flow collects and stores, with a purpose next to each.
  • Remove or mask any field without a clear purpose.
  • Rewrite consent screens as standalone, plain-language notices with an itemised list of data and purposes.
  • Separate KYC consent from marketing and other consents.
  • Make withdrawing consent as easy as giving it, and explain what you'll still keep under RBI rules.
  • Set a retention schedule for each data type, with automatic deletion triggers.
  • Log every access to KYC data and keep those logs for at least a year.
  • Write a breach runbook that covers customers, the Data Protection Board, CERT-In and the RBI.
  • Update every vendor contract to cover the points in the section above.

What to ask your KYC vendors

Your vendors' practices become your compliance risk. Before the core rules apply, ask each of them:

  • What personal data do you receive from us, and what do you store? For how long?
  • Do you use our customers' data for anything other than our checks, such as training models?
  • Which sub-processors and upstream sources do you use, and where is the data processed?
  • How quickly will you notify us of a breach, and what will the notification include?
  • Can you delete our customers' data on request and confirm it in writing?
  • Can you give us logs of every check run on our behalf?

If a vendor can't answer these clearly, that's a useful signal in itself.

How idto approaches DPDP

idto is built to be DPDP-ready. As a verification layer, idto works as a data processor on your behalf, running the checks you ask for and nothing more. Each check goes only to the provider handling it, and results come back in one standard format, so you can store a clear verification outcome instead of piles of raw data.

We're also building two features designed around the Act:

  • Consent capture (coming soon): a record of the notice each customer saw and when they agreed, attached to their verification.
  • Audit trails (coming soon): a complete log of every check, which provider handled it, and who accessed the results.

You can find out more about idto's identity verification on our website.

Frequently asked questions about the DPDP Act and KYC

Does the DPDP Act replace the RBI's KYC rules?

No. The DPDP Act sits alongside RBI rules, PMLA and the Aadhaar Act. You still have to do KYC exactly as the RBI requires. The DPDP Act changes how you collect, use, store and share the personal data involved.

Can a customer ask us to delete their KYC data?

Yes, customers can ask for their data to be erased, and you have to do so unless the law requires you to keep it. For onboarded customers, RBI and PMLA record-keeping rules usually mean you keep their identification records for the required period, then delete them.

Do we need fresh consent from existing customers?

The Act requires you to give a notice to customers whose data you processed on the basis of consent given before it came into force, as soon as reasonably practicable. Plan how you'll reach existing customers well before the core obligations apply.

Is our KYC vendor responsible for DPDP compliance?

Mostly, the responsibility stays with you as the data fiduciary. Vendors, as processors, must follow your instructions and keep data secure under your contract, which is why those contracts matter so much.

When do the DPDP Rules come into force?

In phases. The Rules were notified in November 2025, and most obligations that matter for KYC apply after 18 months, around May 2027.

Does the DPDP Act apply to Video KYC recordings?

Yes. A Video KYC recording contains personal data, so the Act's rules on security, access and retention apply, alongside the RBI's V-CIP requirements. We cover how Video KYC works in our post on Video KYC vs. Video PD.

Getting your KYC journey DPDP-ready

The DPDP Act doesn't ask KYC teams to verify less. It asks them to be clearer with customers, keep less data for less time, and hold vendors to the same standard. Most of the work is in consent screens, retention schedules and contracts, all much easier to fix before May 2027 than after.

This post is for general information only and isn't legal advice. Laws and rules change, so check the current position with your legal counsel.

About the author

Sushmita, marketing manager at idto.ai works on identity verification and compliance with lenders and fintechs. She has extensive experience working with new age fintechs in guiding them to DPDP compliant identity verification journeys.

Get your KYC journey DPDP-ready

See how idto runs each check through one provider and returns a standard result, so you store outcomes, not piles of raw data.