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/05-care.md

View on GitHub
# Security, Impact Assessment and Cross-Border Transfer — Điều 12, 20, 21, 22

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

This is where Vietnam departs most sharply from the other jurisdictions in this skill. Two impact-assessment dossiers must be **filed with the regulator**, each within **60 days**, and the cross-border definition is broad enough to catch ordinary architecture.

## Điều 12 — Encryption and decryption of personal data

Vietnam gives encryption its own article rather than leaving it inside a general security principle. Treat column-level or field-level encryption of sensitive categories as an express expectation, and keep key custody documented.

**Implementation layer:** [03 Data model](../../../layers/03-data-model.md), [02 Architecture](../../../layers/02-architecture.md).

## Điều 21 — Processing impact assessment (DPIA)

**Rule (Điều 21(1)):** the controller, and the controller-and-processor, must prepare and store a processing impact assessment dossier and **send one original to the specialised authority within 60 days from the first day of processing personal data**.

- **(2)** The assessment is performed **once for the entire operating life** of the entity, and updated under Điều 22.
- **(3)** The **processor** prepares and stores its own dossier as agreed with the controller.
- **(4)** The authority may require the dossier to be completed if it is inadequate.
- **(5)** Parties must update the dossier when the submitted content changes.
- **(6)** Competent **state agencies** are exempt.
- **(7)** The Government specifies the dossier contents.

**Engineering consequence:** the 60-day clock starts from **your own first processing**, silently. Nobody sends a reminder. For a new product with Vietnamese users, filing is a launch-window task, not an annual-compliance task.

## Điều 20 — Cross-border transfer

**Điều 20(1) — what counts as a cross-border transfer:**

- a) transferring personal data **stored in Vietnam** to a storage system located outside Vietnam;
- b) an entity **in Vietnam** transferring personal data to an organisation or individual **abroad**;
- c) an entity in Vietnam **or abroad** using a **platform located outside Vietnam** to process personal data **collected in Vietnam**.

**Limb (c) is the one that catches people.** A managed database in another region, an analytics or error-tracking SaaS, a foreign-hosted LLM API — each is a cross-border transfer of data collected in Vietnam. Most products with Vietnamese users are transferring on day one.

**Điều 20(2):** anyone doing any of the above must prepare a **cross-border transfer impact assessment** dossier and send **one original** to the specialised authority **within 60 days from the first day of cross-border transfer**.

**Điều 20(3):** performed **once for the entity's operating life**, updated under Điều 22.

**Điều 20(4):** the authority decides on inspection — **periodic, at most once per year**, or **unannounced** where a violation is found or a data-loss incident occurs.

**Điều 20(5):** the authority may require transfers to be **suspended**.

**Engineering consequence:** treat the sub-processor inventory as the input to this dossier. Every new foreign vendor that touches Vietnamese personal data is a change to the CTIA, which triggers the Điều 22 update duty — so vendor onboarding must have a VN compliance step, not just a DPA review.

## Điều 22 — Updating the assessment dossiers

Both the processing-impact and cross-border-transfer dossiers are updated **every 6 months**, or **immediately** on the triggers in Điều 22(2).

**Operationalisation:** put a recurring 6-month review on the same calendar as your retention sweeps, and wire an immediate-update trigger into the vendor-onboarding and architecture-change paths. A once-for-life dossier that is never updated is worse than none — it is a filed document that has become inaccurate.

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

## Small-entity transition

Small and startup enterprises may **opt out of Điều 21 and 22 for 5 years** from 1 January 2026; household and micro businesses are exempt outright (Điều 38(2)–(3)). Both carve-outs **fall away** where the entity provides data-processing services, directly processes **sensitive** personal data, or processes data of a **large number** of subjects. Check the carve-out before relying on it — most consumer products processing sensitive categories will not qualify.
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