Records of processing activities
Pasal 31
Pengendali Data Pribadi wajib melakukan perekaman terhadap seluruh kegiatan pemrosesan Data Pribadi.
Official copy: salinan p. 14
Implemented by PP 33/2026 Pasal 74 and 75.
Ayat (1) Yang dimaksud dengan "perekaman terhadap seluruh kegiatan pemrosesan Data Pribadi" merupakan catatan yang memuat inventaris dan pemetaan aliran data dari pemrosesan Data Pribadi. Ayat (2) Huruf a Cukup jelas. Huruf b Cukup jelas. Huruf c Cukup jelas. Huruf d Cukup jelas. Huruf e Cukup jelas. Huruf f Cukup jelas. Huruf g Cukup jelas. Huruf h Pihak selain Pengendali Data Pribadi antara lain Kementerian/Lembaga atau pihak ketiga. Huruf i Cukup jelas. Huruf j Cukup jelas. Huruf k Cukup jelas. Huruf l Cukup jelas. Huruf m Cukup jelas. Ayat (3) Cukup jelas. Ayat (4) Cukup jelas. Ayat (5) Cukup jelas. Ayat (6) Pengelolaan hasil perekaman kegiatan pemrosesan Data Pribadi merupakan proses pengendalian hasil perekaman kegiatan pemrosesan Data Pribadi secara efisien, efektif, dan sistematis meliputi penciptaan, penggunaan dan pemeliharaan, serta penyusutan hasil perekaman kegiatan pemrosesan Data Pribadi. Ayat (7) Cukup jelas. Ayat (8) Cukup jelas. Ayat (9) Cukup jelas. Ayat (10) Cukup jelas.
Ayat (1) Cukup jelas. Ayat (2) Cukup jelas. Huruf a Cukup jelas. Huruf b Yang dimaksud dengan "ketentuan Masa Retensi arsip dan ketentuan lainnya" antara lain ketentuan peraturan perundang-undangan, ketentuan yang ada di masing-masing sektor. Huruf c Cukup jelas. Huruf d Cukup jelas. Huruf e Cukup jelas. Huruf f Cukup jelas. Huruf g Cukup jelas. Huruf h Cukup jelas. Huruf i Cukup jelas. Huruf j Cukup jelas.
PP Pasal 74 requires records of all processing activities and Pasal 75 requires a documented retention policy, sanction-backed at Pasal 74(1). The PP carries no equivalent of the GDPR Article 30(5) exemption for organisations under 250 staff, so the duty falls on every controller regardless of scale.
diverges from the GDPRGDPR Article 30
What the GDPR provides. GDPR Article 30 requires a written register, not a log. A controller records the purposes of processing, the categories of data subjects and of personal data, the categories of recipients, transfers to third countries with the safeguards relied on, the envisaged erasure time limits where possible, and a general description of the security measures.
Article 30(2) sets a shorter list for processors, and Article 30(4) makes the register available to the supervisory authority on request. Article 30(5) exempts an organisation employing fewer than 250 persons unless the processing is likely to risk rights and freedoms, is other than occasional, or covers special category or criminal conviction data.
Two differences run here, and the exemption is only the visible one. GDPR Article 30(5) lets an enterprise or organisation employing fewer than 250 persons keep no register, but the relief falls away where the processing is not occasional, where it is likely to result in a risk to rights and freedoms, or where it covers special category or criminal conviction data, and it lifts the register duty alone rather than anything else in the Regulation.
The Indonesian text grants no relief at any size. The second difference is what is being recorded. GDPR Article 30 is an inventory of processing operations, written once and kept current, whereas perekaman terhadap seluruh kegiatan pemrosesan reads naturally as capturing every processing event, which is a duty of a different order and cost.
PP Pasal 74 ayat (2) settles that as an inventory of thirteen fields, and huruf k already carries Masa Retensi, which is the envisaged erasure time limit that GDPR Article 30(1)(f) folds into the register, with PP Pasal 75 adding a separate retention policy document on top.
The role split survives, but by a different route: GDPR Article 30(2) binds the processor in its own name and GDPR Article 30(4) puts the register in front of the supervisory authority on request, while PP Pasal 74 ayat (3) and ayat (5) make the Pengendali ensure the Prosesor records and prescribe the shorter processor list, so the processor duty runs through the controller rather than directly.
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 33 national decisions since 25 May 2018, from 13 countries, as citing Article 30(1), 30(2), 30(4) and 30(5); most come from Belgium (11), Poland (5) and Luxembourg (5). 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).