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

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

Anyone under 18 is a child (s.2(f)). Their data needs a parent’s verifiable consent, and you may not track, behaviourally monitor or target ads at them (s.9).

Every SDK is a disclosure

An analytics or ad SDK that sends user data to its maker is sharing personal data. Your notice has to cover it, and many need consent.

Real-money gaming has changed

The Promotion and Regulation of Online Gaming Act, 2025 prohibits online money games. Former operators still hold KYC, wallet and payout data that must be secured, kept only as long as law requires, then deleted. Confirm the details with counsel.

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.

PartyUsual roleWhy
App or game publisherFiduciaryDecides what to collect, for which features, and how long to keep it.
Analytics and crash-reporting SDKsProcessor — if configured that wayActs for you only if its terms bar its own use. Many reuse data for their own products.
Ad networks and attribution SDKsIndependent fiduciariesUse data for their own advertising purposes as well as yours.
Cloud, game-server and messaging vendorsProcessorHost and deliver on your instructions (s.8(2)).
Moderation and KYC vendorsProcessorReview content or verify identity for you.
Payment partners and app storesIndependentProcess payments under their own terms and regulation.
Users sharing their own contentOutside the Act for personal useIndividuals 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

Whether an SDK is your processor depends on its contract: does it use the data only for you, or also for itself? If the latter, treat it as sharing with another fiduciary — disclose it and get consent where needed.