Let’s talk

Insights for your business.

PDPC Decisions Keep Finding the Same Gaps: A Seven-Point PDPA Self-Check for Singapore SMEs

A red padlock on a black computer keyboard

PDPC enforcement decisions keep exposing the same ordinary gaps: a privacy policy on the website with nothing behind it inside the company, no designated Data Protection Officer, IT vendors without written security duties, unsupported software, administrator accounts without multi-factor authentication, and manual system changes that nobody double-checks. None of these needs a big budget to fix. This article turns recent decisions into a seven-point self-check that a Singapore business owner or manager can complete in an afternoon.

A red padlock on a black computer keyboard
Ordinary businesses can close common personal data protection gaps. Photo by FlyD on Unsplash.

Why read the PDPC’s decisions instead of general PDPA summaries?

The Personal Data Protection Act 2012 (PDPA) sets out the duties in broad terms. The decisions show how the Commission applies them to real businesses and what it expects an organisation to have in place before an incident. They also show that the Commission does not accept the usual excuses, such as relying on a vendor, being a small business or having tightened security after the event.

For the penalty amounts in past cases, see our article on what a data breach really costs a Singapore company. This article focuses on the practical gaps behind those penalties. If you want the wider compliance picture, our PDPA compliance guide covers the full set of obligations.

Gap 1: do you have internal data protection policies, or only a website notice?

In its October 2025 decision on Air Sino-Euro Associates Travel Pte. Ltd. ([2025] SGPDPC 5), the Commission found the company had an external privacy policy but no internal data protection practices or policies. It held that section 12 of the PDPA requires an organisation to develop and implement policies and practices, set up a complaints process, communicate them to staff and make information available on request. The Commission cited an earlier decision, Stylez Pte Ltd ([2021] SGPDPC 8), in which a published policy that promised procedures nobody had implemented was effectively an empty promise.

Check: is there a written internal procedure for each promise in your website privacy notice, and have staff been told about it?

Gap 2: has someone been designated as your Data Protection Officer?

The same decision records that the company did not appoint a DPO until after the incident. The Commission described the appointment under section 11(3) of the PDPA as a basic requirement and said a diligent DPO could have flagged the risk of keeping a large volume of personal data on one server. Appointment does not move the legal responsibility away from the company. Our guides to the DPO duty under section 11 explain who can be appointed and what the role involves.

Check: can you name your DPO, and do staff and customers know how to reach them?

Gap 3: do your IT vendors have written security duties, and do you check them?

Air Sino-Euro had vendors maintaining its systems but no written contracts setting out their responsibilities for patching, maintenance or data protection, and no documented supervision. The Commission said that where an organisation relies on a vendor for IT security, the scope and security requirements should be stipulated in writing and followed through with checks. It has repeatedly said that using a vendor does not remove the organisation’s responsibility. For the liability question, see what happens when your IT vendor is hacked.

Check: does each vendor contract say who patches, who monitors, who reports incidents and how often you receive a review?

Gap 4: are you running software that is no longer supported?

The affected server in that case ran an operating system that had passed its end-of-life date, and the Commission treated this as a vulnerability the attacker could have used. It also found no periodic security reviews, which could have identified the need to upgrade. This is one of the cheapest gaps to close: list every server, laptop and application that holds personal data and note its support status.

Check: is there a current inventory of systems holding personal data, with a support end date for each?

Gap 5: do administrator accounts use multi-factor authentication and strong passwords?

The Commission noted that, following Lovebonito Singapore Pte. Ltd. ([2022] SGPDPC 3), multi-factor authentication is expected as a baseline for administrator accounts with privileged access to sensitive or large volumes of personal data. It also expects a password policy with a minimum level of complexity. The company was missing both. CH Offshore Ltd ([2024] SGPDPC 2) raised the same point.

Check: which accounts can reach customer or employee data, and does each one need a second factor to log in?

Gap 6: does anyone double-check manual changes to systems that hold personal data?

In the Marina Bay Sands decision ([2025] SGPDPC 6), the Commission imposed a financial penalty of S$315,000 after a manual step in a software migration left an interface without the protection the company intended. The Commission said that a new and complex task done by hand, relying on one expert employee with no meaningful second check, was unreasonable given the foreseeable risk of human error. It also said a test after the migration could have detected the problem, rather than waiting for routine testing months later. Most SMEs do not run migrations of that scale, but the lesson applies to any website rebuild, new CRM, new payroll system or cloud move.

Check: for any change to a system holding personal data, who reviews the work and what is tested before and after it goes live?

Gap 7: could you work out what happened after an incident?

In Air Sino-Euro, the vendors reformatted affected laptops without keeping a backup of system logs. The Commission accepted this was done in good faith but said retaining logs would have helped determine the cause. Separately, the PDPC guide on managing and notifying data breaches says an organisation should assess whether a breach is notifiable within 30 calendar days of having reason to believe it occurred, without unreasonable delay, and notify the PDPC within three calendar days of deciding it is notifiable. Our note on mandatory data breach notification and the article on the first 72 hours after ransomware cover the response.

Check: do you keep system and access logs, and does staff know whom to tell the same day a problem is suspected?

What did the penalty and directions look like in a small case?

In Air Sino-Euro the Commission imposed a financial penalty of S$47,000 for breaches of the accountability and protection duties, where the personal data of 336,759 individuals was affected. It also directed the company to put data protection policies in place, review vendor contracts to include security clauses, have a licensed cybersecurity provider run vulnerability assessment and penetration testing, and use multi-factor authentication, all within 90 days with evidence to the Commission. The Commission declined to reduce the penalty so the company could spend the money on security, and said that security measures taken to meet the statutory duty are not mitigating. In the Marina Bay Sands decision the Commission also described the maximum penalty as up to S$1 million, or 10% of annual Singapore turnover for larger organisations.

A one-page summary of the seven checks

Gap Basic fix Who usually owns it
Policies only on the website Write internal procedures and brief staff Management and DPO
No DPO designated Designate in writing, publish contact details Directors
Vendors without duties Add security clauses, request periodic reports Management
Unsupported software Inventory systems, plan upgrades IT lead or vendor
No MFA, weak passwords Enable MFA on admin accounts, set a password policy IT lead or vendor
Unchecked manual changes Second-person review and post-change test IT and DPO
No logs or response plan Keep logs, write a short incident plan DPO and management

Example: a ten-person online retailer runs the check

Example: this is a hypothetical illustration, not a real client. An online retailer holds customer names, addresses and phone numbers in its shop platform and an old spreadsheet. The owner runs the seven checks. The website has a privacy notice but no internal procedure, so a one-page handling guide is written. The accounts manager is formally designated as DPO and her details are added to the site. The web developer has no written contract, so a short service schedule is added covering updates and incident reporting. The spreadsheet sits on a laptop running an unsupported system, so the data is moved to a supported platform and the laptop is retired. Administrator logins get a second factor. A rule is added that any change to the shop’s checkout settings is reviewed by a second person. The owner has the logs switched on. The exercise takes a few hours and leaves a paper trail that shows the company took its duties seriously.

Frequently asked questions

Does a small business really need all seven?

The duties in the PDPA apply to organisations of every size. What counts as reasonable security depends on the amount and sensitivity of the data you hold. A business with few records may need simpler measures, but the Commission has treated a missing DPO and missing policies as basic requirements.

Can we rely on our IT vendor for security?

You can delegate the work but not the responsibility. The Commission expects written terms and oversight. Our article on vendor liability after a hack explores this further.

Do security improvements after a breach reduce the penalty?

Not by much. In Air Sino-Euro the Commission said that taking the measures the law already requires is not mitigating. Admitting liability, cooperating and notifying affected people have been treated as helpful in decisions we have read.

How often should we review security?

The Commission refers to periodic security reviews carried out to a reasonable standard, without setting a fixed interval in the decisions discussed here. Many businesses review at least yearly and after any major system change.

Is a PDPC penalty the only exposure?

No. Individuals who suffer loss may also bring claims, as explained in our article on the PDPA right of private action.

Where can we read the decisions ourselves?

The PDPC publishes its decisions on its website. The decisions discussed here are the Air Sino-Euro Associates Travel decision and the Marina Bay Sands decision. The Commission’s guide on managing and notifying data breaches sets out the notification timelines.

Need help closing your PDPA gaps?

If you would like to review your data protection set-up, contact the Raffles Corporate Services team at [email protected] or on WhatsApp at +65 8501 7133. We can help with DPO designation records, internal policy documents, vendor contract checklists and board or director records of your data protection decisions. Technical security testing is carried out by specialist providers, and this article is general information, not legal advice.

The Raffles Corporate Services Editorial Team, Raffles Corporate Services

Submit a Comment

Your email address will not be published. Required fields are marked *

Real people. Right here in Singapore.

Let’s get to work.

Hop on Raffles Corporate Services