Skip to content

hashgraph-online/awesome-codex-plugins / plugins/AltByteSG/personal-data-protection-skill/skills/personal-data-protection

personal-data-protection

Verified

Personal-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.

FileKindSize
SKILL.mdskill md14.5 KB
checklists/breach-response.mdmarkdown5.6 KB
checklists/new-data-field.mdmarkdown6.8 KB
checklists/new-feature.mdmarkdown11.2 KB
checklists/new-vendor.mdmarkdown7.1 KB
jurisdictions/_index.mdmarkdown12.6 KB
jurisdictions/id-pdp/README.mdmarkdown8.7 KB
jurisdictions/id-pdp/obligations/01-accountability.mdmarkdown12.4 KB
jurisdictions/id-pdp/obligations/02-consent.mdmarkdown7.5 KB
jurisdictions/id-pdp/obligations/03-purpose.mdmarkdown7.0 KB
jurisdictions/id-pdp/obligations/04-access-correction.mdmarkdown8.9 KB
jurisdictions/id-pdp/obligations/05-care.mdmarkdown7.1 KB
jurisdictions/id-pdp/obligations/06-breach-notification.mdmarkdown7.4 KB
jurisdictions/id-pdp/obligations/07-offences.mdmarkdown7.6 KB
jurisdictions/id-pdp/statute-map.mdmarkdown12.5 KB
jurisdictions/my-pdpa/README.mdmarkdown10.2 KB
jurisdictions/my-pdpa/obligations/01-accountability.mdmarkdown6.5 KB
jurisdictions/my-pdpa/obligations/02-consent.mdmarkdown10.0 KB
jurisdictions/my-pdpa/obligations/03-purpose.mdmarkdown9.1 KB
jurisdictions/my-pdpa/obligations/04-access-correction.mdmarkdown11.1 KB
jurisdictions/my-pdpa/obligations/05-care.mdmarkdown11.5 KB
jurisdictions/my-pdpa/obligations/06-breach-notification.mdmarkdown7.6 KB
jurisdictions/my-pdpa/obligations/07-offences.mdmarkdown8.1 KB
jurisdictions/my-pdpa/statute-map.mdmarkdown10.4 KB
jurisdictions/ph-dpa/README.mdmarkdown12.8 KB
jurisdictions/ph-dpa/obligations/01-accountability.mdmarkdown8.3 KB
jurisdictions/ph-dpa/obligations/02-consent.mdmarkdown12.0 KB
jurisdictions/ph-dpa/obligations/03-purpose.mdmarkdown8.7 KB
jurisdictions/ph-dpa/obligations/04-access-correction.mdmarkdown13.4 KB
jurisdictions/ph-dpa/obligations/05-care.mdmarkdown13.6 KB
jurisdictions/ph-dpa/obligations/06-breach-notification.mdmarkdown11.2 KB
jurisdictions/ph-dpa/obligations/07-offences.mdmarkdown11.3 KB
jurisdictions/ph-dpa/statute-map.mdmarkdown10.9 KB
jurisdictions/sg-pdpa/README.mdmarkdown5.4 KB
jurisdictions/sg-pdpa/obligations/01-accountability.mdmarkdown4.0 KB
jurisdictions/sg-pdpa/obligations/02-consent.mdmarkdown6.9 KB
jurisdictions/sg-pdpa/obligations/03-purpose.mdmarkdown4.4 KB
jurisdictions/sg-pdpa/obligations/04-access-correction.mdmarkdown6.5 KB
jurisdictions/sg-pdpa/obligations/05-care.mdmarkdown6.9 KB
jurisdictions/sg-pdpa/obligations/06-breach-notification.mdmarkdown10.5 KB
jurisdictions/sg-pdpa/obligations/07-offences.mdmarkdown6.6 KB
jurisdictions/sg-pdpa/statute-map.mdmarkdown8.0 KB
jurisdictions/th-pdpa/README.mdmarkdown7.3 KB
jurisdictions/th-pdpa/obligations/01-accountability.mdmarkdown7.1 KB
jurisdictions/th-pdpa/obligations/02-consent.mdmarkdown8.5 KB
jurisdictions/th-pdpa/obligations/03-purpose.mdmarkdown4.9 KB
jurisdictions/th-pdpa/obligations/04-access-correction.mdmarkdown7.0 KB
jurisdictions/th-pdpa/obligations/05-care.mdmarkdown7.3 KB
jurisdictions/th-pdpa/obligations/06-breach-notification.mdmarkdown7.0 KB
jurisdictions/th-pdpa/obligations/07-offences.mdmarkdown8.5 KB
jurisdictions/th-pdpa/statute-map.mdmarkdown8.1 KB
jurisdictions/vn-pdpl/README.mdmarkdown9.9 KB
jurisdictions/vn-pdpl/obligations/01-accountability.mdmarkdown5.0 KB
jurisdictions/vn-pdpl/obligations/02-consent.mdmarkdown5.1 KB
jurisdictions/vn-pdpl/obligations/03-purpose.mdmarkdown6.7 KB
jurisdictions/vn-pdpl/obligations/04-access-correction.mdmarkdown4.9 KB
jurisdictions/vn-pdpl/obligations/05-care.mdmarkdown5.0 KB
jurisdictions/vn-pdpl/obligations/06-breach-notification.mdmarkdown5.6 KB
jurisdictions/vn-pdpl/obligations/07-offences.mdmarkdown3.0 KB
jurisdictions/vn-pdpl/obligations/08-sector-specific.mdmarkdown4.4 KB
jurisdictions/vn-pdpl/statute-map.mdmarkdown9.5 KB
layers/01-non-technical.mdmarkdown4.9 KB
layers/02-architecture.mdmarkdown8.0 KB
layers/03-data-model.mdmarkdown8.4 KB
layers/04-controls-and-processes.mdmarkdown9.1 KB
layers/05-feature-ux.mdmarkdown9.0 KB
layers/06-disclosure.mdmarkdown6.5 KB
layers/07-operational.mdmarkdown9.5 KB
templates/INCIDENT_RESPONSE.md.templateother13.2 KB
templates/pdp-nudge.sh.templateother4.5 KB

jurisdictions/vn-pdpl/obligations/02-consent.md

View on GitHub
# Consent and Lawful Processing — Điều 9, 10, 19

> ⚠ **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).

Vietnam does not offer a GDPR-style menu of lawful bases. **Consent is the rule** (Điều 9), and Điều 19 lists the closed set of cases where processing may proceed without it. Điều 10 governs withdrawal and restriction.

## Điều 9 — Consent of the data subject

**Rule:** consent is the data subject permitting the processing of their own personal data, unless the law provides otherwise (Điều 9(1)).

Consent is valid **only** where it is voluntary and the subject knows (Điều 9(2)):

- a) the **types** of personal data processed and the **purpose** of processing
- b) the **controller**, or controller-and-processor
- c) the **rights and obligations** of the data subject

**Form (Điều 9(3)):** consent must be expressed by a clear, specific method that can be **printed or copied in writing**, including electronic or **verifiable** formats. Detail is delegated to the Government (Điều 9(5)).

**Principles (Điều 9(4)) — these are the engineering constraints:**

- a) **Consent is per purpose.** One record per purpose, not one flag per user.
- b) **No bundling.** Consent must not be conditioned on also agreeing to purposes outside the agreed content.
- c) **Consent persists** until the subject changes it or the law provides otherwise.
- d) **Silence or non-response is not consent.** No pre-ticked boxes, no implied opt-in.

**Operationalisation:**

- One row per (subject, purpose) with timestamp, method, and the notice version shown — Điều 9(3)'s "printable or copyable" and "verifiable" requirements mean a boolean column is not enough; you must be able to reproduce what was agreed to.
- Store the notice text or a content hash alongside the record. "Verifiable" implies you can demonstrate *what* was consented to, not just that a click happened.
- Separate toggles per purpose, all defaulting to **off** (Điều 9(4)(d)).

**Implementation layer:** [05 Feature/UX](../../../layers/05-feature-ux.md), [03 Data model](../../../layers/03-data-model.md).

## Điều 10 — Withdrawal of consent and restriction of processing

**Rule:** the subject may withdraw consent, and may **request restriction** of processing where they doubt the scope or purpose of processing, or the accuracy of the data (Điều 10(1)) — except in the Điều 19 cases or where the law provides otherwise.

- **Form (Điều 10(2)):** the request must be **in writing**, including electronic or verifiable formats, and sent to the controller or controller-and-processor.
- **Effect (Điều 10(3)):** the controller receives and performs the request, and must require its **processors** to perform it too, within the period prescribed by law.
- **Not retroactive (Điều 10(4)):** withdrawal and restriction do not apply to processing carried out **before** the request.

**Operationalisation:**

- Withdrawal must fan out to sub-processors, not just flip a local flag — Điều 10(3) puts that propagation duty on you. Your DPA needs a matching flow-down clause.
- Restriction is a **state**, not a deletion: the record stays but further processing stops. Mutation paths must check it. This mirrors TH s34 and ID Pasal 41.
- Because withdrawal is not retroactive, do not retro-delete derived artefacts on withdrawal unless a separate deletion right applies — but do stop further use.

**Implementation layer:** [04 Controls](../../../layers/04-controls-and-processes.md), [03 Data model](../../../layers/03-data-model.md).

## Điều 19 — Processing without consent

Điều 19 sets the closed list of situations where personal data may be processed **without** the subject's consent. It is also the carve-out referenced by Điều 10(1), so a withdrawal or restriction request does not defeat processing that rests on an Điều 19 ground.

**Engineering consequence:** if a processing activity relies on Điều 19 rather than consent, record *which* ground, in the same place you record consent. When a withdrawal request arrives you need to answer, per purpose, whether that purpose was consent-based (stop) or Điều 19-based (continue, and tell the subject why).

**Implementation layer:** [03 Data model](../../../layers/03-data-model.md), [06 Disclosure](../../../layers/06-disclosure.md).

## Cross-jurisdiction note

Vietnam's per-purpose, no-bundling, no-silence rules land close to **ID Pasal 22** in strictness. If you already satisfy Indonesia's form-of-consent requirements, the VN gap is usually the **verifiable format** obligation in Điều 9(3) and the **processor fan-out** duty in Điều 10(3).
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 implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall