Scope and principles of processing
Pasal 16
Official copy: salinan p. 8
Yang dimaksud dengan "penampilan" adalah perbuatan memperlihatkan Data Pribadi untuk tujuan tertentu dan pihak-pihak tertentu.
Yang dimaksud dengan "pengumuman" adalah pemberitahuan sebuah Informasi yang ditujukan kepada orang banyak dan bersifat umum.
Yang dimaksud dengan "transfer" adalah perpindahan, pengiriman, dan/atau penggandaan Data Pribadi baik secara elektronik maupun nonelektronik dari Pengendali Data Pribadi kepada pihak lain.
Implemented by PP 33/2026 Pasal 8, 9 and 58 to 60.
Ayat (3) delegates the detail on carrying out processing to a government regulation, now PP 33/2026. PP Pasal 73 and 89 pass it down again to a Peraturan Lembaga.
Pemrosesan Data Pribadi meliputi:
Pemrosesan Data Pribadi sebagaimana dimaksud dalam Pasal 8 dilakukan sesuai dengan prinsip Pelindungan Data Pribadi meliputi:
Pengendali Data Pribadi wajib melakukan pemrosesan Data Pribadi secara terbatas dan spesifik, sah secara hukum, dan transparan.
Yang dimaksud dengan "sah secara hukum" adalah pemrosesan Data Pribadi dilakukan sesuai dengan ketentuan peraturan perundang-undangan.
Ayat (1) Cukup jelas. Ayat (2) Yang dimaksud dengan "secara jujur dan iktikad baik" antara lain Pengendali Data Pribadi dalam melakukan pemrosesan Data Pribadi memberikan Informasi yang benar, tanpa tipu daya, dan/atau tidak menyesatkan kepada Subjek Data Pribadi, termasuk dalam memenuhi hak Subjek Data Pribadi dan melakukan kewajiban Pengendali Data Pribadi.
PP Pasal 8 fixes the processing cycle and Pasal 58 to 60 give the limited, specific and transparent standard its operative content. The delegation in UU Pasal 16(3) is thereby discharged, with data minimisation at Pasal 59 carrying most of the practical weight.
diverges from the GDPRGDPR Articles 4 and 5
What the GDPR provides. GDPR Article 4(2) defines processing as any operation performed on personal data and gives an open list, running from collection and storage through disclosure to erasure, so nothing turns on whether a given activity is named. Article 5(1) binds all processing to six principles: lawfulness, fairness and transparency; purpose limitation; data minimisation; accuracy; storage limitation; and integrity and confidentiality.
Article 5(2) adds accountability, making the controller responsible for compliance and able to demonstrate it. Lawful bases are not in Article 5 at all; they are the closed list in Article 6.
The eight principles in UU Pasal 16 ayat (2) reach much of GDPR Article 5 by a different arrangement. Limits, specificity, lawfulness and transparency are folded into huruf a, and retention and erasure into huruf g. Two of the eight have no GDPR principle behind them: guaranteeing the subject's rights at huruf c, and notifying purpose, activities and breach at huruf f.
The GDPR carries both as duties, in GDPR Article 13, GDPR Article 14, GDPR Article 33 and GDPR Article 34, rather than as principles binding every act of processing. The item that is not there is fairness. In EU practice fairness is the hook that catches processing which is lawful and transparent yet still exploits an imbalance or a designed-in nudge, and EDPB Guidelines 03/20224 are built on it.
Huruf c and huruf h are the nearest equivalents in the statute, but both point at compliance with rules stated elsewhere rather than at the quality of a design that complies, so the statute has no open standard of the GDPR Article 5(1)(a) kind for a regulator to reach for.
The regulation comes closest: PP Pasal 60 ayat (2) requires transparent processing to be carried out honestly and in good faith, and its elucidation, open-ended with antara lain, reaches deceit and misleading information and the fulfilment of rights and duties. Ayat (1) also differs in kind from GDPR Article 4(2).
The GDPR list is open on its face because it reads such as, while ayat (1) enumerates six activities and PP Pasal 8 repeats the same six, so on the more natural reading the burden of arguing that an unnamed activity is processing falls the opposite way in Jakarta, even if letter b is wide enough to absorb most of it.
The lawful bases that the tracker's existing note assigns here are real but misfiled: they sit at UU Pasal 20, not at Pasal 16.
Commentary on each ayat, a pilot on this article and on Pasal 20, Pasal 46 and Pasal 56. Every citation in it was checked against the source it cites.
Ayat (1) names six groups of activity that count as processing. They are joined by dan/atau, so each is processing on its own, and storage under huruf c is enough: data held and never used still need a basis under UU Pasal 20 ayat (1) and must meet the principles in ayat (2). Article 4(2) GDPR also names storage, and the CJEU treats recording stored data in a new database as further processing (C-77/215, paras 29 and 30).
PP Pasal 8 repeats the list without adding an activity, and the list returns later as a checklist. The elucidation to PP Pasal 138 ayat (2) huruf b reads the duty to document all processing as covering these six activities, so ayat (1) also sets the frame of the record a controller keeps to show accountability under ayat (2) huruf h.
The elucidation to huruf e defines three of its terms. Penampilan shows data for a given purpose to given parties. Pengumuman is information addressed to many people and general in character. Transfer is the movement, sending or copying of data, electronic or not, from the controller to another party. On that definition a backup placed with a vendor is a transfer, although the controller keeps the original.
The definitions separate publication from transfer without making them exclusive, since a publication usually copies data to a host and to every reader. UU Pasal 56 governs transfer abroad, and PP Pasal 160 ayat (3) asks whether a controller makes data available to a receiving controller or processor outside Indonesia. On its words that test can be met when a controller abroad collects from a public page.
Under Directive 95/46 the CJEU held that an individual in a Member State who loaded data onto a web page stored with a host established in the Union made no transfer to a third country, although anyone abroad could read it (C-101/016, para 71). The Court reasoned from the Directive's transfer chapter, which would otherwise have governed the whole internet, and not from a difference between publication and transfer (paras 68 and 69).
Whether a publication hosted in Indonesia and read abroad falls under the cascade in UU Pasal 56 is therefore open. Treating it as pengumuman that needs a basis under UU Pasal 20 but not the cascade is an inference from a case the EDPB describes as decided under the former Directive (Guidelines 05/20217, p. 6, note 8). No Indonesian text or decision settles it.
Ayat (2) binds every act of processing in ayat (1) to eight principles, which PP Pasal 9 restates. The regulation then gives most of them a section of their own in BAB IV, from PP Pasal 58 on limited and specific processing to PP Pasal 138 on accountability. The statute repeats several as controller duties, among them UU Pasal 27, UU Pasal 28, UU Pasal 29 and UU Pasal 47.
Read with UU Pasal 20 ayat (1), ayat (2) sets a double test: every processing needs a basis and must meet all eight principles. The CJEU reads the GDPR the same way. Any processing must comply with the principles in Article 5 GDPR and satisfy one of the conditions of lawfulness in Article 6 GDPR (C-77/215, para 49).
The principles carry no sanction of their own. UU Pasal 57 ayat (1) lists the duty forms but not UU Pasal 16, and PP Pasal 184 ayat (1) lists PP Pasal 58 but not PP Pasal 9. Article 83(5)(a) GDPR, by contrast, fines a breach of Article 5 GDPR directly.
A principle that says more than its duty form, as huruf d does with not misleading, reaches the sanction list through accountability. UU Pasal 47, which UU Pasal 57 ayat (1) lists, binds the controller to show that it has carried out the principles, and PP Pasal 184 ayat (1) lists PP Pasal 138 ayat (1), which repeats it. The surplus is enforceable only as a failure of accountability, a longer route than the direct fine in the GDPR.
Huruf a sets four standards for collection. The duty form in UU Pasal 27, repeated by PP Pasal 58, applies them to all processing, and the elucidation to PP Pasal 58 reads sah secara hukum as processing in accordance with the laws and regulations. PP Pasal 59 turns limited and specific into minimisation, weighed by the data's link to the purpose, their sufficiency, and not exceeding what the purpose needs.
Those three factors track Article 5(1)(c) GDPR: adequate, relevant and limited to what is necessary. The CJEU also reads minimisation as a limit in time, requiring the period of collection to be kept to what is strictly necessary for the objective of the processing (C-446/218, para 52). PP Pasal 59 names no time factor, so duration is left to the retention rules under huruf g.
PP Pasal 60 ayat (1) defines transparency as the subject knowing which data are processed and how, through accessible, understandable information in clear language. PP Pasal 60 ayat (2) requires transparent processing to be carried out honestly and in good faith. Its elucidation gives true information, no deceit and nothing misleading as examples, introduced by antara lain, and extends the standard to the fulfilment of rights and duties.
The EDPB reads fairness under Article 5(1)(a) GDPR as barring processing that is unjustifiably detrimental, unlawfully discriminatory, unexpected or misleading (Guidelines 4/20199, para 69). The elucidation's examples meet the last of these, good faith can reach further, and PP Pasal 184 ayat (1) reaches it through PP Pasal 58. Although it is tied to the transparency duty rather than to all processing, it is the nearest the PP comes to a fairness principle.
Huruf b requires processing to follow its purpose, and UU Pasal 28 states the duty. The elucidation to UU Pasal 27 requires the purpose to be explicit, legitimate and fixed at collection. PP Pasal 67 ayat (2) limits it to a specific aim conveyed to the subject explicitly and firmly, weighed against the subject's interests. PP Pasal 68 requires the purpose and its changes to be documented in internal policy and in the privacy notice.
The CJEU reads Article 5(1)(b) GDPR the same way at the start: purposes are identified at the latest at collection and stated clearly (C-77/215, para 27). The two systems part at further use. Article 6(4) GDPR sets a compatibility test for a new purpose. PP Pasal 67 ayat (4) instead sends an added or new purpose back to the whole regulation, including prior notice of the change under PP Pasal 62 ayat (5).
There is no compatibility route in the Indonesian text. A further use closely tied to the original purpose gets no easier treatment under PP Pasal 67 ayat (4) than an unrelated one. That covers the kind of system testing that the CJEU, guiding the referring court, described as specifically linked to the subscription contracts in C-77/21 (para 44).
Huruf c makes respect for the subject's rights a condition of processing itself. The rights sit in UU Pasal 5 to UU Pasal 13, and UU Pasal 14 routes those in UU Pasal 6 to UU Pasal 11 through a recorded request. PP Pasal 20 to PP Pasal 27 give every right a common procedure: an accessible channel, receipt rules, proportionate verification, and a report to the Lembaga when the controller does not act.
PP Pasal 24 ayat (2) requires every request to attach proof of identity, and PP Pasal 25 asks for verification by a proportionate mechanism. The elucidation to PP Pasal 24 ayat (1) huruf a accepts an official identity or another identity suited to the purpose of processing. That leaves room for the EDPB's approach, which treats a copy of an identity document as disproportionate where the controller has already authenticated the person asking (Guidelines 01/202210, para 73).
PP Pasal 26 lets the controller set the conditions for granting or refusing a request, within the laws and regulations. For some rights the PP fixes the grounds itself, in PP Pasal 77 ayat (4), PP Pasal 95 ayat (1) and PP Pasal 99 ayat (2). Article 12(2) and Article 12(5) GDPR fix the general grounds for refusal in the law and put the burden of showing them on the controller.
Where the PP fixes no grounds, the terms of the guarantee in huruf c are set by the party it binds, and the check on them is a report to the Lembaga under PP Pasal 27.
Huruf d requires processing that is accurate, complete, not misleading, current and accountable. PP Pasal 69 requires the controller to ensure accuracy, completeness and consistency, to verify them against a data-quality standard it sets itself, periodically or at any time, and to document the results. PP Pasal 71 ayat (1) requires correction within 3x24 hours of a request, after verification, and PP Pasal 71 ayat (5) and ayat (7) let the controller refuse, giving reasons.
Five qualities in the principle become three in the duty. UU Pasal 29 ayat (1) and PP Pasal 69 ayat (1) name accuracy, completeness and consistency, and consistency is new. Beyond the restatement in PP Pasal 9, the regulation never uses not misleading or current as qualities of the data; currency is reached through verification or a subject's request under PP Pasal 70.
The elucidation to PP Pasal 69 ayat (1) measures accuracy against another source already determined to be true. Article 5(1)(d) GDPR measures it against the purposes of processing and requires every reasonable step to rectify or erase inaccurate data without delay. On the Indonesian definition, data that match a wrong reference record still count as accurate, and the purpose returns only through the subject's right to correct errors under PP Pasal 70.
Huruf e requires processing that protects data against unauthorised access, disclosure and alteration, misuse, destruction and loss, and UU Pasal 35 states the duty. PP Pasal 123 ayat (1) repeats it, and its elucidation reads security as confidentiality, availability and integrity. PP Pasal 123 ayat (2) lists pseudonymisation and encryption, resilience, timely restoration after an incident and regular testing, the four measures of Article 32(1) GDPR.
PP Pasal 124 adds protection by design, from planning a system to operating it, weighed by technology, cost, nature, scope, context, purpose and risk, the formula of Article 25(1) GDPR. PP Pasal 124 ayat (2) huruf b requires minimisation by default, as Article 25(2) GDPR does. The controller sets its security level under PP Pasal 123 ayat (4), and PP Pasal 123 ayat (7) has the Lembaga draw up the technical steps and the method for setting levels.
Neither instrument says whether a breach proves that the measures failed. The CJEU holds that unauthorised disclosure or access by a third party does not in itself show the measures were inappropriate, because Article 32 GDPR manages risk rather than removing it (C-340/2111, paras 29 and 39). In a damages action the controller must still prove that they were appropriate (operative part, point 3).
The risk-based wording of PP Pasal 123 ayat (1) huruf b and PP Pasal 123 ayat (4) supports the first of these rulings, but neither is settled in Indonesia.
Huruf f requires processing to be carried out with notice of its purpose and activities and of any failure of protection. PP Pasal 62 ayat (1) lists seven items of information, ayat (4) requires them before processing begins, and ayat (5) requires notice before any change. The breach limb is carried by PP Pasal 114 to PP Pasal 119 under UU Pasal 46.
The notice need not reach the subject in person. The elucidations to PP Pasal 62 ayat (3) and PP Pasal 64 accept a general notice through electronic or non-electronic media. For data obtained indirectly, PP Pasal 64 allows 30 Hari after collection, and a Hari is a working day under PP Pasal 1 angka 19. Article 14(3)(a) GDPR sets one month as the outer limit (WP260 rev.0112, para 28).
Article 14(5)(b) GDPR allows the information to be made public only where individual notice is impossible or would take disproportionate effort. On the PP's text, a controller that buys a list may wait some six weeks and then meet the duty with a published notice.
Huruf g requires data to be destroyed or erased when the retention period ends or at the subject's request, unless other law provides otherwise. PP Pasal 1 angka 23 defines the retention period by the purpose or another legal obligation, and PP Pasal 75 requires a written retention policy. PP Pasal 82 and PP Pasal 84 set the duties to erase and to destroy that UU Pasal 43 and UU Pasal 44 state.
The two words differ. PP Pasal 82 ayat (4) measures erasure by who can still reach the data, no one but the controller, although its elucidation speaks of deletion from systems and backups. Destruction under PP Pasal 84 ayat (2), and in the elucidation to UU Pasal 44 ayat (1), leaves data unable to identify the subject. Huruf g joins the two with dan/atau, so erasure alone satisfies it.
Article 5(1)(e) GDPR limits how long data may be kept in a form that identifies the subject. The CJEU reads it to mean that data first processed lawfully must be erased once their purposes are served (C-77/215, para 54). Measured by identifiability, destruction in the PP meets that rule; erasure, on the text of PP Pasal 82 ayat (4), may leave the controller holding identifiable data.
Huruf h requires processing that is responsible and clearly demonstrable, and UU Pasal 47 states the duty. PP Pasal 138 ayat (2) sets the minimum: technical and organisational measures, documentation of all processing, answers to the Lembaga's requests, proof of compliance, and data protection audits both internal and external. PP Pasal 74 adds the record of processing activities.
Article 5(2) GDPR makes the controller responsible for the principles and able to demonstrate compliance, and the CJEU puts the burden of that proof on the controller (C-60/2213, para 53). The external audit in PP Pasal 138 ayat (2) huruf e goes further: the GDPR sets no general duty on controllers to commission one.
PP Pasal 184 ayat (1) sanctions PP Pasal 138 ayat (1) but not ayat (2), so the audit duty is enforced only as part of showing accountability. On the text it binds every controller, whatever its size.
Ayat (3) delegates the detail of carrying out the processing in ayat (1) to a government regulation. PP 33/2026 names this ayat among the ten delegations in its preamble, and it is the only one of them about processing at large: UU Pasal 20 and UU Pasal 46, for example, delegate nothing. PP Pasal 8 and PP Pasal 9 restate ayat (1) and ayat (2), and the rest of BAB III and BAB IV carry the detail.
The regulation was promulgated on 16 July 2026 and takes effect six months later, on 16 January 2027 (PP Pasal 225). Where it leaves the detail of processing to the Lembaga, PP Pasal 223 covers the wait: until the Peraturan Lembaga terkait pemrosesan Data Pribadi is set, controllers and processors carry out processing so far as it does not conflict with the PP. The PP sets no date by which that instrument must be issued.
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 2,056 national decisions since 25 May 2018, from 29 countries, as citing Article 5(1) and 5(2); most come from Italy (350), 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.
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). Read it on GDPRhub
Cited in its commentary on Article 5(1) and 5(2). Read it on GDPRhub
The Lembaga. No decision of the Lembaga exists, because it has not been established (CNBC Indonesia, 16 September 2026).