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

checklists/new-feature.md

View on GitHub
# Checklist — Adding or Modifying a Feature

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

Use when introducing or significantly changing any user-facing feature that touches personal data.

> Walk this checklist against the universal layer files (`../layers/`) for **how** to implement, and against the active jurisdiction's obligation files (`../jurisdictions/<code>/obligations/`) for **what** must be true.

## Contents

- 1\. What data does the feature touch?
- 2\. Jurisdiction-specific review
- 3\. Architecture review ([layer 02](../layers/02-architecture.md))
- 4\. Data model review ([layer 03](../layers/03-data-model.md))
- 5\. Controls / processes review ([layer 04](../layers/04-controls-and-processes.md))
- 6\. Feature / UX review ([layer 05](../layers/05-feature-ux.md))
- 7\. Disclosure review ([layer 06](../layers/06-disclosure.md))
- 8\. Operational review ([layer 07](../layers/07-operational.md))
- 9\. Backwards compatibility
- 10\. Cross-references

## 1. What data does the feature touch?

List **every** data category the feature reads or writes. Be specific (`profiles.email`, not "user info").

If ANY entry is new (not already in your privacy policy's data categories section):
→ Run [`new-data-field.md`](new-data-field.md) for the new field.

## 2. Jurisdiction-specific review

**Do this before the layer reviews below.** Several obligations change what you build
rather than what you check afterwards — MY s7(3) needs bilingual notice copy, PH § 13
needs written consent captured before processing, ID Pasal 34 can make a DPIA a launch
gate. Finding those after the architecture and disclosure work means redoing it.

For each active jurisdiction (see SKILL.md Step 1), walk the relevant obligation files:

**Singapore PDPA** (if active): walk through `../jurisdictions/sg-pdpa/obligations/01–07` and verify the feature satisfies each that applies. Pay particular attention to:
- s14(2)(a) bundled consent — **if adding a new notification channel** (push, SMS, email, in-app): is consent bundled with signup T&Cs, or is it a separate explicit opt-in? Bundled is acceptable **only** if every notification on that channel is *transactional* (verification, friend requests, message delivery). The moment one *marketing* notification is added (digests, retention pushes, promotions), bundled consent is no longer sufficient — you need a separate marketing-opt-in toggle that defaults to **off**.
- s21 access (does the new field need to be in `export_user_data`?)
- s24 protection (RLS / equivalent on any new table)
- s25 retention (TTL on any new column? if storing files: orphan-reaping covered?)
- s26D(1) breach notification (does this feature widen the breach surface? add to runbook?)

**Thailand PDPA** (if active): walk `../jurisdictions/th-pdpa/obligations/01–07`. Particular attention:
- s26 sensitive personal data — broader than SG; add a separate explicit-consent modal where any sensitive category is in scope.
- s32 data portability — export format must be transferable to another controller.
- s34 right-to-restrict — if this feature touches data covered by an active restriction, the mutation path must check the restriction state.
- s37 breach notification (72h from awareness).

**Indonesia UU PDP** (if active): walk `../jurisdictions/id-pdp/obligations/01–07`. Particular attention:
- Pasal 22 form-of-consent — strict; non-compliant consent is null and void; ensure simple language, clear distinction from T&C.
- Pasal 25 — accessibility / alternative consent channels for users with disabilities.
- Pasal 34 mandatory DPIA — **does this feature trigger any of the 7 DPIA triggers** (automation, sensitive PD, large-scale, regular monitoring, data matching, novel tech, rights-restrictive)? If yes, the DPIA artefact must exist before launch.
- Pasal 31 RoPA — update the formal records-of-processing inventory with the new purpose / recipients.
- Pasal 40, 41 — 72-hour SLAs on consent withdrawal and processing-restriction respectively; encode as per-jurisdiction SLA constants in the corresponding handlers.
- Pasal 46 breach notification — 72h to **both** subject and regulator; subject notification is **not** gated on harm.

**Malaysia PDPA** (if active): walk `../jurisdictions/my-pdpa/obligations/01–07`. Particular attention:
- s7(3) — privacy notice and choice mechanism must be available in **both Bahasa Malaysia and English**. Translation review is a release blocker.
- s4 — sensitive personal data now includes **biometric data** (face embeddings, fingerprints, voice prints, gait, iris). Trigger a separate explicit-consent dialog under s40(1)(a).
- s9 / s5(1A) — if this feature changes who-processes-what, recall that data processors are now directly liable under s9 (post-1 April 2025).
- s12B breach notification — 72h Commissioner / 7d subject (per JPDP Guideline 25 Feb 2025). Confirm the runbook has the MY lane.
- s43A data portability — if the feature creates a new export surface, satisfy s43A by exposing a structured machine-readable format and a direct-transmission path.

**Philippines DPA** (if active): walk `../jurisdictions/ph-dpa/obligations/01–07`. Particular attention:
- § 13 sensitive personal information is a **closed statutory list**, not a harm test — if the feature touches any listed category, consent must be written or electronically signed and captured **before** processing.
- § 16(b) right to object covers **automated processing and profiling** explicitly — any new scoring, ranking, or recommendation surface needs an objection path.
- § 16(e) right to **erasure or blocking** — the feature must be able to suspend further processing of a record, not only delete it.
- § 20(f) + NPC Circular 16-03 breach notification — 72h to **NPC and subjects in parallel**. Does this feature widen the breach surface? Add the PH lane to the runbook.
- § 34 personal liability for responsible officers and **§ 30 concealment as its own offence** — escalation paths must not allow an incident to be quietly closed.

**Vietnam PDPL** (if active): walk `../jurisdictions/vn-pdpl/obligations/01–08`. Particular attention:
- **Điều 21 / Điều 20 — the assessments are *filed*, not just held.** One original of the processing-impact dossier to the authority within **60 days of first processing**, and a separate cross-border dossier within **60 days of first transfer**. The clock starts from your own first action, silently.
- **Điều 20(1)(c) — using any platform outside Vietnam** to process data collected in Vietnam is a cross-border transfer. A foreign-region database, analytics SaaS or model API puts the feature in scope on day one.
- **Decree Điều 4(1)(l)** — behaviour-tracking data on online services is **sensitive**. If the feature adds analytics events, it is a sensitive-data feature.
- **Điều 37(1)(h)** — you must prevent unauthorised collection from your own systems, so rate limiting and enumeration defence on endpoints exposing personal data are compliance measures here.
- **Điều 24–32 + Decree Điều 8–12** — check the sector overlay: children, employment, health, finance, advertising, social media, big data / AI / blockchain, cloud, location and biometrics, public recording.

## 3. Architecture review ([layer 02](../layers/02-architecture.md))

- [ ] No raw queries bypass per-user data isolation. Every read filters by current-user identity, enforced at the platform level (RLS or equivalent), not just at the application level.
- [ ] Any new privileged function follows the privileged-function discipline: documented, tightened search path / namespace, audit-logged.
- [ ] Any new external-domain call goes to a vendor that's already in the privacy policy sub-processor list — if not, run [`new-vendor.md`](new-vendor.md).
- [ ] No new place ships service / admin credentials to the client.

## 4. Data model review ([layer 03](../layers/03-data-model.md))

- [ ] If new tables added: per-user isolation enabled (RLS on the table, or equivalent platform mechanism, or RPC-only access).
- [ ] If new tables hold personal data: explicit access policies OR no policies at all (deny-by-default + RPC-only).
- [ ] If new foreign keys to the users table: chosen CASCADE vs SET NULL deliberately (CASCADE for owned data, SET NULL for shared).
- [ ] If new column holds a retention-bound value: documented retention rule + sweep job.
- [ ] If new column is personal data: added to the PII inventory.

## 5. Controls / processes review ([layer 04](../layers/04-controls-and-processes.md))

- [ ] If new admin endpoint added: role check at top + audit log call at end (mutation logger always; throttled read logger for personal-data reads).
- [ ] If new server-side function added that logs: uses sanitised logging helpers (`safeError` / `redactPII` / `redactId`) at every variable interpolation.
- [ ] If new retention rule introduced: cleanup function added to the canonical sweep.
- [ ] If new column in scope of the data-export endpoint: export updated in this PR (don't leave it as a TODO — the export must remain complete).

## 6. Feature / UX review ([layer 05](../layers/05-feature-ux.md))

- [ ] If new OS-level permission required: just-in-time request, soft-prompt before the OS dialog.
- [ ] If new opt-in / consent toggle introduced: settings UI to revoke is symmetric (same effort as granting).
- [ ] If photos uploaded: goes through re-encoding pipeline (EXIF stripped).
- [ ] If new account-data field added: included in delete-account cascade or SET NULL pattern.
- [ ] If new consent collected: writes to consent record with accurate timestamp (not pre-seeded before the user actually consented).

## 7. Disclosure review ([layer 06](../layers/06-disclosure.md))

- [ ] If new personal-data field collected: privacy policy data-categories section updated.
- [ ] If new purpose for existing data: privacy policy purposes table updated.
- [ ] If new retention rule: privacy policy retention table updated AND T&C mirror updated where applicable.
- [ ] If new permission: OS usage string + Android rationale updated.
- [ ] If T&C materially changes: bump T&C version in user-record column; decide on re-acceptance prompt.
- [ ] "Last updated" date bumped on any privacy policy or T&C change.

## 8. Operational review ([layer 07](../layers/07-operational.md))

- [ ] If new cron-relevant cleanup: hooked into the canonical sweep (don't create a new schedule).
- [ ] If feature creates new high-PII surface: consider whether breach-detection signals are needed.
- [ ] If feature touches admin tooling: confirm AUP applies to any new role / permission.

## 9. Backwards compatibility

- [ ] No client-callable function signature change (or, if required, coordinated with version pinning / force-update).
- [ ] No removal of JSON keys from existing function return shapes.
- [ ] No tightened validation on existing functions that would silently break older clients.

## 10. Cross-references

After landing the PR:
- Update any project-level "Open compliance gaps" tracking if this PR closes or opens one.
- Verify the conditional / parking-lot items in your project's notes don't get triggered by this change (e.g. did you add the first marketing notification? → split consent toggles).
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