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/06-breach-notification.md
View on GitHub# Pasal 46 — Breach Notification (72 hours, dual-recipient)
> ⚠ **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's breach notification obligation is in a single dense paragraph of Pasal 46. The 72-hour clock is non-negotiable, and unlike Singapore (PDPC only) or Thailand (regulator only), **Indonesia requires notification to BOTH the Data Subject AND the regulator**.
## Contents
- Pasal 46 — The rule
- Three-tier notification
- What constitutes a "Personal Data protection failure"
- Notification content (Pasal 46(2))
- Channels for notifying Data Subjects
- Subject notification content
- Public notification (Pasal 46(3))
- Vendor / sub-processor breaches
- Records and audit
- Penalty exposure
- Operational checklist (incorporate into the runbook)
- Quick reference
## Pasal 46 — The rule
**Pasal 46(1):** *"In the event of a Personal Data protection failure, the Personal Data Controller must provide a written notification within 3 × 24 hours to: (a) the Data Subject; and (b) the regulator (lembaga)."*
**Pasal 46(2):** the written notification must include at minimum:
a. The Personal Data that was disclosed
b. When and how the Personal Data was disclosed
c. Handling and recovery efforts undertaken by the Controller
**Pasal 46(3):** under certain circumstances, the Controller must also notify the **public**.
## Three-tier notification
| Tier | Recipient | Trigger | Timing |
|---|---|---|---|
| 1 | The regulator (lembaga) | Any breach | Within 72 hours (3 × 24 jam) |
| 2 | Affected Data Subjects | Any breach | Within 72 hours (3 × 24 jam) |
| 3 | The public | "Certain circumstances" — likely large-scale or serious | Per implementing PP |
**Critical:** the clock starts at **awareness of the breach**, not at notifiability assessment. Indonesia does not have an explicit assessment window before the 72-hour clock starts (unlike Singapore where the clock starts at "assessment-as-notifiable").
## What constitutes a "Personal Data protection failure"
The Act uses the phrase *"kegagalan Pelindungan Data Pribadi"* (Personal Data protection failure) without a separate definition. Practical reading: any breach of the Pasal 35–39 security obligations, including:
- Unauthorised access (intrusion, leaked credentials, RLS / IAM bypass)
- Unauthorised disclosure (mistaken email, public-bucket misconfiguration)
- Unauthorised alteration (data tampering)
- Loss of Personal Data (lost device with active credentials, deleted records)
- Vendor / sub-processor breach affecting your data
**Implementation layer:** [07 Operational](../../../layers/07-operational.md) (incident-response runbook).
**Examples that should be triaged as breaches and assessed for the 72-hour clock:**
- Leaked secret (database credential, API key, OAuth key) — once it's leaked, unauthorised access is "likely to occur"
- Access-control bypass discovered in production
- Stolen / lost device with active prod credentials
- Misdirected email containing Personal Data
- Admin / staff accessing data outside their role
- Anomalous traffic exfiltrating data
- A user reports their account was accessed by someone else
- Vendor / sub-processor notifies you of a breach on their side
When in doubt, treat as an incident. The cost of opening a triage case is low; the cost of missing the 72-hour clock is high.
## Notification content (Pasal 46(2))
The written notification must contain:
a. **Personal Data that was disclosed** — types, categories, scale (estimate is fine if exact unknown — update later)
b. **When and how the Personal Data was disclosed** — timeline of awareness, occurrence (if known), and the mechanism of disclosure
c. **Handling and recovery efforts** — containment actions, remediation, and steps taken to prevent recurrence
This is the minimum. The implementing PP may require additional fields — verify current text.
## Channels for notifying Data Subjects
UU PDP doesn't prescribe channels. Practical sequence:
1. **Email** to the address on file
2. **In-app banner** on next launch
3. **Push notification** (only if email + in-app aren't reaching them)
## Subject notification content
Pasal 46(2) fixes the minimum content; the drop-in email body lives once in
[`templates/INCIDENT_RESPONSE.md.template`](../../../templates/INCIDENT_RESPONSE.md.template)
section 5, so it does not drift per jurisdiction. Two ID-specific points when filling it:
- Name **the Indonesian regulator** in the "we notified" line — under Pasal 46(1) the
same 72-hour clock covers both the regulator and the Data Subject.
- ID is the only regime here with **no harm threshold**: every breach notifies the
subject, so the template is sent on all incidents, not just significant-harm ones.
## Public notification (Pasal 46(3))
The Controller must notify the public *"under certain circumstances"* — the Act doesn't enumerate, deferring to implementing PP. Reasonable read: large-scale breaches, breaches involving "specific" (sensitive) data at scale, breaches with public safety implications.
Common channels: a notice on your public website, a press release, posts on official social channels.
## Vendor / sub-processor breaches
**Pasal 51** establishes the Processor's obligation to act on the Controller's
instructions and report issues. The 72-hour clock runs from **your** awareness as
Controller — typically the moment the Processor notifies you.
Procedure, DPA time ceiling, and incident-log chain: [layer 07 Operational](../../../layers/07-operational.md#sub-processor--vendor-breaches).
## Records and audit
**Pasal 31** requires the Controller to keep records of all Personal Data processing
activities, and **Pasal 47** makes accountability demonstrable — so post-incident
remediation belongs in those records. See [layer 07 Operational](../../../layers/07-operational.md#post-incident-records).
## Penalty exposure
Failure to notify per Pasal 46(1) or Pasal 46(3) carries administrative sanctions per Pasal 57:
| Sanction | Source |
|---|---|
| Written warning | Pasal 57(2)(a) |
| Temporary suspension of processing activities | Pasal 57(2)(b) |
| Deletion or destruction of Personal Data | Pasal 57(2)(c) |
| Administrative fine — up to **2% of annual revenue** | Pasal 57(2)(d) + 57(3) |
Plus potential criminal liability (Pasal 67) if the breach involved unauthorised obtaining or disclosure carried out for personal benefit.
## Operational checklist (incorporate into the runbook)
General readiness items: [layer 07 Operational](../../../layers/07-operational.md#runbook-readiness-checklist). ID-specific:
- [ ] Data-subject notification template pre-staged in **Bahasa Indonesia**
- [ ] Regulator submission method verified (Komdigi / the appointed regulator under Pasal 58)
## Quick reference
| Obligation | Singapore PDPA | Thailand PDPA | Indonesia UU PDP |
|---|---|---|---|
| Notify regulator | 3 calendar days from assessment | 72 hours from awareness | **72 hours from awareness** (Pasal 46(1)(b)) |
| Notify affected individuals | If significant harm likely (s26D(2)) | If high risk (s37(4)) | **Always** (Pasal 46(1)(a)) — distinctive |
| Notify public | Not required | Not required | "Under certain circumstances" (Pasal 46(3)) |
Indonesia's "always notify the Data Subject" requirement is broader than Singapore's significant-harm test or Thailand's high-risk test — making the 72-hour cycle operationally heavier.
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 |