Dalam hal Pengendali Data Pribadi menunjuk Prosesor Data Pribadi, Prosesor Data Pribadi wajib melakukan pemrosesan Data Pribadi berdasarkan perintah Pengendali Data Pribadi.
Prosesor Data Pribadi wajib mendapatkan persetujuan tertulis dari Pengendali Data Pribadi sebelum melibatkan Prosesor Data Pribadi lain sebagaimana dimaksud pada ayat (4).
Dalam hal Prosesor Data Pribadi melakukan pemrosesan Data Pribadi di luar perintah dan tujuan yang ditetapkan Pengendali Data Pribadi, pemrosesan Data Pribadi menjadi tanggung jawab Prosesor Data Pribadi.
PP Pasal 13Pengendali Data Pribadi dapat menunjuk Prosesor Data Pribadi.…
(1)
Pengendali Data Pribadi dapat menunjuk Prosesor Data Pribadi.
(2)
Prosesor Data Pribadi harus melakukan pemrosesan Data Pribadi sesuai dengan ketentuan dalam Peraturan Pemerintah ini.
(3)
Pemrosesan Data Pribadi oleh Prosesor Data Pribadi yang ditunjuk oleh Pengendali Data Pribadi sebagaimana dimaksud pada ayat (1) merupakan tanggung jawab Pengendali Data Pribadi.
PP Pasal 15Prosesor Data Pribadi dapat melibatkan Prosesor Data Pribadi…sanction list
(1)
Prosesor Data Pribadi dapat melibatkan Prosesor Data Pribadi lain dalam melakukan pemrosesan Data Pribadi.
(2)
Prosesor Data Pribadi wajib mendapatkan persetujuan tertulis dari Pengendali Data Pribadi sebelum melibatkan Prosesor Data Pribadi lain.
(3)
Prosesor Data Pribadi sebagaimana dimaksud pada ayat (1) harus memastikan Prosesor Data Pribadi lain yang dilibatkan melakukan pemrosesan Data Pribadi sesuai dengan ketentuan dalam Peraturan Pemerintah ini.
(4)
Penunjukan Prosesor Data Pribadi lain oleh Prosesor Data Pribadi diatur dalam perjanjian tertulis dengan memperhatikan tingkat Pelindungan Data Pribadi yang setara sesuai yang disepakati dalam perjanjian antara Pengendali Data Pribadi dan Prosesor Data Pribadi.
(5)
Pemrosesan Data Pribadi oleh Prosesor Data Pribadi lain merupakan tanggung jawab Pengendali Data Pribadi.
PP Pasal 16Pengendali Data Pribadi Bersama dapat menunjuk Prosesor Data…
(1)
Pengendali Data Pribadi Bersama dapat menunjuk Prosesor Data Pribadi.
(2)
Ketentuan mengenai penunjukan Prosesor Data Pribadi oleh Pengendali Data Pribadi sebagaimana dimaksud dalam Pasal 13 dan Pasal 14 berlaku secara mutatis mutandis terhadap penunjukan Prosesor Data Pribadi oleh Pengendali Data Pribadi Bersama.
PP Pasal 13 to 16 require appointment of a processor by written agreement at Pasal 14 and permit sub-processors only with prior written approval at Pasal 15, sanction-backed at Pasal 15(2). The approval requirement is the operative control, because it is what prevents a processing chain from extending beyond the controller's knowledge.
What the GDPR provides.GDPR Article 28(1) lets a controller use only processors that provide sufficient guarantees of appropriate technical and organisational measures. Article 28(3) requires a contract or other legal act binding the processor to the controller and fixes what it must contain, starting with processing only on documented instructions.
Article 28(2) bars the processor from engaging another processor without prior written authorisation, specific or general, and where the authorisation is general the processor must give notice of intended changes so the controller can object. Article 28(4) keeps the first processor fully liable to the controller for the sub-processor's performance, and Article 28(10) turns a processor that determines purposes and means into a controller for that processing.
UU Pasal 51 reaches the same allocation of responsibility, then parts company with Article 28 on two mechanisms. Ayat (6) sits where Article 28(10) sits: responsibility moves to the processor once it processes outside the order and the stated purpose, while ayat (3) keeps instructed processing inside the controller's responsibility.
The GDPR gets there by a change of status, which drags the whole controller regime along with it, including the need for the processor to hold its own lawful basis under Article 6(1). UU Pasal 51 ayat (6) shifts responsibility without saying what the processor then is. On sub-processing the two texts split over liability rather than over consent.
Article 28(2) permits a general written authorisation with a right to object, which is what makes multi-tier cloud chains workable in the EU. Neither UU Pasal 51 ayat (5) nor PP Pasal 15 ayat (2) says whether a standing authorisation counts, so that question is open in Indonesia rather than closed against it.
The liability split is real: Article 28(4) keeps the first processor fully liable to the controller for the sub-processor's performance, while PP Pasal 15 ayat (5) puts processing by the sub-processor back on the controller. The chain is not otherwise unguarded.
UU Pasal 37, applied to the processor by UU Pasal 52 and sanction-backed through UU Pasal 57 ayat (1), requires supervision of every party involved in processing under its control, and PP Pasal 15 ayat (3) and ayat (4) require the first processor to ensure the sub-processor complies and to fix an equivalent level of protection by written agreement.
What has no Indonesian counterpart is the selection standard at Article 28(1) and the mandatory contract content at Article 28(3): PP Pasal 15 ayat (4) and PP Pasal 139 ayat (2) require a written agreement but do not fix what it must say.
4Decisions and guidance
Court of Justice of the EU
C-683/21Nacionalinis visuomenės sveikatos centras prie Sveikatos apsaugos ministerijos v Valstybinė duomenų apsaugos inspekcija5 December 2023
C-807/21Deutsche Wohnen SE v Staatsanwaltschaft Berlin5 December 2023
Decisions of national data protection authorities on the same GDPR provisions, found through The DPO (thedpo.eu), an index of European enforcement decisions, and linked to the authority's own copy. A reference, a date or a fine is shown only where that copy states it. The DPO's summaries are machine-written and none is used here.
Article 28 GDPRProcessor5 of 169 decisions
The DPO tags 169 national decisions since 25 May 2018, from 19 countries, as citing Article 28(1), 28(2), 28(3), 28(4) and 28(10); most come from Latvia (65), Poland (16) and Italy (14). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.
What GDPRhub's commentary on the same GDPR provisions cites, less what is listed above, each linked to the official copy. It is further reading: the commentary on this page does not rest on it.
Article 28 GDPRProcessor1 EDPB document
Cited in its commentary on Article 28(1), 28(2), 28(3), 28(4) and 28(10). Read it on GDPRhub
2PP 33/2026, salinan: Pasal 13 to 16 at pp. 11 to 13.
3Case C-683/21 Nacionalinis visuomenės sveikatos centras prie Sveikatos apsaugos ministerijos v Valstybinė duomenų apsaugos inspekcija, 5 December 2023, ECLI:EU:C:2023:949. EUR-Lex.
4Case C-807/21 Deutsche Wohnen SE v Staatsanwaltschaft Berlin, 5 December 2023, ECLI:EU:C:2023:950. EUR-Lex.
5EDPB, Guidelines 07/2020 on the concepts of controller and processor in the GDPR. EDPB.
6GDPRhub (noyb), commentary on Article 28 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.