Why English? | Writing a Data Processing Agreement Through Parties, Roles, Instructions, Confidentiality, Security, Subprocessors, Assistance, Return, Deletion and Audit

ORIENTATION

What this guide covers

Current fact check

Checked on 8 November 2026, the PDPC's 1 February 2021 guide described written customer-contractor clauses for processing personal data and explained protection, retention and breach-notification responsibilities. PDPC's data-intermediary lifecycle material also covered governance, binding contractual arrangements, communication, monitoring and exit. The official sample is general guidance, not a substitute for adapting terms to the service and current law.

What this guide does not cover

This article owns the reader task of writing data-processing terms for a processor or data intermediary acting on documented instructions. It does not own the information-sharing agreement between independent parties, privacy notice, DPIA, master services agreement, cybersecurity design, breach assessment, cross-border legal analysis or final legal approval.

Worked example

Every chapter returns to a school engages a fictional platform company to host learner accounts, deliver exercises and return authorised usage reports without using the data for its own advertising. It is fictional, low-stakes and educational; it does not report a real school, clinical decision or guaranteed outcome.

Warm up with eduKate’s guides to explaining scientific evidence and asking better questions in class.

CHAPTER 1 OF 15

1. Identify the Parties and Contract Context

Back to contents

Why this move matters

Name the legal entities, service agreement, effective date, order of precedence, contacts and authorised signatories.

Follow one processing instruction

Name the legal entities, service agreement, effective date, order of precedence, contacts and authorised signatories. In the fictional arrangement, The school is the customer and the platform company supplies hosting and support under a named services agreement. Trace the instruction from agreed purpose to authorised access, system action, record, review and deletion.

Separate customer and processor responsibilities

Write who decides purposes, who acts only on documented instructions, who answers individuals, who assesses incidents and who proves completion. Do not let shared activity become shared ambiguity.

Turn safeguards into contract-operable actions

Connect confidentiality, security, subprocessors, transfers, assistance, audit, return and deletion to notice periods, evidence, contacts and escalation. Each promise needs an observable action.

Keep legal and operational judgement visible

A party label cannot change the factual role created by actual decisions and processing. Record assumptions, jurisdiction, professional review, conflicts with the main agreement and change triggers rather than treating sample clauses as automatic approval.

Student, parent and career transfer

Make one evidence card for “Identify the Parties and Contract Context”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports privacy, procurement, education technology, cybersecurity, vendor management, legal operations, data governance, audit and service leadership without promising a grade, admission, funding decision or job.

CHAPTER 2 OF 15

2. Describe the Services and Processing Operations

Back to contents

Why this move matters

List collection, recording, organisation, storage, retrieval, use, disclosure, alteration, export, backup and deletion activities.

Follow one processing instruction

List collection, recording, organisation, storage, retrieval, use, disclosure, alteration, export, backup and deletion activities. In the fictional arrangement, The provider creates accounts, stores submissions, generates progress views and handles support logs. Trace the instruction from agreed purpose to authorised access, system action, record, review and deletion.

Separate customer and processor responsibilities

Write who decides purposes, who acts only on documented instructions, who answers individuals, who assesses incidents and who proves completion. Do not let shared activity become shared ambiguity.

Turn safeguards into contract-operable actions

Connect confidentiality, security, subprocessors, transfers, assistance, audit, return and deletion to notice periods, evidence, contacts and escalation. Each promise needs an observable action.

Keep legal and operational judgement visible

A broad verb such as manage can hide materially different data operations. Record assumptions, jurisdiction, professional review, conflicts with the main agreement and change triggers rather than treating sample clauses as automatic approval.

Student, parent and career transfer

Make one evidence card for “Describe the Services and Processing Operations”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports privacy, procurement, education technology, cybersecurity, vendor management, legal operations, data governance, audit and service leadership without promising a grade, admission, funding decision or job.

CHAPTER 3 OF 15

3. Define Roles From Facts and Current Law

Back to contents

Why this move matters

Explain who determines purposes and essential means, who acts on whose instructions and when a party acts for itself.

Follow one processing instruction

Explain who determines purposes and essential means, who acts on whose instructions and when a party acts for itself. In the fictional arrangement, The school selects educational purposes while the provider follows documented hosting and support instructions. Trace the instruction from agreed purpose to authorised access, system action, record, review and deletion.

Separate customer and processor responsibilities

Write who decides purposes, who acts only on documented instructions, who answers individuals, who assesses incidents and who proves completion. Do not let shared activity become shared ambiguity.

Turn safeguards into contract-operable actions

Connect confidentiality, security, subprocessors, transfers, assistance, audit, return and deletion to notice periods, evidence, contacts and escalation. Each promise needs an observable action.

Keep legal and operational judgement visible

Contract wording alone does not settle a legal classification that depends on facts and law. Record assumptions, jurisdiction, professional review, conflicts with the main agreement and change triggers rather than treating sample clauses as automatic approval.

Student, parent and career transfer

Make one evidence card for “Define Roles From Facts and Current Law”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports privacy, procurement, education technology, cybersecurity, vendor management, legal operations, data governance, audit and service leadership without promising a grade, admission, funding decision or job.

CHAPTER 4 OF 15

4. List Data, People, Purposes and Duration

Back to contents

Why this move matters

Specify data categories, affected people, approved purposes, processing locations, start, review and end points.

Follow one processing instruction

Specify data categories, affected people, approved purposes, processing locations, start, review and end points. In the fictional arrangement, Account identifiers and submissions are allowed; advertising profiles and unrelated enrichment are outside scope. Trace the instruction from agreed purpose to authorised access, system action, record, review and deletion.

Separate customer and processor responsibilities

Write who decides purposes, who acts only on documented instructions, who answers individuals, who assesses incidents and who proves completion. Do not let shared activity become shared ambiguity.

Turn safeguards into contract-operable actions

Connect confidentiality, security, subprocessors, transfers, assistance, audit, return and deletion to notice periods, evidence, contacts and escalation. Each promise needs an observable action.

Keep legal and operational judgement visible

A category such as user data may be too vague for risk, access and deletion decisions. Record assumptions, jurisdiction, professional review, conflicts with the main agreement and change triggers rather than treating sample clauses as automatic approval.

Student, parent and career transfer

Make one evidence card for “List Data, People, Purposes and Duration”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports privacy, procurement, education technology, cybersecurity, vendor management, legal operations, data governance, audit and service leadership without promising a grade, admission, funding decision or job.

CHAPTER 5 OF 15

5. Write Documented Instructions and Change Control

Back to contents

Why this move matters

State the form, sender, recipient, validation, conflict handling, emergency route, cost and record for instructions.

Follow one processing instruction

State the form, sender, recipient, validation, conflict handling, emergency route, cost and record for instructions. In the fictional arrangement, Only named customer contacts can approve a new analytics field through the change process. Trace the instruction from agreed purpose to authorised access, system action, record, review and deletion.

Separate customer and processor responsibilities

Write who decides purposes, who acts only on documented instructions, who answers individuals, who assesses incidents and who proves completion. Do not let shared activity become shared ambiguity.

Turn safeguards into contract-operable actions

Connect confidentiality, security, subprocessors, transfers, assistance, audit, return and deletion to notice periods, evidence, contacts and escalation. Each promise needs an observable action.

Keep legal and operational judgement visible

An instruction should not require unlawful or technically impossible action. Record assumptions, jurisdiction, professional review, conflicts with the main agreement and change triggers rather than treating sample clauses as automatic approval.

Student, parent and career transfer

Make one evidence card for “Write Documented Instructions and Change Control”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports privacy, procurement, education technology, cybersecurity, vendor management, legal operations, data governance, audit and service leadership without promising a grade, admission, funding decision or job.

CHAPTER 6 OF 15

6. Control Confidentiality and Staff Access

Back to contents

Why this move matters

Define authorised roles, least privilege, confidentiality duties, training, joiner-mover-leaver controls and access reviews.

Follow one processing instruction

Define authorised roles, least privilege, confidentiality duties, training, joiner-mover-leaver controls and access reviews. In the fictional arrangement, Support staff receive time-limited access to a ticket's data and their activity is logged. Trace the instruction from agreed purpose to authorised access, system action, record, review and deletion.

Separate customer and processor responsibilities

Write who decides purposes, who acts only on documented instructions, who answers individuals, who assesses incidents and who proves completion. Do not let shared activity become shared ambiguity.

Turn safeguards into contract-operable actions

Connect confidentiality, security, subprocessors, transfers, assistance, audit, return and deletion to notice periods, evidence, contacts and escalation. Each promise needs an observable action.

Keep legal and operational judgement visible

A signed confidentiality promise does not replace access control or supervision. Record assumptions, jurisdiction, professional review, conflicts with the main agreement and change triggers rather than treating sample clauses as automatic approval.

Student, parent and career transfer

Make one evidence card for “Control Confidentiality and Staff Access”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports privacy, procurement, education technology, cybersecurity, vendor management, legal operations, data governance, audit and service leadership without promising a grade, admission, funding decision or job.

CHAPTER 7 OF 15

7. Specify Security Measures and Evidence

Back to contents

Why this move matters

Link risks to organisational and technical measures, testing, vulnerability handling, resilience, recovery and evidence.

Follow one processing instruction

Link risks to organisational and technical measures, testing, vulnerability handling, resilience, recovery and evidence. In the fictional arrangement, Encryption, strong authentication, logging, backup tests and access reviews have named owners and frequencies. Trace the instruction from agreed purpose to authorised access, system action, record, review and deletion.

Separate customer and processor responsibilities

Write who decides purposes, who acts only on documented instructions, who answers individuals, who assesses incidents and who proves completion. Do not let shared activity become shared ambiguity.

Turn safeguards into contract-operable actions

Connect confidentiality, security, subprocessors, transfers, assistance, audit, return and deletion to notice periods, evidence, contacts and escalation. Each promise needs an observable action.

Keep legal and operational judgement visible

The agreement should avoid freezing obsolete technology while still requiring measurable protection. Record assumptions, jurisdiction, professional review, conflicts with the main agreement and change triggers rather than treating sample clauses as automatic approval.

Student, parent and career transfer

Make one evidence card for “Specify Security Measures and Evidence”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports privacy, procurement, education technology, cybersecurity, vendor management, legal operations, data governance, audit and service leadership without promising a grade, admission, funding decision or job.

CHAPTER 8 OF 15

8. Govern Subprocessors and Supply Chains

Back to contents

Why this move matters

Define approval or notice, due diligence, equivalent obligations, location, change objections and continuing accountability.

Follow one processing instruction

Define approval or notice, due diligence, equivalent obligations, location, change objections and continuing accountability. In the fictional arrangement, The provider gives advance notice before replacing its cloud subprocessor and records the services and location. Trace the instruction from agreed purpose to authorised access, system action, record, review and deletion.

Separate customer and processor responsibilities

Write who decides purposes, who acts only on documented instructions, who answers individuals, who assesses incidents and who proves completion. Do not let shared activity become shared ambiguity.

Turn safeguards into contract-operable actions

Connect confidentiality, security, subprocessors, transfers, assistance, audit, return and deletion to notice periods, evidence, contacts and escalation. Each promise needs an observable action.

Keep legal and operational judgement visible

A subprocessor list does not by itself establish effective oversight. Record assumptions, jurisdiction, professional review, conflicts with the main agreement and change triggers rather than treating sample clauses as automatic approval.

Student, parent and career transfer

Make one evidence card for “Govern Subprocessors and Supply Chains”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports privacy, procurement, education technology, cybersecurity, vendor management, legal operations, data governance, audit and service leadership without promising a grade, admission, funding decision or job.

CHAPTER 9 OF 15

9. Coordinate Individual Requests and Complaints

Back to contents

Why this move matters

Set intake, identity verification, search, export, correction, restriction, deadlines, costs and secure response channels.

Follow one processing instruction

Set intake, identity verification, search, export, correction, restriction, deadlines, costs and secure response channels. In the fictional arrangement, The provider searches the account and support systems while the school decides and communicates the response. Trace the instruction from agreed purpose to authorised access, system action, record, review and deletion.

Separate customer and processor responsibilities

Write who decides purposes, who acts only on documented instructions, who answers individuals, who assesses incidents and who proves completion. Do not let shared activity become shared ambiguity.

Turn safeguards into contract-operable actions

Connect confidentiality, security, subprocessors, transfers, assistance, audit, return and deletion to notice periods, evidence, contacts and escalation. Each promise needs an observable action.

Keep legal and operational judgement visible

The responsible party and deadline depend on current law and the actual request. Record assumptions, jurisdiction, professional review, conflicts with the main agreement and change triggers rather than treating sample clauses as automatic approval.

Student, parent and career transfer

Make one evidence card for “Coordinate Individual Requests and Complaints”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports privacy, procurement, education technology, cybersecurity, vendor management, legal operations, data governance, audit and service leadership without promising a grade, admission, funding decision or job.

CHAPTER 10 OF 15

10. Manage Incidents and Breach Notifications

Back to contents

Why this move matters

Define event thresholds, immediate containment, without-undue-delay notice, facts, updates, assessment support and communications control.

Follow one processing instruction

Define event thresholds, immediate containment, without-undue-delay notice, facts, updates, assessment support and communications control. In the fictional arrangement, The provider reports suspected unauthorised access with known systems, times, data, containment and next update. Trace the instruction from agreed purpose to authorised access, system action, record, review and deletion.

Separate customer and processor responsibilities

Write who decides purposes, who acts only on documented instructions, who answers individuals, who assesses incidents and who proves completion. Do not let shared activity become shared ambiguity.

Turn safeguards into contract-operable actions

Connect confidentiality, security, subprocessors, transfers, assistance, audit, return and deletion to notice periods, evidence, contacts and escalation. Each promise needs an observable action.

Keep legal and operational judgement visible

Early notices should label uncertainty rather than delay until every fact is known. Record assumptions, jurisdiction, professional review, conflicts with the main agreement and change triggers rather than treating sample clauses as automatic approval.

Student, parent and career transfer

Make one evidence card for “Manage Incidents and Breach Notifications”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports privacy, procurement, education technology, cybersecurity, vendor management, legal operations, data governance, audit and service leadership without promising a grade, admission, funding decision or job.

CHAPTER 11 OF 15

11. Address Transfers and Processing Locations

Back to contents

Why this move matters

Record hosting, remote access, support locations, approved transfers, safeguards, changes and verification.

Follow one processing instruction

Record hosting, remote access, support locations, approved transfers, safeguards, changes and verification. In the fictional arrangement, A support team outside Singapore may access limited logs only through the approved arrangement. Trace the instruction from agreed purpose to authorised access, system action, record, review and deletion.

Separate customer and processor responsibilities

Write who decides purposes, who acts only on documented instructions, who answers individuals, who assesses incidents and who proves completion. Do not let shared activity become shared ambiguity.

Turn safeguards into contract-operable actions

Connect confidentiality, security, subprocessors, transfers, assistance, audit, return and deletion to notice periods, evidence, contacts and escalation. Each promise needs an observable action.

Keep legal and operational judgement visible

A server address alone may not describe remote access, backups or onward processing. Record assumptions, jurisdiction, professional review, conflicts with the main agreement and change triggers rather than treating sample clauses as automatic approval.

Student, parent and career transfer

Make one evidence card for “Address Transfers and Processing Locations”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports privacy, procurement, education technology, cybersecurity, vendor management, legal operations, data governance, audit and service leadership without promising a grade, admission, funding decision or job.

CHAPTER 12 OF 15

12. Provide Audit, Information and Assurance Rights

Back to contents

Why this move matters

Define questionnaires, certifications, reports, records, inspections, frequency, notice, confidentiality, findings and remediation.

Follow one processing instruction

Define questionnaires, certifications, reports, records, inspections, frequency, notice, confidentiality, findings and remediation. In the fictional arrangement, The customer receives current assurance evidence and can escalate a material gap to a scoped audit. Trace the instruction from agreed purpose to authorised access, system action, record, review and deletion.

Separate customer and processor responsibilities

Write who decides purposes, who acts only on documented instructions, who answers individuals, who assesses incidents and who proves completion. Do not let shared activity become shared ambiguity.

Turn safeguards into contract-operable actions

Connect confidentiality, security, subprocessors, transfers, assistance, audit, return and deletion to notice periods, evidence, contacts and escalation. Each promise needs an observable action.

Keep legal and operational judgement visible

Unlimited audit language may be impractical, but evidence cannot be reduced to trust us. Record assumptions, jurisdiction, professional review, conflicts with the main agreement and change triggers rather than treating sample clauses as automatic approval.

Student, parent and career transfer

Make one evidence card for “Provide Audit, Information and Assurance Rights”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports privacy, procurement, education technology, cybersecurity, vendor management, legal operations, data governance, audit and service leadership without promising a grade, admission, funding decision or job.

CHAPTER 13 OF 15

13. Plan Return, Deletion and Exit

Back to contents

Why this move matters

Set formats, timelines, migration help, backup handling, legal holds, deletion evidence, residual access and service continuity.

Follow one processing instruction

Set formats, timelines, migration help, backup handling, legal holds, deletion evidence, residual access and service continuity. In the fictional arrangement, The provider exports learner records, removes active copies and documents backup expiry after termination. Trace the instruction from agreed purpose to authorised access, system action, record, review and deletion.

Separate customer and processor responsibilities

Write who decides purposes, who acts only on documented instructions, who answers individuals, who assesses incidents and who proves completion. Do not let shared activity become shared ambiguity.

Turn safeguards into contract-operable actions

Connect confidentiality, security, subprocessors, transfers, assistance, audit, return and deletion to notice periods, evidence, contacts and escalation. Each promise needs an observable action.

Keep legal and operational judgement visible

Immediate physical erasure from every backup may conflict with tested recovery designs and lawful retention. Record assumptions, jurisdiction, professional review, conflicts with the main agreement and change triggers rather than treating sample clauses as automatic approval.

Student, parent and career transfer

Make one evidence card for “Plan Return, Deletion and Exit”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports privacy, procurement, education technology, cybersecurity, vendor management, legal operations, data governance, audit and service leadership without promising a grade, admission, funding decision or job.

CHAPTER 14 OF 15

14. Handle Liability, Remedies and Surviving Duties

Back to contents

Why this move matters

Connect the schedule to indemnities, limits, insurance, suspension, confidentiality, records, cooperation and post-termination duties.

Follow one processing instruction

Connect the schedule to indemnities, limits, insurance, suspension, confidentiality, records, cooperation and post-termination duties. In the fictional arrangement, Confidentiality and incident cooperation continue for retained backup data after service end. Trace the instruction from agreed purpose to authorised access, system action, record, review and deletion.

Separate customer and processor responsibilities

Write who decides purposes, who acts only on documented instructions, who answers individuals, who assesses incidents and who proves completion. Do not let shared activity become shared ambiguity.

Turn safeguards into contract-operable actions

Connect confidentiality, security, subprocessors, transfers, assistance, audit, return and deletion to notice periods, evidence, contacts and escalation. Each promise needs an observable action.

Keep legal and operational judgement visible

Remedies require commercial and legal approval and should not be invented by a writing guide. Record assumptions, jurisdiction, professional review, conflicts with the main agreement and change triggers rather than treating sample clauses as automatic approval.

Student, parent and career transfer

Make one evidence card for “Handle Liability, Remedies and Surviving Duties”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports privacy, procurement, education technology, cybersecurity, vendor management, legal operations, data governance, audit and service leadership without promising a grade, admission, funding decision or job.

CHAPTER 15 OF 15

15. Review the Agreement Against Reality

Back to contents

Why this move matters

Set reviews for new purposes, technologies, locations, subprocessors, law, incidents, audits, service changes and renewals.

Follow one processing instruction

Set reviews for new purposes, technologies, locations, subprocessors, law, incidents, audits, service changes and renewals. In the fictional arrangement, A proposed AI feature pauses until instructions, role, data and safeguards are reassessed. Trace the instruction from agreed purpose to authorised access, system action, record, review and deletion.

Separate customer and processor responsibilities

Write who decides purposes, who acts only on documented instructions, who answers individuals, who assesses incidents and who proves completion. Do not let shared activity become shared ambiguity.

Turn safeguards into contract-operable actions

Connect confidentiality, security, subprocessors, transfers, assistance, audit, return and deletion to notice periods, evidence, contacts and escalation. Each promise needs an observable action.

Keep legal and operational judgement visible

An annual review is not enough if a material change occurs first. Record assumptions, jurisdiction, professional review, conflicts with the main agreement and change triggers rather than treating sample clauses as automatic approval.

Student, parent and career transfer

Make one evidence card for “Review the Agreement Against Reality”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports privacy, procurement, education technology, cybersecurity, vendor management, legal operations, data governance, audit and service leadership without promising a grade, admission, funding decision or job.

PRACTICE LAB

Build a data processing agreement decision trail

Student route

1. Choose one original report inside this guide’s scope.
2. Copy its objective and underline actor, action, context, evidence and intended decision.
3. Draw the specific reasoning chain used in this article.
4. Mark each step reported, inferred, contested or unknown.
5. Rewrite the conclusion so it preserves the narrowest important limitation.

Parent or teacher route

Ask the learner to explain turn outsourced personal-data processing into clear instructions, allocated responsibilities, testable safeguards, workable assistance and a controlled exit twice: once to a classmate and once to a method specialist. Praise a precise correction and a well-stated unknown; both show disciplined attention to evidence.

Early-career route

Create a one-page data processing agreement audit with source link, date checked, scope, method logic, decisive wording, contrary evidence, limit and next action. A colleague should be able to continue without guessing.

Continue with eduKate’s guides to reading course and career information and giving useful feedback in group projects.

USEFUL NEXT READING

Connect this narrow owner to its neighbour

Read the information-sharing-agreement guide for a related but different reader job. Return here when the question is specifically how to turn outsourced personal-data processing into clear instructions, allocated responsibilities, testable safeguards, workable assistance and a controlled exit. Use each guide for the reader task named in its heading.

For English practice across research, school and career communication, visit the Singapore English Tuition Centre learning site.

FREQUENTLY ASKED QUESTIONS

Questions students and parents often ask

Is a data processing agreement the same as an information sharing agreement?

No. A processing agreement focuses on processing on another party's instructions; an information-sharing agreement may govern disclosure between parties with their own purposes.

Can we copy the PDPC sample clauses unchanged?

They are general reference and should be adapted to the actual service, facts and current law.

Does calling a supplier a processor settle its legal role?

No. Roles depend on actual activities and applicable law.

Should security controls be listed?

Describe sufficient, reviewable measures and evidence while allowing authorised improvement as threats and technology change.

What should happen after termination?

Plan return, migration, deletion, backups, legal holds, evidence and surviving duties.

Does this article provide legal advice?

No. Real agreements need current legal, privacy, security, procurement and operational review.