Skip to content
Full DPDP obligations apply from 13 May 2027. Check your readiness →

01 · At a glance

Two roles, one deadline

Most DPDP material is written for banks and retailers. A SaaS company's problem is different: you are a Data Fiduciary for some data and a Data Processor for a great deal more — and your enterprise customers will hold you to their obligations long before the Data Protection Board does.

176

days to 13 May 2027

substantive obligations apply

13 Nov

2026

Consent Manager rules (Rule 4)

₹250 Cr

maximum per breach

security safeguards

72 h

Board's detailed report

after you become aware

What's different for SaaS

Your customers are Data Fiduciaries for the data in your product. Their DPDP duties — notices, deletion, breach reporting — only work if your product and contracts support them.

Where the money is

Security safeguards (up to ₹250 crore) and breach notification (up to ₹200 crore) are the two biggest penalty tiers — and both depend on engineering, not policy.

The commercial trigger

Enterprise procurement is already adding DPDP clauses to DPAs and security questionnaires. Being ready is a sales advantage before it is a legal one.

Bottom line: treat DPDP as two programmes. As a fiduciary, fix your own notices, consent, retention and rights for marketing, users and staff. As a processor, make your product, breach process and DPA something your customers can rely on — then use that readiness to win deals.

02 · Know your role

Fiduciary or processor — data by data

Under the Act, whoever decides the purpose and means of processing is the Data Fiduciary. The test is applied per activity, not per company. Most SaaS businesses are both.

DataYour roleWhat it means in practice
Website visitors, leads, newsletterFiduciaryYour notice, your consent for marketing, your retention rules, your rights process.
Your employees and candidatesFiduciaryEmployment is a legitimate use for much of this — but you still owe security, retention and rights.
Customer account admins and billing contactsFiduciaryYou decide why you hold these. Cover them in your own notice.
End-user data inside customer workspacesProcessorProcess only on the customer's instructions, under a contract. Help them meet their duties.
Support tickets with customer dataProcessorSame as workspace data — limit access and retention, delete on instruction.
Product telemetry and analyticsUsually fiduciaryIf you decide to collect it for your own product purposes, it's yours to notice and justify.
Customer data used to train or improve modelsFiduciary for that useUsing processor data for your own purposes makes you its fiduciary — you need a lawful basis and notice.

Watch the line

The fastest way to inherit a customer's obligations is to reuse their data for your own purposes — product analytics on workspace content, benchmarking, or model training. Decide this deliberately, write it into your DPA, and say it in your notice.