DPDP Act for Indian Developers and Startups: A Practical Compliance Checklist (2026)

If you build or run a website, app or SaaS product that handles personal data of people in India, the Digital Personal Data Protection Act, 2023 (DPDP Act) is now part of your engineering reality. The Act passed in 2023, the detailed Rules were notified on 13 November 2025, and the obligations switch on in phases, with the main duties for most businesses due on 13 May 2027. The consent manager provisions began on 13 November 2026.
This guide translates the law into engineering tasks: what consent should look like in your signup form, what to log, how to prepare for a breach and what to fix first. It is written for developers and founders, not lawyers. It is general information, not legal advice, so confirm the details against the official text and talk to a qualified lawyer before making compliance decisions.
What the DPDP Act and Rules actually are
The DPDP Act sets the principles: lawful processing, consent, purpose limits, security and individual rights. The DPDP Rules fill in the practical details: how a notice should read, how breaches are reported, how children's data is treated and how the regulator, the Data Protection Board of India, will work.
Key terms in plain English
Data Principal: the person the data is about, such as your user or customer.
Data Fiduciary: whoever decides why and how personal data is processed. If you run the product, that is you.
Data Processor: a vendor that processes data on your behalf, such as a cloud host, email service or analytics tool.
Consent Manager: a registered intermediary that lets people give, review and withdraw consent across services.
Significant Data Fiduciary: a larger or higher-risk organisation designated by the government, with extra duties such as audits.
The Board: the Data Protection Board of India, which handles complaints and enforcement.
The phased timeline
Period | What it covers |
|---|---|
13 November 2025 | Rules notified. The Data Protection Board, its powers and the opening provisions apply immediately. |
13 November 2026 | Rule 4: registration and obligations of Consent Managers. |
13 May 2027 | Most duties for Data Fiduciaries: notice, consent, security safeguards, breach reporting, children's data, rights and Significant Data Fiduciary duties. |
Treat the period before May 2027 as your build window. Check the official gazette for any corrigenda or amendments before you finalise your plan.
Does it apply to you?
In general, the Act covers digital personal data processed in India, and also processing outside India when you offer goods or services to people in India. A solo developer with a contact form is in scope in principle. Extra duties apply to Significant Data Fiduciaries, which the government designates. The Act lets the government exempt some classes, including notified startups, from certain duties, but only by notification, so do not assume you are exempt. Purely personal or household use of data is outside the Act.
Personal data means anything that identifies a person: name, phone number, email, an IP address tied to an account, device identifiers, order history and so on.
Consent: the core of the law
What valid consent looks like
Consent must be free, specific, informed, unconditional and unambiguous, and it must be given through a clear affirmative action. In product terms:
No pre-ticked boxes.
No "accept everything or you cannot use the app" for data you do not need.
One consent per purpose, not one giant bundle.
Plain language, with the option to read it in English or any language listed in the Constitution's Eighth Schedule.
Some processing does not need consent, for example certain "legitimate uses" such as complying with the law or responding to a medical emergency. Do not assume marketing or analytics fits here.
Notice requirements
Before or when you ask for consent, show a notice that says what personal data you collect, why, how a person can withdraw consent or exercise rights and how to complain to the Board. The Rules expect an itemised, clear description, not legal fog hidden behind a "Privacy Policy" link.
Withdrawal must be as easy as giving consent
If a person agreed with one click, they should be able to withdraw with roughly the same effort. A settings page with a clear toggle is much better than "email us to opt out".
Implementation tips for developers
Store a consent record for each decision: user ID, purpose, timestamp, version of the notice shown and the result (given or withdrawn).
Version your notices, so you can prove what the person saw at that time.
Build a single consent service or table that the rest of your code checks before processing for a purpose, instead of scattering
ifstatements across the codebase.When consent is withdrawn, stop the processing and, unless you are legally required to retain the data, erase it and tell your processors to do the same.
Collect less, keep it shorter
You may process data only for the purpose the person agreed to, and you should erase it once that purpose is served, unless another law requires you to keep it.
Run a simple data audit:
List every personal data field you collect, in each form, API and database table.
Next to each one, write the purpose. If you cannot, stop collecting it.
Set a retention period and automate deletion, for example a scheduled job that removes abandoned signups after 90 days. Large e-commerce, gaming and social media platforms have a fixed outer limit and must warn users 48 hours before erasing data.
Check third-party scripts. Analytics, chat widgets and ad pixels often collect personal data on your behalf, which makes you responsible for them.
Children's data
For anyone under 18, the Act requires verifiable consent from a parent or lawful guardian before processing their personal data. It also prohibits tracking, behavioural monitoring and targeted advertising aimed at children, with limited exemptions set out in the Rules. You must also check that the person giving consent is an adult, for example through reliable age details or a government-issued token.
If your product can be used by minors, such as an education app, a game or a family service, decide early how you will verify age and parental consent. Retrofitting this later is painful. If your product is clearly for adults, state it, and add a basic age gate.
Security safeguards for engineering teams
The Act requires "reasonable security safeguards" to prevent a breach, and the Rules spell out what reasonable includes. Treat the following as a baseline:
Encryption of personal data in transit and at rest, or equivalent controls such as masking and tokenisation.
Access control: least privilege, strong authentication for admin panels and separate accounts for each person.
Logging and monitoring: logs that let you detect and investigate unauthorised access. The Rules require relevant logs and personal data to be kept for one year for that purpose, unless another law requires longer, so plan storage for it.
Backups and continuity: the ability to restore data if it is lost or corrupted.
Processor contracts: written agreements that require your vendors to apply safeguards too.
Our guides on setting up SSH keys properly and understanding API architecture can help with the basics.
Breach response
If personal data is breached, you must tell the Board and each affected person without delay. The Rules then require a detailed report to the Board within 72 hours of becoming aware, which the Board can extend on a written request. Do not wait for a perfect investigation before you start.
Prepare a one-page runbook now:
Detect and contain: who gets alerted, and who can cut access or rotate credentials.
Assess: what data, how many people, what could be misused.
Notify: who drafts the message to the Board and to users, and who approves it.
Record: keep a timeline of events and actions for the follow-up report.
Fix and learn: patch the cause and review what monitoring missed.
Rights of Data Principals
Your users get a set of rights you need to be able to serve:
Access: a summary of the personal data you process and the activities involved, plus the identities of other fiduciaries and processors you shared it with.
Correction and erasure: the right to correct, complete and update data and to ask you to erase it, unless you need it for the stated purpose or the law requires retention.
Grievance redressal: a way to raise a complaint with you first, with a published contact and a reasonable response time.
Nomination: the right to nominate someone to exercise rights if they die or become incapacitated.
For most small products, this means a "My data" page or a documented email workflow, plus a named owner. Build export and delete as internal tools early, even if the first version is a script.
Penalties: why this is worth the effort
The Schedule to the Act sets maximum penalties that can be very large:
Failure | Maximum penalty |
|---|---|
Not taking reasonable security safeguards | Up to ₹250 crore |
Not notifying a breach | Up to ₹200 crore |
Breaching obligations on children's data | Up to ₹200 crore |
Extra duties of Significant Data Fiduciaries | Up to ₹150 crore |
Any other provision of the Act or Rules | Up to ₹50 crore |
A Data Principal breaching their own duties | Up to ₹10,000 |
These are ceilings, not automatic fines, but they explain why even small teams should take the Act seriously.
A practical 90-day plan for a small team
Days 1 to 30: understand your data
Map what you collect and why. Delete what you do not need. List your processors and check their security and data location. Name a person responsible for privacy.
Days 31 to 60: fix consent and notices
Rewrite your notices in plain language. Replace pre-ticked boxes and bundled consent. Add a consent log and a withdrawal path. If you serve minors, design the parental consent flow.
Days 61 to 90: security, rights and breach readiness
Turn on encryption and audit logs, review admin access, and set up log retention. Build the access, correction and erasure workflows. Write and rehearse the breach runbook, including who calls whom.
If you want help building consent management, audit logging or a user data portal, see my custom web application development service or contact me.
Conclusion
The DPDP Act rewards teams that collect less data, explain it clearly, protect it properly and respect people's choices. Start with a data audit, fix your consent flows and write a breach runbook, and you will have done most of the work well before May 2027. Treat this article as a starting map, not a legal opinion.
Was this article helpful?



Comments
Leave a comment
Loading comments...