Data Processing Agreement (Singapore)
DATA PROCESSING AGREEMENT
Personal Data Protection Act 2012 (PDPA) — As Amended 2020
Effective Date: [Effective Date]
PARTIES
This Data Processing Agreement ("DPA") is entered into between:
(1) [Controller Name] (UEN: [Controller UEN]), a company incorporated in Singapore with its registered office at [Controller Address] ("Controller"); and
(2) [Processor Name] (UEN: [Processor UEN]), a company incorporated in Singapore with its registered office at [Processor Address] ("Processor").
The Controller and Processor are each a "Party" and together the "Parties".
1. BACKGROUND
1.1 The Controller has engaged the Processor to provide services pursuant to which the Processor processes personal data on behalf of the Controller.
1.2 The Parties wish to set out the terms governing the Processor's handling of personal data in compliance with the Personal Data Protection Act 2012 (No. 26 of 2012) ("PDPA") as amended by the Personal Data Protection (Amendment) Act 2020, and the directions and guidelines issued by the Personal Data Protection Commission ("PDPC").
2. SCOPE AND NATURE OF PROCESSING
2.1 Purpose: [Processing Purpose]
2.2 Categories of Personal Data: [Data Categories]
2.3 Data Subjects: [Data Subjects]
2.4 Duration: [Processing Duration]
3. PROCESSOR OBLIGATIONS
3.1 The Processor shall process personal data only on documented instructions from the Controller and only for the purposes set out in clause 2.1 of this DPA.
3.2 The Processor shall implement reasonable security arrangements to protect personal data against unauthorised access, collection, use, disclosure, copying, modification, disposal, or similar risks, in accordance with s.24 of the PDPA and the PDPC's Guide to Securing Personal Data in Electronic Medium.
3.3 The Processor shall notify the Controller without undue delay, and in any event within 3 calendar days, upon becoming aware of a data breach affecting personal data processed under this DPA, to enable the Controller to fulfil its mandatory breach notification obligations under s.26C of the PDPA (as amended 2020).
3.4 The Processor shall provide reasonable assistance to the Controller in responding to access and correction requests from data subjects under ss.21 and 22 of the PDPA.
3.5 Upon termination or expiry of this DPA, the Processor shall, at the Controller's election, securely delete or return all personal data within 30 days and certify such deletion or return in writing.
4. CONTROLLER OBLIGATIONS
4.1 The Controller shall ensure it has a valid legal basis (including, where required, individual consent) for the collection and use of all personal data provided to the Processor under this DPA.
4.2 The Controller's DPO contact is: [Controller DPO].
5. GOVERNING LAW
This DPA shall be governed by and construed in accordance with the laws of Singapore. Any dispute arising from or in connection with this DPA shall be subject to the exclusive jurisdiction of the Singapore courts.
EXECUTION
IN WITNESS WHEREOF, the Parties have executed this Data Processing Agreement as of the Effective Date.
For and on behalf of [Controller Name] (Controller):
Signature: _________________________ Name: _________________________ Date: _________________________
For and on behalf of [Processor Name] (Processor):
Signature: _________________________ Name: _________________________ Date: _________________________
Controller
________________
Signature
Processor
________________
Signature
What Is a Data Processing Agreement (Singapore)?
A Data Processing Agreement in Singapore records the terms the parties accept and the commitments each makes to the other.
The Personal Data Protection Commission (PDPC) — the statutory body established under Part IX of the PDPA to administer and enforce the Act — issued Advisory Guidelines on Key Concepts in the Personal Data Protection Act that explain the controller-processor relationship and the contractual obligations that should be established through a DPA. The PDPC has consistently held in enforcement decisions that a controller organisation cannot outsource its PDPA compliance obligations — the controller remains responsible for personal data processed by its data intermediaries, and must take contractual and practical steps to verify the intermediary's compliance.
The 2020 PDPA amendments (effective 1 February 2021) strengthened the data intermediary framework by introducing section 26C, which requires data intermediaries to notify the controller organisation of any data breach affecting the controller's data without undue delay, enabling the controller to meet the mandatory breach notification deadline under section 26D (three calendar days from assessment of notifiability to the PDPC). The DPA must therefore include breach notification provisions aligned with the PDPA's mandatory breach notification framework.
Singapore's position as a data processing hub in Asia-Pacific — hosting major cloud service providers, business process outsourcing centres, and shared services centres — makes the DPA a high-volume document. Cross-border data transfers from Singapore to overseas processors are governed by sections 26 and 26A of the PDPA, which require the controller to take reasonable steps to verify that the overseas processor will protect the personal data to a standard comparable to the PDPA's protection obligation. PDPC-approved contractual clauses, binding corporate rules, or certification to an approved data protection framework (such as the APEC Cross-Border Privacy Rules system) may satisfy this requirement.
Singapore contract law — based on English common law, received under the Application of English Law Act 1993 — governs the formation, validity, and enforcement of DPAs as commercial contracts. A binding DPA requires the common-law elements of a valid contract: offer, acceptance, consideration, and an intention to create legal relations, with free consent of parties competent to contract and a lawful object. DPA disputes are subject to the jurisdiction of the Singapore courts or alternative dispute resolution mechanisms (Singapore Mediation Centre, Singapore International Arbitration Centre) as specified in the agreement.
The PDPC has also published a Guide to Data Protection Clauses for Agreements Relating to the Processing of Personal Data, which provides model clauses that can be incorporated into DPAs. Singapore's participation in the ASEAN Framework on Digital Data Governance and the ASEAN Model Contractual Clauses for Cross-Border Data Flows provides additional reference frameworks for DPAs involving data transfers within the ASEAN region.
When Do You Need a Data Processing Agreement (Singapore)?
A Data Processing Agreement is needed in Singapore whenever an organisation (the data controller) engages another organisation (the data intermediary or processor) to process personal data on its behalf, and the controller must maintain compliance with the Personal Data Protection Act 2012.
Cloud computing and SaaS arrangements require DPAs when Singapore organisations store or process personal data using cloud infrastructure (Amazon Web Services, Microsoft Azure, Google Cloud Platform, Alibaba Cloud) or software-as-a-service applications (CRM systems, HR platforms, accounting software, email services) hosted by third-party providers. The controller organisation remains responsible under the PDPA for personal data processed in the cloud, and the DPA establishes the processor's obligations regarding data security, access controls, breach notification, and data deletion upon contract termination.
Business process outsourcing (BPO) engagements — payroll processing, customer service centres, data entry services, document management — require DPAs when the outsourced function involves access to or processing of personal data belonging to the controller's customers, employees, or business contacts. Singapore's BPO sector, supported by the Economic Development Board (EDB) and Enterprise Singapore (ESG), processes large volumes of personal data for multinational clients.
Data Processing Agreement (Singapore) service provider engagements — managed IT services, cybersecurity monitoring, software development, system integration — require DPAs when the service provider accesses personal data stored in the controller's systems during service delivery. The PDPC's enforcement decisions have found controllers liable for data breaches caused by IT service providers who were not bound by adequate contractual data protection obligations.
Marketing and analytics service providers engaged to process customer data for targeted marketing, customer segmentation, or data analytics require DPAs specifying the permitted uses of personal data and restrictions on secondary use, profiling, and re-identification of anonymised data.
Cross-border data processing requires DPAs with enhanced provisions under sections 26 and 26A of the PDPA. Where personal data is transferred to a processor located outside Singapore — whether in the ASEAN region, Europe, the United States, India, or elsewhere — the DPA must include contractual obligations that provide a standard of protection comparable to the PDPA. The PDPC has published model contractual clauses and guidance on cross-border data transfers that can be incorporated into DPAs.
Group company arrangements within multinational organisations require intra-group DPAs when personal data collected by the Singapore entity is shared with affiliated companies in other jurisdictions for centralised processing (regional HR systems, group-wide CRM, consolidated financial reporting).
What to Include in Your Data Processing Agreement (Singapore)
A Singapore Data Processing Agreement must include the following provisions to satisfy the PDPA's data protection framework, the PDPC's Advisory Guidelines, and commercial standard practices for data processing arrangements.
**Parties and Roles** clearly identifies the data controller (the organisation determining the purposes and means of processing) and the data intermediary (the organisation processing personal data on behalf of the controller). Each party is identified by registered name, UEN issued by ACRA, registered address, and the name and contact details of the Data Protection Officer (DPO) designated under section 11(3) of the PDPA.
**Scope of Processing** defines the personal data to be processed (categories of data subjects and types of personal data), the purposes for which the data will be processed (which must not exceed the purposes for which the controller obtained the individual's consent under section 13 of the PDPA), the nature of the processing activities (storage, analysis, transformation, deletion, etc.), and the duration of the processing.
**Processor Obligations** sets out the data intermediary's duties: process personal data only in accordance with the controller's documented instructions; implement security measures that meet the PDPA's protection obligation under section 24 (protecting personal data against unauthorised access, collection, use, disclosure, copying, modification, disposal, or similar risks); maintain confidentiality of personal data and restrict access to authorised personnel; maintain a log of processing activities; and cooperate with the controller's audits and PDPC investigations.
**Sub-Processor Management** addresses whether the data intermediary may engage sub-processors to perform part of the processing. The DPA should require: prior written consent from the controller before engaging any sub-processor; the data intermediary to impose equivalent data protection obligations on each sub-processor through a written sub-processing agreement; and the data intermediary to remain liable to the controller for the sub-processor's performance.
**Data Breach Notification** requires the data intermediary to notify the controller of any data breach affecting the controller's personal data without undue delay, in accordance with section 26C of the PDPA. The notification must include: the nature of the breach; the categories and approximate number of data subjects affected; the likely consequences of the breach; and the measures taken or proposed to contain and remediate the breach. The DPA should specify the notification timeline (typically within 24 hours of discovery) to give the controller sufficient time to assess the breach and meet the PDPC's three-calendar-day notification deadline under section 26D.
**Cross-Border Data Transfer** governs the transfer of personal data to processors or sub-processors located outside Singapore. Under sections 26 and 26A of the PDPA, the controller must take reasonable steps to verify that the overseas processor will protect the data to a standard comparable to the PDPA. The DPA should specify the countries to which data may be transferred, the safeguards in place (PDPC-approved contractual clauses, binding corporate rules, APEC Cross-Border Privacy Rules certification), and the controller's right to audit the overseas processor's data protection practices.
**Data Retention and Deletion** aligns with the PDPA's retention limitation obligation under section 25. The DPA must require the data intermediary to cease retaining personal data when it is no longer necessary for the processing purpose, and to return or securely delete all personal data (including copies and backups) upon termination or expiry of the DPA. The controller may specify the deletion method (secure overwrite, cryptographic erasure, physical destruction) and require written certification of deletion.
**Controller Obligations** acknowledges the controller's responsibility for: obtaining valid consent under section 13 of the PDPA from data subjects before providing their personal data to the data intermediary; providing lawful processing instructions; notifying the data intermediary of any changes to consent scope or data subject requests (access, correction, withdrawal of consent); and complying with all applicable PDPA obligations.
**Governing Law and Dispute Resolution** states that the DPA is governed by Singapore law, with disputes subject to the jurisdiction of the Singapore courts or resolution through the Singapore Mediation Centre (SMC) or arbitration under the Singapore International Arbitration Centre (SIAC).
The forms-legal.com Data Processing Agreement template covers all PDPA-mandated elements, including modular sections for cross-border data transfers, sub-processor management, and breach notification timelines. Under Singapore law, Section 169 of the Companies Act 1967 (Cap. 50) and Section 8 of the Employment Act 1968 (Cap. 91) govern the core requirements for this type of document. Under Singapore law, Section 22 of the Stamp Duties Act (Cap. 312) and Section 6 of the Conveyancing and Law of Property Act (Cap. 61) govern the core requirements for this type of document.
Cite this page
Reference this free template in an article, syllabus, or research note:
Forms Legal. (2026). Data Processing Agreement (Singapore) (Singapore) [Legal document template]. Forms Legal. https://forms-legal.com/singapore/business/services/data-processing-agreement-singapore
"Data Processing Agreement (Singapore) (Singapore)." Forms Legal, 2026, https://forms-legal.com/singapore/business/services/data-processing-agreement-singapore.
@misc{formslegal-data-processing-agreement-singapore,
author = {{Forms Legal}},
title = {Data Processing Agreement (Singapore) (Singapore)},
year = {2026},
howpublished = {\url{https://forms-legal.com/singapore/business/services/data-processing-agreement-singapore}},
note = {Free legal document template. Based on Personal Data Protection Act 2012 (PDPA)}
}Frequently Asked Questions
The PDPA does not expressly mandate a written Data Processing Agreement between a data controller and a data intermediary. However, the PDPC has consistently emphasised in its Advisory Guidelines and enforcement decisions that a controller organisation cannot outsource its PDPA compliance obligations and must take contractual and practical steps to verify the intermediary's compliance with the PDPA's protection obligation (section 24) and retention limitation obligation (section 25). In practice, the PDPC expects controllers to have written agreements with data intermediaries that specify the processor's obligations regarding data security, permitted processing purposes, breach notification, sub-processing, and data deletion. Controllers that fail to impose adequate contractual obligations on their processors have been found liable by the PDPC for data breaches caused by the processor's inadequate security measures. A written DPA is therefore a practical necessity for PDPA compliance, even if not explicitly required by statute.
Under the PDPA, a data intermediary (data processor) has two primary statutory obligations: the protection obligation under section 24, requiring the intermediary to implement reasonable security measures to protect personal data against unauthorised access, collection, use, disclosure, copying, modification, disposal, or similar risks; and the retention limitation obligation under section 25, requiring the intermediary to cease retaining personal data when it is no longer necessary for the processing purpose. Additionally, section 26C (introduced by the 2020 amendments) requires data intermediaries to notify the controller organisation of any data breach affecting the controller's personal data without undue delay, enabling the controller to assess the breach and meet the three-calendar-day PDPC notification deadline under section 26D. Data intermediaries are not directly subject to the consent obligation (section 13) or the purpose limitation obligation (section 18) — these obligations rest with the controller.
A Singapore DPA should include: identification of the controller and intermediary with registered names, UENs, and DPO contact details; the scope of processing (categories of data subjects, types of personal data, processing purposes, and duration); the intermediary's obligations (processing only per controller instructions, implementing section 24 security measures, maintaining confidentiality, cooperating with audits); sub-processor provisions (prior written consent, equivalent obligations, intermediary liability); data breach notification requirements (notification within 24 hours to allow the controller to meet the PDPC's three-day deadline under section 26D); cross-border data transfer safeguards under sections 26 and 26A; data retention and deletion obligations under section 25 (return or secure deletion upon contract termination); controller obligations (valid consent, lawful instructions); and governing law (Singapore law, with dispute resolution through the Singapore courts, SMC, or SIAC). The PDPC's Advisory Guidelines and model contractual clauses provide a reference framework for DPA drafting.
Singapore's PDPA and the EU's General Data Protection Regulation (GDPR) both regulate cross-border data transfers but differ in approach. The PDPA (sections 26 and 26A) requires the controller to take reasonable steps to verify that the overseas processor will protect personal data to a standard comparable to the PDPA — the PDPC provides model contractual clauses, accepts binding corporate rules, and recognises the APEC Cross-Border Privacy Rules (CBPR) system as a transfer mechanism. The GDPR (Articles 44-49) restricts transfers to countries without an EU adequacy decision and requires Standard Contractual Clauses (SCCs), binding corporate rules, or other approved safeguards. Singapore does not have an EU adequacy decision, so organisations transferring personal data between Singapore and the EU must use GDPR-approved transfer mechanisms for the EU data and PDPA-compliant safeguards for the Singapore data. The PDPA does not require the processor to appoint an EU representative (as required by GDPR Article 27 for non-EU processors targeting EU data subjects), and the PDPA's financial penalties (up to S$1 million or 10% of Singapore turnover) differ from GDPR penalties (up to EUR 20 million or 4% of global annual turnover).
The PDPA does not prohibit data intermediaries from engaging sub-processors, but the controller organisation remains responsible for personal data processed by sub-processors. Best practice — and the PDPC's Advisory Guidelines — recommends that the DPA require the data intermediary to obtain the controller's prior written consent before engaging any sub-processor, impose equivalent data protection obligations on each sub-processor through a written sub-processing agreement, and remain liable to the controller for the sub-processor's performance. The controller should have the right to object to the appointment of a specific sub-processor and to audit the sub-processor's data protection practices. Where the sub-processor is located outside Singapore, sections 26 and 26A of the PDPA require the controller to take reasonable steps to verify that the sub-processor will protect the data to a standard comparable to the PDPA — the DPA should specify the approved countries for sub-processing and the transfer safeguards in place.
Under section 25 of the PDPA (retention limitation obligation), the data intermediary must cease retaining personal data when it is no longer necessary for the processing purpose. A well-drafted DPA specifies the data intermediary's obligations upon termination or expiry: return all personal data to the controller in a format specified by the controller (CSV, database export, encrypted archive); securely delete all copies of personal data, including backups, replicas, and data stored by sub-processors; provide written certification of deletion within a specified period (typically 30 to 90 days); and allow the controller to conduct a deletion audit if requested. The DPA should specify the deletion method — secure overwrite conforming to recognised standards (NIST SP 800-88), cryptographic erasure (destroying the encryption key), or physical destruction of storage media. Data that must be retained for legal or regulatory purposes (e.g., statutory record-keeping under the Companies Act 1967 or the Income Tax Act 1947) should be identified and excluded from the deletion obligation, with an agreed retention period.
This template is provided for informational purposes only and does not constitute legal advice. Laws vary by jurisdiction and change over time. Consult a qualified attorney for advice specific to your situation.Full disclaimer
Found an error? Let us knowRelated Documents
You may also find these documents useful:
Privacy Policy (Singapore)
A PDPA 2012-compliant privacy policy for businesses operating in Singapore. Addresses the Personal Data Protection Commission's (PDPC) nine data protection obligations, mandatory data breach notification under s.26D, consent requirements, purpose limitation, data retention, and the Do Not Call Registry provisions. Suitable for websites, apps, and physical businesses collecting personal data.
Data Protection Policy (Singapore)
An internal PDPA 2012 compliance policy for Singapore organisations covering the nine data protection obligations, DPO appointment and responsibilities, data inventory, consent management, breach response, and staff training requirements. Demonstrates the organisation's accountability to the PDPC and provides the internal governance framework for handling personal data responsibly.
Data Breach Notification (Singapore)
A mandatory data breach notification document for reporting notifiable data breaches to the Personal Data Protection Commission (PDPC) under Section 26D of the PDPA 2012. Covers breach assessment, notification thresholds (500 or more individuals or significant harm), 3-calendar-day reporting deadline, required content, and simultaneous notification to affected individuals.
Do Not Call Registry Compliance (Singapore)
A compliance documentation package for Singapore businesses required to check the Do Not Call (DNC) Registry before sending specified messages to Singapore telephone numbers under Part IX of the PDPA 2012. Covers DNC Registry checking obligations, consent exceptions, record-keeping requirements, and penalties for DNC violations enforced by the PDPC.
Terms of Service (Singapore)
Website and app terms of service governed by Singapore law for businesses offering digital services in Singapore. Covers user obligations, intellectual property, limitation of liability under the Unfair Contract Terms Act, dispute resolution, and compliance with the Electronic Transactions Act 2010 and Computer Misuse Act. Suitable for SaaS platforms, marketplaces, and content websites.