本文へ移動
cccskills
無料GitHub で公開

singapore-pdpa

Guides compliance with Singapore's Personal Data Protection Act 2012 (PDPA). Covers PDPC advisory guidelines, Do Not Call Registry, data intermediary obligations, deemed consent, notification requirements, and the 2020-2021 amendments. Keywords: Singapore PDPA, PDPC, Do Not Call Registry, deemed consent, data intermediary, advisory guidelines.

インストール方法を見る

含まれるファイル(5)

  • SKILL.md11.0 KB
  • assets/template.md2.3 KB
  • references/standards.md2.6 KB
  • references/workflows.md3.7 KB
  • scripts/process.py6.2 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Singapore PDPA Compliance

Overview

Singapore's Personal Data Protection Act 2012 (PDPA, No. 26 of 2012) was enacted on 15 October 2012 and took effect in phases, with the main data protection provisions effective from 2 July 2014. Significant amendments in 2020 (effective 1 February 2021) introduced mandatory breach notification, deemed consent by notification, a data portability obligation, and enhanced enforcement powers.

The Personal Data Protection Commission (PDPC) is the regulatory authority, operating under the Infocomm Media Development Authority (IMDA). The PDPC issues Advisory Guidelines that provide detailed interpretation of the PDPA.

Key PDPA Obligations (Nine Obligations)

The Nine Obligations Framework

ObligationPDPA SectionDescription
ConsentPart IV, Division 1Obtain consent for collection, use, and disclosure; notify of purposes
Purpose LimitationSection 18Collect, use, or disclose only for purposes a reasonable person would consider appropriate
NotificationSection 20Notify individuals of purposes before or at the time of collection
AccessSection 21Provide individuals access to their personal data upon request
CorrectionSection 22Correct errors or omissions in personal data upon request
AccuracySection 23Make reasonable effort to ensure personal data is accurate and complete
ProtectionSection 24Protect personal data with reasonable security arrangements
Retention LimitationSection 25Retain personal data only as long as necessary for business or legal purposes
Transfer LimitationSection 26Transfer overseas only to jurisdictions with comparable protection
Data Breach NotificationPart VIANotify PDPC and affected individuals of notifiable data breaches

Consent Framework

Types of Consent Under PDPA

Consent TypeProvisionDescription
Express consentSection 14Explicit consent given orally, in writing, or electronically
Deemed consent by conductSection 15Consent inferred from voluntary provision of data for a stated purpose
Deemed consent by notificationSection 15A (2020 amendment)Consent deemed after notification with reasonable opt-out period and no opt-out exercised
Deemed consent by contractual necessitySection 15A(2)Consent deemed for disclosure necessary to perform a contract with the individual

Deemed Consent by Notification (Section 15A)

Requirements for valid deemed consent by notification:

  1. The organisation has conducted an assessment and determined that the collection, use, or disclosure is unlikely to have an adverse effect on the individual
  2. The organisation has taken reasonable steps to notify the individual (or bring to attention) of the purpose and that consent will be deemed
  3. The organisation has provided a reasonable period for the individual to opt out
  4. The individual has not opted out within the stated period

Exceptions to Consent (Second, Third, and Fourth Schedules)

Exception CategoryExamples
Business improvementUsing personal data for improving/developing products and services (reasonable expectation standard)
Legal and business purposesDebt recovery, insurance claims, legal proceedings
National interestNational security, public health emergencies
Publicly availableData made publicly available by law or the individual
Vital interestsEmergency affecting life, health, or safety
ResearchResearch and statistics with anonymisation safeguards

Do Not Call (DNC) Registry (Part IX)

DNC Obligations

ElementDetail
ScopeMarketing messages sent to Singapore telephone numbers via voice calls, text messages, or fax
Registry typesNo Voice Call Register, No Text Message Register, No Fax Message Register
Check obligationOrganisations must check the DNC Registry before sending marketing messages to Singapore numbers
Check validityDNC check results valid for 30 days
ExemptionsMessages to existing customers regarding similar products/services (with opt-out); messages with express consent documented
PenaltiesUp to SGD 1 million per breach; financial penalties imposed by the PDPC

Zenith Global Enterprises DNC Compliance

ElementDetail
DNC checkingAutomated daily DNC register check before marketing campaign dispatch
Marketing channelsEmail (not subject to DNC), SMS (DNC checked), phone calls (DNC checked)
Existing customer exemptionApplied for freight service-related communications with documented opt-out mechanism
Consent recordsDocumented express consent stored in CRM for opted-in customers

Data Intermediary Obligations (Section 4(2))

Definition

A data intermediary processes personal data on behalf of another organisation (the data controller) and does not use or disclose the data for its own purposes. Analogous to a "data processor" under GDPR.

Obligations

ObligationDetail
Protection (Section 24)Data intermediary must protect personal data in its possession or control
Retention (Section 25)Must not retain personal data longer than necessary
Transfer (Section 26)Transfer overseas restrictions apply
Breach notification (Part VIA)Must notify the organisation (not the PDPC directly) of a data breach without unreasonable delay
No consent obligationData intermediary not required to obtain consent (this is the data controller's responsibility)

Zenith Global Enterprises Data Intermediary Register

IntermediaryServiceData ProcessedContract Date
CloudServe Asia Pte LtdCloud hostingCustomer and employee data1 March 2025
LogiTech Solutions Pte LtdCustoms IT platformCustoms clearance data15 June 2025
PayGlobal Pte LtdPayment processingTransaction data1 January 2025

Mandatory Breach Notification (Part VIA)

Notifiable Data Breach Definition (Section 26B)

A data breach is notifiable if it results in, or is likely to result in:

  • Significant harm to the affected individuals, OR
  • Is of a significant scale (affecting 500 or more individuals)

Notification Requirements

ElementPDPC NotificationIndividual Notification
When requiredAll notifiable data breachesBreaches likely to result in significant harm
TimelineAs soon as practicable, not later than 3 calendar days of assessment completionAs soon as practicable after assessing the breach
Assessment deadlineMust assess within 30 calendar days of becoming aware of the breachSame assessment period
ContentNature, circumstances, data affected, number of individuals, steps taken, DPO contactNature of breach, steps individual can take, DPO contact

Significant Harm Criteria (Section 26B(2))

  • Unauthorised access to or possession of prescribed personal data (NRIC numbers, financial account information, health information)
  • Financial loss
  • Physical harm
  • Harassment
  • Damage to reputation

Data Portability (Part VIB)

The 2020 amendments introduced a data portability obligation (effective date to be prescribed):

  • Individuals may request their data be transmitted to another organisation
  • Applies to data provided by the individual or arising from the individual's use of the organisation's services
  • Porting organisation may charge a reasonable fee
  • Technical framework being developed by the PDPC

Cross-Border Transfer (Section 26)

Transfer Requirements

Personal data may only be transferred outside Singapore if:

ConditionDetail
Comparable protectionThe recipient country or organisation provides a standard of protection comparable to PDPA (Section 26(1))
Contractual safeguardsLegally enforceable obligations on the overseas recipient to provide comparable protection (PDPC-recommended approach)
Individual's consentConsent with notification of inadequate overseas protection
Binding corporate rulesWithin a corporate group with binding internal rules
PDPC-recognised frameworkAPEC CBPR certification or other PDPC-recognised mechanism

PDPC Advisory Guidelines on Cross-Border Transfers

  • Contractual clauses with the overseas recipient are the most commonly used mechanism
  • Must include: purpose limitation, security obligations, breach notification, sub-processing restrictions, access and correction facilitation
  • No formal adequacy determination process (unlike GDPR)

Enforcement Framework

Financial Penalties (Section 48J, as amended 2020)

Entity TypeMaximum Penalty
OrganisationsUp to SGD 1 million or 10% of annual turnover in Singapore (whichever is higher) for serious breaches
DNC violationsUp to SGD 1 million per breach

Notable PDPC Enforcement Decisions

SingHealth Breach (2019):

  • Fine: SGD 250,000 to IHiS (IT agency) and SGD 750,000 to SingHealth
  • Breach: Unauthorised access to patient records of 1.5 million patients, including Prime Minister's data
  • Significance: Largest PDPC fine at the time; led to strengthened healthcare data protection measures

GrabCar (2021):

  • Fine: SGD 10,000
  • Violation: Unauthorised disclosure of passenger personal data in a data analytics feature
  • Significance: Demonstrated PDPC enforcement on ride-hailing platforms

Razer (2022):

  • Fine: SGD 50,000
  • Violation: Failure to protect personal data of approximately 100,000 customers
  • Significance: Server misconfiguration leading to data exposure

Compliance Programme

ComponentDetail
DPO (Singapore)Tan Wei Lin, Data Protection Manager — Singapore office
Contactdpo-sg@zenithglobal.com.sg
Privacy noticePublished at zenithglobal.com.sg/privacy
Consent frameworkExpress consent for marketing; deemed consent by conduct for service provision
DNC complianceAutomated DNC register checking; 30-day check validity
Breach notification30-day assessment + 3-day PDPC notification workflow
Data intermediary managementContractual clauses with all intermediaries per PDPC guidelines
Cross-border transfersContractual safeguards with overseas recipients
Data subject rightsAccess and correction within 30 days; fees per PDPC guidelines

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Implements 42 CFR Part 2 protections for substance use disorder patient records. Covers written consent requirements stricter than HIPAA, re-disclosure prohibition, court order procedures, qualified service organization agreements, and 2024 amendments aligning Part 2 with HIPAA. Keywords: 42 CFR Part 2, substance use disorder, SUD records, re-disclosure, consent, Part 2 amendments.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Guides assessment of third-country adequacy decisions under GDPR Article 45 for international data transfers. Covers the current EC adequacy decisions list, adequacy assessment criteria, partial adequacy handling, and monitoring of adequacy decision reviews. Keywords: adequacy decision, Article 45, third country, adequate protection, EC adequacy list.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Implements age-gating mechanisms for online services to restrict access based on user age. Covers hard gates versus soft gates, neutral age prompts, re-verification triggers, circumvention prevention, and regulatory requirements under GDPR, COPPA, UK Online Safety Act, and DSA. Keywords: age gate, age restriction, neutral prompt, children, online services, access control.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Evaluates and implements age estimation and verification technologies for online services. Covers facial age estimation, digital ID verification, self-declaration with risk assessment, AI-based age estimation, and the accuracy versus privacy tradeoff. Includes ICO guidance and euCONSENT framework. Keywords: age verification, age estimation, facial analysis, digital ID, children, online safety.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Preparing EU AI Act compliance documentation for high-risk AI systems. Covers Annex III classification, technical documentation under Art. 11, conformity assessment, risk management systems, and CE marking requirements. Keywords: EU AI Act, high-risk AI, Annex III, conformity assessment, CE marking.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Implements GDPR Art. 22 automated decision-making and AI Act Art. 14 human oversight requirements for AI systems. Covers identification of solely automated decisions, meaningful human intervention design, logic explanation mechanisms, and contestation procedures. Keywords: Art. 22, automated decision, human oversight, AI Act, profiling, contestation.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

mukul975 のスキルをすべて見る

このスキルの問題を報告する