Sushegaad/Claude-Skills-Governance-Risk-and-Compliance / plugins/vn-pdpl/skills/vn-pdpl
vn-pdpl
VerifiedExpert Vietnam Personal Data Protection Law (PDPL) compliance advisor for Law No. 91/2025/QH15 and implementing Decree 356/2025/ND-CP (effective January 1, 2026). Use this skill for gap analysis against the Vietnam PDPL, data subject rights fulfilment workflows, cross-border data transfer impact assessments, privacy notices and internal policies, breach notification procedures, sector-specific obligations (finance, AI, cloud, blockchain), and DPO qualification reviews. Trigger whenever a user mentions Vietnam data privacy, VN-PDPL, Nghị định 356, Vietnamese personal data, or cross-border transfers involving Vietnamese citizens' data.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.0 KB |
| references/articles-overview.md | markdown | 12.9 KB |
| references/decree-356-implementation.md | markdown | 14.3 KB |
references/articles-overview.md
View on GitHub# Vietnam PDPL - Law No. 91/2025/QH15: Articles Overview
## Table of Contents
1. [Law Structure](#law-structure)
2. [Article 2 - Definitions](#article-2--definitions)
3. [Article 3 - Principles](#article-3--principles)
4. [Article 4 - Data Subject Rights](#article-4--data-subject-rights)
5. [Article 5 - Application of Personal Data Protection Laws](#article-5--application-of-laws)
6. [Article 37 - Responsibilities of Controllers and Processors](#article-37--responsibilities)
7. [Article 8 - Penalties](#article-8--penalties)
8. [Article 9 - Consent](#article-9--consent)
9. [Article 10 - Consent for Sensitive Data](#article-10--consent-for-sensitive-data)
10. [Article 19 - Processing Without Consent](#article-19--processing-without-consent)
11. [Article 20 - Cross-Border Transfer](#article-20--cross-border-transfer)
12. [Article 21 - Impact Assessment (DPIA)](#article-21--impact-assessment-dpia)
13. [Article 23 - Breach Notification](#article-23--breach-notification)
14. [Article 38 - Entry into Force](#article-38--entry-into-force)
15. [Article 39 - Transitional Provisions](#article-39--transitional-provisions)
---
## Law Structure
The law has **5 chapters and 39 articles**:
| Chapter | Title | Articles |
|---|---|---|
| Chapter I | General Provisions | 1–8 |
| Chapter II | Personal Data Protection | 9–32 |
| Chapter III | Forces and Conditions for Personal Data Protection | 33–35 |
| Chapter IV | Responsibilities | 36–37 |
| Chapter V | Implementation Provisions | 38–39 |
**Chapter II sector-specific articles (Arts. 25–32):**
| Article | Sector / Context |
|---|---|
| 25 | Recruitment and employee data |
| 26 | Health and insurance |
| 27 | Finance, banking, and credit |
| 28 | Advertising |
| 29 | Social media and online services |
| 30 | Big data, AI, blockchain, metaverse, and cloud computing |
| 31 | Location and biometric data |
| 32 | Public recording (audio/video in public places) |
**Administering authority:** Ministry of Public Security (specialized agency for personal data protection)
---
## Article 2 - Definitions
| Term | Definition |
|---|---|
| **Personal data** | Digital data that identifies or can identify a specific natural person; divided into basic and sensitive |
| **Basic personal data** | Defined **abstractly** in the Law; Article 2 delegates the enumeration to the Government. The operative list is in **Decree 356 Article 3**: 10 enumerated categories plus a catch-all item 11, so the list is **non-exhaustive** |
| **Sensitive personal data** | Defined **abstractly** in the Law; Article 2 delegates the enumeration to the Government. The operative list is in **Decree 356 Article 4**: 12 enumerated categories plus a catch-all item (m), so the list is **open-ended** |
| **Processing** | Any operation on personal data including collection, recording, analysis, storage, disclosure, combination, access, retrieval, erasure, or destruction |
| **Personal data controller** | Organisation or individual that decides the purpose and means of processing |
| **Personal data processor** | Organisation or individual that processes personal data at the request of the controller |
| **Controlling-and-processing party** | An entity that both decides purposes AND directly processes personal data |
| **Third party** | Any participant in processing other than the data subject, controller, and processor |
| **De-identification** | Process of removing all information that identifies a specific individual |
| **Impact assessment** | Analysis of impacts and risks arising from personal data processing |
---
## Article 3 - Principles of Personal Data Processing
1. **Lawfulness** - processing must have a valid legal basis
2. **Purpose limitation** - data collected for specified, explicit, legitimate purposes; no further processing incompatible with original purpose
3. **Data minimisation** - collect only what is necessary for the stated purpose
4. **Accuracy** - data must be accurate and kept up to date
5. **Synchronous security measures** - security controls must be implemented before and during processing
6. **Proactive prevention** - risks must be identified and prevented before harm occurs
7. **Harmony with national interests** - processing must not threaten national security, social order, or legitimate rights of other organisations/individuals
---
## Article 4 - Data Subject Rights
Article 4 sets out the rights of data subjects and also their **obligations** (data subjects must comply with the duties the article prescribes alongside their rights).
Data subjects have the following **6 rights**:
**a) Right to be informed:** Know what personal data is processed, by whom, for what purpose, and how.
**b) Right to consent / disagree / withdraw consent:** Give, withhold, or withdraw consent at any time; withdrawal does not affect the lawfulness of prior processing.
**c) Right to access and rectify:** View their personal data and request corrections to inaccurate data.
**d) Right to delete, restrict, or object:** Request erasure of data, restriction of processing, or object to processing for specific purposes.
**e) Right to file complaints, lawsuits, and seek compensation:** Lodge complaints with competent authorities, bring legal action, and claim damages for violations.
**f) Right to request protection measures:** Request authorities to take measures to protect their personal data rights.
**Important distinctions from GDPR:**
- No explicit right to data portability
- No explicit right to human review of automated decisions (but Decree 356 requires opt-out for AI/automated processing)
- Withdrawal of consent does not retroactively invalidate prior processing
---
## Article 5 - Application of Personal Data Protection Laws
Article 5 contains the **lex specialis rules** on how the PDPL interacts with other laws governing data:
- It determines which law applies where the PDPL and other data-related laws both address a matter
- A personal data protection impact assessment conducted under the PDPL **satisfies equivalent assessment duties under other data laws** (one assessment, multiple statutory purposes)
---
## Article 37 - Responsibilities of Controllers and Processors
The controller/processor obligations catalogue sits in **Article 37** (Chapter IV, Responsibilities), not Article 5.
**Controllers must:**
- Establish and maintain a lawful basis for all processing
- Implement technical and organisational security measures
- Notify data subjects of processing activities
- Respond to data subject rights requests within required timeframes
- Notify the authority of breaches within 72 hours
- Conduct impact assessments for new processing (unless SME exempt)
- Appoint a DPO (where required)
**Processors must:**
- Process only on documented instructions from the controller
- Implement security measures equivalent to controller requirements
- Assist controller in fulfilling data subject rights
- Notify controller immediately of any breach
- Delete or return data at end of processing relationship
---
## Article 8 - Penalties
| Violation | Organisation | Individual |
|---|---|---|
| Buying/selling personal data | 10× the proceeds | 10× the proceeds |
| Cross-border transfer violations | Up to 5% of preceding year's revenue in Vietnam | VND 1.5 billion |
| Violations causing serious harm | VND 3 billion | VND 1.5 billion |
| Other administrative violations | Proportional to severity | Half of organisation rate |
**Note:** Criminal liability may also apply under the Penal Code for serious violations.
---
## Article 9 - Consent
**Validity requirements:**
- **Voluntary** - not coerced or made a condition of service where unnecessary
- **Explicit** - clear affirmative action; silence, inaction, or pre-ticked boxes do NOT constitute consent
- **Specific** - separate consent for each distinct purpose
- **Informed** - data subject must know what they are consenting to
- **Recorded** - controller must maintain proof of consent
**Consent must specify:**
- The type of personal data
- The purpose of processing
- The organisation processing the data
- The rights of the data subject
**Withdrawal:** Data subjects may withdraw consent at any time. Processing must cease within the relevant timeframe (15 working days per Decree 356 Article 5). Withdrawal does not affect legality of prior processing.
---
## Article 10 - Consent for Sensitive Personal Data
- **Explicit, separate consent** required for each category of sensitive data
- Controller must clearly distinguish sensitive data consent from general consent
- Processing sensitive data without separate explicit consent is a violation subject to higher penalties
- Children's sensitive data requires consent of parent or legal guardian
---
## Article 19 - Processing Without Consent (Legal Bases Other Than Consent)
Processing without consent is permitted only in these **5 cases**:
1. **Emergency situations** - to protect the life or health of the data subject or another person when the data subject is incapable of giving consent
2. **National/public security threats** - at the request of competent state agencies in accordance with law
3. **State agency statutory functions** - public bodies processing data in exercising their legally assigned functions
4. **Contract performance** - processing is necessary for performance of a contract to which the data subject is party
5. **Other cases as prescribed by law** - specific sectoral laws may permit additional bases
**Note:** This is narrower than GDPR's 6 lawful bases. Legitimate interests is not a standalone basis under VN-PDPL.
---
## Article 20 - Cross-Border Transfer of Personal Data
**General rule:** Personal data of Vietnamese data subjects may be transferred abroad subject to impact assessment.
**Impact assessment dossier:**
- Submit to Ministry of Public Security **within 60 days** of the first transfer
- Must describe: the data to be transferred, recipient, recipient country, purpose, security measures, risk mitigation
- **Update every 6 months** or immediately on any material change (change in purpose, data types, recipient, or security measures)
**Authority's power:** Ministry may **suspend or terminate** a cross-border transfer if it finds a national security, public interest, or other significant risk.
**Exceptions (no impact assessment required):**
1. State agencies exercising statutory functions
2. Organisations storing employee personal data in cloud HR systems (within scope)
3. Data subjects transferring their own data
4. Other cases as the Government may determine
**Penalties for violation:** Up to 5% of the organisation's preceding year's Vietnam revenue.
---
## Article 21 - Impact Assessment (DPIA)
**Trigger:** Any organisation commencing personal data processing.
**Timeline:** Submit to Ministry of Public Security **within 60 days** of first processing.
**Content:**
- Type and scope of personal data processed
- Purpose and legal basis
- Processing methods and third parties involved
- Retention periods
- Security measures (technical and organisational)
- Risk assessment and mitigation
**SME Exemptions:**
- **Small enterprises:** May opt out of Article 21 for 5 years from 1 January 2026, **unless** they process sensitive personal data or process at large scale
- **Micro-enterprises:** Fully exempt unless they process sensitive personal data or at large scale
- Exemption election must be documented
---
## Article 23 - Breach Notification
**72-hour rule:** Personal data controllers must notify the personal data protection authority **within 72 hours** of becoming aware of a breach.
**Notification must include:**
- Description of the nature of the breach
- Categories and approximate number of data subjects affected
- Categories and approximate number of records affected
- Name and contact details of DPO or responsible officer
- Likely consequences of the breach
- Measures taken or proposed to address the breach
**Data subject notification:** Notify affected data subjects simultaneously with or as soon as practicable after the authority notification, unless law enforcement restricts disclosure.
**Internal breach register:** Controllers must maintain a register of all personal data breaches, whether or not they trigger notification obligations.
---
## Article 38 - Entry into Force
Article 38 contains **both** the effective date and the SME/startup opt-out:
- **Law effective date:** 1 January 2026
- **SME/startup opt-out:** small enterprises and startups may opt out of Articles 21, 22, and 33(2) for **5 years** from the effective date - unless they process sensitive data or at large scale
- **Micro-enterprises and household businesses:** exempt from those articles on the same conditions
---
## Article 39 - Transitional Provisions
- **Decree 13-era consents remain valid:** consents lawfully obtained under the prior Decree 13/2023 regime do not need to be re-collected
- **Decree 13-era dossiers remain valid:** impact assessment dossiers submitted under the prior regime continue to be recognised
- **Decree 356** (implementing decree): 31 December 2025, effective 1 January 2026; from 1 January 2026 full compliance with the new framework is required
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 |