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/06-breach-notification.md

View on GitHub
# Section 37(4) — Breach Notification (72 hours)

> ⚠ **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's breach notification obligation lives in a single dense paragraph of s37. The 72-hour clock makes preparation in advance non-negotiable.

## Contents

- Section 37(4) — The rule
- What constitutes a breach
- Risk-to-rights-and-freedoms assessment
- What to file with PDPC
- Notifying affected data subjects (high-risk breach)
- Tech-measure exception?
- Vendor / sub-processor breaches
- Records and audit
- Penalty exposure
- Operational checklist (incorporate into the runbook)

## Section 37(4) — The rule

**Rule (verbatim):** *"notify the Office of any Personal Data breach without delay and, where feasible, within 72 hours after having become aware of it, unless such Personal Data breach is unlikely to result in a risk to the rights and freedoms of the Persons. If the Personal Data breach is likely to result in a high risk to the rights and freedoms of the Persons, the Data Controller shall also notify the Personal Data breach and the remedial measures to the data subject without delay. The notification and the exemption to the notification shall be made in accordance with the rules and procedures set forth by the Committee."*

**Three tiers:**

| Risk level | PDPC notification required? | Data subject notification required? |
|---|---|---|
| **Unlikely** to result in risk to rights and freedoms | No | No |
| **Likely** to result in risk (but not high risk) | Yes — within 72 hours | No |
| **High risk** to rights and freedoms | Yes — within 72 hours | Yes — without delay |

**Critical:** the clock starts at **awareness**, not at occurrence. The Data Controller must be able to demonstrate when awareness occurred (assessment-complete timestamp, ticket creation, etc.).

**"Where feasible, within 72 hours"** — Thai PDPA permits exceeding 72 hours where infeasible, but the burden of justifying the delay falls on the Data Controller. Plan to meet 72 hours; treat any longer window as exceptional.

## What constitutes a breach

The Act doesn't define "Personal Data breach" as a separate term — but s37(1) defines the security obligation in terms of *"unauthorized or unlawful loss, access to, use, alteration, correction or disclosure of Personal Data."* A breach is a failure of any of these.

**Examples that should be triaged as breaches:**
- A leaked secret (database credential, API key, OAuth key, encryption key) where it could enable unauthorised access
- An access-control bypass discovered to return data the caller shouldn't see
- A stolen / lost device with active prod credentials
- A misdirected email with Personal Data
- An admin / developer accessing data outside their role
- A scraper or anomalous traffic exfiltrating data
- A user reports their account was accessed by someone else
- A vendor / sub-processor notifies you of a breach on their side

**Internal-only access** (curious admin, no external disclosure) is still a breach under s37(1) and may require notification depending on the risk assessment. (Thai PDPA does not have an explicit "internal-only is not notifiable" carve-out like Singapore's s26B(4).)

**Implementation layer:** [07 Operational](../../../layers/07-operational.md) (incident-response runbook).

## Risk-to-rights-and-freedoms assessment

**High-risk indicators (data subject notification required):**

- Sensitive data (s26) leaked at any scale
- Authentication credentials leaked in a form usable for account takeover
- Health / medical data leaked
- Children's data leaked
- Financial data leaked
- Data enabling identity theft (national ID, government ID, etc.)

Other inputs to the assessment: volume of affected subjects, identifiability (easily-reversible pseudonymisation does not reduce risk), vulnerability of the cohort (minors, patients), and the realistic misuse path (identity theft, financial fraud, physical safety).

When in doubt, notify both PDPC and affected individuals. Over-notification is recoverable; under-notification is a strict-liability breach.

## What to file with PDPC

PDPC Thailand provides a notification form. Verify the current form and submission method at [pdpc.or.th](https://www.pdpc.or.th). At minimum, expect to provide:

- Nature of the breach (one paragraph)
- When discovered, when it occurred (or "unknown — under investigation")
- Number of affected individuals (estimate is fine if exact unknown — update later)
- Types of Personal Data involved (general + whether s26 sensitive categories)
- Cause (root cause if known; "under investigation" otherwise)
- Likely consequences for individuals
- Containment + remediation actions taken (or planned)
- Steps individuals can take to protect themselves
- DPO contact details

## Notifying affected data subjects (high-risk breach)

**Channels (in order of preference):**
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)

**Content** — explain in plain Thai (or the data subject's language of communication):
- What happened
- When
- What Personal Data was involved
- What you've done about it
- What the data subject should do
- How to contact the DPO

## Tech-measure exception?

Thai PDPA does **not** have an explicit "tech measure renders harm unlikely" exception equivalent to Singapore's s26D(5) or GDPR Article 34(3)(a). However, the **risk-to-rights-and-freedoms** assessment naturally takes into account whether data was encrypted, hashed, or otherwise rendered useless to an attacker. Document the assessment basis.

## Vendor / sub-processor breaches

**s40(2)** requires the Data Processor to notify the Data Controller of the breach.
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

**s39(8)** requires the Data Controller to maintain records of security measures;
post-incident remediation belongs in them, and PDPC will review them on investigation.
See [layer 07 Operational](../../../layers/07-operational.md#post-incident-records).

## Penalty exposure

| Failure | Maximum administrative fine | Source |
|---|---|---|
| Fails s37 (including breach notification) generally | THB 3M | s83 |
| Fails s37 involving sensitive data | **THB 5M** | s84 |

Plus s81 personal liability for directors / managers responsible — and potential s79 criminal liability if the underlying breach involves sensitive-data misuse.

## Operational checklist (incorporate into the runbook)

General readiness items: [layer 07 Operational](../../../layers/07-operational.md#runbook-readiness-checklist). TH-specific:

- [ ] PDPC breach notification form (latest version) pre-filled
- [ ] Data-subject notification template pre-staged in **Thai** (and English if applicable)

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