DPDP Subprocessor Register Guide
Maintain a subprocessor register for DPDP compliance. Track cloud tools, vendor data flows, and processing agreements for Indian privacy. Get expert help.
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 Subprocessor Register 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 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.
Mapping the Subprocessor Chain
Under DPDP, the Data Fiduciary is responsible for the entire life cycle of personal data. This includes data handled by third-party vendors, known as subprocessors. These are often cloud hosting providers, customer support tools, or email delivery services. If a vendor you hire uses another company to store your data, that second company is a subprocessor. You must maintain a clear record of these entities to ensure that the consent provided by the user covers every link in the chain.
Subprocessor Data Risks
| Service Category | Data Involved | DPDP Risk Level |
|---|---|---|
| Cloud Infrastructure | Encrypted databases, user backups | High |
| Marketing Automation | Email addresses, names, tracking cookies | Medium |
| Customer Support | Chat transcripts, identity documents | High |
| Error Logging | IP addresses, user session metadata | Medium |
| Payment Gateways | Billing addresses, transaction metadata | High |
Managing Contractual Flow-Downs
The most common compliance gap is the lack of “back-to-back” agreements. When you engage a Data Processor, your contract must specify that they cannot hire a subprocessor without your authorization. Furthermore, the subprocessor must be bound by the same data protection obligations that you have established with your primary vendor. If a subprocessor experiences a breach, the Data Fiduciary is still the party held accountable under Indian law.
This Week
Identify every SaaS tool your company pays for by reviewing your monthly billing statements. List every tool that handles customer or employee personal data. Create a master table that identifies the legal name of the vendor, the location of their data centers, and the specific purpose for which they process your data.
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 list subprocessors if I use a major cloud provider like AWS?
Yes. Even if you use a major provider, they act as a processor. Any third party they hire to handle your specific data workloads is a subprocessor that must be recorded in your internal register.
How often must the subprocessor register be updated?
Update the register every time you onboard a new SaaS tool or when an existing vendor sends a notice about changes to their own infrastructure partners. Annual reviews are a minimum requirement for data hygiene.
Is linking to a vendor's privacy policy enough for compliance?
No. DPDP requires you to know exactly who is processing the data. You must maintain an internal list of specific entities, their primary processing locations, and the specific data categories they handle.