Compliance CalendarSingaporePDPA

Singapore PDPA deadlines and compliance calendar

Use this calendar to schedule breach assessment, PDPC notification, affected-individual notification, checks, access and correction requests, enforcement responses, and privacy programme reviews.

Each clock starts from a specific event. Record that event, the applicable rule or guidance, the owner, the due date, and evidence of the response.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 24, 2026
Overview

Use this calendar for event-driven PDPA clocks, not as a claim that every item has the same legal force. The three-day breach-notification deadline, DNC checking window, and 28-day reconsideration and appeal periods come from binding instruments; the 30-day breach-assessment point and 14-day preliminary-decision representation period are PDPC guidance; retention and programme reviews use organisation-set dates tied to purpose, risk, and change events. Record the trigger, source, legal status, owner, due date, outcome, and proof for each entry.

Section 1

Breach response clocks to open immediately

Open a breach calendar entry when the organisation has credible grounds to believe that a data breach has occurred, including where a data intermediary reports the breach. The assessment owner should determine whether it is a and document containment, facts established, data affected, likely harm, number of affected individuals, and the decision.

The Act requires reasonable and expeditious assessment. PDPC guidance uses as the operational benchmark: if the organisation cannot finish within that period, it should be ready to explain the time taken or required. Treat 30 days as an escalation point, not permission to delay an assessment that could reasonably be completed earlier.

  • Trigger: credible grounds to believe that a data breach has occurred.
  • Assessment window: take reasonable and expeditious steps to determine notifiability; escalate any assessment still open at and document the reason.
  • PDPC notification: if the breach is notifiable, notify the PDPC as soon as practicable and no later than three calendar days after determining notifiability.
  • Day-count rule: the first day of the three-day PDPC notification period starts on the day after the organisation determines that the breach is notifiable.
  • Affected individuals: where notification is required, notify them as soon as practicable, at the same time as or after notifying the PDPC.
  • Evidence to keep: breach log, containment record, assessment chronology, notifiability rationale, notification submission, late-notification reasons if applicable, and affected-individual communication plan.
Section 2

DNC Registry campaign checks and validity windows

Open a DNC calendar entry before a telemarketing campaign sends specified messages to Singapore telephone numbers, unless the campaign has clear and unambiguous consent in evidential form or another cited exception applies.

results are not evergreen. Campaign operations should treat the result date as a hard expiry control and re-check before continuing telemarketing after the validity period lapses.

  • Trigger: planned voice call, text message, or fax telemarketing campaign to Singapore telephone numbers.
  • Register coverage: check the relevant No Voice Call, No Text Message, and No Fax Message registers before sending.
  • Result validity: results are valid for up to 21 days; re-check after that if telemarketing continues.
  • Bulk filtering service level: bulk filtering results are available within 24 hours, so campaign schedules should leave time for upload, result retrieval, and suppression.
  • Evidence to keep: campaign audience date, DNC submission method, result file, suppression list, consent evidence where relied on, checker account used, and result-expiry date.
Section 3

Access and correction request response timing

Open an access or correction request entry when a written request reaches the DPO business contact information, registered office, principal office, or another accepted channel with enough detail to identify the applicant and request.

The PDPA timing language is not a permission to wait until day 30. Access must be provided as soon as reasonably possible, and correction must be made as soon as practicable, subject to exceptions and valid grounds.

  • Access requests: respond as soon as reasonably possible after receiving the request.
  • Access 30-day update: if the organisation cannot respond within 30 days, inform the individual in writing within 30 days when it will be able to respond.
  • Correction requests: correct personal data as soon as practicable unless satisfied on reasonable grounds that the correction should not be made.
  • Correction 30-day update: if the organisation cannot correct the data within 30 days, inform the individual in writing within 30 days when it will be able to correct it.
  • Correction downstream lookback: send corrected personal data to other organisations to which it was disclosed within the year before the correction request, unless the other organisation does not need it for a legal or business purpose.
  • Evidence to keep: request intake, identity verification, scope clarification, exception or rejection rationale, fee estimate if charged for access, response date, correction notice, annotation where correction is rejected, and preservation record for withheld access data.
Section 4

Enforcement notice, reconsideration, and appeal clocks

Open an enforcement calendar entry as soon as the PDPC issues a written notice, preliminary decision, final decision, direction, or financial penalty. These clocks concern the regulatory process after PDPC action; they do not replace any remediation deadline stated in the notice or direction.

The enforcement guidelines give an organisation or person 14 days to make written representations on a preliminary decision and proposed action. An extension may be requested, but the Commission may grant it only if exceptional circumstances in the particular case warrant more time.

A person aggrieved by an eligible decision, direction, or financial penalty may apply for reconsideration within 28 days, or appeal an eligible decision or direction within 28 days. The available route and standing depend on the specific provision. A reconsideration application or appeal generally does not suspend the contested decision, except for a financial penalty, unless the Commission or appeal committee decides otherwise.

  • Preliminary decision: calendar 14 days for written representations and attach the supporting documents or information on which the response relies.
  • Financial penalty payment: use the payment date stated in the notice; PDPC guidance says it will be no earlier than 28 days after the notice is issued.
  • Reconsideration: calendar 28 days from issuance of the eligible decision, direction, or financial penalty, and record the grounds, required copy, prescribed fee, and any stay request.
  • Appeal: calendar 28 days from issuance of the eligible decision or direction; if reconsideration is also sought for the same matter, the statutory interaction between the two routes must be checked before filing.
  • Evidence to keep: notice and receipt date, preliminary decision, response owner, representations and exhibits, extension request and outcome, final decision, payment instruction, reconsideration or appeal filing, stay request, and proof that each direction was completed.
Section 5

Retention and privacy programme review cadence

The PDPA does not set one universal retention period for all personal data. Calendar entries should therefore track each record class against its collection purpose, legal or business need, retention rationale, and disposal or anonymisation method.

For privacy programme maintenance, PDPC guidance supports both ad-hoc updates when major incidents, legal changes, or organisational changes occur and periodic review at a pre-specified interval chosen by the organisation.

  • Retention trigger: purpose no longer served and retention no longer necessary for legal or business purposes.
  • Retention review: review personal data held on a regular basis to decide whether it is still needed.
  • Long retention periods: document the rationale in the personal data retention policy.
  • Programme review: revise data protection policies immediately for major incidents, legislative or regulatory amendments, and organisational or process changes.
  • Periodic review: schedule a pre-specified interval for policy and process review; PDPC examples also describe quarterly or annual reporting topics for risk monitoring.
  • Evidence to keep: data inventory, retention period by record class, legal or business rationale, disposal or anonymisation record, policy-review date, ad-hoc change trigger, audit finding, and remediation status.
Primary sources

References and citations

pdpc.gov.sg3 citations
Referenced sections
  • Supports access and correction response timing, correction disclosure lookback, data intermediary breach notice language, and retention limitation review logic.
  • Supports the access request response clock, correction request response clock, one-year correction disclosure lookback, and preservation expectations.
  • Supports the retention limitation rule, regular review of personal data held, and the absence of one fixed PDPA retention period.
"inform the individual in writing within 30 days"
More quoted passages
"does not specify a fixed duration"
pdpc.gov.sg3 citations
Referenced sections
  • Supports operational calendar entries for access-request handling, breach management, ad-hoc policy updates, periodic review, and risk reporting cadence examples.
  • Supports using an internal access-request policy that tracks response timeframe, identity verification, exceptions, and request records.
  • Supports ad-hoc and periodic review of data protection policies and examples of quarterly or annual risk reporting.
"every quarter or annually"
More quoted passages
"unable to provide access within 30 days"
"Revision of data protection policies and processes at regular intervals"
pdpc.gov.sg2 citations
Referenced sections
  • Supports calendar entries for preliminary-decision representations, financial-penalty payment timing, reconsideration, appeals, stays, and evidence submitted in the enforcement process.
  • Supports the 14-day representation period, exceptional-circumstances extension, payment date no earlier than 28 days after notice, 28-day reconsideration and appeal windows, and the rules on whether a filing suspends the contested decision.
pdpc.gov.sg2 citations
Referenced sections
  • Supports the DNC duty to check before sending specified messages and the consent-evidence exception framing.
  • Supports the duty to check the DNC Register before sending specified messages unless clear and unambiguous consent in evidential form is available.
"Duty to check the DNC Register"
pdpc.gov.sg2 citations
Referenced sections
  • Supports breach assessment within 30 calendar days, PDPC notification within three calendar days after determining notifiability, affected-individual notification timing, and late-notification evidence.
  • Supports the 30-calendar-day breach assessment window, the three-calendar-day PDPC notification deadline, affected-individual timing, and late-notification evidence.
"no later than three (3) calendar days"
More quoted passages
"within 30 calendar days"
pdpc.gov.sg2 citations
Referenced sections
  • Supports DNC Registry result validity and bulk filtering turnaround used in the calendar.
  • Supports DNC result validity, bulk filtering turnaround, and accepted number format.
"Results returned from the DNC Registry are valid for up to 21 days"
More quoted passages
"valid for up to 21 days"
pdpc.gov.sg2 citations
Referenced sections
  • Supports the public PDPC breach reporting deadline summary for notifiable data breaches.
  • Supports the rule that a notifiable breach must be reported to the PDPC as soon as practicable and no later than three calendar days.
"no later than three (3) calendar days"
sso.agc.gov.sg2 citations
Referenced sections
  • Supports the statutory PDPA context for access, correction, retention, DNC, and data breach notification obligations mapped by this calendar.
  • Provides the current statutory framework for written notices, reconsideration, appeals, and enforcement of PDPC directions and financial penalties.
"Personal Data Protection Act 2012"
Show all related guides (37)

Singapore PDPA Consent and Deemed Consent Workflow

Choose express consent, deemed consent by conduct, contractual necessity, notification, or the legitimate interests exception under Singapore PDPA with fact-based intake fields and evidence records.

Singapore PDPA Consent, Notification and Purpose Rules

How Singapore PDPA consent, notification, purpose limitation, deemed consent, withdrawal, and consent exceptions should be handled in product and privacy workflows.

Singapore PDPA Cross-Border Transfers

Source-cited Singapore PDPA guidance for overseas personal data transfers, comparable protection, ASEAN MCCs, APEC certifications, vendor roles, and evidence records.

Singapore PDPA Data Breach Notification Thresholds

Source-cited Singapore PDPA breach notification thresholds covering significant harm, the 500-individual significant-scale test, assessment records, and notification timing.

Singapore PDPA Data Intermediary Responsibilities

Practical Singapore PDPA guide to data intermediary role boundaries, organisation accountability, protection, retention, breach escalation, and contract evidence.

Singapore PDPA Deemed Consent and Legitimate Interests

How to apply Singapore PDPA deemed consent by conduct, contractual necessity, notification, and legitimate interests with opt-out, adverse-effect, disclosure, and assessment records.

Singapore PDPA DNC and Marketing Messages Guide

A source-cited Singapore PDPA guide to DNC checks, specified marketing messages, Singapore telephone numbers, consent evidence, opt-outs, sender duties, and excluded messages.

Singapore PDPA DNC Marketing Checks

Operational checklist for Singapore PDPA DNC marketing checks: account evidence, register status, 21-day result validity, consent evidence, and campaign owner records.

Singapore PDPA DNC Marketing Workflow

Workflow for Singapore PDPA DNC marketing campaigns: classify specified messages, check Singapore telephone numbers, document consent, suppress opt-outs, and approve sends.

Singapore PDPA DPMP Accountability Guide

Build a Singapore PDPA Data Protection Management Programme with DPO ownership, policies, data inventories, DPIAs, training, monitoring, breach logs, and review records.

Singapore PDPA FAQ: scope, DPO, consent, breaches and DNC

FAQ answers for Singapore PDPA implementation, covering scope, accountability, consent, access and correction, security, retention, transfers, data intermediaries, breach notification, and DNC checks.

Singapore PDPA NRIC Handling Rules

When Singapore organisations may collect, use, disclose, retain, mask, or replace NRIC numbers, including the 31 December 2026 authentication deadline.

Singapore PDPA Penalties and Enforcement Cases

How PDPC enforcement under Singapore's PDPA works: directions, voluntary undertakings, published decisions, financial penalty caps, and implementation lessons from cases.

Singapore PDPA Penalties and Fines

Singapore PDPA penalty ceilings, PDPC directions, undertakings, breach notification context, and practical controls based on official PDPC and Singapore Statutes sources.

Singapore PDPA Privacy Policy Template

A Singapore PDPA privacy policy template for writing notices, DPO contact details, access and correction routes, retention, transfers, protection, withdrawal, and complaint handling without overclaiming compliance.

Singapore PDPA Requirements: Core Obligations

Map Singapore PDPA obligations across consent, notification, access, security, retention, transfers, accountability, breaches, DNC checks, and data intermediaries.

Singapore PDPA Scope, Exclusions, and Data Intermediaries

Classify Singapore PDPA coverage, business contact information, personal or domestic activity, employee acts, and data intermediary obligations using cited statutory boundaries and processing records.

Singapore PDPA Transfer Assessment Workflow

A Singapore PDPA workflow for assessing overseas personal data transfers, comparable protection, ASEAN MCCs, APEC CBPR/PRP certifications, vendor due diligence, onward transfers, and evidence records.

Singapore PDPA Transfer Clauses

Draft Singapore PDPA transfer clauses for overseas vendors, affiliates, data intermediaries, onward transfers, ASEAN MCCs, and APEC or Global CBPR and PRP evidence.

Singapore PDPA Vendor Outsourcing and Contracts

Contract and operating checklist for Singapore PDPA vendor outsourcing: data intermediary status, written terms, security, retention, breach, transfers, sub-contracting, and exit evidence.

Singapore PDPA vs GDPR Comparison

Compare Singapore PDPA and EU GDPR rules for legal bases, DPOs, intermediaries and processors, transfers, breaches, marketing objections, rights, retention, and penalties.

Singapore PDPA anonymisation FAQ

FAQ on anonymisation under the Singapore PDPA: de-identification, pseudonymisation, re-identification risk, when PDPA may no longer apply, and evidence records.

Singapore PDPA breach notification thresholds FAQ

FAQ on Singapore PDPA notifiable data breach tests: significant harm, significant scale, 500 affected individuals, assessment timing, PDPC notices, and affected-individual notices.

Singapore PDPA Data Intermediaries FAQ

FAQ guidance on Singapore PDPA data intermediary roles, direct obligations, organisation accountability, contracts, retention, protection, and breach escalation.

Singapore PDPA Deemed Consent FAQ

FAQ on Singapore PDPA deemed consent by conduct, contractual necessity, notification, opt-out periods, adverse-effect assessment, withdrawal, and direct-marketing limits.

Singapore PDPA DNC checking FAQ: when to check the DNC Registry

FAQ guidance on Singapore PDPA DNC checking: when to check the DNC Registry, which registers apply, 8-digit numbers, 21-day result validity, consent evidence, on-behalf checks, opt-outs, and supported exclusions.

Singapore PDPA DPIAs: when to run and what to document

FAQ-style implementation guidance on Singapore PDPA DPIAs, including when PDPC guidance recommends them, data-flow mapping, risk treatment, DPO review, and evidence records.

Singapore PDPA DPMP Accountability FAQ | DPO, Policies, Evidence

FAQ for implementing Singapore PDPA accountability through a DPMP: DPO designation, policies, evidence, training, monitoring, incident logs, and review records.

Singapore PDPA legitimate interests FAQ

FAQ guidance on Singapore PDPA legitimate interests: assessment fields, adverse effects, mitigation, balancing, disclosure, records, and marketing limits.

Singapore PDPA NRIC Handling FAQ

FAQ guidance on when Singapore organisations may collect, use, disclose, retain, mask, or replace NRIC and other national identification numbers under PDPC guidance.

Singapore PDPA transfer clauses FAQ

FAQ guidance on Singapore PDPA transfer clauses, comparable protection, ASEAN MCCs, APEC CBPR and PRP certifications, onward transfers, and evidence records.