India's Digital Personal Data Protection (DPDP) Act changes what your mobile app is legally required to do with user data. This is a practical, founder-level guide — not legal advice — to what compliance actually requires before you launch.
DPDP Act compliance for mobile apps in India means getting clear, purpose-specific consent, telling users exactly why you collect data, and letting them withdraw consent and request deletion. The Digital Personal Data Protection Rules, 2025 were notified on 14 November 2025, and most obligations apply after an 18-month transition, around May 2027.
Key takeaways
- The DPDP Act, 2023 applies to any app that processes personal data of people in India, wherever the company is registered.
- Penalties reach ₹250 crore for failing to keep reasonable security safeguards, and ₹200 crore for not reporting a breach or breaching children's data duties.
- Bundled "accept all" consent and pre-ticked boxes are the most common gaps in Indian apps we review.
- Users can ask to access, correct or erase their data, and you must respond within 90 days.
- Building consent and deletion flows in from the start typically adds ₹15,000–₹40,000 to an app build; retrofitting costs more.
This guide explains what the law asks of app founders in plain language, in the order you need it: before you brief a development agency, not after a complaint. It is general information, not legal advice. Apps that handle health, financial or children's data should be reviewed by a qualified data protection lawyer before launch.
What Is the DPDP Act, 2023?
The Digital Personal Data Protection Act, 2023 is India's main law on how organisations collect, use, store and delete digital personal data. Parliament enacted it on 11 August 2023, and the DPDP Rules, 2025 that put it into practice were notified on 14 November 2025, according to the Press Information Bureau's backgrounder on the Rules.
The law rests on seven principles: consent and transparency, purpose limitation, data minimisation, accuracy, storage limitation, security safeguards and accountability. It is enforced by the Data Protection Board of India, a digital-first body that hears complaints online. Appeals against the Board go to the Telecom Disputes Settlement and Appellate Tribunal (TDSAT). The Ministry of Electronics and Information Technology publishes the Act, Rules and updates on its data protection framework page.
| Term in the Act | What it means for an app |
|---|---|
| Data Fiduciary | You, the app owner who decides why and how data is processed |
| Data Principal | Your user; for a child, this includes the parent or guardian |
| Data Processor | Vendors who process data for you, such as hosting or analytics providers |
| Consent Manager | A registered India-based platform that lets users give, review and withdraw consent |
| Significant Data Fiduciary | A large or high-risk fiduciary notified by government, with extra duties |
When do the DPDP Rules take effect?
The DPDP Rules, 2025 apply in phases: provisions on the Data Protection Board took effect on notification, Consent Manager registration follows after one year, and most obligations on apps apply after 18 months. For a Rules notification on 14 November 2025, that 18-month mark falls in May 2027.
That window is shorter than it sounds for an app. A consent redesign touches onboarding, settings, the backend and the privacy policy, and each new release has to clear Apple and Google review. Teams that start in 2027 will be shipping compliance features under deadline pressure, which is when mistakes happen. A practical plan is to finish your data map and consent redesign in the next two releases, test them with real users, and leave the final months for fixing what testing reveals rather than for building from scratch.
Does the DPDP Act Apply to My App?
Yes, if your app collects any personal data from people in India. A phone number for OTP login, a name on a profile, a delivery location or payment details are all personal data, so almost every consumer and business app is covered. The Act also applies to companies outside India that offer goods or services to people in India.
- Covered: apps with accounts, bookings, deliveries, payments, chat, analytics tied to users or push notifications linked to a profile.
- Mostly outside scope: data that is fully anonymised so no person can be identified from it.
- Extra duties: a Significant Data Fiduciary must carry out independent audits and data protection impact assessments, and may face restrictions on certain data categories.
What Must a Mobile App Do to Comply?
A compliant app gives a clear notice, takes specific consent, keeps data secure, reports breaches, honours user rights and deletes data it no longer needs. These are the obligations that translate directly into features your developers must build.
- Notice: a separate, plain-language consent notice explaining what data you collect and the specific purpose for each item.
- Consent: free, specific, informed and unambiguous agreement, with withdrawal as easy as giving consent.
- Security safeguards: encryption, access controls and monitoring that are reasonable for the data you hold.
- Breach notification: inform affected users without delay, in plain language, explaining what happened, the likely impact, the steps taken and who to contact, and inform the Data Protection Board.
- User rights: let users access, correct, update and erase their data, and nominate someone to act for them, responding within 90 days.
- Contact point: publish the contact of a designated officer or Data Protection Officer for data queries.
What Does Valid Consent Look Like in an App?
Valid consent is a clear action the user takes for a stated purpose, never a pre-ticked box or a single toggle covering everything. One "I agree to the terms" button that bundles account creation, marketing messages and data sharing with partners is a compliance risk, because the user cannot agree to one purpose without the others.
The Bundled Consent Trap
The Bundled Consent Trap is our name for the most common DPDP gap we see in Indian apps: one onboarding screen that collects agreement to everything at once. It feels efficient, but it defeats the purpose-specific consent the Act expects. The fix is cheap if designed early. Ask for the data essential to the service at sign-up, then ask separately and in context for optional uses such as marketing or personalised recommendations.
| Consent pattern | Compliant? | Better approach |
|---|---|---|
| One "accept all" screen for service, marketing and sharing | Risky | Separate choices for each optional purpose |
| Pre-ticked marketing checkbox | No | Unticked by default; user opts in |
| Location requested at first launch "just in case" | Risky | Ask when the user starts a feature that needs it |
| Withdraw consent only by emailing support | Risky | A toggle in settings that works immediately |
What Should Your App's Privacy Notice Say?
Your privacy notice should list each item of personal data, the specific purpose for it, how users withdraw consent and how they can complain. The Rules ask for a notice that stands on its own and is understandable without reading other documents, so a link to a long legal policy is not enough on its own.
- What you collect: an itemised list, such as phone number, name, delivery address and order history.
- Why you collect each item: the specific purpose, such as "to send your OTP" or "to deliver your order".
- How to withdraw consent: the exact screen or link, not just an email address.
- How to exercise rights: where users request access, correction or erasure.
- How to complain: your grievance contact and the option to approach the Data Protection Board.
Write it at the reading level of your users. If your audience is in Telangana, offering the notice in Telugu as well as English is good practice, and the Act allows notices in English or any language in the Eighth Schedule of the Constitution.
Which Vendors and SDKs Count as Data Processors?
Any third party that handles personal data on your behalf is a Data Processor, and you remain responsible for what it does with that data. That includes your cloud host, but also the SDKs your developers drop into the app in an afternoon.
| Vendor type | Common examples | What to check |
|---|---|---|
| Hosting and database | Cloud servers, managed databases | Where data is stored and who can access it |
| Analytics and crash reporting | Usage analytics, crash logs | Whether events contain user identifiers |
| Messaging | SMS OTP, WhatsApp Business, email | Retention of message content and numbers |
| Payments | Payment gateways | What the gateway stores versus what your app stores |
| AI services | Chatbots and LLM APIs | Whether prompts containing user data are logged or used for training |
AI features deserve extra attention. A support chatbot that sends customer messages to a language model API is sharing personal data with a processor, so it belongs in your data map and your notice. Our guides to building an AI customer support chatbot and AI development cost in India cover how to design these features with data minimisation in mind.
How Much Effort Does DPDP Compliance Add to an App?
For a typical business app, DPDP-ready features add a few weeks of developer effort if planned from the start. Retrofitting the same features into a live app usually takes longer, because onboarding, settings and backend all have to change at once. The effort ranges below are typical for a standard app with one user type and are a planning guide, not a quote.
| Compliance feature | What it involves | Typical effort |
|---|---|---|
| Data map and notice | Inventory of data, purposes and vendors; plain-language notice | 2–4 days |
| Purpose-specific consent | Separate opt-ins, in-context permission prompts, consent records | 3–6 days |
| Rights screens | View, correct, delete data and withdraw consent from settings | 4–8 days |
| Security hardening | Encryption checks, role-based access, access logging | 3–6 days |
| Breach readiness | Alerting, response runbook, user notice template | 1–3 days |
If you are still choosing between off-the-shelf tools and a custom build for handling customer data, our custom vs off-the-shelf software guide explains the trade-offs, including how much control each option gives you over where data goes.
What Are the Penalties for Non-Compliance?
Penalties under the DPDP Act go up to ₹250 crore per instance, depending on the obligation breached. The Data Protection Board decides the amount after looking at factors such as the nature, gravity and duration of the breach.
| Violation | Maximum penalty |
|---|---|
| Failure to take reasonable security safeguards to prevent a breach | Up to ₹250 crore |
| Failure to notify the Board or affected users of a personal data breach | Up to ₹200 crore |
| Breach of additional obligations relating to children | Up to ₹200 crore |
| Breach of Significant Data Fiduciary obligations | Up to ₹150 crore |
| Any other breach of the Act or Rules | Up to ₹50 crore |
The penalty tiers are set out in the Act and summarised in the government's PIB backgrounder linked above.
What Extra Rules Apply to Children's Data?
Apps must obtain verifiable consent from a parent or guardian before processing the personal data of anyone under 18. The Rules allow exceptions for essential services such as healthcare, education and real-time safety. The Act also bars tracking, behavioural monitoring and targeted advertising directed at children.
For an education, gaming or family app, this changes the onboarding flow. You need a way to identify child users, a parent verification step and a separate experience without behavioural ads. Designing this after launch usually means rebuilding sign-up, so it belongs in the first release.
Can My App Store or Process Data Outside India?
Generally, yes: the DPDP Act does not require all personal data to stay in India. Cross-border transfer is allowed unless the Central Government restricts transfers to particular countries by notification. Significant Data Fiduciaries may also be directed to keep certain categories of data in India. Check the current position before you choose cloud hosting or analytics vendors, because notifications can change.
How to Make Your App DPDP-Ready
You make an app DPDP-ready by mapping its data first, then building consent, rights and security into the product before release. These steps follow the order a development team actually works in.
Step 1: Map every piece of personal data
List each data item your app collects, where it is stored, who can access it, which vendors receive it and the purpose for each. This map drives everything else, including your privacy notice.
Step 2: Redesign consent around purposes
Separate essential processing from optional uses, and ask for optional consent in context. Make every optional consent reversible from the settings screen.
Step 3: Build rights into the app
Add self-service screens for viewing, correcting and deleting data and withdrawing consent. App stores already push in this direction: Apple requires in-app account deletion for apps with accounts, and Google Play requires an accurate Data safety section.
Step 4: Secure and monitor your backend
Encrypt data in transit and at rest, restrict staff access by role, and log access to personal data so you can investigate incidents.
Step 5: Prepare your breach plan
Decide who investigates, who informs users and the Board, and keep a plain-language user notice template ready.
Step 6: Publish your contact point and retention rules
Name the person or team handling data requests, and set deletion schedules so data is erased once its purpose is served.
A copyable checklist version:
- 1Data map completed for every screen and vendor.
- 2Separate consent for each optional purpose, nothing pre-ticked.
- 3In-app access, correction, deletion and consent withdrawal.
- 4Encryption, role-based access and access logging live.
- 5Breach response plan and user notice template approved.
- 6Grievance contact published and retention schedule set.
When You Do Not Need a Lawyer Before Launch
For a straightforward business app that collects only standard data, a well-built consent flow and a clear notice often reduce risk enough for launch. A legal review is still sensible as you grow, but these situations rarely justify delaying release:
- Your app collects only name, phone, email and delivery address for a service the user requested.
- You use no third-party advertising SDKs and share data only with processors that run the service.
- You have no users under 18 and verify age at sign-up.
Get a lawyer's review before launch if you handle health records, financial data, children's data or large-scale profiling, or if you could be notified as a Significant Data Fiduciary.
Common DPDP Mistakes in Indian Apps
The mistakes we see most often are design decisions made in the first sprint that are expensive to undo later.
- Bundling every consent into one screen. The Bundled Consent Trap is the single most common gap.
- Copying a privacy policy from another app. It will describe data you do not collect and miss data you do.
- Hiding deletion behind an email address. Make deletion a working in-app feature.
- Forgetting SDKs. Analytics, crash reporting and ad libraries collect personal data too, and they belong in your data map.
- Keeping data forever. Without a retention schedule, every old record is extra breach exposure.
How Nevatrix Builds DPDP-Ready Apps
Nevatrix builds every app with purpose-specific consent flows, encrypted storage, an in-app deletion request flow and a privacy notice drafted from the app's actual data map. Adding these to a standard build typically costs ₹15,000–₹40,000, depending on data complexity. We are a development company, not a law firm: for health, finance or children's apps, we work alongside your lawyer rather than replace them. See our guides to mobile app development cost and writing an app PRD, or our mobile app development services.