The DPDP Act is now a software problem
Sound familiar?
Legal has sent a summary of the DPDP Rules to engineering with one line: "Please make sure we comply." Nobody is sure what that means for the sign-up form, the database, or the logs.
India's Digital Personal Data Protection Act, 2023 (DPDP Act) sets the rules for collecting and using personal data. The DPDP Rules, 2025, notified by the Ministry of Electronics and Information Technology on 13 November 2025, say how and when. Lawyers can write the policy, but most of the obligations only work if your app or website is built to support them: consent that is recorded, notices users can read, rights requests that get answered, and data that is deleted on time.
The Act applies to any business that processes digital personal data of people in India, from a startup with a sign-up form to a large platform. In the Act's terms, your business is the Data Fiduciary, your users are Data Principals, and vendors who process data for you are Data Processors. You stay responsible for what your processors do.
DPDP compliance deadlines
| When | What applies | What it means for your software |
|---|---|---|
| 13 November 2025 | Data Protection Board and foundational provisions | Start planning; the clock is running |
| Around November 2026 | Registration and duties of Consent Managers | Be ready to accept consent through registered consent managers if your users use them |
| 13 May 2027 | Notices, consent, security safeguards, breach reporting, retention, user rights | Every feature in the checklist below must be live |
Eighteen months sounds long, but law firms advise treating 2026 as the year to build. Finding where personal data lives across a product, its databases and its vendors usually takes longer than building the features themselves.
What your app or website has to support
- A clear notice before collection, in plain language, saying what data you collect and why, available in English or any language in the Eighth Schedule of the Constitution
- Consent that is specific and given by a clear action, never pre-ticked or bundled with unrelated purposes
- Withdrawing consent as easy as giving it, and processing that actually stops when it is withdrawn
- A record of who consented to what, and when, that you can produce if asked
- Ways for users to access, correct and erase their data, and to raise a complaint
- Reasonable security safeguards such as encryption, access control and monitoring
- Logs of personal data processing kept for at least one year
- Deleting personal data once its purpose is served, unless a law requires you to keep it
Need your app ready for the DPDP Act?
Get a free consultationBreach reporting and children's data
If personal data is breached, you must inform the Data Protection Board and every affected user without delay, and give the Board a detailed report, normally within 72 hours. That is only possible if your systems can tell you quickly what was exposed and whose data it was. Build that visibility before you need it: logging, alerting, and a map of which systems hold which personal data.
For anyone under 18, you need verifiable consent from a parent or guardian before processing their data. The Act also bars tracking or behavioural monitoring of children and targeting advertising at them. If your product may have under-18 users, plan age checks and a parental consent flow now, because they change the sign-up journey.
A practical DPDP readiness plan
Map your personal data
List every place personal data enters, is stored, is shared and leaves: forms, databases, logs, analytics, backups and third-party tools.
Tie each item to a purpose
Record why you hold it and how long you need it. Data with no clear purpose is a liability; delete it.
Rebuild notice and consent
Replace generic checkboxes with purpose-specific consent, store consent records, and add one-click withdrawal.
Add user rights features
Build self-service or ticketed flows for access, correction, erasure and complaints, with deadlines tracked.
Harden security and logging
Encrypt personal data, tighten access, and keep processing logs for at least a year.
Check your vendors
Update contracts with every processor, and confirm they can delete data and report breaches to you in time.
For help building these features into a web app, mobile app or SaaS product, see our custom web application, mobile app and SaaS development services.
Key takeaway
DPDP compliance is a build project with a fixed date: 13 May 2027. Map your personal data first, then build consent records, user rights, breach visibility and deletion into the product, not just the privacy policy.
This article explains the software side of the DPDP Act and is not legal advice. Confirm your specific obligations with a qualified lawyer.
Frequently Asked Questions
Related service
Custom web applications
Full-stack web applications designed around your users and your process, from customer portals to learning platforms.
Related service
SaaS product development
For founders building an MVP and businesses improving an existing SaaS product: core features, accounts, permissions, billing, and deployment.
Written by
Tricolens
Product & Engineering
