TRW & Co · PDPA and data protection

NRIC Numbers Can No Longer Be Used for Authentication: Compliance by End-2026

Updated 20 October 2026Legal insightSingapore10 min read
Smartphone showing a security lock screen on a desk, reflecting the NRIC authentication ban in Singapore
Photo: Unsplash.

The NRIC authentication ban in Singapore requires private organisations to stop using full or partial NRIC numbers to verify identity by 31 December 2026, with the PDPC stepping up enforcement from 1 January 2027. Collecting NRIC numbers for genuine identification can continue; using them as passwords, PINs or security answers cannot. Here is what must change and how to migrate.

Key pointThe biggest exposure is rarely the login page. It is the encrypted PDF, call-centre script or account-recovery flow that quietly treats NRIC digits as a secret, often controlled by a vendor.

At a glance

01

Deadline is fixed

Private organisations must stop using full or partial NRIC numbers for authentication by 31 December 2026, as announced by the PDPC on 2 February 2026.

02

Enforcement from 2027

From 1 January 2027 the PDPC will step up enforcement and may issue directions or financial penalties under the PDPA Protection Obligation.

03

Identification still allowed

Collecting an NRIC number to identify someone accurately can remain appropriate; the change targets using the number as proof of identity.

04

Sector regulators aligned

IMDA, MAS and MOH have issued guidance for telecommunications, finance and insurance, and healthcare, reinforcing the PDPC deadline in regulated sectors.

05

Penalty ceiling is high

PDPA financial penalties can reach 10% of annual Singapore turnover for organisations above S$10 million turnover, or S$1 million otherwise.

Swipe or scroll →

The NRIC authentication ban in Singapore: the short answer

The NRIC authentication ban in Singapore means that, by 31 December 2026, private organisations must stop using full or partial NRIC numbers to prove that a person is who they claim to be. The Personal Data Protection Commission (PDPC) announced the deadline on 2 February 2026 and has said it will step up enforcement from 1 January 2027.

The change does not make it unlawful to hold an NRIC number. It targets one specific habit: treating a number that is printed on cards, forms and letters as if it were a secret. An NRIC number is an identifier. It was never designed to be a password.

As of October 2026, roughly ten weeks remain. Organisations that still use NRIC numbers as default passwords, as the key to open encrypted attachments, or as the answer to a call-centre security question should treat the remaining period as a migration project, not a policy update.

Board reviewing the NRIC authentication ban in Singapore and customer authentication changes
Boards and data protection officers should confirm, before year-end, that no customer or staff journey still relies on an NRIC number as a secret.

What changed and when it takes effect

The direction of travel was set in June 2025, when the PDPC and the Cyber Security Agency of Singapore (CSA) issued a joint advisory against using NRIC numbers for authentication. In early 2026 the PDPC converted that advice into a firm deadline in its press release, Organisations to cease the use of NRIC numbers for authentication by 31 December 2026.

Sector regulators followed with their own guidance. The Infocomm Media Development Authority (IMDA) addressed telecommunications operators, the Monetary Authority of Singapore (MAS) addressed financial institutions and insurers, and the Ministry of Health (MOH) addressed the healthcare sector. The Association of Banks in Singapore also stated that member banks were phasing out the practice.

The NRIC authentication ban in Singapore therefore applies across the private sector, but its practical weight falls on organisations that run large customer bases through call centres, statements and self-service portals: banks, insurers, telcos, healthcare providers, retailers, education providers, property managers and membership organisations. Public agencies are on a separate track, with the Government progressively moving its own documents away from partial NRIC numbers.

Key milestones for the NRIC authentication change (as of October 2026)
DateMilestoneWhat it means for organisations
June 2025PDPC and CSA joint advisory against NRIC-based authenticationGood practice became clear; reliance on NRIC as a secret was already hard to defend
2 February 2026PDPC announces the 31 December 2026 deadlineA fixed date for migration; sector guidance from IMDA, MAS and MOH follows
31 December 2026Deadline for private organisations to cease using NRIC numbers for authenticationAll customer, staff and partner journeys should be migrated
From 1 January 2027PDPC steps up enforcementUse of NRIC numbers to authenticate access to personal data may be treated as a breach of the PDPA

The PDPC has also set up a public channel for reporting misuse, which means non-compliance is likely to surface through customer complaints as well as through breach investigations.

There is no new statute. The NRIC authentication ban in Singapore rests on the existing Protection Obligation in the Personal Data Protection Act 2012 (PDPA), which requires an organisation to make reasonable security arrangements to protect personal data in its possession or under its control.

The PDPC's position is that authenticating a person with a number that is widely known, often printed in full or in part on documents and easily guessed, is not a reasonable security arrangement. From 1 January 2027, an organisation that uses NRIC numbers to grant access to personal data may be found in breach of that obligation.

The consequences are the ordinary PDPA enforcement tools: directions to remedy the practice and, where appropriate, financial penalties. The PDPA penalty cap is up to 10% of an organisation's annual turnover in Singapore where that turnover exceeds S$10 million, or S$1 million in other cases. Our overview of PDPA enforcement in Singapore explains how the PDPC approaches investigations and undertakings.

Identification is not authentication

The distinction that matters is between identification (who is this person?) and authentication (can this person prove they are who they claim to be?). Where an organisation genuinely needs to identify a person accurately, for example for regulatory checks, employment records or licences, collecting the NRIC number may remain appropriate under the PDPC's longstanding guidance on national identification numbers.

What must stop is using the number, or part of it, as the proof. Put simply, the NRIC authentication ban in Singapore leaves the question of whether to collect an NRIC number to the existing rules, and adds a clear answer to the question of how it may be used: never as a secret.

The Government has It has also signalled that partial NRIC numbers are an unreliable identifier because different people can share the same partial number, and that it will consult before changing guidance on partial numbers.

Which systems and practices must change

In practice, the NRIC authentication ban in Singapore bites hardest on processes that nobody thinks of as authentication. NRIC-based authentication tends to hide in older or informal processes rather than in the main login page. The PDPC's own example is a default password built from an NRIC number combined with a date of birth. Common patterns include:

  • Password-protected PDFs, statements or payslips where the password is the NRIC number or a fragment of it, sometimes with the date of birth.
  • Call-centre or counter verification scripts that treat the last few NRIC characters as proof of identity before discussing an account.
  • First-time login, account recovery or password reset flows that accept an NRIC number plus name or date of birth.
  • Event, membership or loyalty portals that let users retrieve bookings or records by entering an NRIC number.
  • Internal tools where staff look up and act on records after a caller simply quotes an NRIC number.

Each of these should be replaced by a factor that is genuinely secret or possessed only by the individual: a user-chosen password, a one-time code to a verified mobile number or email address, an authenticator app, or a government digital identity login where that is available for the use case. Where the journey gives access to sensitive data or money, multi-factor authentication is the appropriate baseline. Our cybersecurity and incident response team works with IT owners on these designs.

Practical point

Search your outbound document templates, not just your login code. In many organisations the riskiest NRIC-based authentication is a document-encryption default set years ago in a statement or payslip generator, which nobody in the current security team owns.

A practical migration plan before 31 December 2026

With the deadline close, the most efficient approach to the NRIC authentication ban in Singapore is a short, evidence-led programme. The steps below reflect the measures the PDPC itself highlights in its advisory on common data protection lapses, including careful data mapping, separate test environments and security testing before go-live.

  1. Inventory every journey. List each customer, employee, vendor and partner touchpoint where a person proves identity: web, app, phone, counter, email attachment and paper. Record whether any part of an NRIC number is used as the proof.
  2. Classify by data sensitivity. Rank journeys by the personal data and transactions they unlock. Account access, financial data, health data and payslips go first.
  3. Choose the replacement factor. Pick alternatives that suit the user population, including elderly or less digital customers, and document why each choice is reasonable for the risk.
  4. Rebuild safely. Map data fields carefully, keep test environments separate from the internet and free of live credentials, and run vulnerability assessment and penetration testing before release.
  5. Retrain front-line staff. Update call-centre and counter scripts so staff no longer accept NRIC digits as proof, and give them an approved fallback route.
  6. Communicate with users. Tell customers what is changing, how to set new credentials and that the organisation will never ask for an NRIC number as a password.
  7. Evidence and sign off. Keep a short record of the inventory, decisions and testing, approved by the data protection officer and a senior owner, so the organisation can show the PDPC what it did and when.

Replacement authentication options compared

Authentication options to replace NRIC-based verification
OptionBest suited toStrengthsWatch-outs
User-set password with secure resetGeneral account accessFamiliar, low costWeak passwords and reset flows that fall back to NRIC
One-time code to verified mobile or emailStatements, account recovery, moderate-risk accessSimple for most usersNumber recycling and SIM-swap risk; verify contact details first
Authenticator app or device-bound passkeyHigh-value accounts and staff accessStrong and phishing-resistant options existOnboarding friction and support for lost devices
Government digital identity loginServices where it is available and appropriateStrong assurance without holding extra secretsEligibility, integration and fallback for non-users
Call-back or in-person verification with secret dataPhone and counter channelsWorks for less digital customersMust not rely on information printed on documents

Whichever option is chosen, the reasoning should be documented. A short assessment of the kind described in our guide to data protection impact assessments is usually enough to show the choice was proportionate.

Illustrative scenario: a mid-sized insurer

This scenario is illustrative only and uses generic parties. A mid-sized insurance intermediary emails monthly policy statements as encrypted PDFs. The password is the last four NRIC characters followed by the date of birth. Its call centre also verifies callers by asking for the same characters.

Following MAS sector guidance and the PDPC deadline, the intermediary inventories its journeys and finds two further uses: a legacy agent portal and a claims status page. It moves statements behind a customer portal with one-time codes, switches the call centre to a call-back to the registered number plus a customer-set phrase, and retires the claims page.

The intermediary also writes to its outsourced mailing house and its agents, instructing them to stop issuing NRIC-protected documents and to confirm in writing. Under the NRIC authentication ban in Singapore, the intermediary remains responsible for those channels, so the written confirmations form part of its evidence file.

It records each decision, tests the new portal before launch and keeps a dated sign-off from its data protection officer. If a complaint reaches the PDPC in 2027, it can show both the timetable and the reasoning.

Risks and common mistakes

Assuming the ban only covers logins

Most residual exposure sits outside the main login page: encrypted attachments, account recovery, phone verification and staff look-ups. The PDPC's concern is any use of an NRIC number to grant access to personal data. An inventory that only covers the authentication service will miss these channels.

Ask each business unit to show, not describe, how a customer proves identity in every channel they run.

Swapping full NRIC for partial NRIC

Masking an NRIC number does not turn it into a secret. Partial numbers are frequently printed on letters, receipts and cards, and the Government has noted that partial numbers are not reliable even as identifiers. Replacing the full number with the last four characters as a password does not solve the problem and may still be treated as an unreasonable arrangement.

Over-correcting by deleting identification data

Some organisations react by purging NRIC numbers they genuinely need for identification, regulatory checks or record matching. That can create compliance problems elsewhere. The better course is to keep the number where identification is needed, protect it properly, and stop using it as proof of identity.

Retention should still be justified; see our note on retention limitation.

Forgetting vendors and outsourced channels

Payroll bureaux, mailing houses, outsourced call centres and software vendors often control the templates and scripts that use NRIC numbers. The organisation remains responsible for personal data processed on its behalf. Contracts and instructions should require vendors to remove NRIC-based authentication and confirm completion in writing.

Cross-border and group considerations

Regional groups often run shared customer platforms from outside Singapore. The deadline applies to how Singapore residents' personal data is protected by organisations subject to the PDPA, so a shared platform built in another jurisdiction may need a Singapore-specific change if it uses national identification numbers as default passwords.

Groups operating in Bangladesh, the UK, the UAE or China should check whether similar practices exist with local identity numbers. Even where local law is less prescriptive than the NRIC authentication ban in Singapore, a single group-wide standard that bans identity numbers as secrets is simpler to operate and audit. Our data protection and PDPA practice coordinates such reviews with local counsel in each market.

What to do now: checklist for decision-makers

With the NRIC authentication ban in Singapore taking practical effect at the end of the year, senior owners should be able to answer yes to each of the following before 31 December 2026:

  • We have an inventory of every channel where people prove their identity to us, including documents and phone.
  • No channel accepts a full or partial NRIC number, alone or with name or date of birth, as proof of identity.
  • Replacement methods were tested before release and the decisions are documented.
  • Front-line scripts and vendor instructions have been updated and confirmed.
  • Customers have been told what changed and how to get help.
  • Our breach response plan reflects the new authentication design.

If an incident does occur during migration, our guide to data breach response in Singapore sets out the notification steps. For advice on a migration plan, a vendor clause or a PDPC enquiry, please contact TRW & Co. Where Singapore court or tribunal representation is required, we work alongside Singapore-qualified counsel.

Frequently asked questions

01Is it illegal to collect NRIC numbers in Singapore from 2027?

No. The change concerns authentication, not collection. Organisations may still collect NRIC numbers where they genuinely need to identify a person accurately, for example for legal or regulatory requirements, subject to PDPC guidance on national identification numbers and the usual PDPA obligations. What must stop by 31 December 2026 is using a full or partial NRIC number as the proof of identity, such as a default password, PIN or security answer. Organisations should still minimise collection and protect NRIC numbers they hold.

02Can we still use the last four characters of an NRIC as a PDF password?

No. The PDPC deadline covers both full and partial NRIC numbers. Partial numbers are commonly printed on letters and receipts and can be guessed or obtained, so they are not a secret. A password built from NRIC characters, with or without a date of birth, should be replaced by a user-set password, a secure portal with one-time codes, or another method that relies on information only the individual holds or possesses.

03What penalties apply if we miss the 31 December 2026 deadline?

From 1 January 2027, the PDPC has said it will step up enforcement. Using NRIC numbers to authenticate access to personal data may be treated as a failure to make reasonable security arrangements under the PDPA. The PDPC can issue directions and impose financial penalties of up to 10% of annual Singapore turnover for organisations with turnover above S$10 million, or up to S$1 million otherwise. Actual outcomes depend on the facts, including any breach and the remedial steps taken.

04Does the NRIC authentication deadline apply to foreign companies?

It applies to private organisations subject to the PDPA, which can include foreign companies that collect, use or disclose personal data in Singapore. A regional platform serving Singapore customers from another country should therefore check whether it uses NRIC numbers as passwords or verification answers. Groups often adopt one global rule that no national identity number may be used as a secret, which avoids running different authentication logic for each market.

05What should replace NRIC-based verification in a call centre?

Common replacements include calling the customer back on a verified number, sending a one-time code to a registered mobile or email, or asking for a customer-set passphrase. Information printed on cards, letters or statements should not be used as the proof. Staff need updated scripts, a clear escalation path for customers who cannot pass verification, and training so they do not revert to asking for NRIC digits under pressure.

06Do we need to notify the PDPC that we have migrated?

There is no general requirement to file a notice with the PDPC confirming migration. However, organisations should keep a dated record of their inventory, decisions, testing and sign-off. If a complaint or breach later reaches the PDPC, that record is the most practical way to show that reasonable security arrangements were made in time. Separate breach notification duties apply if a notifiable data breach occurs.

Sources and official materials

  1. PDPC: Organisations to cease the use of NRIC numbers for authentication by 31 December 2026 — Deadline, enforcement from 1 January 2027 and sector guidance
  2. Personal Data Protection Commission — Advisories on NRIC numbers and common data protection lapses
  3. Personal Data Protection Act 2012 (Singapore Statutes Online) — Protection Obligation and financial penalties
  4. Cyber Security Agency of Singapore — Joint advisory with PDPC on authentication
  5. Monetary Authority of Singapore — Sector guidance for financial institutions and insurers
  6. Infocomm Media Development Authority — Sector guidance for telecommunications operators

General information only, current as at 20 October 2026. It is not legal advice and does not create a lawyer–client relationship. Singapore law and regulatory practice change; check current official sources and take advice on the facts of your matter.

TRW on LinkedIn & Facebook

From the firm,
this week.

Conference notes, transactions in the news and the people we work with — follow TRW & Co for the full feed.

Call the Singapore desk+880 1779 127165 WhatsApp · message usMessage our team