SaaS companies wear two hats under DPDP.
You're likely a Data Fiduciary for your own users AND a Data Processor for your customers' data. Both sets of obligations apply — to different data.
Fiduciary, Processor, or both? Take the check →
Split your data map in two. Law, from 13 May 2027: for data you decide the purpose of, such as signups and billing, you are a Data Fiduciary. Notice, consent, rights, complaints and breach duties apply. Law: for data your customers put into your product, you act for them as a Processor under a contract (Section 8(2)).
What matters most for you
Common situations
A customer asks for a DPA
Your product uses AWS but the customer didn't consent to AWS
Your AI feature processes customer data
Multi-tenant data architecture
Start here
DPDP Applicability & Action Check
Eight questions to confirm which hat you're wearing for which data — and get the checklist that follows from it.
OpenDeep dives
DPDP Rules, 2025
What the Rules actually require, rule by rule.
ReadCross-border transfers
Where your customer data may legally sit.
ReadFiduciary vs Processor
How the Act splits responsibility between you and your customer.
ReadIndia's AI governance stance
What applies to AI features inside a SaaS product.
ReadRun the readiness checklist
Consent notices, rights requests, retention, breach response, and vendor contracts in one trackable list.
Run it nowWritten by Sandesh Kokate, reviewed against primary sources.Connect on LinkedIn →