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 54 UU PDP

Tasks of the PPDP

awaiting a Peraturan Lembaga

1Legal text

Pasal 54

(1)
Pejabat atau petugas yang melaksanakan fungsi Pelindungan Data Pribadi memiliki tugas paling sedikit:
  1. a.
    menginformasikan dan memberikan saran kepada Pengendali Data Pribadi atau Prosesor Data Pribadi agar mematuhi ketentuan dalam Undang-Undang ini;
  2. b.
    memantau dan memastikan kepatuhan terhadap Undang-Undang ini dan kebijakan Pengendali Data Pribadi atau Prosesor Data Pribadi;
  3. c.
    memberikan saran mengenai penilaian dampak Pelindungan Data Pribadi dan memantau kinerja Pengendali Data Pribadi dan Prosesor Data Pribadi; dan
  4. d.
    berkoordinasi dan bertindak sebagai narahubung untuk isu yang berkaitan dengan pemrosesan Data Pribadi.
(2)
Dalam melaksanakan tugas sebagaimana dimaksud pada ayat (1), pejabat atau petugas yang melaksanakan fungsi Pelindungan Data Pribadi memperhatikan risiko terkait pemrosesan Data Pribadi, dengan mempertimbangkan sifat, ruang lingkup, konteks, dan tujuan pemrosesan.
(3)
Ketentuan lebih lanjut mengenai pejabat atau petugas yang melaksanakan fungsi Pelindungan Data Pribadi diatur dalam Peraturan Pemerintah.

Official copy: salinan p. 22

2Implementing regulation

Implemented by PP 33/2026 Pasal 145 to 147.

Ayat (3) delegates the detail on the data protection officer to a government regulation, now PP 33/2026. PP Pasal 142 to 144 pass it down again to a Peraturan Lembaga.

PP Pasal 145PPDP memiliki tugas paling sedikit: a. menginformasikan dan…
(1)
PPDP memiliki tugas paling sedikit:
  1. a.
    menginformasikan dan memberikan saran kepada Pengendali Data Pribadi atau Prosesor Data Pribadi agar mematuhi ketentuan dalam Undang-Undang mengenai Pelindungan Data Pribadi;
  2. b.
    memantau dan memastikan kepatuhan terhadap ketentuan peraturan perundang-undangan di bidang Pelindungan Data Pribadi dan kebijakan Pengendali Data Pribadi atau Prosesor Data Pribadi;
  3. c.
    memberikan saran mengenai penilaian dampak Pelindungan Data Pribadi dan memantau kinerja Pengendali Data Pribadi dan Prosesor Data Pribadi; dan
  4. d.
    berkoordinasi dan bertindak sebagai narahubung untuk isu yang berkaitan dengan pemrosesan Data Pribadi.
(2)
Dalam melaksanakan tugas sebagaimana dimaksud pada ayat (1), PPDP memperhatikan risiko terkait pemrosesan Data Pribadi, dengan mempertimbangkan sifat, ruang lingkup, konteks, dan tujuan pemrosesan Data Pribadi.

Read it in the regulationsalinan p. 72

PP Pasal 146Untuk efektivitas pelaksanaan tugas PPDP sebagaimana dimaksud…
(1)
Untuk efektivitas pelaksanaan tugas PPDP sebagaimana dimaksud dalam Pasal 145, Pengendali Data Pribadi dan/atau Prosesor Data Pribadi harus:
  1. a.
    memastikan PPDP terlibat dalam semua kegiatan pemrosesan Data Pribadi;
  2. b.
    memastikan PPDP memiliki akses pelaporan ke tingkat manajemen tertinggi;
  3. c.
    memastikan PPDP beroperasi secara objektif, tidak diintervensi, dan independen dalam menjalankan tugasnya sesuai dengan ketentuan peraturan perundang-undangan;
  4. d.
    menyediakan sumber daya yang memadai untuk memungkinkan PPDP memenuhi tugasnya dan mempertahankan tingkat keahliannya;
  5. e.
    memastikan PPDP mendapatkan akses yang sesuai dengan aktivitas pemrosesan Data Pribadi;
  6. f.
    memberikan akses yang sesuai ke layanan lainnya untuk mendapatkan Informasi penting yang berkaitan dengan pemrosesan Data Pribadi;
  7. g.
    meminta saran dari PPDP pada saat melakukan penilaian dampak Pelindungan Data Pribadi; dan
  8. h.
    mendokumentasikan secara detail kegiatan pelaksanaan tugas PPDP.
(2)
Pengendali Data Pribadi dan/atau Prosesor Data Pribadi harus memastikan bahwa tugas PPDP tidak mengakibatkan konflik kepentingan.

Read it in the regulationsalinan p. 73

PP Pasal 147PPDP harus bekerja sama dengan unit, pejabat, atau pihak yang…
(1)
PPDP harus bekerja sama dengan unit, pejabat, atau pihak yang bertanggung jawab dalam pemrosesan Data Pribadi.
(2)
Dalam melakukan kerja sama dengan pihak sebagaimana dimaksud pada ayat (1), PPDP harus:
  1. a.
    memberikan rekomendasi dan saran kepada unit, pejabat, atau pihak yang bertanggung jawab dalam keamanan pemrosesan Data Pribadi yang diproses oleh Pengendali Data Pribadi agar penyelenggaraan keamanan pemrosesan Data Pribadi sesuai dengan ketentuan peraturan perundang-undangan;
  2. b.
    melakukan upaya yang dibutuhkan untuk memastikan unit, pejabat, atau pihak yang bertanggung jawab dalam keamanan pemrosesan Data Pribadi yang diproses oleh Pengendali Data Pribadi menerapkan langkah teknis dan operasional yang turut mempertimbangkan pelindungan hak dan kebebasan Subjek Data Pribadi; dan
  3. c.
    melaporkan kinerja unit, pejabat, atau pihak yang bertanggung jawab dalam keamanan pemrosesan Data Pribadi kepada pemimpin di internal Pengendali Data Pribadi mengenai penilaian unit, pejabat, dan/atau pihak tersebut terhadap penerapan langkah teknis dan operasional dengan mempertimbangkan pelindungan Subjek Data Pribadi sesuai kebutuhan Pengendali Data Pribadi.

Read it in the regulationsalinan p. 73

3Commentary

3.1How the regulation implements it

PP Pasal 145 to 147 set a minimum task list, require resources and access at Pasal 146 and impose cooperation duties at Pasal 147. Independence is protected through the resourcing and access provisions rather than through an express independence clause of the GDPR Article 38 kind.

3.2Where the GDPR stands

ported from the GDPRGDPR Articles 38 and 39

What the GDPR provides. GDPR Article 39(1) gives the officer at least five tasks: informing and advising the controller, processor and staff who process; monitoring compliance with the GDPR and with internal policies, including allocation of responsibilities, awareness raising, training and audits; advising on a data protection impact assessment and monitoring its performance under Article 35; cooperating with the supervisory authority; and acting as its contact point, including for prior consultation under Article 36.

Article 39(2) requires the officer to have due regard to the risk of the processing, taking account of its nature, scope, context and purposes. Article 38 is the other half of the design and governs position rather than work.

It requires timely involvement in all data protection issues, resources and access, no instructions on how to perform the tasks, no dismissal or penalty for performing them, direct reporting to the highest management level, secrecy, and no other tasks that create a conflict of interests.

UU Pasal 54 ayat (1) is Article 39(1) in the same order with the last two limbs folded into one: huruf a is Article 39(1)(a), huruf b is Article 39(1)(b), huruf c sits where Article 39(1)(c) sits, and huruf d merges cooperation with the authority and the contact point role from Article 39(1)(d) and (e), with paling sedikit doing the work of at least in the chapeau.

Huruf c is the one limb that shifted in transposition: Article 39(1)(c) has the officer advise where requested and monitor the performance of the impact assessment, while huruf c drops the request condition and has the officer memantau kinerja of the controller and the processor, which widens the task and overlaps huruf b.

Ayat (2) is Article 39(2) carried across, with risiko, sifat, ruang lingkup, konteks and tujuan in the same sequence as risk, nature, scope, context and purposes.

What did not come across into the statute is Article 38, and that is where the EU litigation has actually been: the questions that reached the Court were whether national law may protect the officer against dismissal under Article 38(3) and whether a manager with operational duties can hold the role at all under Article 38(6).

Neither has a hook in UU Pasal 54, but only the first is missing from the regime as a whole. PP Pasal 146 goes well past resources and access.

Ayat (1) huruf a requires the PPDP to be involved in all processing activities, huruf b requires reporting access to the highest management level, huruf c requires the PPDP to operate objectively, free from intervention and independently, and huruf d requires adequate resources and the maintenance of expertise, while ayat (2) requires the controller and processor to ensure the PPDP's tasks do not produce a conflict of interests.

That answers Article 38(1), the no-instructions and direct-reporting limbs of Article 38(3), Article 38(2) and Article 38(6), so the X-FAB question has a text to be argued under. What has no counterpart is the protection against dismissal or penalty for performing the tasks in the second sentence of Article 38(3), and the secrecy duty at Article 38(5).

A PPDP removed after an unwelcome opinion still has no provision addressed to the removal, and PP Pasal 146 is itself absent from the PP Pasal 184 sanctions list, so the independence guarantees that do exist carry no administrative penalty of their own.

4Decisions and guidance

Court of Justice of the EU

  • C-534/20Leistritz AG v LH22 June 2022
  • C-453/21X-FAB Dresden GmbH & Co. KG v FC9 February 2023

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 38 GDPRPosition of the data protection officer5 of 51 decisions

The DPO tags 51 national decisions since 25 May 2018, from 13 countries, as citing Article 38(1), 38(2), 38(3), 38(5) and 38(6); most come from Belgium (14), Croatia (9) and Poland (8). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.

Article 39 GDPRTasks of the data protection officer2 of 16 decisions

The DPO tags 16 national decisions since 25 May 2018, from 4 countries, as citing Article 39(1) and 39(2); most come from Luxembourg (7), Belgium (5) and Greece (2). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.

  • DKN.5110.14.2022Poland, UODO2 April 2025
  • 07/2024Belgium, GegevensbeschermingsautoriteitBLACK TIGER BELGIUM (voormalig BISNODE BELGIUM NV)16 January 2024

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

5Cross-references

Referred to by

  • No other article of the Law refers to this one.

6Sources

  1. 1UU 27/2022, salinan, p. 22.
  2. 2PP 33/2026, salinan: Pasal 145 to 147 at pp. 72 to 73.
  3. 3Case C-534/20 Leistritz AG v LH, 22 June 2022, ECLI:EU:C:2022:495. EUR-Lex.
  4. 4Case C-453/21 X-FAB Dresden GmbH & Co. KG v FC, 9 February 2023, ECLI:EU:C:2023:79. EUR-Lex.
  5. 5GDPRhub (noyb), commentary on Article 38 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.
  6. 6GDPRhub (noyb), commentary on Article 39 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.