DPDP WorkspaceRequest a demo

DPDP compliance: what the Act and the Rules ask

This is general information, not legal advice. For your own situation, speak to a lawyer.

DPDP compliance means meeting what India's Digital Personal Data Protection Act, 2023 (the Act) and the Digital Personal Data Protection Rules, 2025 (the Rules) ask of a Data Fiduciary: the person or company that decides why and how personal data is processed (s.2(i)). This guide walks through those duties in order, with the section or rule for each, and ends with a printable checklist. The official texts are on MeitY's data protection page and in the Gazette of India.

When the duties apply

The Act's provisions start on different dates (s.1(2)). Setting up the Data Protection Board of India came first: s.18 to s.26 apply from 13 November 2025 (G.S.R. 843(E)). The Board's powers to inquire and to impose penalties (s.27 to s.34) come later, from 13 May 2027, except its power over registration conditions (s.27(1)(d)), from 13 November 2026. Most duties in this guide, from s.3 to s.17, apply from 13 May 2027, as do Rules R.3 and R.5 to R.16 (R.1(4)). For the full timeline, see the DPDP Rules 2025 explained.

Step 1: Check whether the Act applies

The Act applies to digital personal data: personal data collected in digital form, or collected on paper and digitised later, when it is processed in India (s.3(a)). It also applies outside India when the processing is connected with offering goods or services to people in India (s.3(b)).

It does not apply to personal data an individual processes for personal or domestic purposes, or to personal data that the person it is about, or someone under a legal duty, has made publicly available (s.3(c)). Some duties are lifted in specific cases, such as enforcing a legal right or preventing offences (s.17).

Personal data is any data about an individual who can be identified by or in relation to it (s.2(t)); see personal data and data fiduciary in the glossary.

Step 2: Know your personal data and give each purpose one ground

The Act allows processing only for a lawful purpose, on one of two grounds: the person's consent, or one of the legitimate uses listed in s.7 (s.4). The legitimate uses include data a person gave voluntarily for a purpose without objecting to its use (s.7(a)), legal duties to disclose information to the State (s.7(d)), medical emergencies (s.7(f)) and employment (s.7(i)).

To give a notice, a company needs an itemised description of the personal data and the purpose of each processing (R.3(b)). In practice that starts with a map of which systems hold which personal data, and why.

See how DPDP Workspace helps.

Step 3: Give a notice

Every request for consent comes with, or after, a notice (s.5(1)). Under R.3 the notice stands on its own, is in clear and plain language, and gives at least:

  • an itemised description of the personal data;
  • the specified purpose, and the goods, services or uses it enables;
  • a link to the website or app, and any other way, to withdraw consent as easily as it was given, to use the rights under the Act, and to complain to the Board.

The notice and the consent request are offered in English or any language of the Eighth Schedule to the Constitution (s.5(3), s.6(3)). People who consented before the Act's commencement get a notice as soon as practicable (s.5(2)).

How DPDP Workspace helps: Notices in English and the 22 languages of the Eighth Schedule, reviewed by a person.

Consent under the Act is free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, and limited to the personal data the purpose needs (s.6(1)). A part of a consent that breaks the law is invalid (s.6(2)).

Withdrawing consent is as easy as giving it (s.6(4)). After a withdrawal, the Data Fiduciary stops processing, and has its Data Processors stop, within a reasonable time, unless the law requires or allows the processing without consent (s.6(6)). If a question about consent arises, the Data Fiduciary has to prove that the notice was given and the consent obtained (s.6(10)).

How DPDP Workspace helps: A consent banner for websites, an Android SDK and an API for your systems. Consent and notice records can't be edited, and are kept for their full retention period; every compliance action is written to a tamper-evident trail.

Step 5: Take extra care with children's data

A child is anyone under 18 (s.2(f)). Before processing a child's personal data, the Data Fiduciary obtains the verifiable consent of a parent (or lawful guardian) (s.9(1), whose wording was corrected by the Removal of Difficulties Order, S.O. 5458(E)). R.10 describes how to check that the person giving it is an identifiable adult. The Act also rules out processing likely to harm a child's well-being, and tracking, behavioural monitoring or targeted advertising directed at children (s.9(2), s.9(3)). Some classes of Data Fiduciaries and some purposes are exempt from parts of this, under conditions (s.9(4); R.12 and the Fourth Schedule).

More in children's data under the DPDP Act.

Step 6: Protect the data

The Act asks for reasonable security safeguards to prevent a personal data breach, including for processing done by Data Processors (s.8(5)). R.6 lists the minimum: measures such as encryption or masking; access control; logs and monitoring that can detect unauthorised access; backups so processing can continue; keeping those logs for a year unless another law says otherwise; security terms in contracts with Data Processors; and organisational measures to make all this work (R.6(1)).

The Data Fiduciary also keeps personal data complete, accurate and consistent when it is used for a decision about the person or shared with another Data Fiduciary (s.8(3)).

How DPDP Workspace helps: Hosted in India: AWS Mumbai, with disaster recovery in Hyderabad. Your data, backups and logs stay in India. Encrypted in transit and at rest.

Step 7: Report a personal data breach

A personal data breach is any unauthorised processing, or accidental disclosure, use, change, destruction or loss of access, that compromises personal data (s.2(u)). Every breach is reported (s.8(6)); R.7 sets how:

  • to each affected person, without delay: what happened, the likely consequences for them, what is being done, what they can do to protect themselves, and who to contact (R.7(1));
  • to the Board, a first description without delay, then the full details within 72 hours of becoming aware of the breach, or longer if the Board allows it on a written request (R.7(2)).

Sector rules can add their own reports. More in data breach reporting under the DPDP Act.

How DPDP Workspace helps: Deadline clocks for breach reports (6 hours CERT-In, 72 hours Board) and rights requests.

Step 8: Work with Data Processors under contract

A Data Fiduciary may use a Data Processor only under a valid contract (s.8(2)), which provides for reasonable security safeguards (R.6(1)(f)). The Data Fiduciary stays responsible for processing done on its behalf (s.8(1)), and has its Data Processors stop processing and erase data when that is due (s.6(6), s.8(7)(b)).

Step 9: Keep data only as long as it is needed

Personal data is erased once consent is withdrawn or once it is reasonable to assume the purpose is no longer served, whichever is earlier, unless a law requires keeping it (s.8(7)). For e-commerce entities and social media intermediaries with at least two crore registered users in India, and online gaming intermediaries with at least fifty lakh, the Third Schedule sets that point at three years after the person last approached them, with some exceptions, and the person is told at least 48 hours before the data is erased (R.8(1), R.8(2)).

Separately, the personal data, traffic data and logs of any processing are kept for at least one year from the processing, for the purposes in the Seventh Schedule, and then erased unless another law requires keeping them longer (R.8(3)).

Step 10: Publish a contact, and answer rights and grievances

The Data Fiduciary publishes the business contact details of its Data Protection Officer, if it has one, or of a person who can answer questions about the processing, and gives them in every reply to a rights request (s.8(9); R.9).

People whose data it is (each a Data Principal, s.2(j)) have the right to:

  • a summary of their personal data and its processing, and who it was shared with (s.11);
  • correction, completion, updating and erasure (s.12);
  • readily available grievance redressal (s.13);
  • nominate someone to act for them in case of death or incapacity (s.14).

The Data Fiduciary sets up an effective way to redress grievances (s.8(10)), publishes how to make a request and what details identify the person (R.14(1)), and publishes the period for answering grievances, which is at most 90 days (R.14(3)). A person goes to the Data Fiduciary first, before the Board (s.13(3)).

How DPDP Workspace helps: Deadline clocks for breach reports (6 hours CERT-In, 72 hours Board) and rights requests.

Step 11: If notified as a Significant Data Fiduciary

The Central Government may notify a Data Fiduciary, or a class of them, as a Significant Data Fiduciary, looking at factors such as the volume and sensitivity of the data and the risk to people's rights (s.10(1)). A Significant Data Fiduciary appoints a Data Protection Officer based in India and an independent data auditor, and carries out periodic Data Protection Impact Assessments and data audits (s.10(2), as worded after S.O. 5458(E)). Under R.13 the assessment and the audit happen every twelve months, with a report of their significant observations to the Board.

More in significant data fiduciary.

What happens if a duty is breached

The Board may impose a penalty after an inquiry finds a significant breach (s.33(1)). The Schedule sets the highest amounts: for example, up to 250 crore rupees for not taking reasonable security safeguards, and up to 200 crore rupees for not notifying a breach or for breaching the duties on children's data. More in DPDP Act penalties.

The DPDP compliance checklist

What the Act and the Rules ask of a Data Fiduciary, each with where it says so. Print this page for a copy.

  1. Process personal data only for a lawful purpose, on the person's consent or for one of the legitimate uses the Act lists. (s.4, s.7) How DPDP Workspace helps
  2. Give a notice with or before each request for consent, listing the personal data, the purpose, and how to withdraw, use the rights and complain to the Board. (s.5(1); R.3) How DPDP Workspace helps
  3. Offer the notice and the consent request in English or a language of the Eighth Schedule to the Constitution. (s.5(3), s.6(3)) How DPDP Workspace helps
  4. Give people who consented before the Act's commencement a notice as soon as practicable. (s.5(2)) How DPDP Workspace helps
  5. Rely only on consent that is free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, and limited to the personal data the purpose needs. (s.6(1)) How DPDP Workspace helps
  6. Make withdrawing consent as easy as giving it, then stop processing, and have Data Processors stop, within a reasonable time. (s.6(4), s.6(6)) How DPDP Workspace helps
  7. Be able to prove that the notice was given and the consent obtained. (s.6(10)) How DPDP Workspace helps
  8. Obtain verifiable consent of a parent before processing a child's personal data, and do no tracking, behavioural monitoring or targeted advertising directed at children. (s.9; R.10) How DPDP Workspace helps
  9. Take reasonable security safeguards, including access control, logs and backups, and keep those logs for a year. (s.8(5); R.6) How DPDP Workspace helps
  10. Tell each affected person and the Board of a personal data breach without delay, and send the Board the full details within 72 hours. (s.8(6); R.7) How DPDP Workspace helps
  11. Use a Data Processor only under a valid contract that provides for security safeguards. (s.8(2); R.6(1)(f)) How DPDP Workspace helps
  12. Erase personal data once consent is withdrawn or the purpose is no longer served, unless a law requires keeping it, and keep processing logs for at least one year. (s.8(7); R.8) How DPDP Workspace helps
  13. Publish the business contact details of a person who answers questions about the processing. (s.8(9); R.9) How DPDP Workspace helps
  14. Publish how people can use their rights to access, correct, erase and nominate, and answer grievances within the published period of at most 90 days. (s.8(10), s.11 to s.14; R.14) How DPDP Workspace helps
  15. If notified as a Significant Data Fiduciary, appoint a Data Protection Officer based in India and an independent data auditor, and carry out a Data Protection Impact Assessment and an audit every twelve months. (s.10; R.13) How DPDP Workspace helps

To see how these steps look in practice, request a demo.