---
title: "Singapore PDPA DNC checking FAQ: when to check the DNC Registry"
canonical_url: "https://www.sorena.io/artifacts/apac/singapore-pdpa/faq/dnc-checking"
source_url: "https://www.sorena.io/artifacts/apac/singapore-pdpa/faq/dnc-checking"
author: "Sorena AI"
description: "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."
published_at: "2026-05-09"
updated_at: "2026-05-09"
keywords:
  - "Singapore PDPA DNC Registry"
  - "DNC checking Singapore"
  - "Do Not Call Registry"
  - "Singapore telemarketing consent"
  - "Singapore PDPA"
  - "DNC Registry"
  - "Do Not Call"
  - "Telemarketing"
---
**[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 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.

*FAQ* *Singapore PDPA* *DNC checking*

## Singapore PDPA DNC checking FAQ

Check the Singapore DNC Registry before sending covered telemarketing messages to Singapore telephone numbers unless you can rely on clear and unambiguous consent in evidential form or a supported exclusion.

Use this FAQ to brief campaign operations, CRM, sales, and vendor teams on register selection, number format, 21-day result validity, on-behalf checks, consent records, and opt-out handling.

The Singapore PDPA Do Not Call provisions apply to specified marketing messages sent to Singapore telephone numbers. For campaign launch, the operational question is whether the message is covered, whether valid consent or an exclusion applies, and if not, whether the relevant DNC Registry check is current enough to use.

## When must a team check the Singapore DNC Registry before sending marketing messages?

A team should check the DNC Registry before sending a specified marketing voice call, text message, or fax to a Singapore telephone number unless it has clear and unambiguous consent in evidential form for that message to that number, or the message is outside the DNC checking duty because a supported exclusion applies.

Do the check at campaign execution time, not only when a lead is first collected. PDPC guidance says the check is tied to sending the specified message, and DNC Registry results are valid for 21 days from receipt. If the campaign will continue after that window, recheck before continuing telemarketing activity.

Treat third-party lead lists the same way: the sender still needs either usable consent evidence for that sender and number, or a current DNC result showing the number is not listed in the relevant register.

- For voice campaigns, check the No Voice Call Register unless clear and unambiguous consent or a supported exclusion applies.
- For SMS, MMS, and other text campaigns sent to Singapore telephone numbers, check the No Text Message Register unless clear and unambiguous consent or a supported exclusion applies.
- For fax campaigns, check the No Fax Message Register unless clear and unambiguous consent or a supported exclusion applies.
- Record the result receipt date because the 21-day validity window runs from receipt of results, not from list upload or campaign planning.

Sources for this answer:

- [PDPC DNC 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 core duty to avoid sending covered marketing messages to Singapore telephone numbers listed in the DNC Registry.
- [PDPC 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 rule that a sender must check the relevant DNC Register unless clear and unambiguous consent in evidential form is available.
- [PDPC DNC 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 relevant DNC registers and the 21-day validity period for results returned from the Registry.

## Which DNC registers and telephone-number format should campaign systems use?

Route the campaign channel to the matching register: No Voice Call Register for phone calls, No Text Message Register for texts including SMS and MMS, and No Fax Message Register for faxes. PDPC's business-rules page also says submitted numbers are checked against all three registers, so store the per-register status instead of reducing the result to a single allowed or blocked flag.

For system validation, the DNC checking interface accepts only 8-digit numbers starting with 3, 6, 8, or 9. Reject, normalize, or manually review other formats before upload so rejected numbers are not mistaken for cleared numbers.

For small checks, PDPC describes Small Number Lookup for up to 10 telephone numbers with immediate results. For larger lists, PDPC describes Bulk Filtering using a CSV file with a single column of 8-digit telephone numbers, with results available within 24 hours.

- Store the original campaign channel, the submitted 8-digit number, the DNC result for each register, and any rejected-number reason.
- Do not treat a rejected or invalid-format number as approved for sending.
- Use the result receipt timestamp to calculate the end of the 21-day validity window for that campaign run.

Sources for this answer:

- [PDPC DNC 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 register names, accepted 8-digit Singapore number format, Small Number Lookup, Bulk Filtering, and returned result files.
- [Personal Data Protection (Do Not Call Registry) Regulations 2013](https://sso.agc.gov.sg/SL/PDPA2012-S709-2013?ref=sorena.io) - Supports the statutory register definitions for No Fax Message, No Text Message, and No Voice Call registers.

## What consent evidence can replace a DNC check for a Singapore telephone number?

Consent can replace a DNC check only when it is clear, unambiguous, tied to the Singapore telephone number and message channel, and evidenced in written or other retrievable form. A broad marketing-purpose clause or a customer's failure to opt out is weak support if it does not clearly say that specified messages will be sent to the number.

Keep the evidence for as long as the organisation intends to rely on that consent for sending specified messages. For electronic consent, PDPC guidance points to retaining the individual's choice, the date and time of the choice, the webpage or form shown at the time, and the clauses or terms accepted.

If a user withdraws consent, stop relying on that consent for the scope of the withdrawal after the prescribed period and use a DNC check or another valid basis before sending further specified messages.

- Keep the consent statement, channel scope, number captured, positive action, timestamp, and source system.
- For third-party leads, keep evidence showing the individual consented to this sender sending specified messages to that number, or run the DNC check before sending.
- Do not infer clear and unambiguous consent from silence, pre-ticked assumptions, or generic marketing wording.

Sources for this answer:

- [PDPC 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 consent evidence expectations, including retrievable written or electronic records and retention while relying on consent.
- [PDPC DNC 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 exception where the organisation has the recipient's clear and unambiguous consent to receive marketing messages.

## How should teams handle on-behalf checks, vendors, and third-party checkers?

If an account holder checks the DNC Registry on behalf of another organisation, PDPC's business-rules page says the organisation names should be indicated during account creation and can be amended later. For bulk filtering, retain the On Behalf List output because it records the organisations on whose behalf the check was conducted at submission time.

Do not assume outsourcing removes sender responsibility. PDPC guidance treats the person who actually sends, causes, or authorises the specified message as a sender. A brand, marketing agency, and call centre can all fall within the sender analysis depending on the arrangement.

For third-party DNC checkers, keep the checker output, date received, expiry date, and accuracy assurances. PDPC's business page notes that it does not endorse third-party checkers and says liability is on third-party checkers for DNC infringements resulting from erroneous information.

- Contractually require vendors to use the correct campaign channel, DNC register result, and 21-day validity window.
- Keep the on-behalf declaration and output with the campaign approval record.
- Escalate any campaign where the brand, agency, and call centre disagree about who authorised the message or which entity's consent evidence is being relied on.

Sources for this answer:

- [PDPC DNC 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 account setup for checks conducted on behalf of other organisations and the On Behalf List bulk-filtering output.
- [PDPC 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 for persons who send, cause, or authorise specified messages.
- [PDPC DNC 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 caution around third-party checkers and the need for accurate result and expiry information.

## How should opt-outs and excluded messages affect DNC checking?

Opt-outs must be handled separately from DNC checking. PDPC's business page says organisations must provide opt-out information using the same medium and have 21 days after receiving an opt-out request to ensure marketing messages are no longer sent to the individual's telephone number.

A later DNC result should not override an opt-out or withdrawal record. If a person has withdrawn consent or opted out for the relevant sender, number, and channel, suppress the number for that scope even if a register check would otherwise allow sending.

Excluded messages should be used narrowly. Grounded examples include service or reminder messages for services bought by the individual, market survey or research messages, charitable or religious causes, and B2B messages sent to an organisation for the receiving organisation's purposes. The DNC advisory also warns that if a message mixes an excluded purpose with a non-excluded marketing purpose, it can still be a specified message requiring DNC compliance.

- Keep opt-out source, timestamp, channel, number, sender, and scope so suppression rules match the request.
- Classify service, survey, charitable, religious, and B2B messages before campaign launch, and reclassify if promotional copy is added.
- For ongoing-relationship text or fax exemptions, verify the supported conditions before relying on them, including whether the recipient has withdrawn consent, opted out, or otherwise indicated no consent.

Sources for this answer:

- [PDPC DNC 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 opt-out handling, covered message types, and PDPC's listed exception examples for business users.
- [PDPC 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 caution that an excluded-purpose message can still become a specified message if it includes non-excluded marketing content.
- [Personal Data Protection (Exemption from section 43) Order 2013](https://sso.agc.gov.sg/SL-Supp/S817-2013/Published/20131227170000?ref=sorena.io) - Supports the limited exemption for specified fax or text messages in an ongoing relationship and the opt-out conditions attached to that exemption.

## Primary sources

- [PDPC DNC 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 when DNC provisions apply, covered marketing channels, opt-out handling, exception examples, and third-party checker cautions.
  - Quote: "marketing messages to Singapore telephone numbers listed in the DNC Registry"
- [PDPC DNC 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 page supporting account creation, on-behalf checks, accepted 8-digit number format, register checking methods, output files, and 21-day result validity.
  - Quote: "Results returned from the DNC Registry are valid for up to 21 days."
- [PDPC 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 advisory guidance supporting the duty to check, clear and unambiguous consent in evidential form, consent withdrawal, sender responsibility, and treatment of excluded-purpose messages.
  - Quote: "clear and unambiguous consent evidenced in written or other form"
- [Personal Data Protection (Do Not Call Registry) Regulations 2013](https://sso.agc.gov.sg/SL/PDPA2012-S709-2013?ref=sorena.io) - Singapore Statutes Online source supporting the statutory DNC register definitions for No Fax Message, No Text Message, and No Voice Call registers.
  - Quote: "No Voice Call Register"
- [Personal Data Protection (Exemption from section 43) Order 2013](https://sso.agc.gov.sg/SL-Supp/S817-2013/Published/20131227170000?ref=sorena.io) - Singapore Statutes Online source supporting the limited ongoing-relationship exemption for specified fax and text messages and its opt-out conditions.
  - Quote: "the sender is in an ongoing relationship"

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

*Recommended next step*

*Placement: after the DNC checking FAQ*

## Operationalize Singapore PDPA DNC checks

Use Sorena to turn DNC Registry checks, consent evidence, opt-out suppression, vendor records, and 21-day result windows into assigned compliance work.

- [Open Assessment Autopilot for Singapore PDPA](/solutions/assessment.md): Convert DNC checking rules into campaign intake questions, evidence fields, and review tasks.
- [Review Singapore PDPA source evidence](/solutions/research-copilot.md): Use Research Copilot to verify DNC Registry, consent, and opt-out questions against cited source material.
- [Talk through implementation](/contact.md): Review DNC check scope, CRM suppression logic, vendor handling, and consent evidence with Sorena.


---

[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/faq/dnc-checking