Refusing access or change
Pasal 33
Pengendali Data Pribadi wajib menolak memberikan akses perubahan terhadap Data Pribadi kepada Subjek Data Pribadi dalam hal:
Official copy: salinan p. 14
Yang dimaksud dengan "membahayakan keamanan, kesehatan fisik, atau kesehatan mental Subjek Data Pribadi dan/atau orang lain" antara lain perubahan data riwayat penyakit yang berpotensi membahayakan keamanan diri sendiri dan/atau orang lain.
Yang dimaksud dengan "berdampak pada pengungkapan Data Pribadi milik orang lain" antara lain perubahan Data Pribadi nasabah yang berdampak pada pengungkapan Data Pribadi orang lain.
Implemented by PP 33/2026 Pasal 26 and 27.
Pengendali Data Pribadi menentukan kondisi pemenuhan dan/atau penolakan atas permohonan pelaksanaan hak Subjek Data Pribadi sesuai dengan ketentuan peraturan perundang-undangan.
Ayat (1) Laporan kepada Lembaga misalnya laporan dugaan pelanggaran Pelindungan Data Pribadi. Ayat (2) Cukup jelas.
Refusal of access or change runs through the fulfilment-or-refusal conditions at PP Pasal 26 and 27, with reasons owed to the subject and a remedy where the controller does not act. The remedy at Pasal 27 is what distinguishes this from a bare procedural duty.
diverges from the GDPRGDPR Articles 12, 15 and 23
What the GDPR provides. The GDPR does not oblige a controller to refuse an access request. It limits the right instead, and it does so in two different ways. GDPR Article 15(4) is a ceiling that binds the controller directly: the right to obtain a copy shall not adversely affect the rights and freedoms of others, so the controller must hold back the part that would.
GDPR Article 23 is a permission addressed to the legislator, letting Union or member state law restrict Articles 12 to 22, Article 34 and the corresponding parts of Article 5 for a closed list of objectives, national security and defence among them, but only where the restriction respects the essence of the right and is necessary and proportionate.
GDPR Article 23(2) then fixes what such a law must itself contain where relevant, including the scope of the restriction, the safeguards against abuse, and the subject's right to be told a restriction applies unless telling would defeat its purpose. GDPR Article 12(4) requires the controller to tell the subject without delay and at the latest within one month why it is not acting, and to point to the supervisory authority and to judicial remedy.
The mandatory limb is the difference. UU Pasal 33 says wajib menolak, so a controller that grants access on one of the three grounds is itself in breach. The GDPR has no duty to refuse a request as such.
Article 15(4) obliges the controller to hold back only the part of a copy that would harm others, and Article 23 is a permission addressed to the legislator, not to the controller.
The route differs as much as the obligation: under GDPR Article 23 a restriction has to be created by a legislative measure carrying the Article 23(2) content list, so the controller applies a rule someone else drafted and that can be tested for necessity and proportionality, whereas UU Pasal 33 puts the three grounds in the statute and hands the assessment to the controller with no proportionality test on its face.
Limb b, disclosure of another person's data, is the limb the EU has actually litigated: C-487/214 reads GDPR Article 15(4) as requiring, wherever possible, a means of communicating the data that does not infringe the rights of others, and C-579/215 lets employee identities be withheld from log data while the log data itself is handed over, so third party data narrows what must be produced rather than defeating the request.
The national security limb has no controller side counterpart at all, because GDPR Article 23 keeps that judgement with the legislator and leaves it reviewable.
The remedy side does not close the gap either: PP Pasal 26 leaves the conditions of refusal to the controller under other legislation and PP Pasal 27 gives the subject a route to report to the Lembaga, but neither carries the GDPR Article 12(4) duty to give reasons on a one month clock or to point to a judicial remedy.
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 163 national decisions since 25 May 2018, from 16 countries, as citing Article 12(4); most come from Hungary (28), Belgium (24) and Romania (22). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.
The DPO tags 5 national decisions since 25 May 2018, from 4 countries, as citing Article 15(4); most come from Romania (2), Finland (1) and Belgium (1). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.
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.
Cited in its commentary on Article 15(4). Read it on GDPRhub
Cited in its commentary on Article 23(2). Read it on GDPRhub
The Lembaga. No decision of the Lembaga exists, because it has not been established (CNBC Indonesia, 16 September 2026).