Third-Party Risk Management Under DPDP
Learn how to review vendors, processors and contracts because DPDP responsibility does not stop at outsourcing.
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 Third-Party Risk Management Under DPDP, 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 Sub-Processor Transparency
Under DPDP, your responsibility extends to every downstream entity your vendor uses. Most Indian IT service contracts fail to list specific sub-processors or provide a mechanism for you to object to new ones. You must ensure your vendors provide a live list of every data center and third-party tool where they store your users’ personal identifiers.
The Conflict of Audit Rights
A major gap exists between vendor trade secret protection and your legal duty to verify compliance. While vendors often limit “right to audit” clauses to once a year, DPDP requires you to ensure “appropriate” security at all times. If a vendor refuses to share their internal DPDP assessment or SOC2 report, you cannot legally prove you have taken reasonable steps to protect the data they handle.
Vendor Workflow Data Risks
| Workflow | Personal Data Involved | DPDP Risk |
|---|---|---|
| Cloud Hosting | User database, IP logs, metadata | Processing in non-notified geographic regions |
| Payroll Outsourcing | PAN, Aadhaar, bank account details | Retention of data after the service contract ends |
| Customer Support | Voice recordings, chat transcripts | Lack of specific consent for third-party processing |
| Marketing Analytics | Email addresses, browsing behavior | Unauthorized data scraping or profiling by the vendor |
| Software Testing | Real user data in “sandbox” environments | Use of personal data for purposes not in the initial notice |
This week
Select your highest-volume data vendor and check if your contract includes a “Notice of Change” clause. Ensure it requires them to notify you 30 days before they add a new sub-processor so you can verify that new entity’s DPDP readiness.
Now think about your work. Where does personal data enter your workflows? Where does it sit? Who else touches it?
Frequently asked questions
Does a standard indemnity clause protect us from DPDP violations by a vendor?
No, the Data Fiduciary remains the primary point of accountability to the Data Protection Board. While an indemnity clause helps you recover money later, it does not stop the Board from holding your company responsible for the vendor's security failure.
Are we required to audit every small vendor we use?
You must implement "reasonable" measures based on the volume of data. For high-risk vendors handling sensitive financial or identity data, you need documented proof of their compliance, such as an independent audit or a self-assessment mapped to DPDP sections.
What happens if a vendor refuses to delete data after our contract ends?
This creates a direct violation of the "Storage Limitation" principle. Your contracts must specify that the vendor must provide a "Certificate of Destruction" within a set timeframe to prove the data is no longer in their systems or backups.