Singapore PDPA DNC checking FAQ

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.

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.

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.

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.

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.