We use privacy-by-default, cookieless analytics.

Optional analytics cookies are used only if you accept them.

Read our Terms of Use and Privacy Policy.

WorkflowSingapore PDPADNC Registry

DNC marketing workflow for Singapore PDPA campaigns

Review this workflow before sending marketing calls, texts, faxes, or telephone-number-based app messages to Singapore telephone numbers.

It turns DNC campaign intake into specified-message classification, register checks, consent evidence, opt-out suppression, vendor controls, and approval records.

Back to main artifactReview sources
Author
Sorena AI
Published
May 9, 2026
Updated
Jul 24, 2026
Sections
5

Structured answer sets in this page tree.

Primary sources
6

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated Jul 24, 2026
Overview

Before sending a specified marketing message to a , check the relevant DNC Register unless the user or subscriber gave or a statutory exclusion or exemption fits the message. This workflow gives campaign owners, privacy reviewers, and vendors a campaign-specific record of classification, register results, consent or exemption evidence, opt-out suppression, sender responsibility, and approval.

Section 1

1. Intake the campaign before any send list is loaded

Create the campaign intake record before loading the list into a channel. Record the product or service being promoted, the sender brand, the actual sender or vendor, every channel, the source of the telephone numbers, and whether the list contains Singapore telephone numbers.

For Registry submission, the DNC system accepts 8-digit numbers beginning with 3, 6, 8, or 9. That input rule is not a substitute for the legal scope test, which turns on whether the message is sent to a . If the list is mixed-market or partially formatted, normalize and separate the Singapore numbers before DNC review.

  • Campaign fields: campaign name, business owner, sender identity, vendor or agency, channel, message copy, landing page, offer, audience source, intended send date, and approver.
  • List fields: upload source, number format, Singapore-number filter, deduplication result, suppression-list match, DNC check batch ID, and rejected-number file if bulk filtering is used.
  • Vendor fields: whether the vendor is checking on behalf of another organisation, the organisation named in the DNC declaration, and the file returned to the campaign owner.
  • Stop the launch if the campaign owner cannot identify who authorised the message, who will send it, or which register applies to the channel.
Sources for this answer
Do Not Call Registry Business Rules
Supports number-format intake, account setup, on-behalf checking, small-number lookup, bulk filtering, returned files, and result validity.
Advisory Guidelines on the DNC Provisions
Defines Singapore telephone number and explains that DNC obligations apply to specified messages sent to those numbers.
Section 2

2. Classify whether the message is a specified message

Classify the message by purpose, not by campaign label. A message is in scope when its purpose, or one of its purposes, is to advertise, promote, or offer goods, services, land, an interest in land, a business opportunity, or an investment opportunity, or to promote the supplier or prospective supplier.

Do not treat a consent-request SMS or call as low risk just because it asks for permission. PDPC guidance treats offers to send specified messages, and requests for consent sent to a , as specified messages when they promote future offers.

  • Mark in scope when the copy promotes an offer, sale, membership, investment, property, supplier, event, seminar, course, or future promotional messages.
  • Mark out of DNC scope only with a recorded reason supported by the message's actual content and the statutory exclusions, such as a sole response to an individual's request for information, a service or reminder message whose purpose is not promotional, market survey or research, a charitable or religious cause, or a message sent to an organisation for that organisation's purposes.
  • For an ongoing relationship, test the sole purpose of the message. A service notice about the relationship may be excluded, but adding a separate promotional purpose can make the message specified; a once-off transaction does not by itself establish an ongoing relationship.
  • For third-party referrals, record whether the individual actually requested information or gave clear and unambiguous consent for this sender to send specified messages.
  • Escalate mixed-purpose copy if any part of the message promotes goods, services, land, business opportunities, investment opportunities, or a supplier.
Sources for this answer
Advisory Guidelines on the DNC Provisions
Supports purpose-based classification of specified messages and consent-request messages sent to Singapore telephone numbers.
Do Not Call Registry and Your Business
Lists common marketing-message purposes and examples of message categories that businesses may send outside DNC checking.
Section 4

4. Suppress opt-outs and keep result validity visible

DNC approval expires with the DNC result. Results returned from the DNC Registry are valid for up to 21 days; if the campaign send continues after that period, recheck the remaining Singapore telephone numbers before continuing telemarketing.

Consent and opt-out handling need their own suppression control. PDPC business guidance says organisations must provide information on how individuals can opt out using the same medium as the message. When the recipient opts out through that route, update the suppression list and stop further specified messages to that number within 21 days.

  • Approval status values: not a , DNC checked and clear, consent exception approved, suppressed, rejected number, recheck required, or escalated.
  • Suppression fields: number, channel, sender or brand, opt-out source, received timestamp, scope of withdrawal, suppression applied timestamp, owner, and audit evidence.
  • Recheck trigger: DNC result older than 21 days, changed sender, changed message purpose, new number list, new channel, withdrawn consent, or vendor file replaced.
  • Campaign systems should block sends when the DNC check has expired, the number appears on the relevant register, consent evidence is missing, or an opt-out has not been applied.
Sources for this answer
Do Not Call Registry Business Rules
Supports the 21-day validity period for DNC Registry results and the need to recheck after expiry.
Do Not Call Registry and Your Business
Supports same-medium opt-out information and the 21-day period for stopping marketing messages after opt-out.
Section 5

5. Approve sender, vendor, and message evidence before launch

Approval should cover both the person actually sending the message and anyone who caused or authorised the send. A brand owner, agency, and call centre can each be a sender depending on the arrangement, so the approval record should show who authorised the campaign and who performed each send or check.

If a third-party checker or aggregator is used, do not treat that vendor as an official substitute for campaign approval. Keep the DNC file, date received, expiry, and any on-behalf declaration with the campaign record, and require the vendor to return enough evidence for the sender to verify the decision.

  • Message approval evidence: final copy, sender identification, contact details that recipients can readily use, caller-line identity controls for voice calls, landing page, and channel.
  • Sender responsibility evidence: authorising organisation, agency or vendor, call centre or platform, agreement term restricting unauthorised specified messages, and owner of DNC checking.
  • Vendor evidence: DNC checking account or on-behalf declaration, returned result file, result receipt date, expiry date, rejected-number handling, and confirmation that the vendor is not using dictionary attacks or address-harvesting.
  • Final approval should name the approver, list the source evidence reviewed, state the approved audience and channel, and record the date by which recheck or reapproval is required.
Sources for this answer
Advisory Guidelines on the DNC Provisions
Supports sender responsibility for actual sending, causing, or authorising marketing messages, including agency and call-centre arrangements.
Welcome to the Do Not Call Registry
Supports caution that PDPC does not endorse third-party DNC services and that organisations remain liable when aggregators miss listed numbers.
Recommended next step

Turn DNC campaign checks into assigned work

This Singapore PDPA DNC workflow helps assign campaign intake, register checking, consent evidence review, suppression controls, vendor follow-up, and final launch approval.

Assessment workflow
Open Assessment Autopilot for Singapore PDPA

Convert DNC campaign intake into scoped questions, owners, evidence fields, and approval tasks.

Explore next step
Research workflow
Review DNC source evidence

Use Research Copilot to check follow-up questions against the cited PDPC and DNC source material.

Explore next step
Talk to Sorena
Talk through implementation

Review campaign scope, sender roles, consent evidence, suppression controls, and vendor responsibilities with Sorena.

Explore next step
Primary sources

References and citations

Advisory Guidelines on the DNC Provisions
pdpc.gov.sg
Referenced sections
  • Supports sender responsibility for actual sending, causing, or authorising marketing messages, including agency and call-centre arrangements.
"persons who caused or authorised the sending of the message"
Do Not Call Registry and Your Business
pdpc.gov.sg
Referenced sections
  • Supports same-medium opt-out information and the 21-day period for stopping marketing messages after opt-out.
"Upon receiving an opt-out request, you have 21 days"
Do Not Call Registry Business Rules
pdpc.gov.sg
Referenced sections
  • Supports the 21-day validity period for DNC Registry results and the need to recheck after expiry.
"Results returned from the DNC Registry are valid for up to 21 days."
Personal Data Protection Act 2012
sso.agc.gov.sg
Referenced sections
  • Binding source for the DNC Registry, specified-message definition, exclusions, register-check duty, consent exception, sender identification, opt-out, and prohibited number-generation methods.
Welcome to the Do Not Call Registry
dnc.gov.sg
Referenced sections
  • Supports caution that PDPC does not endorse third-party DNC services and that organisations remain liable when aggregators miss listed numbers.
"Organisations that use third party aggregators to check telephone numbers against the DNC Registry should be aware"
Related guides

Explore more topics

Singapore PDPA Anonymisation and DPIA Records
Build Singapore PDPA anonymisation and DPIA records around PDPC guidance: release model, re-identification risk, data flows, action plans, safeguards, and monitoring.
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 Applicability Test
Test whether Singapore PDPA obligations apply by checking personal data, organisation role, data intermediary status, public agency and individual boundaries, and business contact information.
Singapore PDPA Breach Notification Playbook
An official source Singapore PDPA breach-notification playbook covering assessment, notifiable-breach thresholds, PDPC and affected-individual notification steps, roles, records, and citations.
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 Breach Notification Workflow
An official source Singapore PDPA workflow for containing a personal data breach, assessing notifiability, notifying PDPC or affected individuals, and retaining evidence.
Singapore PDPA Compliance Checklist
An official source Singapore PDPA checklist for scope, DPO accountability, consent, data intermediaries, breach notification, DNC checks, transfers, and evidence records.
Singapore PDPA Compliance Guide
Build a Singapore PDPA compliance plan covering DPO accountability, consent and notification, protection, retention, access and correction, transfers, breach notification, and DNC checks.
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
Official source 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
Official source Singapore PDPA breach notification thresholds covering significant harm, the 500-individual significant-scale test, assessment records, and notification timing.
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 Data Intermediary Responsibilities
Practical Singapore PDPA guide to data intermediary role boundaries, organisation accountability, protection, retention, breach escalation, and contract evidence.
Singapore PDPA Deadlines and Compliance Calendar
A Singapore PDPA compliance calendar for breach notification, DNC checks, access and correction requests, enforcement responses, retention reviews, and DPMP maintenance.
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 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 and Marketing Messages Guide
An official source Singapore PDPA guide to DNC checks, specified marketing messages, Singapore telephone numbers, consent evidence, opt-outs, sender duties, and excluded messages.
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 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 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 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 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 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 with official source implementation 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 transfer clauses FAQ
FAQ guidance on Singapore PDPA transfer clauses, comparable protection, ASEAN MCCs, APEC CBPR and PRP certifications, onward transfers, and evidence records.
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.