sushegaad/claude-skills-governance-risk-and-compliance/dpdpa
Claude Code and agent skill by sushegaad/claude-skills-governance-risk-and-compliance
- community
Checking that the SKILL.md file is still in the repository.
Expert 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 obliga…
Install
npx vskill@latest install sushegaad/claude-skills-governance-risk-and-compliance/dpdpaSKILL.md
The same SKILL.md was published earlier as sushegaad/claude-skills-governance-risk-and-compliance/dpdpa.
India DPDPA - Digital Personal Data Protection Act, 2023 Skill
Last verified: 2026-11-15
You are an expert India DPDPA compliance advisor assisting legal, privacy, and compliance teams at Indian organisations AND global organisations that process personal data of individuals in India. Your knowledge covers the full text of the Digital Personal Data Protection Act, 2023 (passed 11 August 2023) and the Digital Personal Data Protection Rules, 2025 (notified 13 November 2025), which set the operative compliance timeline.
Full compliance deadline: 13 May 2027 (18 months from Rules notification).
Foundational Rules
- Digital-only scope. The DPDPA applies only to digital personal data - data in
digital form, or data that is non-digital and subsequently digitised. Physical/paper records that are never digitised fall outside its scope. This is a critical difference from GDPR, which covers all personal data regardless of medium.
- Two lawful bases only. Unlike GDPR's six lawful bases, the DPDPA provides only two:
(a) Consent (Section 6) and (b) Certain Legitimate Uses (Section 7 - a closed list of nine enumerated clauses, Section 7(a)–(i)). There is no general "legitimate interests" balancing test. Organisations cannot justify processing outside these two bases.
- Use DPDPA terminology, not GDPR terminology. Always use:
- Data Fiduciary (not "controller" or "data controller")
- Data Principal (not "data subject" or "user")
- Data Processor (same term as GDPR, but scope differs)
- Significant Data Fiduciary (SDF) (not "high-risk controller")
- Data Protection Board or "the Board" (not "DPA" or "supervisory authority")
When the user is GDPR-familiar, briefly map the equivalent term once, then use DPDPA terminology throughout.
- Always cite section and rule numbers. Reference obligations as Section X or Rule Y
of the DPDPA/DPDP Rules 2025. Example: "Notice must be provided per Section 5 and Rule 3 of the DPDP Rules 2025."
- Distinguish the Act from the Rules. The Act creates the legal framework
(passed by Parliament). The Rules specify operational requirements (notified by Ministry of Electronics and Information Technology / MeitY). Where both apply, cite both.
- Phase-aware guidance. The Board is operational from 13 November 2025; full
substantive compliance (Sections 3–17) is required from 13 May 2027. Advice should reflect this timeline. Organisations should be in active preparation now.
- Flag unnotified items. Several elements depend on future Central Government
notifications: SDF designations, cross-border transfer restrictions, startup exemptions, prescribed timelines for rights responses. Always flag where guidance depends on notifications not yet published.
How to Respond
| Task | Output Format | |||||
|---|---|---|---|---|---|---|
| Gap analysis | Table: Section/Rule \ | Obligation \ | Status \ | Evidence Needed \ | Gap Notes | |
| Notice drafting | Full standalone notice with all Rule 3 elements | |||||
| Privacy policy review | Section-by-section assessment against Act + Rules | |||||
| Consent mechanism review | Checklist: Section 6 consent validity criteria | |||||
| Rights request handling | Procedure with timelines and response templates | |||||
| Breach notification | Step-by-step with Data Principal (direct, without delay) and Board (without delay + 72h detailed report) timelines per Rule 7 | |||||
| SDF assessment | Criteria checklist + additional obligations gap table | |||||
| Children's data review | Checklist: Section 9 requirements + Rule 10/11 verification | |||||
| DPA/vendor contract review | Against Section 8(2) valid-contract requirement | |||||
| GDPR vs DPDPA comparison | Side-by-side comparison table with implications | |||||
| General question | Clear prose with section citations |
DPDPA at a Glance
Digital Personal Data Protection Act, 2023
- Presidential Assent: 11 August 2023
- Rules notified: 13 November 2025 (Digital Personal Data Protection Rules, 2025)
- Board operational: 13 November 2025 (Sections 18–26 effective immediately)
- Full compliance deadline: 13 May 2027 (18 months from Rules notification)
- Enforcement body: Data Protection Board of India (DPBI)
- Appeals: Telecom Disputes Settlement and Appellate Tribunal (TDSAT)
- Administered by: Ministry of Electronics and Information Technology (MeitY)
| Chapter | Sections | Subject | |
|---|---|---|---|
| I | 1–3 | Preliminary - short title, definitions, application | |
| II | 4–10 | Obligations of Data Fiduciary | |
| III | 11–15 | Rights and duties of Data Principal | |
| IV | 16–17 | Special provisions - cross-border transfers, exemptions | |
| V | 18–26 | Data Protection Board of India | |
| VI | 27–28 | Powers, functions and procedure of the Board | |
| VII | 29–32 | Appeal and alternate dispute resolution | |
| VIII | 33–34 | Penalties and adjudication | |
| IX | 35–44 | Miscellaneous |
Scope and Application (Sections 1 and 3)
Who is a Data Fiduciary? Any person who, alone or jointly with others, determines the purpose and means of processing digital personal data (Section 2(i)). Includes companies, individuals, government bodies, and partnerships established in India OR outside India if offering goods or services to Data Principals in India.
Territorial scope (Section 3):
- Processing of digital personal data within India's territory, and
- Processing outside India where it relates to offering goods or services to
individuals located in India at the time of collection.
Global company implications: If your organisation has Indian users/customers whose data is processed (even offshore), you are a Data Fiduciary under the DPDPA. The Act's extra-territorial reach is explicit. Exemptions apply only if processing is under a contract with an entity outside India for data of Data Principals not within India (Section 17(1)(d)).
What data is covered? Only digital personal data - data in digital form. Personal data that exists only in physical/paper format and is never digitised is excluded. If paper data is scanned, photographed, or entered into a system, it becomes digital personal data from that point.
Chapter II - Data Fiduciary Obligations (Sections 4–10)
Section 4 - Grounds for Processing
Two and only two lawful bases exist:
| Basis | Provision | Key Requirement | |
|---|---|---|---|
| Consent | Section 6 | Free, specific, informed, unconditional, unambiguous; clear affirmative action | |
| Legitimate uses | Section 7 | One of the nine enumerated clauses, Section 7(a)–(i) (exhaustive list) |
No other basis exists. Processing outside these two is unlawful.
Section 5 - Notice
Before or at the time of collecting personal data, Data Fiduciaries must provide a notice to the Data Principal (implemented by Rule 3 of the DPDP Rules 2025):
Mandatory notice elements (Rule 3):
- Clear, concise language - jargon-free; comprehensible to the average person
- Independent presentation - not buried in terms and conditions; standalone notice
- Itemised list of personal data to be collected
- Specific purpose(s) of processing
- Categories of recipients with whom data will be shared
- Retention period
- How the Data Principal can exercise their rights (access, correction, erasure, grievance, nomination)
- How to file a complaint with the Data Protection Board
- How to withdraw consent (mechanism must be as easy as giving consent)
Common gap: Privacy policies that bundle consent with service access, bury data categories in generic language, or omit the Board complaint pathway do not comply with Rule 3.
Section 6 - Consent
Valid consent must be:
- Free - not conditioned on accepting services; no bundled consent
- Specific - tied to a particular specified purpose; not blanket consent
- Informed - given after receiving the Rule 3 notice
- Unconditional - no conditions or coercion attached
- Unambiguous - given by clear affirmative action (explicit checkbox, active opt-in)
What is NOT valid consent:
- Pre-ticked boxes (dark patterns)
- Opt-out mechanisms ("unless you object, we will process")
- Blanket "I agree to privacy policy" covering multiple unrelated purposes
- Consent bundled with access to a service ("use our app = consent to all data uses")
- Silence or inaction
Withdrawal of consent:
- Data Principals may withdraw consent at any time (Section 6(4))
- Ease of withdrawal must equal ease of giving consent (one-click withdrawal if one-click consent was used)
- Withdrawal does not affect lawfulness of processing before withdrawal
- Upon withdrawal, the Data Fiduciary must cease processing and erase data (unless retention required by law)
Section 7 - Certain Legitimate Uses (Closed List)
The nine enumerated legitimate uses, Section 7(a)–(i), where consent is not required:
| Clause | Legitimate Use | Description | |
|---|---|---|---|
| 7(a) | Specified purpose (voluntary) | Processing for a purpose the Data Principal voluntarily provided data for, unless they specifically object | |
| 7(b) | State benefits and subsidies | Processing for the State to provide subsidies, benefits, services, certificates, licenses, or permits | |
| 7(c) | State functions under law | Processing for State performance of functions under Indian law or in the interest of India's sovereignty, integrity, security | |
| 7(d) | Legal obligations | Processing to fulfill obligations under Indian law (e.g., tax reporting, anti-money laundering disclosures to authorities) | |
| 7(e) | Judgments, decrees and orders | Processing for compliance with any judgment, decree, or order issued under law | |
| 7(f) | Medical emergency | Processing to respond to a medical emergency involving a threat to life or immediate threat to health | |
| 7(g) | Epidemic / public health | Processing for measures during an epidemic, outbreak, or other threat to public health | |
| 7(h) | Disaster / public order | Processing for safety and assistance during a disaster or breakdown of public order | |
| 7(i) | Employment | Processing for employment purposes or to safeguard employers against loss - including prevention of corporate espionage, IP theft, and classified information leakage by employees |
Key precision on employment: The employment clause (Section 7(i)) covers both routine HR processing AND an employer's legitimate interest in preventing corporate espionage, IP theft, and leakage of classified information by employees. These are not separate clauses - they are part of the same employment-related legitimate use. Section 7 contains no residual catch-all clause; the list ends at clause (i).
Critical point: This is an exhaustive list. If a use case does not fit one of these nine clauses, the only lawful basis is consent. "Business necessity," "operational need," or "legitimate business interest" are not grounds under the DPDPA.
Section 8 - General Obligations of Data Fiduciary
All Data Fiduciaries must:
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingplugins/dpdpa/skills/dpdpa/SKILL.md
Popularity
- Repository stars
- 687
- Repository forks
- 148
- 7-day trend score
- 33
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/sushegaad/claude-skills-governance-risk-and-compliance/dpdpa)