Powered by
The UU PDP wiki
Salinan v5.8 · 28 Sep 2026
BAB VIKEWAJIBAN PENGENDALI DATA PRIBADI DAN PROSESOR DATA PRIBADI DALAM PEMROSESAN DATA PRIBADI

Pasal 52 UU PDP

Processor obligations

sanctioned by Pasal 57 ayat (1)

1Legal text

Pasal 52

Ketentuan mengenai kewajiban Pengendali Data Pribadi sebagaimana dimaksud dalam Pasal 29, Pasal 31, Pasal 35, Pasal 36, Pasal 37, Pasal 38, dan Pasal 39 berlaku juga terhadap Prosesor Data Pribadi.

Official copy: salinan p. 21

2Implementing regulation

Implemented by PP 33/2026 Pasal 139 to 141.

PP Pasal 139Dalam hal Pengendali Data Pribadi menunjuk Prosesor Data…sanction list
(1)
Dalam hal Pengendali Data Pribadi menunjuk Prosesor Data Pribadi, Prosesor Data Pribadi wajib melakukan pemrosesan Data Pribadi berdasarkan perintah Pengendali Data Pribadi.
(2)
Kewajiban melakukan pemrosesan Data Pribadi berdasarkan perintah Pengendali Data Pribadi sebagaimana dimaksud pada ayat (1) harus terdokumentasi dan dilaksanakan sesuai perjanjian antara Prosesor Data Pribadi dan Pengendali Data Pribadi.
(3)
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.

Read it in the regulationsalinan p. 69

PP Pasal 140Ketentuan mengenai kewajiban Pengendali Data Pribadi…sanction list
repeats UU Pasal 52

Ketentuan mengenai kewajiban Pengendali Data Pribadi sebagaimana dimaksud dalam Pasal 69, Pasal 74, Pasal 123, Pasal 125, Pasal 126, Pasal 129, dan Pasal 130 berlaku juga terhadap Prosesor Data Pribadi.

Read it in the regulationsalinan p. 70

PP Pasal 141Prosesor Data Pribadi harus bertanggung jawab atas pemrosesan…
(1)
Prosesor Data Pribadi harus bertanggung jawab atas pemrosesan Data Pribadi dan menunjukkan pertanggungjawaban dalam pemenuhan kewajiban sesuai dengan ketentuan peraturan perundang-undangan.
(2)
Dalam melaksanakan pertanggungjawaban sebagaimana dimaksud pada ayat (1), Prosesor Data Pribadi harus:
  1. a.
    mendokumentasikan seluruh kegiatan pemrosesan Data Pribadi;
  2. b.
    merespons permintaan Informasi dari Lembaga;
  3. c.
    menunjukkan pemenuhan kepatuhan dan bukti dokumentasi seluruh kegiatan pemrosesan Data Pribadi; dan
  4. d.
    melakukan audit.

Read it in the regulationsalinan p. 70

3Commentary

3.1How the regulation implements it

PP Pasal 139 to 141 require the processor to act only on the controller's instruction, carry over specified controller duties at Pasal 140 and require demonstrable responsibility at Pasal 141. Pasal 139(1) and Pasal 140 are both sanction-backed, so the processor is directly exposed rather than exposed only through its contract.

3.2Where the GDPR stands

aligned with the GDPRGDPR Articles 28, 29, 30, 32 and 33

What the GDPR provides. The GDPR does not switch controller duties onto processors in a single clause. It names the processor inside each article that binds it: Article 29 and Article 28(3)(a) confine it to the controller's documented instructions, Article 30(2) gives it its own record of processing activities, Article 32 imposes security on controller and processor alike, and Article 33(2) requires it to notify the controller of a breach without undue delay.

Those duties bind directly, and Article 83(4)(a) exposes the processor to fines for breaching them regardless of what its contract says. Duties the GDPR keeps with the controller, such as lawful basis, transparency and answering data subject requests, never transfer; the processor only assists under Article 28(3)(e) and (f).

The destination is close and the route is not. UU Pasal 52 is one cross-reference clause switching a fixed block of controller duties onto the processor: accuracy and verification at UU Pasal 29, records of processing at UU Pasal 31, security at UU Pasal 35, confidentiality at UU Pasal 36, supervision of every party involved at UU Pasal 37, and protection against unlawful processing and unauthorised access at UU Pasal 38 and UU Pasal 39.

UU Pasal 57 ayat (1) lists Pasal 52 by number, so the block is sanction-backed and the Indonesian processor answers to the regulator and not only to its customer, which is the same exposure Article 83(4)(a) creates in the EU.

PP Pasal 140 repeats the cross-reference against the PP's own numbering, and PP Pasal 141 adds a free-standing accountability duty covering documentation, responses to the Lembaga, evidence of compliance and audits, which the GDPR asks of the controller under Article 5(2) and Article 24 and not of the processor. Two limbs do not line up.

UU Pasal 29 puts accuracy, completeness, consistency and verification on the processor, where the accuracy principle in the EU stays with the controller. And the block carries no breach duty at all: the counterpart to Article 33(2) is PP Pasal 118, which requires the processor to report a breach to the controller at the first opportunity, sits outside UU Pasal 52, and is absent from the PP Pasal 184 sanctions list.

The article-by-article technique has one property the cross-reference cannot reproduce: the EU list maintains itself, because whether a duty reaches the processor is settled inside the duty itself, where UU Pasal 52 fixes the answer as a list of article numbers that has to be amended whenever the substantive articles move. The other difference is at the boundary of obedience.

The closing subparagraph of Article 28(3), attached to point (h), obliges the processor to tell the controller at once if, in its opinion, an instruction infringes the law, and Article 28(10) states the consequence of going further, so acting on instructions is a defence with a stated limit.

UU Pasal 52 imports duties but not that exchange, and the nearest equivalent sits back at UU Pasal 51 ayat (6), which reallocates responsibility after the event rather than requiring the processor to raise the objection before it acts.

4Decisions and guidance

National supervisory authorities

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 150 decisions

The DPO tags 150 national decisions since 25 May 2018, from 19 countries, as citing Article 28(3) and 28(10); most come from Latvia (65), Poland (12) and Italy (11). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.

  • Decision of 28 July 2026Greece, HDPA
  • DKN.5131.12.2022Poland, UODO11 June 2026
  • 10281706Italy, Garante per la protezione dei dati personaliAcquirente Unico S.p.A.18 June 2026
  • 102/2026Belgium, Gegevensbeschermingsautoriteit12 May 2026Under appeal to the Market Court, as the authority's copy said on 27 September 2026.
  • DecisionGermany, BlnBDIBerliner Verkehrsbetriebe (BVG)2026
Article 29 GDPRProcessing under the authority of the controller or processor3 of 59 decisions

The DPO tags 59 national decisions since 25 May 2018, from 14 countries, as citing Article 29; most come from Romania (12), Greece (10) and Lithuania (9). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.

  • DecisionRomania, ANSPDCP2026 · fine EUR 2,000
  • 10266338Italy, Garante per la protezione dei dati personali11 June 2026 · fine EUR 4,500
  • DKN.5112.13.2023Poland, UODO27 February 2026 · fine EUR 232
Article 30 GDPRRecords of processing activities5 of 102 decisions

The DPO tags 102 national decisions since 25 May 2018, from 20 countries, as citing Article 30; most come from Belgium (30), France (21) and Greece (8). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.

Article 32 GDPRSecurity of processing5 of 931 decisions

The DPO tags 931 national decisions since 25 May 2018, from 29 countries, as citing Article 32; most come from Denmark (155), Romania (152) and Latvia (70). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.

  • 10297203Italy, Garante per la protezione dei dati personali3 September 2026
  • DecisionRomania, ANSPDCP2026 · fine EUR 5,000
  • DKN.5131.5.2025Poland, UODO25 May 2026
  • DecisionIreland, Data Protection Commission2026 · fine EUR 300,000
  • DecisionGermany, BlnBDIBerliner Verkehrsbetriebe (BVG)2026
Article 33 GDPRNotification of a personal data breach to the supervisory authority5 of 284 decisions

The DPO tags 284 national decisions since 25 May 2018, from 25 countries, as citing Article 33; most come from Denmark (44), Poland (43) and Latvia (32). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.

  • DKN.5131.27.2023Poland, UODO19 May 2026
  • 10268672Italy, Garante per la protezione dei dati personali18 June 2026 · fine EUR 2,075
  • DecisionRomania, ANSPDCP2026
  • 102/2026Belgium, Gegevensbeschermingsautoriteit12 May 2026Under appeal to the Market Court, as the authority's copy said on 27 September 2026.
  • DecisionIreland, Data Protection Commission2026

Cited on GDPRhub

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 32 GDPRSecurity of processing2 judgments · 1 EDPB document

Cited in its whole commentary on Article 32. Read it on GDPRhub

Article 33 GDPRNotification of a personal data breach to the supervisory authority1 EDPB document

Cited in its commentary on Article 33(2). Read it on GDPRhub

The Lembaga. No decision of the Lembaga exists, because it has not been established (CNBC Indonesia, 16 September 2026).

5Cross-references

Referred to by

Refers to

  • Pasal 29Accuracy and verificationthe article
  • Pasal 31Records of processing activitiesthe article
  • Pasal 35Security of personal datathe article
  • Pasal 36Duty of confidentialitythe article
  • Pasal 37Supervision of processing partiesthe article
  • Pasal 38Protection from unlawful processingthe article
  • Pasal 39Prevention of unauthorised accessthe article

6Sources

  1. 1UU 27/2022, salinan, p. 21.
  2. 2PP 33/2026, salinan: Pasal 139 to 141 at pp. 69 to 70.
  3. 3EDPB, Guidelines 07/2020 on the concepts of controller and processor in the GDPR. EDPB.
  4. 4GDPRhub (noyb), commentary on Article 28 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.
  5. 5GDPRhub (noyb), commentary on Article 29 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.
  6. 6GDPRhub (noyb), commentary on Article 30 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.
  7. 7GDPRhub (noyb), commentary on Article 32 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.
  8. 8GDPRhub (noyb), commentary on Article 33 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.