India version. Written for India: the Digital Personal Data Protection Act 2023, its consent notice, Data Principal rights, the Consent Manager role, breach intimation to the Board and Significant Data Fiduciary duties. US version
Data Protection Readiness Checklist (India)
India’s data law is consent-first. Issue a clear notice, honour Data Principal rights, appoint the contacts, and prepare to report a breach to the Board.
The interactive tool loads here when JavaScript runs.
About this toolWhat is the Data Protection Readiness Checklist?
India’s Digital Personal Data Protection Act 2023 is not a GDPR translation, and treating it as one produces the wrong compliance programme. It is consent-first: processing digital personal data generally requires consent, obtained with a clear notice, or one of the specified legitimate uses. The long menu of lawful bases that European compliance is built around does not exist here.
The vocabulary differs too and the words carry obligations. The person is a Data Principal, whoever decides the purpose and means is a Data Fiduciary, and a processor is a Data Processor acting under contract. A Consent Manager is a registered intermediary through which consent can be given, managed and withdrawn, which has no equivalent elsewhere.
The practical starting point is the same as anywhere: know what personal data you hold and why. The difference is what you then have to be able to produce, which is a notice in plain language, in English or any language in the Eighth Schedule to the Constitution, and a working route for a Data Principal to withdraw consent as easily as they gave it.
- Written to the Digital Personal Data Protection Act 2023, not adapted from GDPR
- Uses Data Principal, Data Fiduciary and Consent Manager correctly
- Covers consent withdrawal, the grievance mechanism and Data Principal rights
- Includes children’s data duties and Significant Data Fiduciary obligations
- Tick, reword and delete items, then export as a Google Form, PDF, CSV or Markdown
Updated
How to use the Data Protection Readiness Checklist
- Map the digital personal data you hold, the purpose for each, and who processes it for you.
- For each purpose, identify consent or the specific legitimate use you rely on, and write the notice in plain language.
- Build consent withdrawal that is as easy as consent, and an internal grievance mechanism that works.
- Put processor contracts in place, set retention periods, and document your security safeguards.
- Prepare breach intimation to the Board and to affected Data Principals, and check whether you are a Significant Data Fiduciary.
Worked examples
App built to a GDPR checklist
Input
Lawful basis items
Output
Rebuilt on consent plus specific legitimate uses
The Act is consent-first and does not offer a general legitimate interests basis, so a European compliance design leaves processing without a basis under Indian law.
Signup bundling optional data
Input
Consent items
Output
Unbundled to the data necessary for the stated purpose
Consent must be specific and limited to what the purpose needs, so a single acceptance covering unnecessary collection does not meet the standard.
Service used by teenagers
Input
Children items
Output
Verifiable parental consent and no behavioural tracking
Children’s data carries specific duties including verifiable guardian consent and prohibitions on tracking and targeted advertising, which affects the product design rather than only the policy.
Complaint from a user
Input
Grievance items
Output
Internal grievance mechanism handled it first
A Data Principal is generally expected to use the Data Fiduciary’s grievance mechanism before approaching the Board, which makes having a working one a requirement rather than a courtesy.
Background and insight
Consent under the Act must be free, specific, informed, unconditional and unambiguous with a clear affirmative action, and limited to the data necessary for the stated purpose. Withdrawal must be as easy as giving it, and on withdrawal the Data Fiduciary must cease processing within a reasonable time unless another legal basis requires retention. Consent obtained by bundling unnecessary data into a single acceptance does not meet the standard.
Legitimate uses are the Act’s alternative to consent in defined situations, including where the Data Principal has voluntarily provided data for a specified purpose and certain state functions, employment-related purposes and emergencies. They are specific and narrow rather than a general-purpose fallback, so relying on one requires identifying which.
Data Principal rights include access to information about processing, correction and erasure, grievance redressal, and nomination of another person to exercise rights in the event of death or incapacity. The grievance route matters procedurally: a Data Principal is generally expected to exhaust the Data Fiduciary’s own grievance mechanism before approaching the Data Protection Board, which means a working internal mechanism is a compliance requirement rather than a nicety.
Children’s data carries specific obligations, including verifiable consent from a parent or lawful guardian below the specified age and prohibitions on tracking, behavioural monitoring and targeted advertising directed at children. Services that cannot tell whether a user is a child need to think about this before launch rather than after.
Breach obligations require intimation to the Data Protection Board and to each affected Data Principal, and the Act and rules frame this without the single familiar European deadline, so the operational answer is to be able to move immediately rather than to plan to a specific hour. Significant Data Fiduciaries, designated on specified criteria, carry extra duties including appointing a Data Protection Officer based in India, an independent data auditor and periodic impact assessment.
Finally, security safeguards are a positive obligation rather than a risk-based aspiration, and penalties under the Act are substantial, which makes documented safeguards and a retention schedule the two cheapest things to get right early.
Common use cases
Building for Indian users
Consent-first design rather than a GDPR port.
Writing the notice
Plain language, and the Eighth Schedule languages.
Products used by children
Verifiable consent and the tracking prohibition.
Before a breach
Intimation to the Board and to each affected person.
Tips and limitations
- Do not port a GDPR programme. There is no general legitimate interests basis here.
- Withdrawal must be as easy as consent, which is a product requirement, not a policy line.
- The notice must be available in plain language and in the Eighth Schedule languages.
- Build the internal grievance mechanism; the Board route generally comes after it.
- If you cannot tell whether a user is a child, design for the possibility before launch.
Sources and further reading
- Data protection framework, Ministry of Electronics and Information Technology. The DPDP Act 2023 and rules made under it
- Ministry of Electronics and Information Technology, Government of India. The administering ministry and official notifications
- Unique Identification Authority of India, Government of India. Aadhaar data handling obligations where Aadhaar is used
Frequently asked questions
Which law governs personal data in India?
The Digital Personal Data Protection Act 2023, with rules made under it, overseen by the Data Protection Board of India. It is consent-first and uses its own vocabulary, so it is not a GDPR equivalent and should not be implemented as one.
What does consent have to look like under the DPDP Act?
Free, specific, informed, unconditional and unambiguous with a clear affirmative action, accompanied by a notice in plain language, and limited to the data necessary for the stated purpose. Bundling unnecessary collection into one acceptance does not satisfy it.
Is there a legitimate interests basis like GDPR?
No. The Act provides specific legitimate uses as alternatives to consent in defined situations, including data voluntarily provided for a specified purpose, certain employment purposes, state functions and emergencies. They are narrow, so relying on one means naming which.
What are Data Principal rights?
Access to information about processing, correction and erasure, grievance redressal, and nomination of another person to exercise rights on death or incapacity. The grievance mechanism of the Data Fiduciary is generally the first route before the Board.
What is a Consent Manager?
A registered intermediary through which a Data Principal can give, manage, review and withdraw consent, accountable to the Data Principal. It is a structural feature of the Indian regime with no direct equivalent in other data protection laws.
What extra duties does a Significant Data Fiduciary have?
Designation is based on specified criteria, and the additional duties include appointing a Data Protection Officer based in India, engaging an independent data auditor and carrying out periodic data protection impact assessments.
Is there an in-depth guide to the Data Protection Readiness Checklist?
Yes. “Why Checklists Work, and How to Use One Properly” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.