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

Duty of confidentiality

sanctioned by Pasal 57 ayat (1)

1Legal text

Pasal 36

Dalam melakukan pemrosesan Data Pribadi, Pengendali Data Pribadi wajib menjaga kerahasiaan Data Pribadi.

Official copy: salinan p. 16

2Implementing regulation

Implemented by PP 33/2026 Pasal 125.

PP Pasal 125Dalam melakukan pemrosesan Data Pribadi, Pengendali Data…sanction list
repeats UU Pasal 36
(1)
Dalam melakukan pemrosesan Data Pribadi, Pengendali Data Pribadi wajib menjaga kerahasiaan Data Pribadi.
what the PP adds
(2)
Kewajiban menjaga kerahasiaan Data Pribadi sebagaimana dimaksud pada ayat (1), termasuk memastikan Prosesor Data Pribadi yang ditunjuk oleh Pengendali Data Pribadi mampu mendukung kewajiban Pengendali Data Pribadi dalam menjaga kerahasiaan Data Pribadi.

Read it in the regulationsalinan p. 61

3Commentary

3.1How the regulation implements it

Confidentiality is stated as a direct obligation at PP Pasal 125, sanction-backed at Pasal 125(1). GDPR reaches the same result through contract and controller instruction under Articles 28 and 29, so the Indonesian duty binds without the need for an intermediating agreement.

3.2Where the GDPR stands

diverges from the GDPRGDPR Articles 5, 28, 29, 32 and 90

What the GDPR provides. The GDPR has no free-standing duty of confidentiality resting on the controller. GDPR Article 5(1)(f) pairs confidentiality with integrity and states it as a security principle, protection against unauthorised or unlawful processing and against accidental loss, destruction or damage, by appropriate technical and organisational measures.

Secrecy as such is handled by other instruments: GDPR Article 28(3)(b) requires the processor contract to bind the processor's authorised persons to confidentiality or to an existing statutory secrecy duty, and GDPR Article 29 with Article 32(4) stops anyone acting under the controller's or the processor's authority from processing except on instructions.

GDPR Article 90 creates no secrecy duty of its own; it lets member states set out how far a supervisory authority's powers under Article 58(1)(e) and (f) reach into controllers already bound by professional secrecy.

The two provisions do different jobs behind similar words. UU Pasal 36 is a secrecy duty, keep the data confidential, stated once and owed by the Pengendali. GDPR Article 5(1)(f) is a security duty that happens to use the word confidentiality, requiring appropriate security of the data, and it is read with GDPR Article 32 rather than as an independent obligation of silence.

The GDPR's secrecy obligations reach natural persons through instruments and not directly, by contract at GDPR Article 28(3)(b) for a processor's authorised persons and by instruction at GDPR Article 29 and Article 32(4) for anyone acting under the controller's authority. That gives the two systems different failure points.

In the EU a controller that took no steps to bind its own staff to instructions breaches Article 32(4), while the leaking employee ordinarily answers to national law rather than as a controller, though Guidelines 07/20203 accept that a person who processes for their own purposes outside the organisation's activities can become a controller in their own name.

Under UU Pasal 36 the duty and the sanction land on the Pengendali whether or not any instrument exists, and PP Pasal 125 ayat (2) then folds the processor in by making the controller ensure the Prosesor can support the same confidentiality, which is the work of GDPR Article 28(3)(b) done without a contract term.

The consequence is that an EU controller answers first for the instruments it put in place, and an Indonesian one answers for the confidentiality whether or not it put any instrument in place at all.

4Decisions and guidance

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 5 GDPRPrinciples relating to processing of personal data5 of 1,976 decisions

The DPO tags 1,976 national decisions since 25 May 2018, from 29 countries, as citing Article 5(1); most come from Italy (340), Spain (193) and Latvia (171). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.

Article 28 GDPRProcessor5 of 147 decisions

The DPO tags 147 national decisions since 25 May 2018, from 19 countries, as citing Article 28(3); 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.

  • Decision of 28 July 2026Greece, HDPA
  • DKN.5131.12.2022Poland, UODO11 June 2026
  • 10281706Italy, Garante per la protezione dei dati personaliAcquirente Unico S.p.A.18 June 2026
  • 102/2026Belgium, Gegevensbeschermingsautoriteit12 May 2026Under appeal to the Market Court, as the authority's copy said on 27 September 2026.
  • DecisionGermany, BlnBDIBerliner Verkehrsbetriebe (BVG)2026
Article 29 GDPRProcessing under the authority of the controller or processor3 of 59 decisions

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.

  • DecisionRomania, ANSPDCP2026 · fine EUR 2,000
  • 10266338Italy, Garante per la protezione dei dati personali11 June 2026 · fine EUR 4,500
  • DKN.5112.13.2023Poland, UODO27 February 2026 · fine EUR 232
Article 32 GDPRSecurity of processing4 of 74 decisions

The DPO tags 74 national decisions since 25 May 2018, from 11 countries, as citing Article 32(4); most come from Romania (44), Lithuania (7) and Croatia (7). 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 90 GDPRObligations of secrecy3 judgments

Cited in its whole commentary on Article 90. 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 125 at p. 61.
  3. 3EDPB, Guidelines 07/2020 on the concepts of controller and processor in the GDPR. EDPB.↑
  4. 4GDPRhub (noyb), commentary on Article 5 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.
  5. 5GDPRhub (noyb), commentary on Article 28 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.
  6. 6GDPRhub (noyb), commentary on Article 29 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.
  7. 7GDPRhub (noyb), commentary on Article 32 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.
  8. 8GDPRhub (noyb), commentary on Article 90 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.