Singapore version. Opens on a Singapore filter with the PDPA: its data protection obligations as the PDPC lists them, the DPO, breach notification and the Do Not Call Registry. US version

Software Compliance Checklist (Singapore)

Build a PDPA checklist for a Singapore app or SaaS: the data protection obligations, DPO, breach notification to the PDPC and DNC checks, plus global standards.

The interactive tool loads here when JavaScript runs.

About this tool

What is the Software Compliance Checklist?

This version opens on the Singapore filter, which lists the Personal Data Protection Act 2012. The PDPC describes it as the baseline standard for personal data in Singapore, sitting under sector rules such as the Banking Act and Insurance Act, and covering data held electronically or on paper. The card turns the PDPC's list of obligations into checklist lines: accountability with a named data protection officer, notification and consent, purpose limitation, accuracy, protection, retention and transfer limits, access and correction, and breach notification.

Two scope rules matter for product teams. The Act generally does not apply to business contact information, such as a person's name, title, work phone and work email, so a B2B tool that only holds that has a lighter load. It also does not apply to public agencies, but a vendor building for one still handles personal data as an organisation. Marketing teams have a separate duty: the Act set up the national Do Not Call Registry, and Singapore numbers on it opt out of telemarketing messages.

Breach handling is where software teams need a runbook. Organisations must assess whether a data breach is notifiable, which the PDPC expects within 30 calendar days, and if it is likely to cause significant harm or is of significant scale, notify the PDPC as soon as practicable and no later than 3 calendar days after assessing that the breach is notifiable, and notify affected individuals as soon as practicable. Switch to Global for ISO 27001, SOC 2 and PCI DSS, which enterprise buyers may ask about in supplier reviews, or to EU if you serve customers there.

  • 31 laws, standards and frameworks with requirements and penalties
  • Search plus domain and geography filters
  • Custom checklist downloaded as Markdown task list
  • CSV export of the filtered list
  • Runs in your browser with no account
Read the guide: Which Compliance Rules Apply to Your Software? A Map for Engineers

Updated

How to use the Software Compliance Checklist

  1. On the Browse Compliances tab, type in Search compliances (for example "cookies" or "health") and narrow with the Domain and Geography filters.
  2. Click a card to open its details: requirements, applicability, penalties, related items and official resources.
  3. Click the + on a card to add it to your checklist.
  4. Open the My Checklist tab, rename the checklist, and click Download MD to save a Markdown file with a checkbox for every requirement.
  5. Use Export Report on the Browse tab to download the currently filtered list as CSV.

Worked examples

Clinic booking app for Singapore patients

Input

Geography: Singapore

Output

1 result: the Personal Data Protection Act 2012 (PDPA), with nine requirements

Patient names, NRIC-linked bookings and contact numbers are personal data, so every line applies. Add ISO 27001 from the Global filter if a healthcare group asks for a certified security programme.

S$49-a-month B2B invoicing SaaS that stores only work contacts

Input

Geography: Singapore, open the PDPA card and read its applicability

Output

Business contact information is generally outside the Act

If the product later stores end customers' home addresses or phone numbers, those are personal data again; keep the PDPA lines in the checklist for that release.

Background and insight

Most software teams meet compliance through a product decision rather than a legal memo: a signup form that collects a birth date, a checkout that stores card numbers, an analytics script that sets cookies for EU visitors. Each of those pulls in a different regime. Card data brings PCI DSS, health records held for a US covered entity bring HIPAA, children under 13 bring COPPA, and EU residents' personal data brings GDPR wherever the company is based.

The documents differ in kind. GDPR, CCPA and HIPAA are laws with regulators and fines; GDPR's upper tier is EUR 20 million or 4 percent of worldwide annual turnover, whichever is higher, and it requires breach notification to the authority within 72 hours. PCI DSS is a contractual standard set by the card brands (version 4.0 became the only active version in 2024). SOC 2 is an attestation report by an independent CPA firm against AICPA criteria, not a certification. WCAG 2.2, published by the W3C in October 2023, is the technical yardstick most accessibility laws point to.

Engineering work tends to repeat across regimes: an inventory of personal data, access control and audit logs, encryption in transit and at rest, retention and deletion, breach response, vendor contracts, and accessible UI. Building those once and mapping them to each framework is cheaper than treating every framework as a separate project.

Common use cases

  • Scoping a new product

    List the regimes a feature might trigger before design starts, while changes are cheap.

  • Answering a security questionnaire

    Get a quick summary of SOC 2, ISO 27001 or HIPAA terms an enterprise buyer asks about.

  • Planning an engineering roadmap

    Download a Markdown checklist and turn requirement lines into tickets.

  • Onboarding new engineers

    Give a team a shared vocabulary for the frameworks their product is subject to.

Tips and limitations

  • Publish how to reach your data protection officer; the PDPC lists making the DPO's business contact information public as part of the accountability obligation.
  • Record the purpose of each data field when you design a form, so the notification and purpose limitation lines have evidence behind them.
  • Before a telemarketing campaign by SMS or call, check Singapore numbers against the DNC Registry through the PDPC e-service.
  • The data portability obligation is listed by the PDPC but takes effect only when its regulations are issued; track it rather than build for it now.

Sources and further reading

  1. PDPA Overview, Personal Data Protection Commission. What the PDPA covers, its exclusions and the DNC Registry.
  2. Data Protection Obligations, Personal Data Protection Commission. The eleven obligations, including breach notification and data portability.
  3. Guide on Managing and Notifying Data Breaches under the PDPA, Personal Data Protection Commission. Assess within 30 calendar days of credible grounds to believe a breach occurred; notify the PDPC no later than 3 calendar days after determining a breach is notifiable, and affected individuals as soon as practicable.
  4. Enforcement of the Act, Personal Data Protection Commission. Directions, financial penalties and investigation offences.

Frequently asked questions

Does the PDPA apply to a small start-up in Singapore?

Size is not the test. The obligations apply to organisations that collect, use or disclose personal data. The exclusions are for individuals acting in a personal or domestic capacity, employees acting for their organisation, public agencies and business contact information.

Do I need a data protection officer under the PDPA?

Yes. The accountability obligation includes designating a DPO and making their business contact information available to the public, as well as making your data protection policies and complaints process available on request.

When must a data breach be reported to the PDPC?

After you assess that it is notifiable: when it is likely to result in significant harm to individuals or is of significant scale. The PDPC expects that assessment within 30 calendar days of having credible grounds to believe a breach has occurred. Notify the PDPC as soon as practicable and no later than 3 calendar days after assessing that the breach is notifiable, and notify affected individuals as soon as practicable, at the same time or after notifying the PDPC.

Can I store Singapore customer data on overseas cloud servers?

Under the transfer limitation obligation you may transfer personal data out of Singapore only in line with the prescribed requirements, so that the protection stays comparable to the PDPA. Put this in your hosting and sub-processor contracts.

What can the PDPC do if we breach the PDPA?

It can direct an organisation to stop collecting, using or disclosing personal data in breach of the Act, destroy data collected in contravention, give access or make corrections, or pay a financial penalty. Altering or destroying data during an investigation is an offence.

Is there an in-depth guide to the Software Compliance Checklist?

Yes. “Which Compliance Rules Apply to Your Software? A Map for Engineers” covers the background, how it works, common pitfalls and worked examples. Read the full guide.