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/02-consent.md

View on GitHub
# Chapter II Part I + Sections 24, 26 — Consent, Lawful Bases, Sensitive Data

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

## Contents

- Section 19 — Consent required (general rule)
- Section 20 — Minor consent
- Section 21 — Purpose limitation tied to consent
- Section 24 — Lawful bases (collection without consent)
- Section 25 — Collection from sources other than the data subject
- Section 26 — Sensitive Personal Data
- Penalty exposure (this Part)

## Section 19 — Consent required (general rule)

**Rule (verbatim):** *"The Data Controller shall not collect, use, or disclose Personal Data, unless the data subject has given consent prior to or at the time of such collection, use, or disclosure, except the case where it is permitted to do so by the provisions of this Act or any other laws."*

**Form requirements:**
- Consent must be **explicit**, in writing or via electronic means (unless impossible by nature)
- The request must be **clearly distinguishable** from other matters
- In **easily accessible and intelligible** form
- In **clear and plain language**
- **Not deceptive or misleading** about the purpose
- The Committee may prescribe specific forms

**Freely given:** the request must take into account that consent is freely given. **Bundled consent prohibited:** entering a contract or service must not be conditioned on consenting to processing not necessary or not related to the contract / service.

**Withdrawal (s19 paragraph 5–6):**
- The data subject **may withdraw consent at any time**, with the **same ease as giving it**, unless restricted by law or by a contract benefiting the data subject
- Withdrawal does not affect prior lawful processing
- The Data Controller **must inform** the data subject of the consequences of withdrawal where withdrawal will affect them

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

## Section 20 — Minor consent

**Rule:** when the data subject is a minor:
- Below age 10: consent must be obtained from the **holder of parental responsibility**
- 10 and above (still a minor not sui juris): consent is generally required from the parent in addition to the minor, except where the act is one a minor may legally do alone (specific Civil and Commercial Code provisions)

Same rules apply for incompetent / quasi-incompetent data subjects (custodian / curator gives consent).

**Implementation layer:** [05 Feature/UX](../../../layers/05-feature-ux.md) (age gating + parental-consent flow if minors are permitted users).

## Section 21 — Purpose limitation tied to consent

**Rule:** Personal Data must be collected, used, or disclosed **according to the purpose notified to the data subject** prior to or at the time of collection. New purposes require either:
1. Notifying the data subject of the new purpose AND obtaining new consent, OR
2. Permission under the Act or other law.

See [03-purpose.md](03-purpose.md) for purpose-limitation depth.

## Section 24 — Lawful bases (collection without consent)

**Rule:** the Data Controller may NOT collect Personal Data without consent, **except** under one of six bases:

1. **Research / archival in public interest** — with safeguards per Committee notification
2. **Vital interests** — preventing or suppressing a danger to a person's life, body, or health
3. **Contractual necessity** — performance of a contract to which the data subject is a party, or pre-contractual steps at the data subject's request
4. **Public-interest task / official authority** — necessary for a task in public interest, or exercising official authority vested in the Data Controller
5. **Legitimate interests** — necessary for the legitimate interests of the Data Controller or third parties, **except where overridden** by the data subject's fundamental rights
6. **Legal obligation** — necessary for compliance with a law to which the Data Controller is subject

**This is a closed list** — but materially close to the GDPR Article 6 lawful bases. Singapore PDPA's enumerated 1st/2nd Schedule cases differ in structure.

**Implementation layer:** [06 Disclosure](../../../layers/06-disclosure.md) (lawful-basis register / privacy policy purposes table).

**Operationalisation:**
- Maintain a per-data-flow lawful-basis register
- For Legitimate Interests reliance: document an LIA-style assessment proving necessity AND that data subject's rights are not overridden
- For Vital Interests reliance: notify the data subject after the use where practicable (general accountability principle)

## Section 25 — Collection from sources other than the data subject

**Rule:** the Data Controller may not collect Personal Data from sources other than the data subject directly, **except**:

1. The Data Controller **informs the data subject** of the collection from another source within **30 days** and obtains consent, OR
2. The collection falls within the s24 (lawful basis) or s26 (sensitive-data) exceptions

**Notification timing:** within 30 days from the date of collection. Special cases (where the Personal Data is used for direct communication with the data subject; or where disclosure to a third party is envisaged) may shift the timing.

**Implementation layer:** [01 Non-technical](../../../layers/01-non-technical.md) (partner integration MOUs), [04 Controls](../../../layers/04-controls-and-processes.md) (notification flow).

## Section 26 — Sensitive Personal Data

**Rule (verbatim, key categories):** *"Any collection of Personal Data pertaining to racial, ethnic origin, political opinions, cult, religious or philosophical beliefs, sexual behavior, criminal records, health data, disability, trade union information, genetic data, biometric data, or of any data which may affect the data subject in the same manner, as prescribed by the Committee, is prohibited, without the explicit consent from the data subject."*

**Compared to Singapore:** much broader than Singapore PDPA's "deemed significant harm" categories. Many data points your application might collect routinely (health for medical apps, location-derived political affiliation, etc.) are sensitive under Thai law.

**Sensitive-data exceptions (without explicit consent):**

1. Vital interests (data subject incapable of consent)
2. Legitimate activities by foundations / associations / not-for-profits — with appropriate safeguards, no external disclosure
3. Information already disclosed publicly with explicit data subject consent
4. Establishment, compliance, exercise, or defence of legal claims
5. Compliance with a law for specific purposes:
   - (a) Preventive / occupational medicine, medical diagnosis, health/social care, or services management — subject to confidentiality
   - (b) Public-health purposes (cross-border contagious disease, medicinal product safety, etc.)
   - (c) Employment / social security / health welfare / road accident victim protection — with safeguards
   - (d) Scientific, historical, or statistical research with safeguards

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

**Operationalisation:**
- **Audit your data inventory** for sensitive categories. Many apps inadvertently collect sensitive data — e.g. health-related (fitness apps), religious (community apps), political (advocacy apps).
- **Explicit consent** for sensitive data must be captured separately from general consent (no bundling).
- The s84 administrative fine for sensitive-data violations is **THB 5M** — the highest tier. Don't assume sensitive-data handling is the same risk as general data.

## Penalty exposure (this Part)

| Failure | Maximum administrative fine | Source |
|---|---|---|
| Fails consent form requirements (s19 para 3) or impact-of-withdrawal notice (s19 para 6) | THB 1M | s82 |
| Violates s24 (collection without lawful basis) | THB 3M | s83 |
| Violates s26 paragraph 1 or 3 (sensitive data without explicit consent or per exceptions) | **THB 5M** | s84 |
| Obtains consent by deception about purpose | THB 3M | s83 |
| Violates s27 (use/disclosure without consent) involving sensitive data | **THB 5M** + criminal liability under s79 | s84, s79 |

Plus s81 personal liability for directors / managers responsible for the offence.
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