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

View on GitHub
# Part 4 Division 1 — Consent (s13–17)

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

## s13 — Consent required before collection / use / disclosure

**Rule (verbatim):** *"An organisation must not collect, use or disclose personal data about an individual unless the individual gives, or is deemed to have given, his or her consent under this Act to the collection, use or disclosure, or the collection, use or disclosure is required or authorised under this Act or any other written law."*

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

**Operationalisation:**
- Active opt-in at signup (T&C / privacy policy checkbox)
- Just-in-time OS-level permission prompts (camera, photos, location, notifications) — see [layer 05](../../../layers/05-feature-ux.md)
- No silent collection — every endpoint maps either to a consented purpose or to a s17 exception

## s14(2)(a) — No bundled consent beyond what is reasonable

**Rule (verbatim):** *"An organisation must not, as a condition of providing a product or service, require an individual to consent to the collection, use or disclosure of personal data about the individual beyond what is reasonable to provide the product or service."*

**Practical effect:** marketing / promotional consent must be **separable** from operational / transactional consent. A single "I agree" checkbox covering both is non-compliant if the application sends marketing.

**Implementation layer:** [05 Feature/UX](../../../layers/05-feature-ux.md).

**Operationalisation:**
- Mandatory signup data: keep minimal (full name, contact for verification, anything required for service delivery)
- Optional data and marketing: separate toggles, default off
- If everything in the app is transactional (no marketing pushes / emails): a single bundled consent is acceptable. The line shifts the moment marketing is added.

## s14(2)(b) — No deceptive consent practices

**Rule (verbatim):** *"An organisation must not obtain or attempt to obtain consent for collecting, using or disclosing personal data... by providing false or misleading information... or using deceptive or misleading practices."*

**Practical effect:** plain-language disclosures, no pre-checked boxes for non-essential purposes, no dark patterns ("agree" button visually dominant, "decline" hidden).

**Implementation layers:** [05 Feature/UX](../../../layers/05-feature-ux.md), [06 Disclosure](../../../layers/06-disclosure.md).

## s15 — Deemed consent (voluntary provision + contract necessity)

**Rule:** an individual is deemed to consent if they voluntarily provide the personal data and it is reasonable that they would do so. Sub-flows in s15(3) and s15(6) cover sharing data with sub-processors during contract performance.

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

**Operationalisation:**
- Document which fields rely on deemed vs explicit consent
- For data shared with sub-processors during contract performance, the s15(3)/(6) chain applies — and respects contractual purpose limits (don't expand the sub-processor's permitted use)

## s15A — Deemed consent by notification (opt-out)

**Rule:** an individual may be deemed to consent to a new use of existing data if (a) the organisation conducts an assessment that the use is **not likely to have an adverse effect** on the individual; (b) takes reasonable steps to inform of intent, purpose, and a reasonable opt-out window; (c) the individual does not opt out within that window. Excludes prescribed purposes.

**When relevant:** introducing a new use of data already collected, without going back for fresh consent.

**Operationalisation:**
- Run and document an adverse-effect assessment **before** relying on this basis
- In-app notice + email with clear opt-out and stated window (≥ 14 days is a defensible default)
- Implement an opt-out endpoint and honour opt-outs **before** the new use begins

## s16 — Withdrawal of consent

**Rule (verbatim, key language):** an individual *"may at any time withdraw any consent"*; the organisation *"must inform the individual of the likely consequences of withdrawing"*; *"must not prohibit"* withdrawal; on withdrawal *"must cease (and cause its data intermediaries and agents to cease) collecting, using or disclosing the personal data."*

**Implementation layers:** [05 Feature/UX](../../../layers/05-feature-ux.md) (settings toggles), [04 Controls](../../../layers/04-controls-and-processes.md) (cessation propagation to sub-processors).

**Operationalisation:**
- Settings toggles for each consent the user gave, with equal effort to revoke as to grant
- Confirmation dialog stating the consequences of withdrawal where they're non-obvious
- On withdrawal, cessation must propagate to:
  - Database state (notification flag flipped, push token nulled)
  - Sub-processors (push provider de-registered, OAuth token revoked, etc.)
  - Future operations (retention sweeps, scheduled jobs)
- Target cessation latency: ASAP; PDPC guidance is ≤ 30 days

## s17 + First/Second Schedules — Collection / use / disclosure without consent

**Rule:** specific enumerated cases where consent is not required. Not a general balancing test (unlike GDPR's legitimate interests).

**Common cases for consumer apps:**

| Schedule item | When it applies |
|---|---|
| 1st Sch Pt 1 — Vital interests | Lost-pet emergency, safety / medical situations |
| 1st Sch Pt 3 §1 — Legitimate Interests | Fraud prevention, abuse moderation, safety. Requires written assessment + reasonable user access to information about the use |
| 1st Sch Pt 3 §3 — Investigations | Police / abuse reports |
| 1st Sch Pt 4 — Business asset transactions | Acquisition / sale of the business; users notified post-deal; data destroyed if deal fails |
| 1st Sch Pt 5 / 2nd Sch Pt 2 Div 2 — Business improvement | Single-org product analytics. Identifiable form must be necessary AND a reasonable person would consider use appropriate. **Cannot be used for marketing.** |
| 2nd Sch Pt 2 Div 3 — Research | Strict purpose limitation |

**Operationalisation:**
- Maintain a per-data-flow lawful-basis register
- For Legitimate Interest reliance: document the assessment (LIA) before launch
- For Vital Interest reliance: notify the individual *"as soon as is practicable"* after the use
- For Business Improvement reliance: never extend to marketing use

## Cross-references

- [05-care.md](05-care.md) for the related Protection (s24) and Retention (s25) obligations
- [03-purpose.md](03-purpose.md) for the related Purpose Limitation and Notification of Purpose obligations
- [06-breach-notification.md](06-breach-notification.md) for cessation duties triggered by a breach
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