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/th-pdpa/obligations/04-access-correction.md

View on GitHub
# Chapter III — Rights of the Data Subject (Sections 30–36)

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

Thailand PDPA grants seven distinct data-subject rights. Each must be supported by the Data Controller; rejections require recorded reasons in the s39 records.

## Contents

- Section 30 — Access right
- Section 31 — Data portability right
- Section 32 — Right to object
- Section 33 — Right to erasure ("right to be forgotten")
- Section 34 — Right to restrict processing
- Section 35 — Accuracy obligation
- Section 36 — Correction request handling
- Penalty exposure (this Part)
- What "complete" means in practice

## Section 30 — Access right

**Rule:** the data subject may request **access to and a copy** of the Personal Data, OR request disclosure of the source from which the data was obtained without consent.

**Response window:** **within 30 days** of receiving the request (or longer per Committee rules).

**Permitted rejections:**
- Permitted by law or court order
- Where access would adversely affect the rights and freedoms of others

**On rejection:** record the rejection with reasons in the s39 records.

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

**Operationalisation:**
- A function or endpoint that returns the user's complete Personal Data set
- Delivered via in-app share / download / email
- Rate-limit to prevent abuse
- Include the disclosure-source information for any data collected without consent (s24 / s26 exceptions)

## Section 31 — Data portability right

**Rule:** the data subject has the right to **receive Personal Data** about them in a format that is readable or commonly used by automatic tools, AND to:
1. Request the Data Controller send / transfer to another Data Controller (where feasible by automatic means), OR
2. Receive the data directly to send to another Data Controller themselves (unless impossible due to technical circumstances)

**Scope:** applies to Personal Data the data subject has consented to AND data collected under the s24(3) contractual necessity basis (or per Committee rules).

**Exceptions:** does not apply to Personal Data sent / transferred for public-interest tasks or legal compliance.

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

**Operationalisation:**
- Same as the access endpoint, but with explicit machine-readable format (JSON, CSV) and an export specifically intended for transferring to another service
- Supabase-style projects: this is a separate function from a "human-readable" export

## Section 32 — Right to object

**Rule:** the data subject may **object** to the collection / use / disclosure of their Personal Data at any time, in three circumstances:

1. **Where the data was collected under s24(4) public-interest task or s24(5) legitimate interests** — UNLESS the Data Controller can prove (a) compelling legitimate grounds, or (b) the processing is for legal claims
2. **Direct marketing** — no balancing test; the controller must stop
3. **Scientific / historical / statistical research** — UNLESS necessary for a public-interest task

**On objection:** the Data Controller must immediately distinguish the objected-to data and stop processing.

**On rejection:** record the rejection with reasons in the s39 records.

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

**Operationalisation:**
- Settings UI for stopping marketing communications (toggle to off + immediate effect)
- For legitimate-interest reliance: have the LIA documentation ready to defend the "compelling legitimate grounds" argument

## Section 33 — Right to erasure ("right to be forgotten")

**Rule:** the data subject may request the Data Controller to **erase, destroy, or anonymise** Personal Data where:

1. **No longer necessary** for the original purpose
2. **Consent withdrawn** AND no other lawful basis applies
3. **Objection upheld** (s32 exercise where the controller cannot defend)
4. **Unlawfully processed** under this Chapter

**Exceptions:** retention may continue where necessary for:
- Freedom of expression
- s24(1) research / archival, s24(4) public-interest task, s26(5)(a) preventive/occupational medicine, s26(5)(b) public health
- Legal claims
- Legal compliance

**Public disclosure:** if the Personal Data was disclosed publicly, the Data Controller must take **technological action AND bear the expense** to inform other Data Controllers of the erasure request.

**Recourse:** on Data Controller failure to act, the data subject may complain to the expert committee.

**Implementation layer:** [04 Controls](../../../layers/04-controls-and-processes.md), [03 Data model](../../../layers/03-data-model.md) (deletion vs anonymisation patterns).

## Section 34 — Right to restrict processing

**Rule:** the data subject may request the Data Controller to **restrict the use** of their Personal Data where:

1. The Data Controller is examining an accuracy challenge (s36)
2. The data should be erased per s33(4) (unlawful) but the data subject prefers restriction instead
3. No longer necessary for the purpose, but the data subject needs it retained for legal claims

**Implementation layer:** [03 Data model](../../../layers/03-data-model.md) (restricted-state flag), [04 Controls](../../../layers/04-controls-and-processes.md) (read-path enforcement).

## Section 35 — Accuracy obligation

**Rule:** the Data Controller must ensure Personal Data remains **accurate, up-to-date, complete, and not misleading**.

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

## Section 36 — Correction request handling

**Rule:** when the data subject requests correction per s35 and the Data Controller does not act, the Data Controller must record the request and reasons in the s39 records.

The provisions of s34 paragraph 2 (restricted-use processing while the request is examined) apply.

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

## Penalty exposure (this Part)

| Failure | Maximum administrative fine | Source |
|---|---|---|
| Fails s30 paragraph 4 (30-day access response) | THB 1M | s82 |
| Fails s32 paragraph 2 (immediate cessation on objection) | THB 3M | s83 |
| Failure to maintain s39 records of rejected requests | THB 1M | s82 |

Plus s81 personal liability for directors / managers responsible.

## What "complete" means in practice

When implementing the access right, the export must include all Personal Data the org holds, not just the most-used fields. Use the data-field inventory (see [layer 03](../../../layers/03-data-model.md)) and the [`new-data-field` checklist](../../../checklists/new-data-field.md) to keep the export current as new fields are added.
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