--- title: "Singapore PDPA DNC Marketing Checks" canonical_url: "https://www.sorena.io/artifacts/apac/singapore-pdpa/dnc-marketing-checks" source_url: "https://www.sorena.io/artifacts/apac/singapore-pdpa/dnc-marketing-checks" author: "Sorena AI" description: "Operational checklist for Singapore PDPA DNC marketing checks: account evidence, register status, 21-day result validity, consent evidence, and campaign owner records." published_at: "2026-05-09" updated_at: "2026-05-09" keywords: - "Singapore PDPA DNC checks" - "DNC Registry marketing" - "Singapore telemarketing checks" - "PDPA consent evidence" - "Singapore PDPA" - "DNC Registry" - "Marketing checks" - "Telemarketing compliance" --- **[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 Marketing Checks Operational checklist for Singapore PDPA DNC marketing checks: account evidence, register status, 21-day result validity, consent evidence, and campaign owner records. *Artifact Guide* *Singapore* *DNC Marketing Checks* ## Singapore PDPA DNC Marketing Checks Before sending specified marketing messages to Singapore telephone numbers, teams need a campaign record that shows the DNC account used, the numbers checked, the channel-specific register status, and whether consent evidence was used instead of a DNC clearance. This page turns PDPC and DNC Registry guidance into operating language for marketing, sales operations, privacy, and vendor teams. This guidance is practical, source-linked, and should be validated against current legal and policy requirements before implementation. Use this page as a launch checklist for Singapore PDPA DNC marketing checks. It focuses on the records a campaign owner should keep before voice, text, or fax telemarketing goes live: DNC Registry account evidence, relevant register status, result validity, consent evidence, sender responsibility, and when a new check is supported by the source material. ## When a campaign needs a DNC marketing check Start with the message, not the audience list label. Under PDPC guidance, a commercial marketing message to a Singapore telephone number is generally a specified message when one purpose is to advertise, promote, or offer goods, services, land, an interest in land, a business opportunity, or an investment opportunity. For each campaign, record whether the message will be sent by voice call, text channel, fax, or a data application that uses a Singapore telephone number. If the team is relying on clear and unambiguous consent instead of checking the DNC Registry, keep the consent evidence in the same launch record and make the approval say exactly which sender, number, channel, and message category the consent covers. - Classify the message as specified, excluded from specified-message treatment, or blocked for legal review because the purpose is unclear. - Identify every sender: the brand, business unit, agency, call centre, or platform that sends, causes, or authorises the message. - Separate voice, text, and fax channels because the DNC Regulations define separate No Voice Call, No Text Message, and No Fax Message Registers. - Do not treat a request for telemarketing consent sent to a Singapore telephone number as outside DNC controls; PDPC guidance treats offers to send specified messages as specified messages. 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 duty to check the DNC Register before sending specified messages unless clear and unambiguous consent in evidential form is available. - [Personal Data Protection (Do Not Call Registry) Regulations 2013](https://sso.agc.gov.sg/SL/PDPA2012-S709-2013?ref=sorena.io) - Defines the No Voice Call, No Text Message, and No Fax Message Registers used for channel-specific DNC status checks. ## Account and sub-account evidence to keep The DNC Registry business rules distinguish the main account from sub-accounts. A useful campaign file should show which main account was used, which sub-account or user submitted the check, and whether the checker was acting for its own organisation or on behalf of another organisation. For agency, reseller, group-company, or outsourced call-centre launches, keep the on-behalf evidence with the DNC check output. The campaign owner should be able to show who authorised the marketing, who submitted the DNC check, and which organisation names were declared for on-behalf checking at the time of submission. - Record the main account holder, sub-account user, submission timestamp, campaign owner, and approving privacy or legal reviewer. - For Singapore-registered organisations, keep the UEN or account registration evidence used for DNC account administration; for overseas organisations, keep the company registration evidence used for the account. - For on-behalf checks, retain the downloaded On Behalf List or equivalent export with the campaign record. - Do not approve a vendor-sent campaign unless the record names both the business authorising the message and the vendor or call centre that will send it. Sources for this answer: - [Do Not Call Registry Business Rules](https://www.dnc.gov.sg/org_more.html?ref=sorena.io) - Supports keeping main-account and sub-account evidence because the DNC Registry account model allows one main account and sub-accounts for multiple users. - [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 on-behalf evidence because bulk filtering output includes an On Behalf List for organisations covered by the submission. - [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 naming both business and vendor senders because PDPC guidance treats persons who send, cause, or authorise specified messages as responsible senders. ## How to use DNC check results The campaign approval should store the submitted list, rejected-number report, filtered-number output, summary, and any on-behalf export. The business rules say submitted telephone numbers are checked against all three DNC Registers, but the launch decision should still compare the campaign channel with the relevant register status: voice campaign to No Voice Call, SMS or MMS campaign to No Text Message, and fax campaign to No Fax Message. Treat the 21-day validity window as a ceiling, not a general review cadence. A result supports telemarketing activity only while the returned result remains valid and while the campaign facts still match the checked list, sender, channel, and message. If the validity period has lapsed and the organisation intends to continue telemarketing, perform another DNC check. - Accept only Singapore telephone numbers in the DNC submission format supported by the Registry and keep rejected-number reasons out of the approved send list. - For Small Number Lookup, retain the immediate result; for Bulk Filtering, retain the downloaded filtered numbers, summary, on-behalf list, and rejected numbers files. - Block channel sends where the relevant register status says the number is listed and no clear, unambiguous, channel-specific consent evidence is being relied on. - Re-check only where supported by the operational facts: the 21-day result period has lapsed, the number list changed, rejected numbers were corrected and resubmitted, or the team no longer has the consent evidence it planned to rely on. Sources for this answer: - [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 retaining DNC output files because bulk filtering provides filtered-number, summary, on-behalf, and rejected-number files. - [Do Not Call Registry Business Rules](https://www.dnc.gov.sg/org_more.html?ref=sorena.io) - Supports channel-status review because DNC submissions are checked against all three DNC Registers. - [Do Not Call Registry Business Rules](https://www.dnc.gov.sg/org_more.html?ref=sorena.io) - Supports the 21-day result-validity window and re-checking after the window lapses if telemarketing continues. *Recommended next step* *Placement: after the DNC marketing check guidance* ## Turn DNC checks into campaign launch evidence Use Sorena to capture Singapore PDPA DNC account evidence, register results, consent proof, sender ownership, and re-check triggers before marketing campaigns go live. - [Open Assessment Autopilot for Singapore PDPA](/solutions/assessment.md): Convert DNC campaign facts into evidence fields, owners, and approval tasks. - [Review DNC source evidence](/solutions/research-copilot.md): Use Research Copilot to answer follow-up DNC questions with cited PDPC and DNC Registry material. - [Talk through DNC implementation](/contact.md): Review account setup, consent evidence, register results, and campaign owner records with Sorena. ## Consent evidence and campaign owner records If a campaign proceeds because the organisation has clear and unambiguous consent in evidential form, the campaign owner should retain the specific consent artefact rather than a generic CRM flag. PDPC guidance expects consent evidence to be accessible for later reference and, for electronic consent, to show the individual's choice, date and time, the relevant screen or form, and the clauses consented to. The launch record should also show withdrawal handling. If consent is withdrawn, the team needs a record of the notice, its scope, the affected channel, the sender or agent instructed to stop, and the date when the stop action was completed. - Keep the consent text, positive action, number, channel, sender, timestamp, capture location, and terms that applied when consent was given. - For third-party sourced numbers, keep evidence that the user or subscriber gave clear and unambiguous consent for this sender to send specified messages to that Singapore telephone number, or perform the DNC check before sending. - For outsourced campaigns, require the vendor to return send logs, suppression results, withdrawal notices, and proof that agents stopped sending when instructed. - Do not rely on inaction, a broad marketing-purpose statement, or consent for the wrong telephone number as a substitute for DNC clearance. 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 retaining reproducible consent evidence, including electronic records of choice, timestamp, screen or form, and consent clauses. - [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 rejecting opt-out-by-inaction as clear and unambiguous consent for specified messages. - [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 requiring third-party source evidence when the sender obtains Singapore telephone numbers from a referrer or list source. ## Primary sources - [Do Not Call Registry Business Rules](https://www.dnc.gov.sg/org_more.html?ref=sorena.io) - Primary operational source for DNC Registry account creation, main and sub-account use, register checks, all-register output, and 21-day result validity. - Quote: "Results returned from the DNC Registry are valid for up to 21 days." - [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) - PDPC business-owner page supporting submission methods, downloaded result files, on-behalf evidence, and rejected-number handling. - Quote: "The following files will be available for download" - [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) - PDPC guidance supporting the duty to check, sender responsibility, specified-message analysis, and consent evidence requirements. - Quote: "unless the person has obtained clear and unambiguous consent in evidential form" - [Personal Data Protection (Do Not Call Registry) Regulations 2013](https://sso.agc.gov.sg/SL/PDPA2012-S709-2013?ref=sorena.io) - Official regulations defining the DNC registers and channel-specific message categories used for voice, text, and fax checks. - Quote: "No Voice Call Register, No Text Message Register or No Fax Message Register" ## 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): A grounded 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): A grounded 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): A grounded 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 grounded intake 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): Grounded 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): Grounded 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): A grounded 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 and Marketing Messages Guide](/artifacts/apac/singapore-pdpa/dnc-and-marketing-messages.md): A grounded 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](/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 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 grounded in 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 grounded 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-marketing-checks