6 min read

You Cannot Protect Data You Have Not Found

The Wire's 19 October 2026 PTI release quotes ComplyDP's Vipul Abhishek on why BFSI programmes have to start with discovery, keep personal data in place, and meet DPDP, CERT-In, RBI and SEBI clocks together.

Written byVipul Abhishek· Former Advocate, Supreme Court of India

19 October 2026 · The Wire · PTI release

The Wire published a PTI release in which Vipul Abhishek, co-founder and CTO of ComplyDP, explains why banks, NBFCs, insurers and capital-market firms need a DPDP programme that starts with discovery. Most DPDP obligations apply from 13 May 2027. For financial groups the Act sits beside RBI directions, SEBI norms, CERT-In reporting and CERSAI filings.

Built from the DPDP Act, not a GDPR settings page

Abhishek says most tools were designed for Europe's GDPR and then adapted for India. ComplyDP was built the other way round. In ComplyDP's scan of 1,680 company websites, 82.4% of financial-services sites had no consent banner detected.

"Indian financial groups do not need a GDPR tool with an India settings page," Abhishek said. "They need software that starts from the DPDP Act and understands the RBI, SEBI and CERT-In obligations that sit around it."

Findings that trace back to a provision

Neurosymbolic compliance turns the Act and the Rules into rules a machine can check, and uses language models only where the text needs interpretation. "A regulator will not accept a confidence score," Abhishek said. "When we say a process is non compliant, we can show the exact provision, the exact rule and the exact evidence."

Personal data stays in the institution

Connectors scan databases, applications and file stores inside the client's environment and send back metadata and findings only. Customer records are not copied to ComplyDP. "It makes no sense to fix a privacy problem by creating a new copy of everyone's data," Abhishek said. "Our connectors go to the data. The data never comes to us."

You cannot protect data you have not found

"You cannot protect data you have not found," he said. "A bank's personal data does not live only in its core system. It sits in loan origination tools, call centre recordings, KYC folders, marketing platforms and vendor systems." The map also includes KYC records sent to the Central KYC Registry and security-interest filings with CERSAI.

From that map ComplyDP builds a record of processing: what is collected, for which purpose, on what basis, where it is stored, who receives it and how long it is kept. The Act does not use the term ROPA. The record is what makes notices, consent, rights requests, retention and erasure provable.

One group, several fiduciaries

A group may run a bank or NBFC, an insurer, a broker and a technology subsidiary, each a separate data fiduciary. The suite maps what each entity holds, what it received from a sister company, and what it is answerable for.

One breach, several clocks

A breach can require notice to the Data Protection Board and affected people, with a detailed Board report within 72 hours, a CERT-In report within six hours, and the incident reports RBI or SEBI already require. The workflow uses the data map to name the affected data and people and to track each deadline. Penalties under the Act go up to Rs 250 crore per breach.

"For BFSI, May 2027 is closer than it looks," Abhishek said. "Discovery and mapping across a multi entity group takes months." ComplyDP is ISO 27001 certified and is operated by Nihonium Labs Private Limited. It is supported by NVIDIA Inception, Google Cloud for Startups, T-Hub and DST, and is a member of DSCI.

Expanded implementation notes for compliance leads

This article focuses on regulatory timing and market readiness under India's Digital Personal Data Protection Act, 2023 and the 2025 Rules. Use it alongside your RoPA, notice library, and breach playbook when preparing for Data Protection Board scrutiny.

Distinct questions your board should ask this quarter

Does You Cannot Protect Data You Have Not Found change how we document consent, respond to grievances within prescribed timelines, or prove erasure? If not yet, schedule a cross-functional review with legal, security, and product owners.

Keep this page fresh after each release

Revisit the guidance whenever you add a new data collection field, SDK, processor, or India-facing marketing channel so crawlers and customers always see current practice—not stale 2024 assumptions.

Sources