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/id-pdp/obligations/07-offences.md
View on GitHub# BAB VIII (Pasal 57) + BAB XIII–XIV (Pasal 65–73) — Administrative Sanctions, Prohibitions, Criminal Penalties
> ⚠ **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.
UU PDP splits enforcement into **administrative sanctions** (Pasal 57), **prohibitions** (Pasal 65–66), and **criminal penalties** (Pasal 67–73). Corporate criminal liability under Pasal 70 is significantly broader than Singapore or Thailand.
## Contents
- BAB VIII — Administrative Sanctions (Pasal 57)
- BAB XIII — Prohibitions (Pasal 65–66)
- BAB XIV — Criminal Penalties (Pasal 67–73)
- Mental model
- Penalty cap calculation in practice
- Cross-references
## BAB VIII — Administrative Sanctions (Pasal 57)
### Pasal 57(1) — Triggering provisions
Administrative sanctions apply for violations of any of the following Pasal:
> 20(1), 21, 24, 25(2), 26(3), 27, 28, 29, 30, 31, 32(1), 33, 34(1), 35, 36, 37, 38, 39(1), 40(1), 41(1)/(3), 42(1), 43(1), 44(1), 45, 46(1)/(3), 47, 48(1), 49, 51(1)/(5), 52, 53(1), 55(2), 56(2)–(4)
That covers virtually every substantive Controller and Processor obligation.
### Pasal 57(2) — Sanction types
The regulator may impose:
a. **Written warning** (peringatan tertulis)
b. **Temporary suspension** of Personal Data processing activities
c. **Deletion or destruction** of Personal Data
d. **Administrative fine**
These are not exclusive — multiple may apply for the same violation. Sanctions (b), (c), and (d) can be operationally devastating: a temporary suspension of processing means you cannot run your service.
### Pasal 57(3) — Fine ceiling
> *"Administrative sanctions in the form of administrative fines as referred to in paragraph (2) letter d are at most **2% (two percent) of annual revenue or annual receipts** against the variable of the violation."*
**Practical effect:**
- 2% of annual revenue is the absolute cap per violation
- "Variable of the violation" — the implementing PP refines what constitutes a single violation; multiple findings in one investigation can stack
- For a small organisation: 2% of small revenue is small in absolute terms but proportional
- For a large organisation: 2% of large revenue is a significant penalty (similar in spirit to GDPR's 4% / EUR 20M ceiling, though GDPR is higher)
### Pasal 57(4) — Imposed by the regulator (lembaga)
Administrative sanctions are imposed by the regulator (lembaga) — currently administered through Komdigi pending the establishment of the dedicated Personal Data Protection authority by Presidential Regulation.
## BAB XIII — Prohibitions (Pasal 65–66)
These prohibitions establish the conduct that becomes criminal under Pasal 67–68.
### Pasal 65 — Prohibitions on use of others' data
It is prohibited to:
(1) **Unlawfully obtain or collect** Personal Data not belonging to oneself, with intent to benefit oneself or another, **in a way that may cause loss to the Data Subject**
(2) **Unlawfully disclose** Personal Data not belonging to oneself
(3) **Unlawfully use** Personal Data not belonging to oneself
### Pasal 66 — Prohibition on falsification
It is prohibited to **make false Personal Data or falsify Personal Data**, with intent to benefit oneself or another, **in a way that may cause loss to others**.
**Implementation layers:** [01 Non-technical](../../../layers/01-non-technical.md) (staff AUP), [04 Controls](../../../layers/04-controls-and-processes.md) (admin audit log).
## BAB XIV — Criminal Penalties (Pasal 67–73)
### Pasal 67 — Three-tier criminal offences
Built on the Pasal 65 prohibitions:
| Pasal 67 paragraph | Conduct | Maximum penalty |
|---|---|---|
| (1) | Intentionally + unlawfully **obtaining or collecting** another's Personal Data with intent to benefit, causing loss | **5 years imprisonment** + IDR 5,000,000,000 fine (~USD 320k) |
| (2) | Intentionally + unlawfully **disclosing** another's Personal Data | **4 years imprisonment** + IDR 4,000,000,000 fine (~USD 256k) |
| (3) | Intentionally + unlawfully **using** another's Personal Data | **5 years imprisonment** + IDR 5,000,000,000 fine (~USD 320k) |
Each paragraph allows the court to impose imprisonment, fine, or both.
### Pasal 68 — Falsification
Intentional falsification of Personal Data (per Pasal 66) carries:
- **6 years imprisonment** + IDR 6,000,000,000 fine (~USD 384k)
### Pasal 69 — Additional penalties
In addition to Pasal 67–68 penalties, the court may also impose:
- **Confiscation of profits or assets** obtained from the criminal act
- **Compensation payment** to the victim
### Pasal 70 — Corporate criminal liability
**Rule:** Pasal 67–68 offences committed by a Corporation expose management, controlling shareholders, instruction-givers, beneficial owners, and/or the Corporation itself. Corporate fines stack to **up to 10×** the natural-person maximum (Pasal 70(3)) — Pasal 67(1) corporate ≤ IDR 50B (~USD 3.2M); Pasal 68 corporate ≤ IDR 60B (~USD 3.8M). Pasal 70(4) adds non-monetary penalties: business suspension, activity bans, location closure, licence revocation, and **dissolution**. Indonesia is the only one of the four populated jurisdictions where a court can dissolve the corporation for PDP offences.
**Engineering relevance:** the audit trail (audit logs, breach register, RoPA, vendor inventory, DPIA artefacts, training records) is the input to any due-diligence defence and to mitigation in sentencing. Make those queryable and durable.
### Pasal 71–73 — Enforcement procedures
Procedural — covers payment timelines (1 month from finalisation), asset seizure if unpaid, conversion of unpaid fines to imprisonment for natural persons, business suspension for corporations.
## Mental model
Three concepts to internalise:
1. **Administrative + criminal layers stack.** Pasal 57 (administrative) and Pasal 67–73 (criminal) can both apply to the same incident. A breach that involves unauthorised disclosure for personal benefit triggers both.
2. **2% revenue ceiling is per-violation.** Multiple findings in one investigation can stack. A single root cause that triggers violations of multiple Pasal can produce a multi-tier fine.
3. **Audit trail is the engineering input to any defence.** Pasal 70 corporate liability is broader than the peer jurisdictions; the artefacts that anchor a due-diligence / mitigation argument are all engineering surfaces — RoPA (Pasal 31), DPIA (Pasal 34), audit logs, breach register, vendor inventory.
## Penalty cap calculation in practice
**Compared across jurisdictions:**
| Aspect | Singapore PDPA | Thailand PDPA | Indonesia UU PDP |
|---|---|---|---|
| Administrative org penalty | SGD 1M, or 10% SG turnover above SGD 10M | THB 1M / 3M / 5M tiered | **2% of annual revenue per violation** |
| Personal criminal penalty | SGD 5,000 + 2 years (s48D/E/F) | THB 500k–1M + 6mo–1yr (s79–81) | IDR 4–6 billion (~USD 256k–384k) + 4–6 years (Pasal 67–68) |
| Corporate criminal additional measures | None | None | **Suspension, ban, licence revocation, dissolution** (Pasal 70(4)) |
Indonesia's penalty surface is the broadest in absolute terms once corporate criminal liability is in play.
## Cross-references
- [02-consent.md](02-consent.md) — sensitive ("specific") data and explicit consent
- [05-care.md](05-care.md) — security measures and cross-border transfer
- [01-accountability.md](01-accountability.md) — DPO, records of processing, controller / processor duties
- [01 Non-technical](../../../layers/01-non-technical.md) — staff AUP and director / manager responsibilities
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 |