Sushegaad/Claude-Skills-Governance-Risk-and-Compliance / plugins/dpdpa/skills/dpdpa
dpdpa
VerifiedExpert India Digital Personal Data Protection Act, 2023 (DPDPA) compliance advisor. Use this skill whenever a user asks about the DPDPA, DPDP Act, DPDP Rules 2025, India data privacy law, Data Fiduciary obligations, Data Principal rights, Significant Data Fiduciary, Data Protection Board of India, consent under DPDPA, notice requirements, breach notification India, children's data India, cross-border data transfer India, India privacy compliance, DPDPA gap analysis, DPDPA vs GDPR, or any obligation under India's personal data protection framework. Also trigger for: "Section 6 consent", "Section 7 legitimate uses", "Section 9 children's data", "Section 10 SDF", "Section 16 cross-border", "Rule 7 breach notification", "Rule 13 SDF obligations", "Data Protection Board complaint", "verifiable parental consent India", "DPDPA compliance roadmap", or "India privacy law global company".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 28.1 KB |
| references/gdpr-comparison.md | markdown | 12.1 KB |
| references/rights-and-obligations.md | markdown | 23.6 KB |
| references/rules-2025.md | markdown | 12.7 KB |
| references/sections-reference.md | markdown | 19.4 KB |
references/sections-reference.md
View on GitHub# DPDPA - Section-by-Section Reference
Digital Personal Data Protection Act, 2023. Presidential Assent: 11 August 2023.
44 Sections across 9 Chapters.
---
## Chapter I - Preliminary (Sections 1–3)
### Section 1 - Short Title, Extent, Commencement and Application
Establishes the short title: "Digital Personal Data Protection Act, 2023."
- Extends to the whole of India
- Commencement by phased notification in the Official Gazette
- Applies to digital personal data processing within India AND processing outside India
related to offering goods or services to individuals located in India
### Section 2 - Definitions
28 defined terms including:
| Term | Definition |
|------|-----------|
| **Appellate Tribunal** | Telecom Disputes Settlement and Appellate Tribunal (TDSAT) |
| **Board** | Data Protection Board of India |
| **Child** | Individual who has not completed **18 years of age** |
| **Consent Manager** | Body corporate registered by the Board enabling Data Principals to manage consent across multiple Data Fiduciaries via a single interoperable platform |
| **Data Fiduciary** | Any person who alone or jointly with others determines the **purpose and means** of processing of digital personal data (= GDPR "controller") |
| **Data Principal** | The individual to whom the personal data relates (= GDPR "data subject") |
| **Data Processor** | Any person who processes digital personal data on behalf of a Data Fiduciary under a contract (= GDPR "processor") |
| **Data Protection Officer (DPO)** | Individual appointed by a Significant Data Fiduciary as representative before the Board and grievance contact |
| **Digital personal data** | Personal data in digital form |
| **Personal data** | Any data about an individual who is identifiable directly or indirectly from such data |
| **Personal data breach** | Unauthorised processing or accidental disclosure causing loss of confidentiality, integrity, or availability of digital personal data |
| **Processing** | Any automated operation on digital personal data including collection, recording, storage, retrieval, use, sharing, transmission, erasure, and destruction |
| **Significant Data Fiduciary (SDF)** | Data Fiduciary notified by Central Government based on volume/sensitivity, risk to rights, impact on sovereignty, electoral democracy, state security, or public order |
| **Specified purpose** | The purpose mentioned in the Data Fiduciary's notice for which the Data Principal provided personal data |
### Section 3 - Application (Territorial Scope)
The Act applies to:
- Processing of digital personal data **within India**, and
- Processing **outside India** if it relates to offering goods or services to individuals
located in India at the time the personal data is collected
Partial exemption: Processing under contracts with foreign entities of data of
Data Principals **not located in India** is exempt from most obligations (Section 17(1)(d)).
---
## Chapter II - Obligations of Data Fiduciary (Sections 4–10)
### Section 4 - Grounds for Processing Personal Data
Two and only two lawful bases:
- **(a) Consent** as specified in Section 6
- **(b) Certain legitimate uses** as enumerated in Section 7
No other lawful basis exists. Processing outside these two grounds is unlawful.
### Section 5 - Notice to Data Principal
Before or at the time of requesting consent, Data Fiduciaries must provide a notice:
- In clear and plain language (implemented by Rule 3 of DPDP Rules 2025)
- As a standalone, independent document (not bundled in T&Cs)
- Containing: purposes; data categories; recipients; retention period; Data Principal rights; Board complaint mechanism; consent withdrawal procedure
**Key obligation:** Notice must be retrievable at any time from the Data Fiduciary's platform or website.
**Existing data (Section 5(2)):** For data collected before the Act's commencement but still being processed, Fiduciaries must provide a notice of the same content within prescribed time after the Act takes effect.
### Section 6 - Consent
Consent must be:
- **Free** - not conditioned on acceptance of services
- **Specific** - for a particular specified purpose
- **Informed** - given after receiving the Section 5 notice
- **Unconditional** - no conditions or coercion
- **Unambiguous** - expressed by clear affirmative action
**Section 6(2):** Consent is invalid to the extent it infringes the Act (invalidity provision).
**Section 6(3):** Every request for consent must be presented in clear and plain language, with the contact details of a Data Protection Officer (where applicable) or other person authorised to respond to Data Principal communications.
**Section 6(4):** Data Principals may withdraw consent at any time. Ease of withdrawal must match ease of giving consent.
**Section 6(5):** The consequences of withdrawal are borne by the Data Principal; withdrawal does not affect the lawfulness of processing done before withdrawal.
**Sections 6(7)–(9):** Consent may be given, managed, reviewed, and withdrawn through a Consent Manager registered with the Board; the Consent Manager is accountable to the Data Principal.
**Section 6(10):** The burden of proving that notice was given and valid consent obtained lies on the Data Fiduciary.
### Section 7 - Certain Legitimate Uses (Closed List)
Nine enumerated legitimate uses, clauses 7(a)–(i), where consent is NOT required:
- **(a)** Purpose the Data Principal voluntarily provided data for (unless specifically objected)
- **(b)** State benefits, subsidies, services, certificates, licenses, or permits
- **(c)** State functions under Indian law or interests of sovereignty/security/integrity
- **(d)** Legal obligation to disclose to State or its instrumentalities
- **(e)** Compliance with any judgment, decree, or order issued under law
- **(f)** Responding to a medical emergency involving a threat to life or immediate threat to health
- **(g)** Measures during an epidemic, outbreak, or other threat to public health
- **(h)** Safety and assistance during a disaster or breakdown of public order
- **(i)** Employment purposes or safeguarding employer against loss/liability - including prevention of corporate espionage, IP theft, and classified information leakage by employees
> **Precision note:** The employment category (Section 7(i)) covers both routine HR processing AND the employer's interest in preventing corporate espionage/IP theft by employees. These are part of a single clause - not separate categories. Section 7 contains **no residual catch-all clause**; the list ends at clause (i).
This list is **exhaustive**. No general "legitimate interests" balancing test.
### Section 8 - General Obligations of Data Fiduciary
Every Data Fiduciary must:
1. **Appoint Data Processors under contract** - valid written contract (Section 8(2))
2. **Ensure data quality** - accuracy, completeness, consistency for data used in decisions or shared with other Fiduciaries (Section 8(3))
3. **Implement security safeguards** - reasonable security safeguards (Section 8(5)) per Rule 6 (technology-neutral: encryption, obfuscation, masking or virtual tokens; access control; logs)
4. **Erase data** when: purpose fulfilled; consent withdrawn; Data Principal exercises erasure right; retention no longer necessary
5. **Direct Processors to erase** data upon termination of processing engagement
6. **Intimate personal data breach** to each affected Data Principal directly without delay, and to the Board without delay with a detailed report within 72 hours (extendable on request) per Rule 7
7. **Grievance mechanism** - Establish effective, accessible grievance mechanism and respond within prescribed period
**Section 8(7) - Retention and Erasure:**
Data Fiduciaries must erase data from their systems and from Processors' systems upon:
- Withdrawal of consent (unless retention required by law)
- Purpose fulfilment
- Section 12(3) erasure request
### Section 9 - Processing of Children's Personal Data
**Age threshold:** Under 18 years.
**Section 9(1):** Verifiable parental/lawful guardian consent required before any child data processing.
**Section 9(2) - Prohibited processing (no exceptions unless prescribed):**
- Tracking or behavioural monitoring of children
- Targeted advertising directed at children
- Any processing likely to cause detrimental effect on child's well-being
**Section 9(3) - Exemptions:** May be prescribed for certain classes of Data Fiduciaries (health, safety, education, essential services).
**Penalty:** Maximum ₹200 crore per violation. One of the highest penalty tiers.
### Section 10 - Additional Obligations of Significant Data Fiduciaries
**Designation:** Central Government notifies entities as SDFs based on:
- Volume and sensitivity of data processed
- Risk of harm to Data Principals' rights
- Impact on India's sovereignty, integrity, security
- Risk to electoral democracy or public order
**Additional obligations (beyond Section 8):**
- **India-based Data Protection Officer** - individual resident in India; sole Board representative; Data Principal grievance contact
- **Annual Data Protection Impact Assessment (DPIA)** - evaluates compliance, Data Principal rights exercise, safeguard adequacy, large-scale processing risks
- **Annual independent data audit** - by qualified external auditor; report submitted to the Board
- **Data localization** - specified data categories must remain within India (when notified)
- **Comply with any other prescribed measures** as directed by government
---
## Chapter III - Rights and Duties of Data Principal (Sections 11–15)
### Section 11 - Right to Access Information
Data Principals may request, and Data Fiduciaries must provide (within prescribed period):
- Summary of personal data being processed
- Description of the processing activities (purpose, legal basis, duration)
- Identities and contact details of all Data Fiduciaries and Processors holding or processing the data
- Description of personal data shared with each recipient
### Section 12 - Right to Correction, Completion, Updating, and Erasure
Data Principals may:
- **(12(1)(a))** Request correction of inaccurate or misleading personal data
- **(12(1)(b))** Request completion of incomplete personal data
- **(12(1)(c))** Request updating of outdated personal data
- **(12(3))** Request erasure of personal data no longer necessary for the specified purpose
**Limitations on erasure (Section 12(4)):**
Data Fiduciaries may refuse erasure where:
- Retention necessary for the specified purpose
- Retention required by law (statutory record-keeping)
- Retention necessary to enforce/defend legal rights or claims
### Section 13 - Right of Grievance Redressal
- Data Principals must have access to an effective grievance mechanism provided by the Data Fiduciary or Consent Manager
- Mechanism must be accessible, responsive, and as prescribed by rules
- Data Fiduciaries must respond within the prescribed timeframe
- **Mandatory exhaustion:** Data Principals must exhaust the Fiduciary's grievance mechanism before filing a complaint with the Data Protection Board
### Section 14 - Right to Nominate
Data Principals may nominate an individual to exercise their Section 11, 12, and 13 rights in the event of:
- Death of the Data Principal, or
- Incapacity (defined as unsoundness of mind or infirmity of body rendering the Principal unable to exercise rights)
Nominees exercise rights as if they were the Data Principal.
### Section 15 - Duties of Data Principal
Data Principals must:
- Comply with all applicable laws when exercising rights
- Not register false or frivolous complaints with Fiduciaries or the Board
- Not furnish false particulars or suppress material information
- Not impersonate another individual
- Not misuse their rights to harass Data Fiduciaries
Breach of these duties: penalty up to **₹10,000** (personal liability).
---
## Chapter IV - Special Provisions (Sections 16–17)
### Section 16 - Transfer of Personal Data Outside India
**Mechanism: Blacklist approach**
Data Fiduciaries may transfer personal data outside India to **any country or territory**, EXCEPT those specifically **notified by the Central Government as restricted**.
**Current status (April 2026):** No countries have been notified. All transfers currently permitted.
**Government notification power:** Central Government may restrict transfers based on national security concerns, weak data protection frameworks, public policy considerations. Monitor MeitY Official Gazette.
**Operational guidance:**
- Transfers permitted to all countries absent a notification
- Apply contractual safeguards with recipients regardless
- Do not assume permanent unrestricted status; plan for potential future restrictions
- Sensitive data categories: apply enhanced protection even when transfer is technically permitted
### Section 17 - Exemptions
Exemptions from Chapters II, III, and Section 16:
| Provision | Category | Scope of Exemption |
|-----------|----------|-------------------|
| 17(1)(a) | Legal rights enforcement | Processing to enforce legal rights or claims |
| 17(1)(b) | Judicial/regulatory functions | Courts, tribunals, regulatory/supervisory bodies in official capacity |
| 17(1)(c) | Law enforcement | Prevention, detection, investigation, prosecution of offences |
| 17(1)(d) | Offshore processing / foreign contracts | Processing within India of personal data of Data Principals not within India, under a contract with a person outside India |
| 17(1)(e) | Mergers and schemes | Processing necessary for approved schemes of merger, amalgamation, demerger, or similar arrangements |
| 17(1)(f) | Loan-default financial information | Processing to ascertain financial information, assets, and liabilities of a loan defaulter |
| 17(2)(a) | State security (notified) | State instrumentalities notified by Central Government - sovereignty, integrity, security, public order, friendly foreign relations |
| 17(2)(b) | Research and statistics | Research, archiving, statistical processing not used for decisions specific to a Data Principal, per prescribed standards |
| 17(3) | Startups and notified classes | Central Government may notify startups and certain classes of Data Fiduciaries as exempt from Sections 5, 8(3), 8(7), 10 and 11 |
**Note:** Section 17(1) contains clauses (a)–(f) only; there are no clauses (g)–(j).
---
## Chapter V - Data Protection Board of India (Sections 18–26)
### Section 18 - Establishment
Creates the Data Protection Board of India as a **body corporate** with perpetual succession; power to acquire/hold/dispose property; to contract; to sue and be sued.
### Section 19 - Composition
- **Chairperson** - Appointed by Central Government; expertise in data governance, IT, cyber law, public administration
- **Members** - Notified number; appointed by Central Government; similar qualification criteria
### Section 20–21 - Tenure and Removal
Fixed terms; removal possible only for misconduct, incapacity, or insolvency.
### Sections 22–24 - Officers, Employees, and Board Administration
Appointment of officers and employees of the Board and related administrative and service provisions (consult the Act text for exact titles).
### Section 25 - Members and Officers Deemed Public Servants
The Chairperson, Members, officers, and employees of the Board are **deemed public servants** - enabling criminal liability for breach of duty.
### Section 26 - Other Chapter V Provisions
Remaining Board-related provision of Chapter V (consult the Act text for the exact title).
---
## Chapter VI - Powers, Functions and Procedure of the Board (Sections 27–28)
### Section 27 - Powers and Functions of the Board
- Receive and adjudicate complaints from Data Principals
- Investigate personal data breaches
- Issue financial penalties
- Issue binding compliance directions
- Accept voluntary undertakings from Data Fiduciaries
### Section 28 - Procedure of the Board
Board functions as a digital office and conducts proceedings consistent with natural justice (right to be heard, impartial adjudication), including evidence presentation and examination.
---
## Chapter VII - Appeal and Alternate Dispute Resolution (Sections 29–32)
### Sections 29–30 - Appeal to TDSAT and Related Appellate Provisions
Orders of the Board may be appealed to the **Telecom Disputes Settlement and Appellate Tribunal (TDSAT)** within the prescribed period (Section 29). Section 30 contains related appellate provisions (consult the Act text for the exact title).
### Section 31 - Alternate Dispute Resolution
Board may refer disputes to mediation or other dispute resolution processes between Data Principals and Data Fiduciaries.
### Section 32 - Voluntary Undertaking
Data Fiduciaries may offer voluntary undertakings to remedy violations. Board may accept. Breach of an accepted voluntary undertaking is treated as a breach of the Act: the penalty is capped at the extent applicable to the underlying breach in respect of which the undertaking was given (no separate flat cap).
---
## Chapter VIII - Penalties and Adjudication (Sections 33–34)
### Section 33 - Financial Penalties
**Penalty Schedule:**
| Violation | Maximum Penalty |
|-----------|----------------|
| Failure to implement reasonable security safeguards (Section 8(5)) | ₹250 crore |
| Failure to give notice of a personal data breach (Section 8(6)/Rule 7) | ₹200 crore |
| Violation of children's data obligations (Section 9) | ₹200 crore |
| SDF non-compliance with additional obligations (Section 10) | ₹150 crore |
| Breach of voluntary undertaking (Section 32) | Up to the extent applicable for the underlying breach (no separate flat cap) |
| Other violations (Schedule residual item) | ₹50 crore |
| Data Principal duty violation (false complaints, impersonation) | ₹10,000 |
**Section 33(2) - Factors (a)–(g) for penalty determination:**
1. Nature, gravity, and duration of the breach
2. Type and nature of the personal data affected
3. Repetitive nature of the breach
4. Whether the person realised a gain or avoided a loss as a result of the breach
5. Action taken to mitigate the effects and consequences, and its timeliness and effectiveness
6. Whether the penalty is proportionate and effective (observance and deterrence)
7. Likely impact of the penalty on the person
### Section 34 - Crediting of Penalties
All penalty amounts credited to the Consolidated Fund of India.
---
## Chapter IX - Miscellaneous (Sections 35–44)
### Section 35 - Protection of Action Taken in Good Faith
No suit, prosecution, or other legal proceeding lies against the Central Government, the Board, or its Chairperson, Members, officers, or employees for anything done in good faith under the Act or the Rules.
### Sections 36–39 and 41–42
Other miscellaneous provisions, including the power to call for information and related machinery provisions (consult the Act text for exact titles).
### Section 40 - Power to Make Rules
Central Government has the power to make rules to carry out the provisions of the Act. Rules subject to laying before Parliament.
### Section 43 - Power to Remove Difficulties
Central Government may, by order, make provisions to remove difficulties arising in giving effect to the Act.
### Section 44 - Amendments to Other Laws
Section 44 amends:
- The **Telecom Regulatory Authority of India (TRAI) Act, 1997**
- The **Information Technology Act, 2000** - Section 43A (compensation for failure to protect data) is **omitted**; Section 72A of the IT Act is **not** amended and remains in force
- The **Right to Information Act, 2005** - Section 8(1)(j) (personal information exemption) is amended
The DPDPA is the lex specialis for digital personal data protection; the IT Act's Section 43A compensation regime no longer applies.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |