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/01-accountability.md

View on GitHub
# Chapter I + Section 37, 39, 41–42 — Accountability, Controller / Processor Duties, DPO

> ⚠ **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 37 — Data Controller duties
- Section 39 — Records of Processing Activities
- Section 40 — Data Processor duties
- Section 41 / 42 — DPO (engineering touch-points)
- Chapter I — Personal Data Protection Committee (s8–18)
- Penalty exposure (this Part)

## Section 37 — Data Controller duties

The Data Controller has five enumerated duties:

### (1) Security measures

**Rule:** *"provide appropriate security measures for preventing the unauthorized or unlawful loss, access to, use, alteration, correction or disclosure of Personal Data, and such measures must be reviewed when it is necessary, or when the technology has changed in order to efficiently maintain the appropriate security and safety. It shall also be in accordance with the minimum standard specified and announced by the Committee."*

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

PDPC Thailand has issued subordinate notifications specifying the minimum security standard — verify the current text at [pdpc.or.th](https://www.pdpc.or.th) for the binding details.

### (2) Onward-disclosure protection

**Rule:** when Personal Data is provided to other persons, the Data Controller must take action to prevent unlawful or unauthorised use / disclosure by those recipients.

**Implementation layer:** [01 Non-technical](../../../layers/01-non-technical.md) (vendor contracts), [04 Controls](../../../layers/04-controls-and-processes.md) (sub-processor dispatch sanitisation).

### (3) Erasure / destruction system

**Rule:** put in place an examination system for erasure or destruction of Personal Data when:
- The retention period ends, OR
- The Personal Data is irrelevant or beyond the necessary purpose, OR
- The data subject requests erasure, OR
- The data subject withdraws consent (and there's no other lawful basis).

Exceptions: freedom of expression, archival/research under s24(1) or (4), public-health under s26(5)(a)/(b), legal claims, legal compliance.

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

### (4) Breach notification — 72 hours

See [06-breach-notification.md](06-breach-notification.md).

### (5) Designate Thai representative (for non-Thai controllers)

**Rule:** controllers outside Thailand serving Thai users (per s5 paragraph 2) must designate **in writing** a representative in the Kingdom of Thailand, authorised to act on behalf of the Data Controller without limitation of liability.

**Implementation layer:** [01 Non-technical](../../../layers/01-non-technical.md).

Exception (s38): does not apply to public authorities or to small operations not handling sensitive data and not handling large-scale data per the s41(2) threshold.

## Section 39 — Records of Processing Activities

**Rule:** the Data Controller must maintain records (paper or electronic) covering at minimum:

1. The Personal Data collected
2. The purpose of collection per category
3. Details of the Data Controller
4. Retention period
5. Rights and methods for access; conditions of access
6. Use or disclosure under s27 paragraph 3
7. Records of rejected access / objection / accuracy requests (s30, s31, s32, s36)
8. Explanation of security measures under s37(1)

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

**Small organisation exception:** items (1), (2), (3), (4), (5), (6), and (8) may not apply to small organisations — UNLESS the processing is likely to result in a risk to rights and freedoms, OR the processing is non-occasional, OR the processing involves sensitive data (s26). Items (7) always apply.

The "small organisation" threshold is defined by PDPC notification — verify current text.

## Section 40 — Data Processor duties

The Data Processor has three enumerated duties:

1. **Process only on the Data Controller's instructions** (except where instruction is contrary to law / PDPA)
2. **Provide appropriate security measures** AND **notify the Data Controller of any breach**
3. **Maintain records of processing activities** per Committee rules

**Critical:** if the Data Processor fails to comply with (1) — i.e. processes data outside the Data Controller's instructions — **the Data Processor is regarded as the Data Controller** for that processing. This shifts liability significantly.

The Data Controller must prepare a written agreement with the Data Processor controlling the activities. **Implementation layer:** [01 Non-technical](../../../layers/01-non-technical.md) (DPAs).

## Section 41 / 42 — DPO (engineering touch-points)

DPO designation is required where the controller / processor is a public authority, conducts large-scale regular monitoring, or has sensitive data (s26) as a core activity. Designation, qualifications, dismissal protections, conflict-of-interest warranties, and the full s42 duties (advise / investigate / coordinate / confidentiality) are governance — see [01 Non-technical](../../../layers/01-non-technical.md).

**Engineering surface:**

- Published DPO contact in the privacy notice — the email address must route to a real human and not silently bounce.
- DPO needs access to audit logs, breach-register, and processing records to perform s42 monitoring duties — wire those reads on day one rather than retrofitting.
- For affiliated groups under a s29 PDPC-certified policy, a shared DPO is permitted; ensure your privacy notice still names a contactable address per consumer-facing brand.

## Chapter I — Personal Data Protection Committee (s8–18)

The PDPC is the regulator. Composition and powers are governance-level — not directly relevant to compliance implementation. Engineers should know:

- The PDPC has the power to issue notifications that bind Data Controllers and Processors (e.g. defining "small organisation," "large amount," sensitive-data sub-categories, security minimum standards, breach-notification rules)
- The Committee can prescribe forms and statements for consent
- Subordinate notifications continue to be issued — verify current text at [pdpc.or.th](https://www.pdpc.or.th)

## Penalty exposure (this Part)

| Failure | Maximum administrative fine | Source |
|---|---|---|
| Fails to notify per s37 (general) | THB 3M | s83 |
| Fails to notify per s37 involving sensitive data | THB 5M | s84 |
| Fails to maintain records under s39 | THB 1M | s82 |
| Fails to designate DPO under s41 | THB 1M | s82 (controller) / s85 (processor) |
| DPO performance failures under s42 paragraph 2/3 | THB 1M | s82 / s85 |
| Failure to designate Thai representative (s37(5)) | THB 3M | s86 (when applies to processor via s38) |

Plus s81 personal liability for directors / managers whose instructions or omissions led to 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