Why it belongs in requirements
If software collects, uses or discloses personal data in Singapore, the Personal Data Protection Act (PDPA) shapes what the system must do. Treating it as a list of constraints during requirements analysis is cheaper than adding it after release. This page is an introduction, not legal advice.
Obligations that turn into features
The Personal Data Protection Commission (PDPC) describes the obligations organisations must meet (PDPC Advisory Guidelines). Several translate directly into requirements:
| Obligation | What it can mean for the software |
|---|---|
| Consent, including withdrawal | Record what was agreed and when; offer a way to withdraw |
| Purpose limitation and notification | Collect only fields with a stated purpose; show that purpose at collection |
| Access and correction | Be able to find and export one person's data; correct it |
| Accuracy | Validation and ways for people to update their details |
| Protection | Access control, encryption, logging, security testing |
| Retention limitation | Deletion or anonymisation when data is no longer needed |
| Transfer limitation | Know where hosting and backups are located when data leaves Singapore |
| Accountability | Documented policies and a designated Data Protection Officer |
| Data breach notification | Logs and processes to assess and report a breach |
Breach notification timing
A data breach is notifiable if it causes, or is likely to cause, significant harm to affected individuals, or is, or is likely to be, of a significant scale (PDPA s 26B). Once an organisation has assessed a breach as notifiable, it must notify the PDPC as soon as practicable and no later than 3 calendar days after that assessment (PDPA s 26D). Software should make that assessment possible: who accessed what, and when.
If your organisation also falls under the EU GDPR, Article 33 asks for notification to the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of a breach (GDPR Art. 33).
Penalties
For contraventions from 1 October 2022, the maximum financial penalty for an organisation with annual turnover in Singapore above S$10 million is 10% of that turnover; in other cases it is S$1 million (PDPA s 48J).
Developers as data intermediaries
A supplier that processes personal data on your behalf under a written contract can be a data intermediary. According to the PDPC guidelines, data intermediaries are mainly subject to the protection and retention limitation obligations and must tell the organisation about a breach they discover. The organisation that engages them remains responsible for the data, so the contract should say how data is protected, retained and returned.
A checklist for your brief
- Which personal data fields are needed, and why.
- Who may see each field.
- How long each kind of record is kept.
- Where hosting and backups are located.
- How a person's data can be found, exported, corrected and deleted.
- Who your Data Protection Officer is.
Sources
- PDPC, Advisory Guidelines on Key Concepts in the PDPA (17 May 2022)
- Personal Data Protection Act 2012 (Singapore), section 26B
- Personal Data Protection Act 2012 (Singapore), section 26D
- Personal Data Protection Act 2012 (Singapore), section 48J
- General Data Protection Regulation (EU) 2016/679, Article 33
Sources checked on 17 November 2026.