hashgraph-online/awesome-codex-plugins / plugins/AltByteSG/personal-data-protection-skill/skills/personal-data-protection
personal-data-protection
VerifiedPersonal-data-protection compliance reference for engineers building applications subject to Singapore PDPA, Indonesia UU PDP, Thailand PDPA, Malaysia PDPA, Philippines DPA (RA 10173), or Vietnam PDPL (91/2025/QH15). Use when reviewing or modifying code that touches personal data — signup/auth/consent, data export, account deletion, retention/purging, admin access to personal-data stores, third-party processors, breach response, or privacy/T&C documents.
jurisdictions/vn-pdpl/obligations/01-accountability.md
View on GitHub# Accountability and Governance — Điều 33–37 + Decree Điều 13–16
> ⚠ **Reference material only — not legal advice.** See [DISCLAIMER.md](https://github.com/AltByteSG/personal-data-protection-skill/blob/main/DISCLAIMER.md). Verify against the official statute and consult a qualified DPO / lawyer.
>
> **Unofficial translation.** Law 91/2025/QH15 and Decree 356/2025/NĐ-CP have no official
> English version. English wording below is the maintainer's rendering of the Vietnamese;
> load-bearing terms carry the original. **In any conflict the Vietnamese wins.** See the
> translation caveat in [README.md](../README.md).
## Điều 33 — Personal data protection force
The protection force comprises (Điều 33(1)): the specialised authority under the **Ministry of Public Security**; the **unit or personnel** inside each agency or organisation; **service providers**; and mobilised parties.
**Điều 33(2) — the operative duty:** every agency and organisation must **designate a unit or personnel with adequate protection capability, or engage a service provider**.
**No threshold.** Unlike MY (JPDP guideline at 20,000 subjects) or TH (core-activity test), this applies to every organisation in scope. The only relief is the Điều 38 transition for small, startup, household and micro entities — and that falls away for anyone processing sensitive data or data of a large number of subjects.
Decree Điều 13 sets the **conditions** for that personnel, Điều 14 their **duties**, and Điều 15–16 the regime for individual and organisational **service providers**.
### Decree Điều 14 — what the unit is actually responsible for
- a) Building **policies, procedures, regulations and forms** for compliance
- b) Implementing **data subject rights** operationally
- c) **Periodic self-assessment** of the organisation's compliance, as a report measuring performance against statutory obligations, proposing improvements and risk controls
- d) Preparing the **cross-border transfer impact assessment** dossier
Point (c) is worth noting: a periodic written compliance self-assessment is expected, not optional. That is an artefact to schedule, alongside the Điều 22 six-month dossier review.
**Implementation layer:** [01 Non-technical](../../../layers/01-non-technical.md), [04 Controls](../../../layers/04-controls-and-processes.md).
## Điều 37 — Responsibilities of controller, processor, and controller-processor
Điều 37(1) sets the controller's duties. The engineering-relevant ones:
- a) **State each party's responsibilities, rights and obligations in the contract** covering processing
- b) Decide the **purpose and means** of processing in the documents and agreements with the subject
- c) Apply appropriate **management and technical measures**, and **review and update them when necessary**
- d) **Notify violations under Điều 23**
- đ) **Select an appropriate processor**
- e) **Ensure the data subject rights in Điều 4**
- g) **Be liable to the data subject for damage caused by processing**
- h) **Prevent unauthorised collection of personal data from its own systems, equipment and services**
- i) Coordinate with the Ministry of Public Security and competent state agencies
Limb (h) is unusual and specific: you are responsible for stopping *others* scraping or harvesting personal data out of your product. Rate limiting, bot defence and enumeration protection on endpoints exposing personal data become compliance measures here, not just abuse controls.
Limb (đ) makes processor selection a named statutory duty — vendor due diligence is evidence, not hygiene.
**Implementation layer:** [02 Architecture](../../../layers/02-architecture.md), [04 Controls](../../../layers/04-controls-and-processes.md).
## What an inspection will ask you for — Điều 35 + Decree Điều 31
Inspection of protection activities is a live possibility, not a theoretical one: for cross-border transfers the regulator may inspect **annually as of right**, and without notice after a violation or data-loss incident (Điều 20(4)).
Everything it can ask for is an artefact you either have or do not. Keep these retrievable, not reconstructable:
- [ ] The **filed** processing-impact dossier, and its acknowledgement (Điều 21(1))
- [ ] The **filed** cross-border transfer dossier (Điều 20(2)), matching your current sub-processor list
- [ ] Evidence of the 6-monthly dossier review (Điều 22)
- [ ] Named data-protection personnel or the service-provider contract (Điều 33(2))
- [ ] The periodic compliance self-assessment (Decree Điều 14(1)(c))
- [ ] Consent records reproducible per purpose, in a verifiable format (Điều 9(3))
- [ ] Incident records and any `biên bản` confirmations (Điều 23(2))
The gap that bites is usually the second item: the transfer dossier is filed once and the vendor list moves on without it. Wire the dossier update into vendor onboarding.
Điều 34 (technical standards) and Điều 36 (state management) allocate responsibility between state bodies and carry no engineering surface.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |