Proof of consent
Pasal 24
Dalam melakukan pemrosesan Data Pribadi, Pengendali Data Pribadi wajib menunjukkan bukti persetujuan yang telah diberikan oleh Subjek Data Pribadi.
Official copy: salinan p. 12
Implemented by PP 33/2026 Pasal 36.
Ayat (1) Cukup jelas. Ayat (2) Yang dimaksud dengan "dalam rangka akuntabilitas pemrosesan Data Pribadi" antara lain untuk kepentingan pemenuhan kewajiban Pengendali Data Pribadi dan hak Subjek Data Pribadi atau dalam rangka pengawasan dari Lembaga.
PP Pasal 36 places the burden of demonstrating consent on the controller and makes that duty sanction-backed at Pasal 36(1). Evidentiary practice therefore becomes a compliance obligation rather than a matter of internal record-keeping.
ported from the GDPRGDPR Articles 5 and 7
What the GDPR provides. GDPR Article 7(1) provides that where processing is based on consent, the controller must be able to demonstrate that the data subject has consented. It allocates the burden of proof rather than prescribing any record. GDPR Article 5(2) carries the same idea across every principle as accountability, so the controller must be able to show compliance generally and not only on consent. Neither provision fixes a form, a retention period or an evidential standard.
The mechanism comes from GDPR Article 7(1): consent is something the controller must prove, not something the data subject must disprove. Two things change on the way across. GDPR Article 7(1) is conditional, opening with where processing is based on consent, while UU Pasal 24 opens with dalam melakukan pemrosesan Data Pribadi and drops the condition.
The implementing text closes that gap, because PP Pasal 36 ayat (1) repeats the duty word for word inside the explicit consent paragraph and ayat (2) says it is discharged in the interest of accountability, so the duty reads as a consent duty rather than one owed under every basis in UU Pasal 20 ayat (2).
And GDPR Article 7(1) asks the controller to be able to demonstrate, a standing capability tested if challenged, where wajib menunjukkan bukti reads as a duty to produce. The content of the GDPR duty has been built by the Court rather than the text: C-61/193 held a controller cannot discharge it with a pre-completed contractual clause, and C-673/174 that a pre-ticked box leaves nothing to verify because there was no act to record.
The wider accountability hook is not missing on the Indonesian side, because UU Pasal 16 ayat (2) huruf h already requires processing to be bertanggung jawab dan dapat dibuktikan secara jelas. The difference is reach rather than price: GDPR Article 5(2) runs across every principle and every basis, which is what lets a supervisory authority put the burden on the controller in the far larger set of cases where consent is not the basis at all.
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 464 national decisions since 25 May 2018, from 26 countries, as citing Article 5(2); most come from Latvia (72), Hungary (58) and Belgium (54). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.
The DPO tags 23 national decisions since 25 May 2018, from 12 countries, as citing Article 7(1); most come from Belgium (7), France (3) and Lithuania (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).