DPDP Data Processor Governance Guide
Manage third-party data processors and subprocessors under DPDP. Learn to handle DPAs, audits, and liability in vendor management workflows.
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 Processor Governance Guide, 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 callNow think about your work. Where does personal data enter your workflows? Where does it sit? Who else touches it?
Frequently asked questions
Is the Data Fiduciary liable for a processor's data breach?
The Data Fiduciary is legally responsible for any breach that happens at the processor level. While you can sue the processor for damages based on your contract, the Data Protection Board holds your organization accountable for the initial failure.
Can a processor refuse to delete data if the Fiduciary asks?
The DPDP Act mandates that processors must delete personal data once the specific purpose is finished. Your contract must explicitly state that the processor must erase or return data upon your request without delay.
How do we track subprocessors located outside of India?
You must maintain a list of all locations where your data is stored by third parties. Your contract should require the primary processor to disclose the physical location of all subprocessor data centers to ensure they comply with Indian cross-border transfer rules.