Processor obligations
Pasal 52
Official copy: salinan p. 21
Implemented by PP 33/2026 Pasal 139 to 141.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cited in its whole commentary on Article 32. Read it on GDPRhub
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).