DPDP Data Breach Notification Compliance
How to handle a data breach under India's DPDP Act 2023 — notification timelines, who to inform, and. Talk to our experts.
Discuss this page with an LLM
DPDP Action Sheet
Use this before your next workflow goes live. It keeps the useful parts visible and turns DPDP into checks your team can actually answer.
For DPDP Data Breach Notification Compliance, the DPDP question is how personal data enters the workflow, where it is stored, which tools touch it, what purpose was explained, and how deletion or withdrawal will work.
1. Lead Forms
Check:
- What data are you collecting?
- Is the purpose clear at the point of collection?
- Is marketing consent separate from service communication?
- Can the user withdraw consent later?
Common mistake: one checkbox that silently covers newsletters, sales calls, partner sharing and remarketing.
2. Email and WhatsApp
Check:
- Who is on the list?
- Where did consent come from?
- Is the list imported from a vendor, event, webinar, scrape or old CRM?
- Can you prove the source of consent?
Common mistake: treating every lead as permanently marketable.
3. Ads and Retargeting
Check:
- Are pixels or ad platforms receiving identifiable user behavior?
- Are audiences built from customer lists?
- Are lookalike or remarketing audiences using personal data?
Common mistake: assuming "the ad platform handles it" means your company has no DPDP responsibility.
4. Website Analytics
Check:
- Which tools run on the site?
- Are IP address, device identifiers, session IDs or form fields being captured?
- Is analytics used only for measurement, or also for profiling and targeting?
Common mistake: installing tools first and asking privacy questions later.
5. Vendor List
Make a quick list:
- CRM
- Email platform
- WhatsApp provider
- Analytics
- Ad pixels
- Form tool
- Landing page builder
- Webinar tool
For each vendor, answer: what data goes there, why, who can access it and how deletion works.
6. This Week's Action
Map one campaign from first click to final follow-up. Mark every place personal data is collected, enriched, shared, uploaded or used for targeting.
If your team cannot answer where the data came from and where it goes next, start with a data flow map before rewriting policy copy.
Book a DPDP clarity callWant all of this handled, end to end? Sanctum is the all-in-one DPDP compliance programme behind this site: legal position, data map, gap analysis, implementation, tooling, training, readiness opinion, and breach cover under one accountable owner. How all-in-one DPDP compliance works or see the Sanctum programme.
Managing Forensic Investigation Data
During a breach investigation, your server logs and forensic images capture IP addresses, device IDs, and user activity patterns linked to Indian residents. DPDP classifies these investigation artifacts as personal data. You must ensure that the third-party security firms you hire to analyze these logs are bound by data processor contracts that limit their use of this data strictly to incident response.
The Forensic vs. Reporting Timeline
You face a conflict between technical accuracy and the “immediate” reporting mandate. Waiting for a final root-cause analysis from a cybersecurity vendor often takes weeks, which violates the DPDP requirement to notify the Board and users promptly. You must establish a “staged notification” workflow where you report the initial discovery to the Board while the forensic investigation is still active.
| Workflow | Personal Data Involved | DPDP Risk |
|---|---|---|
| Incident Logging | IP addresses, MAC IDs, Usernames | Retaining forensic logs longer than the “specified purpose” of security |
| Impact Assessment | KYC details, Transaction history | Exposing sensitive data to unauthorized internal “war room” members |
| User Notification | Email addresses, Mobile numbers | Using unverified contact lists that result in “misdirected” breach notices |
| Forensic Imaging | Production database snapshots | Storing unencrypted PII on external consultant hardware |
This week
Review your incident response plan to identify the specific individual authorized to sign off on a Board notification. Ensure this person has a secure, out-of-band communication channel to reach your legal team if your primary email or Slack workspace is compromised.
Now think about your work. Where does personal data enter your workflows? Where does it sit? Who else touches it?
Frequently asked questions
Do I need to notify the Board if the leaked data was encrypted?
Yes, DPDP requires notification for any personal data breach regardless of technical safeguards. The Board will consider the encryption strength when determining if the breach likely caused harm to individuals.
Can I use my CERT-In incident report for DPDP compliance?
No, because CERT-In focuses on the technical nature of the cyberattack. A DPDP notification must specifically list the categories of personal data affected and the steps you are taking to protect the impacted individuals.
Who should I notify first: the Board or the affected users?
You must notify both the Board and the affected individuals. In practice, notifying the Board first creates an official record of your compliance before a public announcement or user-facing notification goes live.