facebook-pixel

Singapore PDPA vs GDPR: Key Differences Every Business Must Know in 2026

L
Lunyb Security Team
··10 min read

If your business operates in Singapore but serves customers in Europe — or vice versa — you are almost certainly subject to two of the world's most influential privacy laws: Singapore's Personal Data Protection Act (PDPA) and the European Union's General Data Protection Regulation (GDPR). While both frameworks protect personal data and share a common DNA, they differ in significant ways that affect how you collect consent, appoint data officers, transfer data across borders, and respond to breaches.

This guide breaks down the key differences between the PDPA and GDPR so you can build a compliance programme that satisfies both regulators without duplicating effort.

What Is the Singapore PDPA?

The Personal Data Protection Act (PDPA) is Singapore's primary data protection law, enacted in 2012 and significantly amended in 2020 and 2021. It is administered by the Personal Data Protection Commission (PDPC) and governs how private sector organisations collect, use, disclose, and care for personal data of individuals in Singapore.

The PDPA is built around nine core obligations, including Consent, Purpose Limitation, Notification, Access and Correction, Accuracy, Protection, Retention Limitation, Transfer Limitation, and Accountability. The 2020 amendments also introduced mandatory data breach notification and increased financial penalties.

What Is the GDPR?

The General Data Protection Regulation (GDPR) is the EU's comprehensive data protection law, which took effect on 25 May 2018. It applies across all 27 EU Member States and the European Economic Area, and is widely regarded as the strictest and most influential privacy regulation in the world.

GDPR is organised around seven key principles: lawfulness, fairness and transparency; purpose limitation; data minimisation; accuracy; storage limitation; integrity and confidentiality; and accountability. It grants individuals an expansive set of rights, including the right to erasure ("right to be forgotten"), data portability, and the right to object to automated decision-making.

PDPA vs GDPR: Quick Comparison Table

The table below summarises the most important structural differences between the two regimes.

Area Singapore PDPA EU GDPR
Regulator Personal Data Protection Commission (PDPC) National Data Protection Authorities + EDPB
Territorial scope Organisations collecting data in Singapore Any processing of EU residents' data, globally
Lawful bases Primarily consent, with deemed/legitimate interests exceptions Six lawful bases including consent, contract, legitimate interests
Data Protection Officer Mandatory for all organisations Mandatory only in specific cases
Breach notification Within 3 calendar days (notifiable breaches) Within 72 hours of awareness
Maximum fine Up to SGD 1 million or 10% of annual turnover (for orgs > SGD 10M) €20 million or 4% of global annual turnover
Right to erasure Limited (correction and withdrawal of consent) Explicit right to be forgotten
Data portability Introduced in 2020 amendments (not yet in force) Explicit right
Do Not Call Registry Yes, enforced under PDPA Covered separately under ePrivacy rules

Territorial Scope: Who Each Law Covers

Scope is where many Singapore businesses underestimate their exposure. The PDPA applies to organisations that collect, use, or disclose personal data in Singapore, regardless of whether the organisation itself is based locally. The GDPR, meanwhile, has extraterritorial reach — it applies to any organisation anywhere in the world that offers goods or services to individuals in the EU, or monitors their behaviour.

Practical implication: a Singapore e-commerce store that ships to Germany, or a SaaS company with EU subscribers, must comply with both laws simultaneously. Simply being headquartered in Singapore does not exempt you from GDPR.

Lawful Bases for Processing

This is one of the most structural differences between the two regimes.

PDPA: Consent-Centric

The PDPA places consent at the centre of lawful processing. Organisations must obtain consent before collecting, using, or disclosing personal data, with limited exceptions such as:

  • Deemed consent — when an individual voluntarily provides data for an obvious purpose.
  • Deemed consent by notification — introduced in 2020, allowing use for secondary purposes after notification and opt-out opportunity.
  • Legitimate interests exception — processing where benefits outweigh adverse effects, with documented assessment.
  • Business improvement exception — for internal analytics and product improvement.

GDPR: Six Equal Lawful Bases

Under Article 6 of GDPR, consent is just one of six lawful bases, which include:

  1. Consent
  2. Performance of a contract
  3. Legal obligation
  4. Vital interests
  5. Public interest / official authority
  6. Legitimate interests

Importantly, GDPR requires consent to be freely given, specific, informed, and unambiguous — pre-ticked boxes and bundled consents are not valid. The PDPA is slightly more flexible on how consent is captured, but still prohibits false or misleading consent requests.

Data Protection Officer (DPO) Requirements

This is an area where the PDPA is actually stricter than the GDPR.

Under the PDPA, every organisation — regardless of size — must appoint at least one Data Protection Officer and publish their business contact information. This is a universal obligation.

Under the GDPR (Article 37), appointing a DPO is only mandatory when:

  • The organisation is a public authority;
  • Its core activities require large-scale, regular, and systematic monitoring of individuals; or
  • Its core activities involve large-scale processing of special category data (health, biometrics, etc.).

So a small Singapore bakery must have a DPO under the PDPA, but the same business operating purely in Europe might not need one under GDPR.

Individual Rights

Both laws grant individuals meaningful rights, but GDPR's catalogue is broader.

Rights Under the PDPA

  • Right to be informed about purposes
  • Right to access personal data held
  • Right to correction
  • Right to withdraw consent
  • Right to data portability (legislated but not yet in force as of 2026)

Rights Under GDPR

  • Right to be informed
  • Right of access
  • Right to rectification
  • Right to erasure ("right to be forgotten")
  • Right to restrict processing
  • Right to data portability
  • Right to object
  • Rights related to automated decision-making and profiling

Notably, GDPR's right to erasure has no direct PDPA equivalent — Singapore's framework focuses on withdrawal of consent and retention limitation rather than compelled deletion on request.

Data Breach Notification

Both regimes now mandate breach notification, but the triggers and timelines differ.

PDPA: Organisations must notify the PDPC within 3 calendar days of assessing that a breach is notifiable. A breach is notifiable if it (a) results in significant harm to affected individuals, or (b) involves 500 or more individuals. Affected individuals must also be notified when significant harm is likely.

GDPR: Controllers must notify the supervisory authority within 72 hours of becoming aware of a breach, unless the breach is unlikely to result in a risk to individuals' rights and freedoms. Individuals must be notified when the breach poses a high risk.

In practice, GDPR's clock starts earlier (upon awareness, not after assessment), making it the tighter standard.

Cross-Border Data Transfers

Both laws restrict international data transfers, but the mechanics differ.

The PDPA requires organisations transferring data overseas to ensure the recipient provides a standard of protection "comparable" to the PDPA. This is typically achieved through contractual clauses, binding corporate rules, or certification schemes like APEC CBPR and Singapore's DPTM.

The GDPR is considerably more prescriptive. Transfers outside the EEA require one of the following:

  • An adequacy decision (Singapore does not currently have one);
  • Standard Contractual Clauses (SCCs);
  • Binding Corporate Rules (BCRs);
  • Approved certifications or codes of conduct;
  • Specific derogations (explicit consent, contract necessity, etc.).

Since the Schrems II ruling, organisations must also conduct Transfer Impact Assessments (TIAs) to evaluate the legal environment of the destination country.

Penalties and Enforcement

Both regulators have sharpened their teeth in recent years.

Under the amended PDPA, maximum financial penalties increased to SGD 1 million or 10% of annual turnover in Singapore (whichever is higher) for organisations with turnover above SGD 10 million. GDPR penalties remain the global benchmark at €20 million or 4% of worldwide annual turnover, whichever is higher.

Beyond fines, both regimes allow directions, undertakings, and — under GDPR — bans on processing. Reputational damage from public enforcement decisions is often the bigger cost for both frameworks.

Practical Compliance Checklist for Dual-Regime Businesses

If your organisation is subject to both laws, build a unified programme rather than two parallel ones. Here is a streamlined compliance checklist:

  1. Map your data flows — know what personal data you collect, where it is stored, who accesses it, and where it travels.
  2. Appoint a DPO — mandatory under PDPA; align the role to also handle GDPR obligations.
  3. Document lawful bases — for each processing activity, identify the PDPA basis and the GDPR Article 6 basis.
  4. Refresh consent flows — ensure consent is granular, opt-in, and easy to withdraw.
  5. Publish a layered privacy notice — one notice can serve both regimes with regional annexes.
  6. Implement a rights-request workflow — handle PDPA access/correction and GDPR's wider rights through a single intake form.
  7. Prepare a breach response playbook — target the stricter 72-hour clock to satisfy both regulators.
  8. Review vendors and transfer mechanisms — put SCCs and TIAs in place for EU transfers; comparable-protection clauses for PDPA transfers.
  9. Use privacy-respecting tooling — whenever you share links, forms, or marketing URLs, choose services that minimise tracking. A privacy-first link platform like Lunyb helps reduce the personal data footprint associated with click analytics, which simplifies both PDPA and GDPR obligations. For a deeper look, see our honest review of Lunyb.
  10. Train staff annually — most enforcement actions stem from human error, not system failure.

Where the Two Laws Actually Agree

It is easy to focus on the differences, but the overlap is substantial. Both regimes:

  • Require transparency about what data is collected and why;
  • Demand proportionality — collect only what you need;
  • Impose accountability on the organisation, not just its vendors;
  • Require appropriate technical and organisational security measures;
  • Grant individuals meaningful access and correction rights;
  • Mandate breach notification to regulators.

A business that implements a GDPR-quality programme will satisfy most PDPA requirements by default — with the notable exception of the DPO appointment and the PDPA-specific Do Not Call provisions.

Final Thoughts

For Singapore businesses with international reach, the practical question is rarely "PDPA or GDPR?" but rather "how do we satisfy both efficiently?" The answer is a single, well-documented privacy programme built to the stricter standard where the two laws diverge — tight breach timelines, lawful-basis documentation, and robust transfer safeguards — while fully implementing PDPA-specific obligations such as the DPO role and Do Not Call compliance.

Regulatory expectations will only continue to converge. Treating privacy as a product feature rather than a legal checkbox positions your business for both markets — and for the next wave of privacy laws emerging across Asia-Pacific.

Frequently Asked Questions

Does my Singapore business have to comply with GDPR?

Yes, if you offer goods or services to individuals located in the EU/EEA, or monitor their behaviour (such as through website tracking). GDPR has extraterritorial scope, so your Singapore headquarters does not shield you from compliance. In that case you must comply with both PDPA and GDPR.

Is the PDPA stricter than the GDPR?

Generally, GDPR is stricter in terms of individual rights, consent standards, breach notification timing (72 hours vs 3 days), and penalties. However, the PDPA is stricter on one key point: it requires every organisation, regardless of size, to appoint a Data Protection Officer — while GDPR only requires one in specific circumstances.

Does Singapore have a GDPR adequacy decision?

As of 2026, Singapore does not have a formal EU adequacy decision. Transfers of personal data from the EU to Singapore must therefore rely on another transfer mechanism, most commonly Standard Contractual Clauses (SCCs) accompanied by a Transfer Impact Assessment.

What is the maximum PDPA fine in Singapore?

Following the 2022 enforcement amendments, the maximum financial penalty is SGD 1 million or 10% of the organisation's annual turnover in Singapore, whichever is higher. The 10% cap applies to organisations with annual Singapore turnover exceeding SGD 10 million.

Can one privacy policy cover both PDPA and GDPR?

Yes, with care. The best practice is a single layered privacy notice that addresses shared principles (purpose, retention, security, rights) and includes regional annexes for PDPA-specific disclosures (DPO contact, withdrawal of consent) and GDPR-specific disclosures (lawful basis for each purpose, international transfer mechanisms, supervisory authority contact).

Protect your links with Lunyb

Create secure, trackable short links and QR codes in seconds.

Get Started Free

Related Articles