01 · At a glance
Scale, minors and SDKs
Consumer apps meet the DPDP Act at its sharpest points: children who sign up without asking, behavioural data that powers growth and ads, and third-party SDKs that send data to companies you've never contracted with directly.
176
days to 13 May 2027
substantive obligations apply
₹200 Cr
children's duties
maximum penalty
3 years
inactive accounts
large platforms only
₹250 Cr
maximum per breach
security safeguards
Assume children are there
Every SDK is a disclosure
Real-money gaming has changed
Bottom line: know who your users are, audit every SDK, separate what the app needs to work from what growth and ads want, and make deletion real — especially if you cross the Rule 8 user thresholds.
02 · Know your role
Who is the fiduciary in an app?
The app publisher is the Data Fiduciary for its users. The harder questions are about the dozens of services built into the app.
| Party | Usual role | Why |
|---|---|---|
| App or game publisher | Fiduciary | Decides what to collect, for which features, and how long to keep it. |
| Analytics and crash-reporting SDKs | Processor — if configured that way | Acts for you only if its terms bar its own use. Many reuse data for their own products. |
| Ad networks and attribution SDKs | Independent fiduciaries | Use data for their own advertising purposes as well as yours. |
| Cloud, game-server and messaging vendors | Processor | Host and deliver on your instructions (s.8(2)). |
| Moderation and KYC vendors | Processor | Review content or verify identity for you. |
| Payment partners and app stores | Independent | Process payments under their own terms and regulation. |
| Users sharing their own content | Outside the Act for personal use | Individuals acting for personal or domestic purposes aren't fiduciaries (s.3(c)(i)). The platform still is. |
Read the SDK's terms, not its marketing