Powered by
The UU PDP wiki
Salinan v5.8 · 28 Sep 2026
BAB VIKEWAJIBAN PENGENDALI DATA PRIBADI DAN PROSESOR DATA PRIBADI DALAM PEMROSESAN DATA PRIBADI

Pasal 29 UU PDP

Accuracy and verification

sanctioned by Pasal 57 ayat (1)awaiting a Peraturan Lembaga

1Legal text

Pasal 29

(1)
Pengendali Data Pribadi wajib memastikan akurasi, kelengkapan, dan konsistensi Data Pribadi sesuai dengan ketentuan peraturan perundang-undangan.
(2)
Dalam memastikan akurasi, kelengkapan, dan konsistensi Data Pribadi sebagaimana dimaksud pada ayat (1) Pengendali Data Pribadi wajib melakukan verifikasi.

Official copy: salinan p. 13

2Implementing regulation

Implemented by PP 33/2026 Pasal 69.

PP Pasal 69Pengendali Data Pribadi wajib memastikan akurasi, kelengkapan,…sanction listPeraturan Lembaga
repeats UU Pasal 29
(1)
Pengendali Data Pribadi wajib memastikan akurasi, kelengkapan, dan konsistensi Data Pribadi sesuai dengan ketentuan peraturan perundang-undangan.
what the PP adds
(2)
Dalam memastikan akurasi, kelengkapan, dan konsistensi Data Pribadi sebagaimana dimaksud pada ayat (1), Pengendali Data Pribadi wajib melakukan verifikasi.
(3)
Dalam melaksanakan kewajiban melakukan verifikasi sebagaimana dimaksud pada ayat (2), Pengendali Data Pribadi terlebih dahulu menentukan mekanisme dan/atau standar penerapan kualitas data.
(4)
Verifikasi sebagaimana dimaksud pada ayat (2) dilakukan secara berkala dan/atau sewaktu-waktu sesuai dengan ketentuan peraturan perundang-undangan.
(5)
Verifikasi sebagaimana dimaksud pada ayat (2) dilakukan paling sedikit terhadap:
  1. a.
    tingkat kebenaran dan/atau ketepercayaan Data Pribadi;
  2. b.
    kelengkapan Data Pribadi yang dibutuhkan untuk memenuhi tujuan pemrosesan Data Pribadi;
  3. c.
    jenis atau keseragaman bentuk, tipe, atau format Data Pribadi yang dapat diterima oleh Pengendali Data Pribadi; dan
  4. d.
    kebutuhan Pengendali Data Pribadi untuk melakukan verifikasi Data Pribadi secara berkala.
(6)
Dalam hal proses verifikasi membutuhkan pemrosesan Data Pribadi, Pengendali Data Pribadi wajib menerapkan Pelindungan Data Pribadi sesuai dengan ketentuan peraturan perundang-undangan.
(7)
Dalam melakukan verifikasi sebagaimana dimaksud pada ayat (2), Pengendali Data Pribadi dapat bekerja sama dengan Pengendali Data Pribadi lain.
(8)
Pengendali Data Pribadi mendokumentasikan hasil verifikasi Data Pribadi sebagaimana dimaksud pada ayat (2).
(9)
Ketentuan lebih lanjut mengenai pelaksanaan verifikasi diatur dalam Peraturan Lembaga.
its elucidation

Ayat (1) Yang dimaksud dengan "akurasi" merupakan kualitas data yang menunjukan tingkat kebenaran/kepercayaan antara satu Informasi dengan sumber Informasi lain yang telah ditentukan adalah benar. Yang dimaksud dengan "kelengkapan" merupakan kualitas data yang menunjukan sejauh mana tingkat data memiliki semua atribut data yang dibutuhkan untuk suatu tujuan tertentu. Yang dimaksud dengan "konsistensi" merupakan kualitas data yang menunjukan tingkat kesamaan Informasi dengan Informasi lainnya yang sejenis. Ayat (2) Cukup jelas. Ayat (3) Cukup jelas. Ayat (4) Cukup jelas. Ayat (5) Huruf a Cukup jelas. Huruf b Contoh: Dalam registrasi pelanggan jasa telekomunikasi, verifikasi kelengkapan Data Pribadi antara lain nomor induk kependudukan dan nomor kartu keluarga. Huruf c Cukup jelas. Huruf d Cukup jelas. Ayat (6) Verifikasi yang membutuhkan pemrosesan Data Pribadi, misalnya dalam hal Pengendali Data Pribadi melakukan verifikasi membutuhkan pemrosesan data tambahan yang diperoleh dari Subjek Data Pribadi dan/atau pihak lainnya, Pengendali Data Pribadi wajib menerapkan Pelindungan Data Pribadi terhadap pemrosesan data tambahan tersebut. Ayat (7) Cukup jelas. Ayat (8) Cukup jelas. Ayat (9) Cukup jelas.

Read it in the regulationsalinan p. 34

3Commentary

3.1How the regulation implements it

PP Pasal 69 requires accuracy, completeness and consistency and adds a verification duty, sanction-backed at Pasal 69(1) and (2). Verification is left to a Peraturan Lembaga for its standard, so the duty is enforceable while the benchmark against which it will be judged is not yet fixed.

3.2Where the GDPR stands

diverges from the GDPRGDPR Articles 5 and 16

What the GDPR provides. GDPR Article 5(1)(d) requires personal data to be accurate and, where necessary, kept up to date. The duty is framed as an obligation of means: every reasonable step must be taken to erase or rectify inaccurate data without delay, having regard to the purposes for which it is processed. There is no standalone duty to verify, and completeness and consistency are not named as separate qualities.

Article 16 supplies the subject-driven counterpart, including completion of incomplete data by a supplementary statement.

Article 5(1)(d) is purpose relative, so the reasonable steps to erase or rectify are measured against what the data is used for. C-434/163 is the clearest statement of that logic, holding that a candidate's written answers at a professional examination are personal data whose accuracy is assessed for what the record is, not for whether the answers were correct.

UU Pasal 29 ayat (1) carries no such qualifier and adds kelengkapan and konsistensi as duties in their own right, and ayat (2) converts a standard into a process by making verification freestanding. That inverts the burden of design: an EU controller argues that no reasonable step was called for here, while an Indonesian controller has to show the verification happened, and UU Pasal 57 ayat (1) lists Pasal 29 among the provisions carrying administrative sanction.

The benchmark is not blank. PP Pasal 69 ayat (3) makes the controller fix the mechanism or data quality standard first, ayat (5) sets a floor of four things every verification must reach, the truth or trustworthiness of the data, its completeness against the purpose, uniformity of form or format, and how often verification is needed, ayat (4) makes it periodic or ad hoc, and ayat (8) requires the result to be documented.

What ayat (9) defers to a Peraturan Lembaga is implementation, so the open question is how a regulator will test a controller's own standard, not what the duty covers.

4Decisions and guidance

Court of Justice of the EU

  • C-434/16Peter Nowak v Data Protection Commissioner20 December 2017

National supervisory authorities

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.

Article 5 GDPRPrinciples relating to processing of personal data5 of 1,976 decisions

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.

Article 16 GDPRRight to rectification5 of 65 decisions

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.

Cited on GDPRhub

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.

Article 5 GDPRPrinciples relating to processing of personal data1 judgment

Cited in its commentary on Article 5(1)(d). Read it on GDPRhub

Article 16 GDPRRight to rectification1 judgment

Cited in its whole commentary on Article 16. Read it on GDPRhub

The Lembaga. No decision of the Lembaga exists, because it has not been established (CNBC Indonesia, 16 September 2026).

5Cross-references

Referred to by

6Sources

  1. 1UU 27/2022, salinan, p. 13.
  2. 2PP 33/2026, salinan: Pasal 69 at p. 34.
  3. 3Case C-434/16 Peter Nowak v Data Protection Commissioner, 20 December 2017, ECLI:EU:C:2017:994. EUR-Lex.↑
  4. 4EDPB, Guidelines 4/2019 on Article 25 Data Protection by Design and by Default. EDPB.
  5. 5GDPRhub (noyb), commentary on Article 5 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.
  6. 6GDPRhub (noyb), commentary on Article 16 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.