Singapore - Synthetic Data Generation Guide

Proposed Guide on Synthetic Data Generation (PDPC)

Singapore

RAI-SG-NA-PGSDGXX-2024
Proposed(Officially filed for action)As published at pdpc.gov.sg · checked 10 Sep 2026

Singapore - Synthetic Data Generation Guide is Proposed in Singapore as of 10 Sep 2026, according to www.pdpc.gov.sg.

GuidelineData Protection and PrivacyRisk ManagementGovernance and Oversight
Export PDF

The Personal Data Protection Commission (PDPC) of Singapore published the Proposed Guide on Synthetic Data Generation on 15 July 2024 to explain the uses, risks and good practices for generating structured synthetic data as a Privacy Enhancing Technology (PET). Jointly developed with A*STAR and supported by IMDA, the Guide provides a five‑step approach, case archetypes, and an annexed handbook of technical and governance controls to mitigate re‑identification risks.

Summary

The PDPC’s Proposed Guide on Synthetic Data Generation (published 15 July 2024) is a practical, non‑binding resource intended to help organisations understand how to generate and use structured synthetic data (SD) as a Privacy Enhancing Technology (PET) while minimising re‑identification risks. The Guide focuses on fully synthetic data used across three core archetypes: (1) generating training datasets for AI/ML models (including augmentation and diversity enhancement), (2) data analysis and collaboration (previewing and sharing), and (3) software development and testing (replacing production data). It describes synthetic data as artificial data produced by purpose-built mathematical, statistical or ML models that can retain statistical properties of source data but remains potentially risky if resemblance to source records allows re‑identification.

Key deliverables in the Guide include a five‑step operational approach (Know your data; Prepare your data; Generate synthetic data; Assess re‑identification risks; Manage residual risks), an Annex A 'Handbook on Key Considerations and Best Practices' with process checklists, an Annex C listing example generation methods, and Annexes on re‑identification risks and evaluation techniques. Technical measures recommended cover data minimisation, pseudonymisation, removing outliers, adding controlled noise, reducing granularity, employing differential privacy or other provable privacy techniques where appropriate, and selecting model types that balance utility and disclosure risk. Governance recommendations include clear articulation of purpose and lawful basis for relevant processing, designated accountability (roles and responsibilities), contractual clauses when engaging third‑party suppliers, documentation and versioning of synthetic data pipelines, validation and testing protocols, and retention and access controls.

The Guide is positioned as an evolving resource and is intended to be offered within IMDA’s PET Sandbox to support experimentation and regulatory engagement. PDPC emphasises that synthetic data is not inherently devoid of privacy risk and that organisations should perform risk assessments and periodically evaluate re‑identification risk with appropriate metrics. The Guide stresses sector sensitivities (notably healthcare and finance) and suggests conservative technical and contractual controls for high‑sensitivity contexts. On enforcement and legal context, PDPC reminds organisations that synthetic data generation activities occur within the ambit of Singapore’s Personal Data Protection Act (PDPA) and that non‑compliance with PDPA obligations can attract directions, fines and other sanctions under existing law (including increased penalty caps introduced in 2022).

Overall, the Proposed Guide is practical and implementation‑oriented: it combines high‑level policy framing with operational checklists, sample data dictionaries, method descriptions, and worked examples to help technical teams, data protection officers and senior decision makers evaluate and operationalise synthetic data projects while protecting individuals’ privacy.

Full article

Read full text ↗

Overview

The PDPC Proposed Guide on Synthetic Data Generation (15 July 2024) sets out good practices for producing structured synthetic data as a Privacy Enhancing Technology (PET). The Guide was jointly developed with the Agency for Science, Technology and Research (A*STAR) and is intended to be available as a resource within the IMDA PET Sandbox. It frames synthetic data as artificial data generated by purpose‑built mathematical or ML models that can mimic statistical properties of source datasets while warning that synthetic output may still pose re‑identification risks. The Guide focuses on fully synthetic structured data, provides three common use case archetypes (AI training, data sharing/analysis, software testing), and offers a five‑step process and annexed handbook to guide organisations in technical, governance and contractual controls to mitigate residual risks. It emphasises a risk‑based approach, recognising trade‑offs between utility and privacy, and positions the document as a living guide to be updated as the technology and evaluation methods evolve.

Definitions

The Guide defines key terms used throughout: "synthetic data" as artificially generated data created by mathematical or ML models trained on source data; "fully synthetic" (no real records preserved) and "partially synthetic" (some original values retained) distinctions; "re‑identification risk" meaning the probability an individual in source data can be matched to synthetic records; and "Privacy Enhancing Technology (PET)" covering data obfuscation, encrypted computation and federated analytics. The Guide focuses on structured tabular data and clarifies that while high‑quality synthetic data can preserve statistical properties and utility, it is not automatically non‑personal data and still requires privacy risk assessment.

Governance and Institutional Framework

The Guide outlines governance expectations for organisations that generate synthetic data, including role‑based accountability (CIO/CTO/CDO/Data Protection Officer), documented policies, and cross‑functional oversight. It recommends integrating synthetic data governance into existing data protection management systems and PDPA compliance programmes, and using contractual safeguards when engaging external vendors or cloud providers. The PDPC suggests organisations adopt explicit project charters specifying purpose, legal basis, data sources, expected end‑uses and retention timelines. Where appropriate, organisations are encouraged to engage regulators and the IMDA PET Sandbox (IMDA PET Sandbox) for early regulatory feedback. The Guide also recommends periodic board reporting for higher‑risk projects and inclusion of synthetic data projects in enterprise risk registers and privacy impact assessments.

Key Focus Areas

The Guide’s technical and process focal points include: (1) data understanding and minimisation—identify sensitive fields, remove outliers and restrict granularity where feasible; (2) synthetic generation choices—select generation methods (statistical, model‑based, GANs, probabilistic models) appropriate to data types and risk tolerance; (3) privacy controls—apply pseudonymisation on source data, inject calibrated noise, and consider differential privacy for metrics or model training where provable bounds are needed; (4) utility validation—define and measure downstream performance metrics to ensure synthetic data supports intended tasks without overfitting to real individuals; (5) re‑identification testing—use membership, attribute and record linkage tests and threshold‑based risk criteria described in Annex D and Annex E; and (6) contractual and operational controls—access restrictions, purpose limitation clauses, logging, and incident response integration with existing PDPA obligations. The Guide emphasises iterative trade‑off analysis between utility and disclosure risk and recommends conservative deployments in high‑sensitivity domains (e.g., healthcare, finance) unless robust mitigation is in place.

Implementation Framework

The Guide offers a practical five‑step implementation flow: Step 1—Know your data: catalogue fields, provenance and sensitivity; Step 2—Prepare data: pseudonymise/anonymise and remove outliers, apply minimisation; Step 3—Generate synthetic data: choose model architecture and training protocols, incorporate noise or constraints as needed; Step 4—Assess re‑identification risks: apply quantitative and qualitative tests from Annexes D/E and compare to predefined risk thresholds; Step 5—Manage residual risk: apply contractual, organisational and technical safeguards, maintain documentation and monitoring. Each step includes recommended artifacts (data dictionaries, model cards, risk assessment reports) and acceptance criteria for release. The Guide further provides a sample data dictionary format (Annex B) and examples of generation methods (Annex C) to aid implementation teams.

Monitoring and Evaluation

The Guide requires ongoing monitoring of synthetic data projects: scheduled re‑identification testing, validation of downstream model performance, incident detection and reporting, and periodic review of assumptions (e.g., changes in linkable external datasets that might raise re‑identification risk). It recommends maintaining logs of generation runs, model versions and random seeds where feasible for reproducibility and audit. The Guide encourages organisations using synthetic data in production to include synthetic data metrics in their privacy KPI dashboards, and to re‑evaluate risk when dataset composition, use cases or external threat models change. Where possible, results from the IMDA PET Sandbox pilots and public case studies should inform refinements.

Penalties, Liability, and Appeals

Although the Guide itself is non‑binding, organisations are reminded that synthetic data generation activities remain subject to the PDPA and other sectoral rules. PDPC enforcement powers under the PDPA include directions and financial penalties; since 1 October 2022 the PDPA regime allows penalties of up to 10% of an organisation's annual turnover in Singapore (for qualifying thresholds) or SGD 1,000,000 (whichever is higher) depending on circumstances. Organisations are therefore encouraged to document risk assessments, follow the Guide’s practices, and consult PDPC where novel or high‑risk designs are proposed. The Guide also notes that civil liability or sectoral regulatory sanctions may arise from misuse of data or harms traceable to synthetic outputs; it recommends clear allocation of contractual liability and dispute/appeal mechanisms in supplier contracts.

Relationship to Other Instruments

The Guide complements and builds on existing PDPC materials such as advisory guidelines on AI use and prior PDPC technology guides (e.g., anonymisation guidance). It is designed to be used alongside IMDA’s PET Sandbox resources and sectoral rules (e.g., health, finance) administered by agencies like the Ministry of Health and the Monetary Authority of Singapore where more stringent controls may apply. The Guide references OECD/PDP research and international best practices on PETs and situates synthetic data guidance within the PDPA accountability framework, recommending alignment of synthetic data project governance with organisational PDPA accountability obligations.

International Alignment

The Guide acknowledges analogous instruments internationally — for example, PET guidance and synthetic data research emerging from OECD, EU data protection authorities, and standards bodies — and seeks alignment on terminology and evaluation approaches. PDPC suggests interoperability with international standards and encourages use of internationally recognised privacy techniques (e.g., differential privacy) and measurable re‑identification tests to facilitate cross‑border collaborations while respecting local legal constraints. Through IMDA’s sandbox and international engagement, Singapore aims to harmonise practices to support data sharing, research collaboration and trade while maintaining strong privacy safeguards.

Implementation Timeline

MilestoneDate / Window
Guide published (proposed)15 July 2024
Inclusion in IMDA PET Sandbox resourcesQ3–Q4 2024 (ongoing)
PDPC updates / living document reviewsPeriodic review — next review indicated 2024–2025 (no fixed date)

Sources and References

SourceType
PDPC, Proposed Guide on Synthetic Data Generation (PDF)Primary Source
PDPC, Proposed Guide on Synthetic Data Generation (web summary)Primary Source
IMDA, Privacy Enhancing Technology SandboxesPrimary Source

Requirements for a company

What an organisation has to do under Singapore - Synthetic Data Generation Guide, at a glance. Not legal advice — the table below gives the provision and deadline for each item.

Not yet in force (Proposed). These requirements apply once the instrument takes effect and may change before then.

Must do

13
  • Document risk assessments for synthetic data generation activities.Organisations generating synthetic data.
  • Complete a data dictionary with sensitivity assessment.Organisations generating synthetic data.
  • Identify sensitive fields and minimise data before generation.Organisations generating synthetic data.
  • Apply pre-generation mitigations like pseudonymisation or outlier removal.Organisations generating synthetic data.
  • Conduct re-identification testing using specified methods and risk criteria.Organisations generating synthetic data.
  • Monitor synthetic data projects for re-identification risk and performance periodically.Organisations using synthetic data in production.
  • +7 more in the table below

Must not do

0

Nothing in this category.

Should do

1
  • Engage regulators for early feedback on novel or high-risk synthetic data projects.Organisations with novel or high-risk synthetic data projects.

Should not do

0

Nothing in this category.

Who must do what

The obligations under Singapore - Synthetic Data Generation Guide, most serious first. Not legal advice — verify against the official text before relying on it.

#WhoRequirementBy whenWhereSeverity
1Organisations generating synthetic data.Document risk assessments for synthetic data generation activities.
“Organisations are therefore encouraged to document risk assessments, follow the Guide’s practices...”
Before placing on marketPenalties, Liability, and AppealsCritical
2Organisations generating synthetic data.Complete a data dictionary with sensitivity assessment.
“Data dictionary (Annex B) completed”
Before generationImplementation FrameworkCritical
3Organisations generating synthetic data.Identify sensitive fields and minimise data before generation.
“(1) data understanding and minimisation—identify sensitive fields, remove outliers and restrict granularity where feasible;”
Before generationKey Focus AreasCritical
4Organisations generating synthetic data.Apply pre-generation mitigations like pseudonymisation or outlier removal.
“(3) privacy controls—apply pseudonymisation on source data, inject calibrated noise...”
Before generationKey Focus AreasCritical
5Organisations generating synthetic data.Conduct re-identification testing using specified methods and risk criteria.
“(5) re‑identification testing—use membership, attribute and record linkage tests and threshold‑based risk criteria...”
Before placing on marketKey Focus AreasCritical
6Organisations using synthetic data in production.Monitor synthetic data projects for re-identification risk and performance periodically.
“The Guide requires ongoing monitoring of synthetic data projects: scheduled re‑identification testing, validation of downstream model performance...”
OngoingMonitoring and EvaluationCritical
7Organisations generating synthetic data.Document project purpose, scope, lawful basis, and use cases.
“The PDPC suggests organisations adopt explicit project charters specifying purpose, legal basis, data sources, expected end‑uses and retention timelines.”
Before project commencementGovernance and Institutional FrameworkImportant
8Organisations generating synthetic data.Integrate synthetic data governance into existing data protection management systems.
“It recommends integrating synthetic data governance into existing data protection management systems and PDPA compliance programmes...”
NullGovernance and Institutional FrameworkImportant
9Organisations engaging external vendors for synthetic data.Use contractual safeguards with external vendors for synthetic data projects.
“...and using contractual safeguards when engaging external vendors or cloud providers.”
Before vendor engagementGovernance and Institutional FrameworkImportant
10Organisations generating synthetic data.Include synthetic data projects in enterprise risk registers and privacy impact assessments.
“...inclusion of synthetic data projects in enterprise risk registers and privacy impact assessments.”
Before project commencementGovernance and Institutional FrameworkImportant
11Organisations generating synthetic data.Validate synthetic data utility by measuring downstream performance metrics.
“(4) utility validation—define and measure downstream performance metrics to ensure synthetic data supports intended tasks...”
Before placing on marketKey Focus AreasImportant
12Organisations generating synthetic data.Implement access restrictions, purpose limitation, and logging for synthetic data.
“(6) contractual and operational controls—access restrictions, purpose limitation clauses, logging...”
Before placing on marketKey Focus AreasImportant
13Organisations generating synthetic data.Maintain logs of synthetic data generation runs and model versions.
“It recommends maintaining logs of generation runs, model versions and random seeds where feasible...”
OngoingMonitoring and EvaluationImportant
14Organisations with novel or high-risk synthetic data projects.Engage regulators for early feedback on novel or high-risk synthetic data projects.
“Where appropriate, organisations are encouraged to engage regulators and the IMDA PET Sandbox for early regulatory feedback.”
Before project commencementGovernance and Institutional FrameworkRecommended

© Regulations.AI · updated on 20 Sep 2026 · reviewed against official sources on 10 Sep 2026