Data protection impact assessment
Pasal 34
Official copy: salinan p. 15
Penilaian dampak Pelindungan Data Pribadi dilakukan untuk mengevaluasi potensi risiko yang timbul dari suatu pemrosesan Data Pribadi serta upaya atau langkah yang harus dilakukan untuk memitigasi risiko, termasuk terhadap hak Subjek Data Pribadi dan mematuhi Undang-Undang ini.
Implemented by PP 33/2026 Pasal 120 to 122.
Ayat (3) delegates the detail on impact assessment to a government regulation, now PP 33/2026. PP Pasal 122 passes it down again to a Peraturan Lembaga.
Ayat (1) Penilaian dampak Pelindungan Data Pribadi dilakukan untuk mengevaluasi potensi risiko yang timbul dari suatu pemrosesan Data Pribadi serta upaya atau langkah yang harus dilakukan untuk memitigasi risiko, termasuk terhadap hak Subjek Data Pribadi dan mematuhi Undang-Undang mengenai Pelindungan Data Pribadi. Ayat (2) Huruf a Keputusan secara otomatis yang memiliki akibat hukum atau dampak yang signifikan terhadap Subjek Data Pribadi antara lain keputusan tentang akses individu ke produk, layanan, peluang, atau manfaat yang didasarkan pada pengambilan keputusan otomatis, termasuk pembuatan profil. Huruf b Cukup jelas. Huruf c Pemrosesan Data Pribadi dalam skala besar antara lain dengan mempertimbangkan faktor yang terkait seperti jumlah Data Pribadi yang diproses, jumlah Subjek Data Pribadi yang terlibat, durasi pemrosesan Data Pribadi, jenis Data Pribadi, tujuan pemrosesan Data Pribadi, dan wilayah geografis yang terkena dampak pemrosesan Data Pribadi. Huruf d Cukup jelas. Huruf e Cukup jelas. Huruf f Penggunaan teknologi baru dalam pemrosesan Data Pribadi antara lain kecerdasan buatan, machine learning, smart technology, internet of things, dan lain sebagainya. Huruf g Cukup jelas.
Ayat (1) Cukup jelas. Ayat (2) Penilaian dampak Pelindungan Data Pribadi dilakukan secara sistematis. Ayat (3) Cukup jelas. Ayat (4) Mendokumentasikan penilaian dampak Pelindungan Data Pribadi termasuk mendokumentasikan saran dari PPDP. Ayat (5) Cukup jelas. Ayat (6) Cukup jelas.
PP Pasal 120 sets the high-risk triggers, Pasal 121 requires the assessment before processing begins and Pasal 122 fixes its minimum content, sanction-backed at Pasal 120(1). The divergence from GDPR is at the next step: Article 36 makes prior consultation mandatory where residual risk stays high, while Pasal 122 provides only that the controller may consult the Lembaga, so the external check on a failed assessment is discretionary.
diverges from the GDPRGDPR Articles 35 and 36
What the GDPR provides. GDPR Article 35(1) requires a data protection impact assessment before processing likely to result in a high risk to rights and freedoms, in particular where new technologies are used. GDPR Article 35(3) names three cases where one is always required: systematic and extensive automated evaluation producing legal or similarly significant effects, large scale processing of special category or criminal conviction data, and large scale systematic monitoring of a publicly accessible area.
GDPR Article 35(2), (7) and (9) add advice from the data protection officer, a fixed minimum content of description, necessity and proportionality test, risk assessment and mitigating measures, and the views of data subjects where appropriate.
GDPR Article 36(1) then requires the controller to consult the supervisory authority before processing where the assessment shows the processing would be high risk in the absence of measures taken to mitigate that risk, which recital 94 and WP248 rev.014 read as a test of the risk left after mitigation.
The seven triggers at UU Pasal 34 ayat (2) do not track GDPR Article 35(3), which names three. They correspond to the WP29 impact assessment guidelines, WP248 rev.014, whose nine criteria are evaluation or scoring, automated decision making with legal or similarly significant effect, systematic monitoring, sensitive data, large scale processing, matching or combining datasets, vulnerable data subjects, innovative use of new technology, and processing that in itself prevents subjects from exercising a right.
Eight of the nine appear in ayat (2), all but vulnerable data subjects, compressed into seven limbs because huruf d carries evaluation or scoring and systematic monitoring together, which is why the list is longer and flatter than Article 35(3).
The article stops tracking at the back half, where GDPR Article 35(4) makes every supervisory authority publish a list of processing that always needs an assessment and GDPR Article 36(1) makes consultation mandatory where mitigation has not removed the high risk, while PP Pasal 122 leaves consultation with the Lembaga to the controller's choice.
What Article 36 measures is the risk left after mitigation, so a controller that mitigates well never consults, and dropping the duty removes the single moment at which a regulator sees a failed assessment before processing starts. C-634/215, an Article 22 ruling, fixes the threshold the first Indonesian trigger uses, holding that the automated production of a probability value counts as the decision where a third party draws strongly on it.
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 31 national decisions since 25 May 2018, from 11 countries, as citing Article 35(1), 35(2), 35(3) and 35(4); most come from Belgium (8), Denmark (8) and Greece (4). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.
The DPO tags 10 national decisions since 25 May 2018, from 5 countries, as citing Article 36; most come from Austria (3), Denmark (3) and Finland (2). 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).