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/06-breach-notification.md

View on GitHub
# Personal Data Breach Notification — Điều 23

> ⚠ **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 has a **72-hour** clock running from **detection of the violating act**, to the specialised authority under the Ministry of Public Security. The trigger is **harm-based, not scale-based** — there is no affected-count threshold to measure against.

## Điều 23(1) — The rule

The controller, controller-and-processor, or **third party** that detects a violation of personal-data-protection rules which **may cause harm to**:

- national defence, national security, social order and safety; **or**
- the **life, health, honour, dignity or property** of the data subject

must notify the specialised authority **no later than 72 hours from detecting the violating act** (`chậm nhất là 72 giờ kể từ khi phát hiện hành vi vi phạm`).

Where the **processor** detects the violation, it must promptly notify the controller or controller-and-processor.

**Read the trigger carefully.** Two things differ from the rest of this skill:

1. **The clock starts at detection of the act**, not at assessment (SG s26D) and not at awareness of a breach's consequences. There is no assessment window buffering the deadline.
2. **The threshold is qualitative.** "May cause harm" to the listed interests — including *honour* and *dignity*, which have no counterpart in the other four regimes. A small leak of embarrassing data can qualify where a large leak of innocuous data may not.

**Implementation layer:** [07 Operational](../../../layers/07-operational.md).

## Điều 23(2) — Record and cooperate

The controller or controller-and-processor must **make a written record** (`biên bản`) confirming that the violation occurred, and coordinate with the specialised authority in handling it.

**Operationalisation:** the incident log is not merely good practice here — a confirmation record is a statutory artefact. Capture detection time, detector, the act, affected data categories, and the notification timestamp. Detection time is the field that determines whether you met the clock, so record it the moment anyone raises the alarm, not when triage concludes.

## Điều 23(3) — Additional notification cases

Organisations and individuals notify the specialised authority where:

- a) a violation of personal-data-protection rules is detected;
- b) personal data is processed **for the wrong purpose**, or contrary to the agreement between the subject and the controller;
- c) the **rights of the data subject** are not ensured, or are performed incorrectly;
- d) other cases provided by law.

**This is broader than a security-incident duty.** Điều 23(3)(b) and (c) mean a purpose-creep bug, or a failure of your access/deletion path, is itself a notifiable matter — not only a leak. Nothing equivalent exists in SG, TH, ID, MY or PH.

## Điều 23(4) — Authority's role

The specialised authority receives notifications and handles violations.

## Decree Điều 28 — What the notification must contain

The Decree fixes both the content and the channel.

**Content (Điều 28(1)):**

- a) **Nature of the violation** — time, place, the act, the organisations and individuals involved, the **categories of personal data** and the **volume** concerned
- b) **Contact details** of the data-protection unit or personnel, or of the service provider
- c) Description of the **possible consequences and damage**
- d) Description of the **measures taken** to resolve and mitigate

**Channel (Điều 28(2)):** submitted to the specialised authority **or via the national personal-data-protection portal**, using **Form No. 08** in the Decree's Appendix.

**Operationalisation:** pre-fill Form No. 08 before you need it, and make sure your incident log captures the fields it asks for — especially *data categories* and *volume*, which are hard to reconstruct after the fact under time pressure. Điều 29 covers notification specifically for sensitive personal data.

## Examples that should be triaged

Use the general detection-signal and triage guidance in [layer 07 Operational](../../../layers/07-operational.md#sub-processor--vendor-breaches). VN-specific additions:

- A bug that processed data outside its consented purpose → Điều 23(3)(b), notifiable in its own right
- A broken export or deletion path → Điều 23(3)(c)
- Leak of data touching honour or dignity (private messages, images, health) at **any** scale → Điều 23(1)

## Operational checklist (incorporate into the runbook)

General readiness items: [layer 07 Operational](../../../layers/07-operational.md#runbook-readiness-checklist). VN-specific:

- [ ] Detection timestamp captured at first signal — the 72h clock runs from here, with no assessment buffer
- [ ] **Form No. 08** (Decree Appendix) pre-filled; route confirmed — specialised authority or the national personal-data-protection portal — with two people holding access
- [ ] `biên bản` confirmation-record template pre-staged (Điều 23(2))
- [ ] Incident log captures **data categories and volume** (Decree Điều 28(1)(a)) — hard to reconstruct later
- [ ] Triage rules cover the Điều 23(3)(b)/(c) non-security cases, not only leaks
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