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/id-pdp/obligations/04-access-correction.md

View on GitHub
# BAB IV — Data Subject Rights (Pasal 5–15) + Operational Windows (Pasal 30, 32, 40, 41, 43)

> ⚠ **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 grants 9 data subject rights. Each must be supported by the Controller; refusals require recorded reasons.

## Contents

- Pasal 5 — Right to information about the Controller
- Pasal 6 — Right to correction
- Pasal 7 — Right to access + obtain copy
- Pasal 8 — Right to end processing, erasure, and destruction
- Pasal 9 — Right to withdraw consent
- Pasal 10 — Right to object to automated decision-making
- Pasal 11 — Right to suspend or restrict processing
- Pasal 12 — Right to sue for damages
- Pasal 13 — Right to data portability
- Pasal 14 — How to exercise rights
- Pasal 15 — Exceptions to Subject rights
- Operational summary — the 72-hour SLAs
- Penalty exposure (this Part)

## Pasal 5 — Right to information about the Controller

**Rule:** the Data Subject has the right to receive Information about:
- The identity of the Controller
- The legal interest basis for processing
- The purpose of the request and use of Personal Data
- Accountability of the party requesting the data

**Implementation layer:** [06 Disclosure](../../../layers/06-disclosure.md) (privacy policy + at-collection notices).

## Pasal 6 — Right to correction

**Rule:** the Data Subject has the right to **complete, update, and/or correct errors and/or inaccuracies** in their Personal Data.

**Implementation layer:** [05 Feature/UX](../../../layers/05-feature-ux.md) (self-service edit), [04 Controls](../../../layers/04-controls-and-processes.md).

**Operational window:** the Controller must act on the request **within 3 × 24 hours (72 hours)** per Pasal 30, AND notify the Subject of the result.

## Pasal 7 — Right to access + obtain copy

**Rule:** the Data Subject has the right to **access and obtain a copy** of their Personal Data.

**Implementation layer:** [04 Controls](../../../layers/04-controls-and-processes.md).

**Operational window:** the Controller must provide access **within 3 × 24 hours (72 hours)** per Pasal 32(2).

The access response must include the **processing trail** (rekam jejak pemrosesan) — i.e. who has accessed / used the data and how, within the retention period.

## Pasal 8 — Right to end processing, erasure, and destruction

**Rule:** the Data Subject has the right to **terminate processing**, **erase**, and/or **destroy** their Personal Data.

**Implementation layers:** [04 Controls](../../../layers/04-controls-and-processes.md), [05 Feature/UX](../../../layers/05-feature-ux.md) (delete-account flow).

**Operational details:**
- Pasal 42: Controller must end processing when retention met, purpose achieved, or Subject requests
- Pasal 43: Controller must erase Personal Data on 4 grounds (no longer needed, consent withdrawn, Subject requests, unlawfully processed)
- Pasal 44: Controller must destroy Personal Data on 4 grounds (similar)

The split between erasure and destruction reflects archival practice: erasure removes from active systems; destruction is permanent (more applicable to physical records or backups).

## Pasal 9 — Right to withdraw consent

**Rule:** the Data Subject has the right to **withdraw consent** previously given.

**Implementation layer:** [05 Feature/UX](../../../layers/05-feature-ux.md) (settings toggles), [03 Data model](../../../layers/03-data-model.md) (consent log).

**Operational window:** Pasal 40(2) — processing must stop **within 3 × 24 hours (72 hours)** of the consent withdrawal request. This propagates to:
- Database state (notification flag flipped, etc.)
- Sub-processors (push provider de-registered, OAuth tokens revoked)
- Future scheduled jobs

## Pasal 10 — Right to object to automated decision-making

**Rule:** the Data Subject has the right to **object to decisions based solely on automated processing, including profiling**, that produce legal effects or significantly affect the Subject.

This is **explicit and standalone** — comparable to GDPR Article 22.

**Implementation layers:** [04 Controls](../../../layers/04-controls-and-processes.md) (object-to-automation mechanism), [05 Feature/UX](../../../layers/05-feature-ux.md) (UI to invoke).

**Operationalisation:** for any feature that takes automated decisions (pricing, content moderation, recommendation that affects access, scoring, etc.) with legal or significant impact, you need:
- A way for the Subject to object
- Either human review on objection, OR a different processing path for objecting users
- Documented limits on what counts as "significant impact" (PP refines this)

## Pasal 11 — Right to suspend or restrict processing

**Rule:** the Data Subject has the right to **suspend or restrict processing** of Personal Data, in accordance with the purpose of processing.

**Implementation layers:** [04 Controls](../../../layers/04-controls-and-processes.md) (restriction state + read-path enforcement), [05 Feature/UX](../../../layers/05-feature-ux.md) (Settings toggle).

**Operational window:** Pasal 41 — Controller must comply **within 3 × 24 hours (72 hours)**.

**Exceptions to compliance** (Pasal 41(2)):
a. Other laws require continued processing
b. Suspension would endanger others' safety
c. A written contract with the Subject prevents suspension

The Controller must **notify the Subject** when the suspension/restriction is in force.

**Compared to other jurisdictions:**
- Singapore PDPA: no equivalent right — would require building net-new code if launching in SG and re-using for ID
- Thailand PDPA s34: equivalent right — same code mechanism works for both

## Pasal 12 — Right to sue for damages

**Rule:** the Data Subject has the right to **sue and receive damages** for violations.

Procedural — relevant during litigation, not a UX feature. But note that this exists; it changes the risk calculus when designing high-impact processing.

## Pasal 13 — Right to data portability

**Rule:** the Data Subject has the right to:

(1) **Obtain or use** their Personal Data from the Controller in a format aligned with the structure / format commonly used or readable by electronic systems
(2) **Have the data sent or transferred** to another Controller, when the systems involved can communicate securely

**Implementation layer:** [04 Controls](../../../layers/04-controls-and-processes.md).

**Operationalisation:**
- Same as the access endpoint (Pasal 7) but with explicit machine-readable format requirement (JSON / CSV)
- Optional: an interface to push data directly to another Controller (rare in consumer apps)
- The "secure inter-system communication" qualifier limits the practical scope — most apps satisfy by providing a downloadable JSON the user can manually upload elsewhere

## Pasal 14 — How to exercise rights

**Rule:** the Subject exercises rights under Pasal 6–11 via a **recorded request** (written or electronic), submitted to the Controller.

**Implementation layer:** [05 Feature/UX](../../../layers/05-feature-ux.md) (in-app request channels), [04 Controls](../../../layers/04-controls-and-processes.md) (admin-side intake).

In-app self-service satisfies "recorded electronic request." Email also works.

## Pasal 15 — Exceptions to Subject rights

**Rule:** the rights under **Pasal 8 (end processing / erasure), 9 (withdraw consent), 10(1) (object to automated decision-making), 11 (suspend / restrict), and 13 (portability)** are **excluded** for:

a. National defence and security
b. Law enforcement
c. Public administration in the interest of the state
d. Financial-sector supervision (banking, monetary, payment, financial-system stability) for state interests
e. Statistical and scientific research

The exceptions apply only when implementing law (Pasal 15(2)).

**Implementation note:** the rights to **information (Pasal 5), correction (Pasal 6), access (Pasal 7), legal action (Pasal 12), and on-demand information (Pasal 14)** are NOT subject to these exceptions — those are absolute.

## Operational summary — the 72-hour SLAs

| Right | Pasal | Window |
|---|---|---|
| Correction | 30 | 72 hours from request |
| Access (incl. processing trail) | 32 | 72 hours from request |
| Stop processing on consent withdrawal | 40 | 72 hours from withdrawal |
| Suspend / restrict processing | 41 | 72 hours from request |

Four parallel 72-hour SLAs is operationally aggressive. Customer-support / engineering must:
- Triage incoming requests fast (target: same business day)
- Have automation paths for the common cases (self-service edit; settings-toggle effect)
- Have admin-mediated escalation paths for the rest with sub-72-hour latency

## Penalty exposure (this Part)

Failures across the access/correction/restriction/erasure obligations all carry administrative sanctions per Pasal 57 — ceiling 2% of annual revenue. See [07-offences.md](07-offences.md).
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