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/03-purpose.md

View on GitHub
# Principles, Data Classification and Purpose — Điều 3, 11, 16, 18 + Decree Điều 3, 4

> ⚠ **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 3 — Protection principles

1. Comply with the Constitution, this Law and related law.
2. **Collect and process only within the correct scope and a specific, clear purpose.**
3. Ensure **accuracy**, correct/update/supplement when necessary; store for a period **appropriate to the processing purpose**, unless the law provides otherwise.
4. Apply institutional, technical and human measures **synchronously and effectively**.
5. Proactively prevent, detect, stop and handle violations promptly.
6. Tie data protection to national interests, socio-economic development, defence, security and foreign affairs; balance protection against the lawful rights of agencies, organisations and individuals.

Principles 2 and 3 are the ones with direct engineering consequences: purpose limitation at collection, and retention tied to purpose rather than to a fixed default.

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

## Data classification — Decree 356/2025/NĐ-CP, Điều 3 and Điều 4

Law Điều 2(2) delegates the catalogue to Government decree. Decree 356/2025/NĐ-CP supplies both halves, and the structure matters: **sensitive is a closed list, basic is the residual**.

### Basic personal data — Decree Điều 3 (`dữ liệu cá nhân cơ bản`)

*Translated list — the Vietnamese original governs.*

1. Surname, middle name and birth name; other names
2. Date of birth; date of death or disappearance
3. Gender
4. Place of birth, birth registration, permanent residence, temporary residence, current residence, native place, contact address
5. Nationality
6. **Image of the individual**
7. Phone number, personal identification number, passport number, driving licence number, vehicle plate number
8. Marital status
9. Family relationship information (parents, children, spouse)
10. **Digital account information of the individual**
11. **Any other information tied to, or helping identify, a specific person that does not fall under Điều 4**

Item 11 makes this residual: if a field identifies a person and is not in the sensitive list, it is basic by default. There is no "not personal data" gap between the two catalogues.

### Sensitive personal data — Decree Điều 4(1) (`dữ liệu cá nhân nhạy cảm`)

*Translated list — the Vietnamese original governs. Where a classification decision is close, check the Vietnamese wording before relying on it.*

- a) Racial or ethnic origin
- b) Political, religious or belief views
- c) **Private life, personal secrets, family secrets**
- d) Health status
- đ) **Biometric data, genetic characteristics**
- e) Sex life, sexual orientation
- g) Crime and law-violation data collected and stored by law-enforcement agencies
- h) **Location of the individual determined through positioning services** (`vị trí của cá nhân được xác định qua dịch vụ định vị`)
- i) **Login name and password of an electronic identification account; images of the căn cước / căn cước công dân / chứng minh nhân dân ID cards**
- k) **Bank account login name and password; bank card information; bank account transaction history; financial and credit information; activity and transaction history in finance, securities and insurance** held at credit institutions, foreign bank branches, payment intermediaries, securities and insurance organisations
- l) **Behaviour-tracking data — use of telecommunications, social media, online communication and other cyberspace services** (`dữ liệu theo dõi hành vi`)
- m) Other personal data that the law requires to be kept secret or strictly secured

**Four of these will catch engineers out**, because they are not sensitive in SG, TH, ID, MY or PH:

| Item | Why it surprises |
|---|---|
| **(h) location** | GPS or positioning-derived location is sensitive outright — not "sensitive when paired with identity" |
| **(i) credentials + ID images** | An identity-document upload flow is a sensitive-data pipeline |
| **(k) financial** | Transaction history and card data are sensitive, far broader than elsewhere |
| **(l) behaviour tracking** | **Ordinary product analytics** — event streams on how users use your service — is sensitive personal data in Vietnam |

Item (l) is the one to check first on any new feature. A standard analytics SDK recording screen views and taps is processing sensitive personal data under Vietnamese law.

### Decree Điều 4(2) — mandatory controls for sensitive data

When processing sensitive personal data, organisations **must establish access-limiting permission rules, processing procedures, and security measures**. This is a positive obligation, not a recommendation: RLS or equivalent, a documented processing procedure, and stated security measures.

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

## Điều 16 — Publication, and the default-visibility trap

Điều 16 governs making personal data **public**. Read it before shipping any feature where a profile, post, list or activity is visible by default to anyone other than the user.

The failure mode is not a deliberate "publish" button — it is a default. A new profile field that inherits the profile's existing visibility, a social graph that exposes who follows whom, an activity feed that leaks a private action: each publishes personal data without anyone deciding to.

**Practical check on any new user-visible field:** what is its default audience, and did the user choose it? Điều 9(4)(d) is relevant here too — silence is not consent, so a default-public field is not made lawful by the user having failed to change it.

Điều 11 (collection, analysis and aggregation) and Điều 18 (other processing) carry the general purpose-limitation discipline into specific activities; the engineering constraint is the one in Điều 3(2) above — collect only within the stated purpose.

**Implementation layer:** [05 Feature/UX](../../../layers/05-feature-ux.md), [06 Disclosure](../../../layers/06-disclosure.md).
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