---
title: "Singapore PDPA DNC and Marketing Messages Guide"
canonical_url: "https://www.sorena.io/artifacts/apac/singapore-pdpa/dnc-and-marketing-messages"
source_url: "https://www.sorena.io/artifacts/apac/singapore-pdpa/dnc-and-marketing-messages"
author: "Sorena AI"
description: "An official source Singapore PDPA guide to DNC checks, specified marketing messages, Singapore telephone numbers, consent evidence, opt-outs, sender duties, and excluded messages."
published_at: "2026-05-09"
updated_at: "2026-05-09"
keywords:
  - "Singapore PDPA DNC"
  - "Do Not Call Registry Singapore"
  - "specified messages"
  - "marketing consent Singapore"
  - "Singapore telephone numbers"
  - "Singapore PDPA"
  - "Do Not Call Registry"
  - "DNC marketing messages"
  - "Marketing consent"
---
**[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform

[Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io)

---

# 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.

*Artifact Guide* *Singapore PDPA* *DNC marketing*

## Singapore PDPA DNC and marketing messages

This guide helps decide when a Singapore PDPA Do Not Call Registry check is required before sending marketing calls, texts, faxes, or number-based app messages to Singapore telephone numbers.

The control should prove the message type, the register checked, the consent or exclusion relied on, the opt-out handling, and who is responsible as sender.

The DNC provisions sit beside the PDPA data protection obligations. For marketing operations, the practical question is whether a planned message is a specified message sent to a Singapore telephone number and, if so, whether the sender has a valid DNC check, clear and unambiguous consent in evidential form, or a supported exclusion.

## When does a DNC check apply to a Singapore marketing message?

Treat a campaign as DNC-relevant when it sends a specified message to a Singapore telephone number by voice call, text, fax, or a data application that uses the Singapore telephone number. PDPC guidance says Singapore telephone numbers are eight-digit numbers beginning with 3, 6, 8, or 9, and DNC business rules state that only those numbers are accepted for registry checks.

A specified message generally includes commercial marketing purposes such as offering, advertising, or promoting goods, services, land, interests in land, business opportunities, or investment opportunities. The sender must check the relevant DNC Register before sending unless it has clear and unambiguous consent in evidential form from the user or subscriber of the number.

- Classify the channel: No Voice Call Register for phone calls, No Text Message Register for SMS, MMS, and other text messages, and No Fax Message Register for fax messages.
- Record the telephone-number validation result before upload: the DNC system accepts eight-digit numbers starting with 3, 6, 8, or 9.
- Keep the DNC result receipt date because PDPC guidance and business rules describe DNC results as valid for up to 21 days from receipt.
- If the number appears on the relevant register, do not send the specified message unless a separate clear and unambiguous consent record supports that sender, number, message purpose, and channel.

Sources for this answer:

- [Do Not Call Registry and Your Business](https://www.pdpc.gov.sg/overview-of-pdpa/do-not-call-registry/business-owner/do-not-call-registry-and-your-business?ref=sorena.io) - Supports the page scope by explaining that the DNC provisions generally prohibit marketing messages to Singapore telephone numbers listed in the DNC Registry.
- [Do Not Call Registry Business Rules](https://www.pdpc.gov.sg/Overview-of-PDPA/Do-Not-Call-Registry/Business-Owner/Do-Not-Call-Registry-Business-Rules?ref=sorena.io) - Supports the operational lookup steps, accepted Singapore telephone number format, register types, and 21-day validity of DNC check results.
- [Advisory Guidelines on the Do Not Call Provisions](https://www.pdpc.gov.sg/guidelines-and-consultation/2020/02/advisory-guidelines-on-the-do-not-call-provisions?ref=sorena.io) - Supports the legal framing for specified messages, Singapore telephone numbers, the duty to check, and clear and unambiguous consent in evidential form.

## What consent record can replace a DNC check?

A sender can avoid the DNC check only when it has clear and unambiguous consent in evidential form from the user or subscriber for the sending of the specified message to that Singapore telephone number. PDPC guidance treats consent as stronger when the notice clearly says specified messages will be sent to the telephone number and the individual gives a positive action, such as selecting a channel checkbox, signing next to a marketing clause, replying yes, or submitting an online form.

Do not treat silence, failure to opt out, or a broad statement about marketing use as enough for this DNC exception. The evidence must be accessible later and must show the individual choice, date and time, the interface or form shown, and the clause or channel terms accepted when consent was collected electronically.

- Capture the exact sender name or group entity that will rely on the consent; do not assume consent given to one sender automatically covers another independent marketer.
- Store the telephone number, channel, campaign purpose, consent wording, user action, timestamp, source form or screen, and applicable terms.
- For consent obtained through a third party, retain evidence that the user or subscriber gave clear and unambiguous consent for this sender to send specified messages to that number.
- Retain consent evidence for as long as the sender intends to rely on it, then handle the record under the PDPA retention limitation obligation.

Sources for this answer:

- [Advisory Guidelines on the Do Not Call Provisions](https://www.pdpc.gov.sg/guidelines-and-consultation/2020/02/advisory-guidelines-on-the-do-not-call-provisions?ref=sorena.io) - Supports the requirement that consent must be clear, unambiguous, evidenced in written or other accessible form, and tied to specified messages sent to the Singapore telephone number.
- [Personal Data Protection Act 2012](https://sso.agc.gov.sg/Act/PDPA2012?ref=sorena.io) - Supports the statutory context for the DNC provisions, including Part 9, specified messages, consent withdrawal, and dictionary-attack and address-harvesting prohibitions.

## How should opt-outs, sender identity, and sender responsibility be handled?

Every specified message should identify the sender clearly and give contact information that lets the recipient readily contact the sender. For text and fax messages, the PDPC business guidance also says organisations must provide information on how individuals can opt out using the same medium by which the message is sent. For voice calls containing specified messages, the caller's identity must not be concealed.

Sender responsibility is broader than the team pressing send. PDPC guidance treats the person who actually sends, causes, or authorises the message or voice call as a sender. A brand, agency, campaign manager, and call centre can therefore all need DNC controls depending on the arrangement.

- Include a sender name or alias that actually identifies the sender; generic pronouns, informal nicknames, or fictitious names are weak identification.
- Provide direct contact details, such as an operational Singapore telephone number or valid email address; PDPC guidance says short codes and no-reply email addresses are not contact information for readily contacting the sender.
- Process withdrawal notices within the prescribed period described by PDPC guidance as 21 days, and make agents stop sending messages within the withdrawn scope.
- When using agencies, call centres, affiliates, or joint-offer partners, document who checks the DNC Register, who holds consent evidence, whose identity appears in the message, and who actioned opt-outs.

Sources for this answer:

- [Do Not Call Registry and Your Business](https://www.pdpc.gov.sg/overview-of-pdpa/do-not-call-registry/business-owner/do-not-call-registry-and-your-business?ref=sorena.io) - Supports practical requirements for opt-out information, sender identification for text and fax messages, and non-concealment of caller identity.
- [Advisory Guidelines on the Do Not Call Provisions](https://www.pdpc.gov.sg/guidelines-and-consultation/2020/02/advisory-guidelines-on-the-do-not-call-provisions?ref=sorena.io) - Supports sender responsibility, identification and contact information requirements, and the 21-day period for effecting withdrawal of DNC consent.

## Which messages and number sources need special treatment?

Do not send every operational message through the DNC workflow. PDPC guidance identifies excluded messages, including messages by public agencies for non-commercial programmes, personal or domestic messages, emergency messages, transaction confirmations, warranty, recall, safety or security information, delivery of product updates or services the recipient is entitled to receive, market research or survey messages with no marketing element, and B2B messages sent to an organisation for that organisation's purposes.

The exclusion analysis must be strict. If a message mixes an excluded purpose with advertising or promotion that is not excluded, treat it as a specified message and apply the DNC check or consent path. Separately, do not use generated or harvested number lists: PDPC guidance says section 48B prohibits sending, causing, or authorising any message where the recipient telephone number was obtained by dictionary attack or address-harvesting.

- For ongoing-relationship messages, confirm the message's sole purpose relates to the subject of that ongoing relationship; a one-off transaction alone does not establish the relationship.
- For survey or market research outreach, keep the script free of goods, services, supplier promotion, or disguised incentives that convert the contact into a specified message.
- For B2B outreach, document that the message is sent to an organisation for the receiving organisation's purposes, not to an individual acting in a personal or domestic capacity.
- Screen lead-generation sources for address-harvesting software, random or sequential number generation, and automated number permutations; a DNC check does not cure a dictionary-attack source.

Sources for this answer:

- [Advisory Guidelines on the Do Not Call Provisions](https://www.pdpc.gov.sg/guidelines-and-consultation/2020/02/advisory-guidelines-on-the-do-not-call-provisions?ref=sorena.io) - Supports the excluded-message categories, the limits on ongoing-relationship and B2B exclusions, and the prohibition on dictionary attacks and address-harvesting software.
- [Personal Data Protection Act 2012](https://sso.agc.gov.sg/Act/PDPA2012?ref=sorena.io) - Supports the statutory existence of the Eighth Schedule exclusions and section 48B prohibition referenced by the PDPC DNC guidance.

*Recommended next step*

*Placement: after the DNC implementation guidance*

## Turn Singapore PDPA DNC checks into campaign controls

This guide helps build campaign intake fields for message purpose, Singapore telephone number format, DNC result date, consent evidence, opt-out handling, sender identity, and excluded-message review.

- [Open Assessment Autopilot for Singapore PDPA](/solutions/assessment.md): Convert DNC marketing checks into campaign questions, evidence requests, and assigned review tasks.
- [Review Singapore PDPA source evidence](/solutions/research-copilot.md): Use Research Copilot to verify DNC edge cases against official PDPC and Singapore Statutes Online sources.
- [Talk through Singapore PDPA DNC implementation](/contact.md): Review marketing-message scope, consent records, opt-out handling, and sender responsibility with Sorena.

## Primary sources

- [Do Not Call Registry and Your Business](https://www.pdpc.gov.sg/overview-of-pdpa/do-not-call-registry/business-owner/do-not-call-registry-and-your-business?ref=sorena.io) - Official PDPC business guidance supporting DNC scope, covered marketing-message purposes, sender responsibility for direct or authorised sends, opt-out handling, and listed practical exceptions.
  - Quote: "generally prohibits organisations from sending marketing messages"
- [Do Not Call Registry Business Rules](https://www.pdpc.gov.sg/Overview-of-PDPA/Do-Not-Call-Registry/Business-Owner/Do-Not-Call-Registry-Business-Rules?ref=sorena.io) - Official PDPC business rules supporting account setup, relevant DNC registers, accepted Singapore telephone-number format, lookup methods, returned files, and 21-day DNC result validity.
  - Quote: "Results returned from the DNC Registry are valid for up to 21 days"
- [Advisory Guidelines on the Do Not Call Provisions](https://www.pdpc.gov.sg/guidelines-and-consultation/2020/02/advisory-guidelines-on-the-do-not-call-provisions?ref=sorena.io) - Official PDPC advisory guidance supporting specified-message classification, DNC check duties, consent in evidential form, sender identification, withdrawal, excluded messages, and address-harvesting rules.
  - Quote: "Requirement to Obtain Clear and Unambiguous Consent in Evidential Form"
- [Personal Data Protection Act 2012](https://sso.agc.gov.sg/Act/PDPA2012?ref=sorena.io) - Singapore Statutes Online source supporting the statutory basis for the PDPA, the Do Not Call Register, Eighth Schedule exclusions, and dictionary-attack and address-harvesting provisions.
  - Quote: "Do Not Call Registry"

## Related Topic Guides

- [Singapore PDPA Anonymisation and DPIA Records](/artifacts/apac/singapore-pdpa/anonymisation-and-dpias.md): 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](/artifacts/apac/singapore-pdpa/faq/anonymisation.md): 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](/artifacts/apac/singapore-pdpa/applicability-test.md): 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](/artifacts/apac/singapore-pdpa/breach-notification-playbook.md): 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](/artifacts/apac/singapore-pdpa/faq/breach-thresholds.md): 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](/artifacts/apac/singapore-pdpa/breach-notification-workflow.md): 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](/artifacts/apac/singapore-pdpa/checklist.md): 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](/artifacts/apac/singapore-pdpa/compliance.md): 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](/artifacts/apac/singapore-pdpa/consent-and-deemed-consent-selection-workflow.md): Choose express consent, deemed consent by conduct, contractual necessity, notification, or the legitimate interests exception under Singapore PDPA with based ontake fields and evidence records.
- [Singapore PDPA Consent, Notification and Purpose Rules](/artifacts/apac/singapore-pdpa/consent-notification-and-purposes.md): 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](/artifacts/apac/singapore-pdpa/cross-border-transfers.md): 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](/artifacts/apac/singapore-pdpa/breach-notification-thresholds.md): 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](/artifacts/apac/singapore-pdpa/faq/data-intermediaries.md): FAQ guidance on Singapore PDPA data intermediary roles, direct obligations, organisation accountability, contracts, retention, protection, and breach escalation.
- [Singapore PDPA Data Intermediary Responsibilities](/artifacts/apac/singapore-pdpa/data-intermediary-responsibilities.md): Practical Singapore PDPA guide to data intermediary role boundaries, organisation accountability, protection, retention, breach escalation, and contract evidence.
- [Singapore PDPA Deadlines and Compliance Calendar](/artifacts/apac/singapore-pdpa/deadlines-and-compliance-calendar.md): An official source Singapore PDPA compliance calendar for breach notification, DNC checks, access and correction requests, retention reviews, and DPMP maintenance.
- [Singapore PDPA Deemed Consent and Legitimate Interests](/artifacts/apac/singapore-pdpa/deemed-consent-and-legitimate-interests.md): 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](/artifacts/apac/singapore-pdpa/faq/deemed-consent.md): 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](/artifacts/apac/singapore-pdpa/faq/dnc-checking.md): 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](/artifacts/apac/singapore-pdpa/dnc-marketing-checks.md): 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](/artifacts/apac/singapore-pdpa/dnc-marketing-workflow.md): Workflow for Singapore PDPA DNC marketing campaigns: classify specified messages, check Singapore telephone numbers, document consent, suppress opt-outs, and approve sends.
- [Singapore PDPA DPIAs: when to run and what to document](/artifacts/apac/singapore-pdpa/faq/dpias.md): 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](/artifacts/apac/singapore-pdpa/faq/dpmp-accountability.md): 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](/artifacts/apac/singapore-pdpa/dpmp-accountability.md): 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](/artifacts/apac/singapore-pdpa/faq.md): 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](/artifacts/apac/singapore-pdpa/faq/legitimate-interests.md): FAQ guidance on Singapore PDPA legitimate interests: assessment fields, adverse effects, mitigation, balancing, disclosure, records, and marketing limits.
- [Singapore PDPA NRIC Handling FAQ](/artifacts/apac/singapore-pdpa/faq/nric-handling.md): 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](/artifacts/apac/singapore-pdpa/nric-handling.md): When Singapore organisations may collect, use, disclose, retain, mask, or replace NRIC numbers under PDPC guidance.
- [Singapore PDPA Penalties and Enforcement Cases](/artifacts/apac/singapore-pdpa/pdpa-penalties-and-enforcement-cases.md): 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](/artifacts/apac/singapore-pdpa/penalties-and-fines.md): 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](/artifacts/apac/singapore-pdpa/pdpa-privacy-policy-template.md): 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](/artifacts/apac/singapore-pdpa/requirements.md): 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](/artifacts/apac/singapore-pdpa/scope-exclusions-and-data-intermediaries.md): 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](/artifacts/apac/singapore-pdpa/transfer-assessment-workflow.md): 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](/artifacts/apac/singapore-pdpa/transfer-clauses.md): Draft Singapore PDPA transfer clauses for overseas vendors, affiliates, data intermediaries, onward transfers, breach support, ASEAN MCCs, and APEC CBPR or PRP evidence.
- [Singapore PDPA transfer clauses FAQ](/artifacts/apac/singapore-pdpa/faq/transfer-clauses.md): 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](/artifacts/apac/singapore-pdpa/vendor-outsourcing-and-contracts.md): 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](/artifacts/apac/singapore-pdpa/singapore-pdpa-vs-gdpr.md): Compare Singapore PDPA and GDPR implementation work across consent, DPO accountability, processors, transfers, breach notification, DNC marketing, rights, retention, and penalties.


---

[Privacy Policy](https://www.sorena.io/privacy) | [Terms of Use](https://www.sorena.io/terms-of-use) | [DMCA](https://www.sorena.io/dmca) | [About Us](https://www.sorena.io/about-us)

(c) 2026 Sorena AB (559573-7338). All rights reserved.

Source: https://www.sorena.io/artifacts/apac/singapore-pdpa/dnc-and-marketing-messages