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

Prevention of unauthorised access

sanctioned by Pasal 57 ayat (1)

1Legal text

Pasal 39

(1)
Pengendali Data Pribadi wajib mencegah Data Pribadi diakses secara tidak sah.
(2)
Pencegahan sebagaimana dimaksud pada ayat (1) dilakukan dengan menggunakan sistem keamanan terhadap Data Pribadi yang diproses dan/atau memproses Data Pribadi menggunakan sistem elektronik secara andal, aman, dan bertanggung jawab.
(3)
Pencegahan sebagaimana dimaksud pada ayat (2) dilakukan sesuai dengan ketentuan peraturan perundang-undangan.

Official copy: salinan p. 16

2Implementing regulation

Implemented by PP 33/2026 Pasal 130.

PP Pasal 130Pengendali Data Pribadi wajib mencegah Data Pribadi diakses…sanction list
repeats UU Pasal 39
(1)
Pengendali Data Pribadi wajib mencegah Data Pribadi diakses secara tidak sah.
what the PP adds
(2)
Pencegahan sebagaimana dimaksud pada ayat (1) dilakukan dengan menggunakan sistem keamanan terhadap Data Pribadi yang diproses dan/atau memproses Data Pribadi menggunakan sistem elektronik secara andal, aman, dan bertanggung jawab.
(3)
Pencegahan sebagaimana dimaksud pada ayat (2) dilakukan sesuai dengan ketentuan peraturan perundang-undangan.

Read it in the regulationsalinan p. 63

3Commentary

3.1How the regulation implements it

PP Pasal 130 requires prevention of unauthorised access through system security, sanction-backed at Pasal 130(1). Read with Pasal 123, it ties the security obligation to the electronic system rather than to the data alone.

3.2Where the GDPR stands

diverges from the GDPRGDPR Articles 32, 33 and 34

What the GDPR provides. Unauthorised access is both a security question and a breach question under the GDPR. GDPR Article 32(1)(b) requires measures ensuring the ongoing confidentiality, integrity, availability and resilience of processing systems and services, and GDPR Article 32(2) names unauthorised disclosure of or access to personal data among the risks that set the appropriate level. GDPR Article 32(1)(d) requires a process for regularly testing, assessing and evaluating the effectiveness of those measures.

GDPR Article 4(12) then defines a personal data breach as a breach of security leading to, among other things, unauthorised access to personal data. A security failure that lets someone in therefore engages GDPR Article 33, which requires notification to the supervisory authority without undue delay and where feasible within 72 hours of the controller becoming aware, unless the breach is unlikely to result in a risk to rights and freedoms.

GDPR Article 34 then requires the subject to be told where the risk is high.

The GDPR duty attaches to processing. The Indonesian duty attaches to the electronic system. UU Pasal 39 ayat (2) requires the system to be operated andal, aman, dan bertanggung jawab, which is the formula UU ITE Pasal 15 ayat (1) already uses for electronic system operators rather than anything drawn from GDPR Article 32, and ayat (3) then sends the reader back out to the wider legislation.

That produces an effect the two texts do not show side by side: an Indonesian controller's security question is answered partly by the electronic system regime and its sectoral rules, while an EU controller's is answered inside Article 32 and its state of the art test, with no external standard doing the work.

The second asymmetry is at the back end, where GDPR Article 32 is joined to Articles 33 and 34, so a failure of prevention is also a personal data breach under Article 4(12) and puts the controller on a clock that starts when it becomes aware, subject to the risk threshold at Article 33(1), while UU Pasal 39 stops at prevention and leaves the consequence to the notification provisions elsewhere.

C-340/213 is where both halves met, an unauthorised access at a tax authority, with the Court holding that the fact of the intrusion does not by itself prove the Article 32 measures were inadequate and that the burden of proving they were appropriate sits on the controller.

4Decisions and guidance

Court of Justice of the EU

  • C-340/21VB v Natsionalna agentsia za prihodite14 December 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 32 GDPRSecurity of processing5 of 518 decisions

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

  • DecisionRomania, ANSPDCP2026 · fine EUR 5,000
  • DKN.5131.5.2025Poland, UODO25 May 2026
  • 10280177Italy, Garante per la protezione dei dati personaliDocplanner Italy S.r.l.18 June 2026 · fine EUR 10,000
  • 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 126 decisions

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

Article 34 GDPRCommunication of a personal data breach to the data subject5 of 150 decisions

The DPO tags 150 national decisions since 25 May 2018, from 20 countries, as citing Article 34; most come from Poland (40), Lithuania (15) and Denmark (14). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.

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 34 GDPRCommunication of a personal data breach to the data subject1 EDPB document

Cited in its whole commentary on Article 34. 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

6Sources

  1. 1UU 27/2022, salinan, p. 16.
  2. 2PP 33/2026, salinan: Pasal 130 at p. 63.
  3. 3Case C-340/21 VB v Natsionalna agentsia za prihodite, 14 December 2023, ECLI:EU:C:2023:986. EUR-Lex.↑
  4. 4EDPB, Guidelines 9/2022 on personal data breach notification under GDPR. EDPB.
  5. 5GDPRhub (noyb), commentary on Article 32 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.
  6. 6GDPRhub (noyb), commentary on Article 33 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.
  7. 7GDPRhub (noyb), commentary on Article 34 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.