Appointing a PPDP
Pasal 53
Official copy: salinan p. 22
Yang dimaksud dengan "pejabat atau petugas yang melaksanakan fungsi Pelindungan Data Pribadi" adalah pejabat atau petugas yang bertanggung jawab untuk memastikan pemenuhan kepatuhan atas prinsip Pelindungan Data Pribadi dan mitigasi risiko pelanggaran Pelindungan Data Pribadi.
Implemented by PP 33/2026 Pasal 142 to 144.
PP Pasal 142 to 144 require appointment of a PPDP where the statutory triggers are met, set professional criteria at Pasal 143 and fix the timing at Pasal 144, sanction-backed at Pasal 142(1). The triggers are alternative, not cumulative: Putusan 151/PUU-XXII/20244 requires the dan closing huruf b to be read dan/atau, and PP Pasal 142(1) writes that reading into the implementing text.
The criteria at Pasal 143 are what will determine whether the role can be filled from within an existing compliance function.
ported from the GDPRGDPR Article 37
What the GDPR provides. GDPR Article 37(1) requires a controller or processor to designate a data protection officer in three cases. The first is processing carried out by a public authority or body, courts acting in a judicial capacity excepted. The second is core activities that by their nature, scope or purposes require regular and systematic monitoring of data subjects on a large scale.
The third is core activities consisting of large-scale processing of special categories under Article 9 and of criminal conviction and offence data under Article 10. The three cases are alternatives, and each names the processor as well as the controller. Article 37(5) sets the selection standard: professional qualities, in particular expert knowledge of data protection law and practice, and the ability to fulfil the Article 39 tasks.
Article 37(6) allows a staff member or a service contract, Article 37(2) allows a group of undertakings to share one officer who is easily accessible from each establishment, and Article 37(7) requires the contact details to be published and given to the supervisory authority.
The tracking is limb for limb: UU Pasal 53 ayat (1) huruf b carries the Article 37(1)(b) formula intact, with kegiatan inti and sifat, ruang lingkup, dan/atau tujuan sitting where core activities and nature, scope and/or purposes sit, huruf c carries Article 37(1)(c) down to the criminal offence category, ayat (2) follows Article 37(5) in the same order and ayat (3) is Article 37(6).
Huruf a is the first departure, because it triggers on processing for public services rather than on the identity of a public authority, so it reaches private operators running public service functions that Article 37(1)(a) would not touch, and it drops the exclusion of courts acting judicially.
The chapeau addresses controller and processor together, as Article 37(1) does, but huruf b and huruf c then speak only of kegiatan inti Pengendali Data Pribadi, so on the face of the text a processor whose own core activity is large-scale monitoring escapes the trigger that Article 37(1)(b) and (c) apply to it expressly.
The limbs are also joined by dan where Article 37(1) joins its three cases with or, which on a strict reading would demand all three triggers at once. PP Pasal 142 ayat (1) answers one of these and not the other: huruf b there ends dan/atau, which settles the alternative reading, while huruf b and huruf c still speak only of the controller's core activities, so the processor gap survives into the regulation.
The UU also leaves out Article 37(2) and Article 37(7), so nothing at statute level lets a group share one officer or requires the contact details to reach the authority. One departure runs the other way: Article 37(1)(c) joins special categories and criminal offence data with and, and huruf c writes dan/atau, which settles a reading the EU text leaves open.
The word dan in Pasal 53 ayat (1) huruf b is conditionally unconstitutional and without binding force unless read as dan/atau. At [3.13] the Court reasoned that high-risk processing warrants closer supervision, so a controller or processor meeting any one of the three criteria in Pasal 53 ayat (1) must appoint a data protection officer; a cumulative reading would strip that protection from Article 28G(1) of the 1945 Constitution.
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 45 national decisions since 25 May 2018, from 11 countries, as citing Article 37(1), 37(2), 37(5), 37(6) and 37(7); most come from Italy (14), Luxembourg (12) and Greece (5). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.
The Lembaga. No decision of the Lembaga exists, because it has not been established (CNBC Indonesia, 16 September 2026).