Ending processing
Pasal 42
Official copy: salinan p. 17
Implemented by PP 33/2026 Pasal 80 and 81.
Ayat (1) Cukup jelas. Ayat (2) Cukup jelas. Ayat (3) Penyampaian pengakhiran pemrosesan Data Pribadi kepada Subjek Data Pribadi dilakukan antara lain secara langsung kepada Subjek Data Pribadi atau tidak langsung melalui media massa.
PP Pasal 80 and 81 require processing to end on completion of purpose, expiry of the retention period or withdrawal of consent, sanction-backed at Pasal 80(1). Retention policy under Pasal 75 is the document against which this duty is measured.
diverges from the GDPRGDPR Articles 5 and 17
What the GDPR provides. GDPR Article 5(1)(e) requires data to be kept in identifiable form no longer than necessary for the purposes, with longer storage allowed only for archiving, research or statistics under the Article 89(1) safeguards. Article 5(1)(b) requires the purposes to be specified at collection and bars further processing incompatible with them, compatible further processing being permitted and tested under Article 6(4).
Article 17(1)(a) turns the same idea into a right once the data are no longer necessary, and Article 7(3) stops future consent based processing on withdrawal. There is no GDPR article that says processing must end; the end is an effect of the principles plus the erasure right.
Both regimes stop processing at the same three points, but the GDPR never states the duty, it derives it. That changes what an enforcer has to prove, and C-77/213 shows how narrow the finding then is.
The Court held that purpose limitation does not preclude copying data into a test database where the further processing is compatible with the purposes of the original collection, compatibility being tested against the Article 6(4) criteria, and it located the infringement in Article 5(1)(e) alone, for keeping the copy longer than the tests required.
UU Pasal 42 ayat (1) is an express wajib with a named trigger, so nothing has to be reconstructed from principle. Article 5(1)(e) fixes no period at all, and what makes it auditable is the disclosure duty at Article 13(2)(a) and the envisaged erasure time limits recorded under Article 30(1)(f), while Pasal 42 ayat (1) huruf a points at a masa retensi that PP Pasal 75 turns into a standing policy document, a heavier artefact than anything the GDPR names.
The third trigger is the real divergence: Pasal 42 ayat (1) huruf c reads as an unqualified subject request, whereas GDPR request grounds are closed at Article 17(1) and cut down further by Article 17(3), so the Indonesian text is broader on its face and narrowed only by the reference back to legislation at ayat (2).
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 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.
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.
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 5(1)(b) and 5(1)(e). Read it on GDPRhub
Cited in its commentary on Article 17(1) and 17(3). Read it on GDPRhub
The Lembaga. No decision of the Lembaga exists, because it has not been established (CNBC Indonesia, 16 September 2026).