Users Pricing

articles

Home Articles DPDP Act Compliance in 2027: A Practical Guide for Indian Software Companies – MindStick
DPDP Act Compliance in 2027: A Practical Guide for Indian Software Companies

DPDP Act Compliance in 2027: A Practical Guide for Indian Software Companies

Anirban Roy 16 19 Nov 2026

Updated: November 2026. This guide is general information, not legal advice.

For years, Indian software companies handled personal data under the fairly light-touch IT Act, 2000 and the SPDI Rules, 2011. That era is ending. The Digital Personal Data Protection Act, 2023 (DPDP Act) and the DPDP Rules, 2025 create a full data protection regime, and the substantive obligations kick in during 2027.

If you build or run software that touches personal data, such as user accounts, customer databases, HR systems, CRMs, mobile apps or analytics, this applies to you. Here’s what to know and what to do.

The timeline that matters

The DPDP Rules were notified in November 2025 with a phased rollout over 18 months:

PhaseWhenWhat applies
Phase 1November 2025 (immediately)Definitions, the Data Protection Board of India, and procedural rules for the Board
Phase 2About one year after notification (November 2026)Registration and obligations of Consent Managers
Phase 318 months after notification (around 13 May 2027)Most substantive obligations: notices, consent, security safeguards, breach reporting, children’s data, retention, rights of data principals, and Board complaint handling

The older SPDI Rules, 2011 continue during the transition. But by mid-May 2027, your products and processes need to be DPDP-ready.

Key terms in plain language

TermMeaning
Data PrincipalThe person the data is about (your user, customer, employee)
Data FiduciaryThe organisation that decides why and how data is processed (usually your company, or your client)
Data ProcessorAn organisation processing data on behalf of a fiduciary (e.g. a software vendor, cloud provider or outsourced support team)
Significant Data Fiduciary (SDF)A fiduciary notified by the government based on factors like data volume and risk, with extra obligations
Consent ManagerA registered entity that helps people give, manage and withdraw consent

Important for IT service companies: if you build and host software for clients, you’re often a Data Processor for that client’s data, and a Data Fiduciary for your own employee and customer data. Your contracts should say which role applies where.

The core obligations, explained

1. Lawful basis: consent or “legitimate uses”

You can process personal data either with the person’s consent or for certain legitimate uses listed in the Act (for example, where a person voluntarily provides data for a specific purpose, certain employment-related purposes, or legal obligations).

Consent must be:

  • free, specific, informed, unconditional and unambiguous
  • given through a clear affirmative action (no pre-ticked boxes)
  • limited to data necessary for the stated purpose

2. Clear notices

Before or at the time of asking for consent, you must give a notice that explains, in clear and plain language:

  • what personal data you’re collecting
  • the specific purpose
  • how the person can withdraw consent and exercise their rights
  • how to complain to the Data Protection Board

The Rules require notices to be understandable on their own, not buried in a 40-page privacy policy. Notices should be available in English or any language in the Eighth Schedule of the Constitution, where requested.

3. Withdrawal as easy as giving consent

If a user can consent with one tap, they should be able to withdraw just as easily. Build a visible “manage consent” or “withdraw consent” option, and make sure withdrawal actually stops processing downstream, including in analytics and marketing tools.

4. Reasonable security safeguards

The Rules expect fiduciaries to implement reasonable security safeguards, including measures such as:

  • encryption, obfuscation or masking of personal data
  • access controls and visibility of who accessed what
  • logging and monitoring to detect unauthorised access
  • backups and continuity measures
  • appropriate contractual safeguards with processors

Keep access logs and related records for the period specified in the Rules.

5. Breach notification

If a personal data breach happens, you must inform:

  • affected Data Principals, without delay, in plain language
  • the Data Protection Board, with an initial intimation and a detailed report within the timeline specified in the Rules

Prepare templates and an incident response plan now. Writing breach notices during a crisis is how mistakes happen.

6. Children’s data

For users under 18, the Act requires verifiable consent from a parent or lawful guardian. Tracking, behavioural monitoring and targeted advertising directed at children are restricted, with limited exemptions. If your product could have child users (edtech, gaming, social features), this needs careful design.

7. Data retention and erasure

Don’t keep personal data forever. Erase it when the purpose is served or consent is withdrawn, unless the law requires you to retain it. For certain classes of large platforms, the Rules set specific retention periods and require advance notice to users before erasure.

8. Rights of Data Principals

Users can:

  • request information about processing
  • request correction, completion, updating and erasure
  • seek grievance redressal
  • nominate someone to exercise rights on their behalf in case of death or incapacity

Publish contact details for a person who can answer data-related questions, such as a Data Protection Officer for SDFs or a designated contact for others, and respond within the timelines set by the Rules.

Penalties

The Act provides for financial penalties that can run up to ₹250 crore per instance for serious failures, such as not taking reasonable security safeguards to prevent a breach. Other violations carry lower but still significant maximum penalties. The Data Protection Board decides penalties after an inquiry, considering factors like the nature, gravity and duration of the breach.

A 90-day action plan for software teams

Days 1–30: Discover

  1. Map your data: what personal data each system collects, where it’s stored, who accesses it, and which vendors process it.
  2. Identify your role for each system: fiduciary, processor or both.
  3. List all consent points: sign-up forms, cookie banners, marketing opt-ins, mobile app permissions.

Days 31–60: Design

  1. Rewrite notices in plain language, purpose by purpose.
  2. Design consent flows with clear opt-in, granular choices and easy withdrawal.
  3. Define retention periods for each data category.
  4. Review contracts with clients and vendors for processor obligations, security and breach reporting.

Days 61–90: Build and prepare

  1. Implement technical controls: encryption, access logs, role-based access, data masking in non-production environments.
  2. Build user rights workflows: access, correction and erasure requests, with tracking.
  3. Write a breach response playbook and run a tabletop exercise.
  4. Train your teams: developers, support staff and sales.

Common mistakes to avoid

  • Using production data in test environments without masking
  • Collecting “just in case” data with no clear purpose
  • Ignoring third-party SDKs in mobile apps that collect data silently
  • Treating the privacy policy as compliance, without changing systems
  • Forgetting backups and logs when handling erasure requests
  • No processor agreements with cloud, email, SMS or analytics vendors

Key takeaways

DPDP compliance is not a legal document you file once. It’s a set of product and engineering decisions about what you collect, why you collect it, how you protect it and how long you keep it.

The 18-month runway sounds long, but redesigning consent flows, retrofitting audit logs and renegotiating vendor contracts takes time. Teams that start in late 2026 will find May 2027 manageable. Teams that wait until April will not.

This article provides general information and is not legal advice. Please consult a qualified legal professional and refer to the official text of the DPDP Act, 2023 and DPDP Rules, 2025 for your specific obligations.


Anirban Roy

Dot Net Developer at Tata Consultancy Services

Working as Dot Net Developer with Tata Consultancy Services, Kolkata. I have 6 years of experience in C# and ASP.NET Core application development, and earlier worked with Swiggy as Dot Net Developer. I did my B.Tech in Computer Science from the Indian Institute of Technology Delhi. In my free time I like reading history books and travelling to new places.


Markdown for AI

A clean, structured version of this page for AI assistants and LLMs.

Open .md