Duty to destroy
Pasal 44
Official copy: salinan p. 18
Yang dimaksud dengan "memusnahkan" adalah tindakan untuk menghilangkan, melenyapkan, atau menghancurkan Data Pribadi sehingga tidak lagi dapat digunakan untuk mengidentifikasi Subjek Data Pribadi.
Implemented by PP 33/2026 Pasal 84 to 89.
Ketentuan lebih lanjut mengenai mekanisme pengakhiran pemrosesan, penghapusan, dan pemusnahan Data Pribadi diatur dengan Peraturan Lembaga.
PP Pasal 84 and 85 treat destruction as a duty distinct from erasure, triggered by expiry of the retention period or by request, sanction-backed at Pasal 84(1). GDPR does not draw this distinction, so a compliance programme built on GDPR mappings will not have a corresponding control.
diverges from the GDPRGDPR Articles 17 and 89
What the GDPR provides. The GDPR has no destruction duty distinct from erasure. It uses the word destruction in Article 4(2), where destruction is one form of processing, and in Article 4(12), Article 5(1)(f) and Article 32, where it is something a breach does to data.
Disposal in the Regulation runs on three provisions: the storage limitation principle at Article 5(1)(e), the erasure obligation at Article 17, and the processor's duty at Article 28(3)(g) to delete or return the data at the end of the service. The Regulation prescribes no method, so deletion, overwriting and irreversible anonymisation are each capable of discharging it.
Article 17(3)(b), (d) and (e) hold data back where they are needed for a legal obligation, for archiving in the public interest under Article 89(1), or for legal claims, and Article 89(3) lets Union or member state law derogate from the rights in Articles 15, 16, 18, 19, 20 and 21 for archiving in the public interest.
Three of the four Pasal 44 triggers are GDPR erasure grounds wearing another name: huruf a is Article 5(1)(e) with Article 17(1)(a), huruf b is a request under Article 17(1), and huruf d is Article 17(1)(d). What diverges is the architecture and one trigger.
Europe runs a single disposal track, principle at Article 5(1)(e), obligation and right at Article 17, processor clean up at Article 28(3)(g), while Indonesia runs penghapusan at Pasal 43 and pemusnahan at Pasal 44 as separate wajib with separate sanctions, so the destruction duty and its sanction at PP Pasal 84(1) have nowhere to land in a control set derived from GDPR mappings.
Pasal 44 ayat (1) huruf c is the trigger with no European shape at all. The limbs are joined by dan/atau, so on its face the absence of a link to penyelesaian proses hukum can start the duty on its own, a reading that cannot be intended and is better treated as an open drafting question.
Read either way it runs against Article 17(3)(e), which makes the presence of a legal claim a shield against erasure, so the same diligence output is a defence in Europe and a condition on the Indonesian side. The jadwal retensi arsip hook at huruf a ties the trigger to Indonesian archives law, and the GDPR supplies no answer of its own, because Article 89 gives safeguards and a derogation power for archiving rather than an archive schedule.
One design consequence follows: anonymisation can discharge Article 17 because the GDPR test is identifiability, whereas Pasal 44 is keyed to the archive schedule and to lawfulness of acquisition, so one technical measure does not necessarily close both.
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 129 national decisions since 25 May 2018, from 17 countries, as citing Article 17(1) and 17(3); most come from Hungary (20), Belgium (17) and Finland (17). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.
The DPO tags 18 national decisions since 25 May 2018, from 8 countries, as citing Article 89; most come from Belgium (5), Greece (4) and Austria (2). 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 17(1), 17(3)(b) and 17(3)(e). Read it on GDPRhub
The Lembaga. No decision of the Lembaga exists, because it has not been established (CNBC Indonesia, 16 September 2026).