Data Processing Agreement
Version 2.0 (12 November 2026), effective 12 November 2026.
This agreement forms part of the Sterling Academy terms for organisations and of every order an organisation places for Sterling Academy. It sets out how Sterling processes personal data on the organisation's behalf. It applies under every data protection law that covers the processing, including:
- the EU General Data Protection Regulation (GDPR) and the UK GDPR;
- the UAE Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data;
- the Philippine Data Privacy Act of 2012;
- India's Digital Personal Data Protection Act, 2023.
It also applies under Saudi Arabia's Personal Data Protection Law and under any other data protection law that covers the organisation's learners. A reference to a "data protection law" means each of these, as amended or replaced.
1. Roles. The organisation is the controller (in India, the data fiduciary). Sterling is the processor (in India, the data processor). Sterling processes the personal data only to provide Sterling Academy to the organisation, as described in Annex 1.
2. Instructions. Sterling processes the personal data only on the organisation's documented instructions. These terms, the order and the organisation's use of the client console are those instructions. If Sterling believes an instruction breaks the law, it tells the organisation. If the law requires Sterling to process data in another way, it tells the organisation first, unless the law forbids that.
3. Confidentiality. Everyone at Sterling who can access the personal data is bound by confidentiality and is trained in data protection.
4. Security. Sterling keeps appropriate technical and organisational measures to protect the personal data. Annex 2 lists them. Sterling may improve these measures, but will not reduce the overall level of protection.
5. Sub-processors. The organisation authorises Sterling to use the sub-processors on the sub-processor list, including Sterling group companies that support the organisation's account. Sterling gives notice of a new sub-processor at least 30 days before it starts, by updating the list and e-mailing the organisation's client administrators. The organisation may object on reasonable data protection grounds within that period. If the parties cannot agree, the organisation may end the affected order and receive a refund of unused places. Sterling binds each sub-processor to data protection terms at least as protective as these, and remains responsible for it.
6. Transfers outside the country. Learner records are hosted in the United Arab Emirates. Some sub-processors work in other countries (see the list). Where the law requires a transfer safeguard, Sterling uses the one the law recognises. For personal data transferred from the European Economic Area, the European Commission's Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914) apply: module 2 (controller to processor) between the organisation and Sterling, and module 3 (processor to processor) between Sterling and its sub-processors. For the United Kingdom, the UK International Data Transfer Addendum to those clauses applies. For the UAE, Saudi Arabia, the Philippines, India and other countries, Sterling uses the safeguards their law requires. The clauses are incorporated by reference, and Sterling provides a completed, signed copy on request.
7. Helping the organisation. Sterling helps the organisation, as far as it reasonably can:
- to answer learners who exercise their rights (access, correction, deletion, restriction, objection, portability). A request sent to Sterling directly is passed to the organisation, and Sterling does not answer it on its own;
- with data protection impact assessments and consultations with regulators that concern Sterling Academy;
- to meet its own security and breach obligations.
8. Personal data breaches. Sterling tells the organisation without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting its data. The notice describes, as far as known: what happened, the data and learners affected, the likely consequences, and what Sterling has done and will do. Sterling updates the organisation as it learns more, and does not notify learners or regulators about the organisation's data without the organisation's agreement, unless the law requires it.
9. Return and deletion. During the order, the organisation can ask Sterling for a copy of its training records, in a common electronic format. When the organisation's account closes, Sterling deletes or returns the personal data as the organisation instructs. Without an instruction, Sterling deletes it 36 months after the account closes, as the privacy notice states. Two kinds of record are kept longer. First, invoices and purchase records, for as long as tax law requires. Second, the certificate register (certificate number, learner name, course and date), which Sterling keeps as controller so that anyone can verify a certificate for as long as it may be relied on.
10. Audits. Sterling makes available the information needed to show it meets this agreement. That includes its security page, its ISO/IEC 27001 certification for its UAE, India and Philippines offices, and written answers to reasonable security questionnaires. The organisation, or an independent auditor it appoints under confidentiality, may audit Sterling's compliance once a year, on 30 days' written notice, during business hours, at its own cost. It may audit more often after a personal data breach or at a regulator's request.
11. Liability. Each party's liability under this agreement is subject to clause 15 of the Sterling Academy terms for organisations, including its separate limit for breach of this agreement.
12. Term. This agreement lasts as long as Sterling processes personal data for the organisation.
Annex 1: Details of the processing
| Item | Details |
|---|---|
| Subject matter | Online training: course access, progress tracking, final exams and certificates of completion |
| Duration | The order period, plus the retention period in clause 9 |
| Purposes | Give learners access; track progress; run and mark the final exam; issue and verify certificates; report progress to the organisation's client administrators; send sign-in and course e-mails |
| Learners covered | The organisation's employees, contractors and other people it enrols, and its client administrators |
| Personal data | Name and e-mail address; if provided, employee number, department and site; courses assigned; modules played and when; practice answers; final exam answers, result and dates; certificate number; sign-in time, internet address and browser |
| Sensitive data | None needed. The organisation should not upload sensitive data in learner fields. |
| Where hosted | United Arab Emirates (Microsoft Azure) |
Annex 2: Security measures
The measures on the security page form this annex, in the version that applies on the date of the order.
Annex 3: Sub-processors
The sub-processor list forms this annex. Clause 5 explains how it changes.