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/07-offences.md
View on GitHub# Prohibited Acts and Penalties — Điều 7, 8
> ⚠ **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 7 — Prohibited acts
1. Processing personal data **against the State**, affecting national defence, security, social order and safety, or the lawful rights of agencies, organisations and individuals
2. **Obstructing** personal data protection activities
3. **Abusing** data protection activities to commit violations
4. Processing personal data **contrary to law**
5. Using another person's personal data, or letting another use yours, to commit unlawful acts
6. **Buying or selling personal data**, unless the law provides otherwise
7. **Appropriating, intentionally disclosing, or losing** personal data
Item 7 is the one to note: **intentional disclosure or loss is a prohibited act in itself**, distinct from the notification duty in Điều 23. Item 6 pairs with the Điều 8(3) penalty below.
Re-identification of de-identified data is prohibited separately — see [04-access-correction](04-access-correction.md) on Điều 14 read with Điều 2(1).
## Điều 8 — Handling of violations
**Điều 8(1):** depending on nature, severity and consequences, violators may face **administrative penalties or criminal prosecution**; where damage is caused, **compensation** is owed.
**Điều 8(2):** administrative penalties follow Điều 8(3)–(7) and the general law on handling administrative violations.
### The two caps engineers should know
| Provision | Maximum |
|---|---|
| **Điều 8(3)** — buying or selling personal data | **10× the revenue gained from the violation**. Where there is no such gain, or the calculated figure is lower than the Điều 8(5) cap, the Điều 8(5) cap applies instead |
| **Điều 8(4)** — cross-border transfer violations, organisations | **5% of revenue** |
Two features distinguish this from the rest of the skill:
- **Điều 8(3) is a multiplier on illicit gain, not a ceiling.** Selling data profitably does not cap exposure at a fixed sum; it scales it. Indonesia's 2%-of-revenue and Malaysia's fixed per-principle fines both behave differently.
- **The 5% cross-border cap is the highest revenue-based penalty among the six jurisdictions covered here** — above Indonesia's 2% under Pasal 57(3). Given how broadly Điều 20(1)(c) defines cross-border transfer, the exposure attaches to a very ordinary architectural decision: processing Vietnamese users' data on a platform outside Vietnam without having filed the assessment.
**Implementation layer:** [01 Non-technical](../../../layers/01-non-technical.md).
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 |