Prohibition on falsifying data
Pasal 66
Setiap Orang dilarang membuat Data Pribadi palsu atau memalsukan Data Pribadi dengan maksud untuk menguntungkan diri sendiri atau orang lain yang dapat mengakibatkan kerugian bagi orang lain.
Official copy: salinan p. 30
PP 33/2026 has no article implementing this one. The reading below says what that leaves.
UU Pasal 66 forbids making or falsifying personal data with intent to benefit oneself or another where it may cause another loss, and the PP has no counterpart. It reaches false data only through the controller or processor holding it, whose accuracy duty at PP Pasal 69, applied to processors by PP Pasal 140, is sanction-backed. UU Pasal 57 ayat (1) attaches no administrative sanction to the prohibition itself, and its penalty sits in UU Pasal 68.
diverges from the GDPRGDPR Articles 4, 5, 16 and 84
What the GDPR provides. The GDPR has no offence of fabricating data about another person, but it does not leave the fabricator outside its scope. Recording personal data is processing under Article 4(2), so a person who writes down invented data about another is a controller of it under Article 4(7) and needs a legal basis under Article 6(1), unless Article 2(2)(c) puts the act in the purely personal or household sphere.
Article 5(1)(d) requires personal data to be accurate and, where necessary, kept up to date, and Article 16 gives the data subject a right to rectification without undue delay against the controller. Article 4(12) treats alteration of personal data, accidental or unlawful, as a personal data breach, but only where it follows a breach of security.
The GDPR reaches the forger. What differs is what it can do to him. A person who records invented data about another is processing personal data under Article 4(2), and outside the household sphere in Article 2(2)(c) he is its controller under Article 4(7), so he needs a legal basis under Article 6(1) and is bound by Article 5(1)(a) and Article 5(1)(d).
What the GDPR lacks is a criminal grip: his exposure is an administrative fine and a rectification claim under Article 16, not a prosecution. UU Pasal 66 states the wrong as an offence with two limbs, intent to benefit and risk of loss to another, and asks nothing about whether the forger is a controller. The second real difference is the trigger for a controller who receives the forged record.
Article 4(12) reaches it only where there was a breach of security, so a forged form filed with a bank is a data quality problem under Article 5(1)(d) and not a notifiable breach under Article 33. In Europe the criminal charge is forgery or fraud under the ordinary criminal code, a field the Regulation does not occupy, so the comparison worth drawing in the tracker is UU Pasal 66 against those codes rather than against the GDPR.
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 417 national decisions since 25 May 2018, from 27 countries, as citing Article 4; most come from Austria (78), Lithuania (63) and Denmark (41). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.
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 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.
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 4(2), 4(7) and 4(12). Read it on GDPRhub
Cited in its commentary on Article 5(1)(a) and 5(1)(d). Read it on GDPRhub
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).