Right to correct data
Pasal 6
Subjek Data Pribadi berhak melengkapi, memperbarui, dan/atau memperbaiki kesalahan dan/atau ketidakakuratan Data Pribadi tentang dirinya sesuai dengan tujuan pemrosesan Data Pribadi.
Official copy: salinan p. 5
Implemented by PP 33/2026 Pasal 70 to 73.
Subjek Data Pribadi berhak melengkapi, memperbarui, dan/atau memperbaiki kesalahan dan/atau ketidakakuratan Data Pribadi tentang dirinya sesuai dengan tujuan pemrosesan Data Pribadi.
Ayat (1) Cukup jelas. Ayat (2) Cukup jelas. Ayat (3) Yang dimaksud dengan "terverifikasi" merupakan hasil penilaian atas permohonan Subjek Data Pribadi sesuai dengan ketentuan dalam Peraturan Pemerintah ini. Ayat (4) Cukup jelas. Ayat (5) Cukup jelas. Ayat (6) Cukup jelas. Ayat (7) Cukup jelas.
Ayat (1) Cukup jelas. Ayat (2) Yang dimaksud dengan "dianggap tidak memungkinkan atau melibatkan upaya yang tidak seimbang" antara lain langkah upaya penyampaian pembaruan membutuhkan waktu dan sumber daya yang tidak proporsional secara signifikan apabila diberitahukan kepada Pengendali Data Pribadi lain. Contoh:
Ketentuan lebih lanjut mengenai pelengkapan, pembaruan, dan/atau perbaikan Data Pribadi diatur dalam Peraturan Lembaga.
PP Pasal 70 to 73 operationalise completion, updating and correction, and Pasal 72 extends the duty through to other controllers and processors holding the same data. Without that flow-through the right would end at the first controller, which is the practical failure the provision is drafted against.
aligned with the GDPRGDPR Articles 16 and 19
What the GDPR provides. GDPR Article 16 gives the data subject the right to obtain rectification of inaccurate personal data without undue delay, and to have incomplete data completed, including by a supplementary statement, having regard to the purposes of the processing. Accuracy is also a standing controller duty under Article 5(1)(d), which requires reasonable steps to erase or rectify inaccurate data without delay.
Article 19 then makes the controller communicate every rectification to each recipient of the data, unless that proves impossible or involves disproportionate effort, and tell the data subject who those recipients are on request.
UU Pasal 6 reaches the same two acts as GDPR Article 16, correction of inaccuracy and completion of what is incomplete, but it does not track the article's shape: the limbs run in the reverse order, memperbarui is added as a third act, and the purpose qualifier closes the whole right where GDPR Article 16 attaches it only to the completion limb.
That qualifier decides more than it looks: in C-434/163 the Court measured accuracy against the purpose of the data to hold that rectification reaches the record of what a candidate wrote, not the correctness of the answers. Memperbarui is not a separate act in the EU right, because keeping data up to date sits in the GDPR Article 5(1)(d) duty and runs without any request.
Indonesia has the same standing duty rather than lacking one: UU Pasal 16 ayat (2) huruf d requires data to be mutakhir, and UU Pasal 29 makes accuracy, completeness and consistency a continuing obligation backed by verification. On timing the UU is the harder instrument.
GDPR Article 16 says without undue delay; UU Pasal 30 ayat (1) gives 3 x 24 hours from receipt of the request, and ayat (2) requires the controller to tell the subject the result. The GDPR Article 19 function is the one piece the statute does not carry, since UU Pasal 30 ayat (2) notifies the subject and not the recipients.
PP Pasal 72 supplies it, with ayat (1) reaching other controllers and processors and ayat (2) carrying the impossible-or-disproportionate-effort escape, but nothing there answers to the second sentence of GDPR Article 19, the right to be told who the recipients are.
PP Pasal 71 adds two things the EU right does not have on either side: a supplementary note at ayat (4) where replacement is impossible, which is close to the GDPR Article 16 supplementary statement, and a power to refuse the request at ayat (5), which GDPR Article 16 does not give.
On burden, C-460/204 placed on the person asserting inaccuracy the duty to show it, at least in the de-referencing setting, which is the allocation UU Pasal 6 leaves open.
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 65 national decisions since 25 May 2018, from 14 countries, as citing Article 16; most come from Italy (13), Belgium (9) and Lithuania (8). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.
The DPO tags 32 national decisions since 25 May 2018, from 12 countries, as citing Article 19; most come from Italy (8), Greece (7) and Lithuania (3). 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 whole commentary on Article 16. Read it on GDPRhub
Cited in its whole commentary on Article 19. Read it on GDPRhub
The Lembaga. No decision of the Lembaga exists, because it has not been established (CNBC Indonesia, 16 September 2026).