Lawful bases for processing
Pasal 20
Official copy: salinan p. 10
Yang dimaksud dengan "kepentingan vital Subjek Data Pribadi" adalah terkait dengan keberlangsungan hidup dari Subjek Data Pribadi misalnya ketika pemrosesan Data Pribadi diperlukan untuk tindakan perawatan medis serius.
Implemented by PP 33/2026 Pasal 30 to 57.
Ayat (1) Cukup jelas. Ayat (2) Cukup jelas. Ayat (3) Huruf a Cukup jelas. Huruf b Cukup jelas. Huruf c Cukup jelas. Huruf d Yang dimaksud dengan "kepentingan vital Subjek Data Pribadi" adalah terkait dengan keberlangsungan hidup dari Subjek Data Pribadi misalnya ketika pemrosesan Data Pribadi diperlukan untuk tindakan perawatan medis serius. Huruf e Cukup jelas. Huruf f Cukup jelas. Ayat (4) Cukup jelas.
Pengendali Data Pribadi harus memastikan pemrosesan Data Pribadi tidak bersifat diskriminatif kepada Subjek Data Pribadi.
Yang dimaksud dengan "bersifat diskriminatif" yaitu segala bentuk pembedaan, pengecualian, pembatasan, atau pemilihan berdasarkan pada ras dan etnis yang mengakibatkan pencabutan atau pengurangan pengakuan, perolehan, atau pelaksanaan hak asasi manusia dan kebebasan dasar dalam suatu kesetaraan di bidang sipil, politik, ekonomi, sosial, dan budaya sebagaimana diatur dalam peraturan perundang-undangan yang mengatur di bidang penghapusan diskriminasi.
Ayat (1) Cukup jelas. Ayat (2) Yang dimaksud dengan "ambigu" misalnya pemberian persetujuan pemrosesan Data Pribadi digabungkan dengan pemberian persetujuan terhadap syarat dan ketentuan sehingga Subjek Data Pribadi dianggap telah memberikan persetujuan atas pemrosesan Data Pribadi hanya dengan membaca syarat dan ketentuan.
Ayat (1) Cukup jelas. Ayat (2) Mekanisme perolehan persetujuan antara lain penyediaan kolom, laman, atau fitur persetujuan. Mekanisme perolehan persetujuan secara elektronik, misalnya penyediaan laman dari website Pengendali Data Pribadi untuk kemudian diberikan persetujuan oleh Subjek Data Pribadi melalui penandatanganan secara elektronik, pemberian fitur check box, atau fitur tanda persetujuan. Mekanisme perolehan persetujuan secara nonelektronik, misalnya penyediaan formulir untuk kemudian diberikan persetujuan oleh Subjek Data Pribadi melalui penandatanganan dan pemberian nama yang jelas. Ayat (3) Yang dimaksud dengan "terhubung dengan Informasi" adalah Informasi yang dibutuhkan oleh Subjek Data Pribadi dapat diakses dalam rangka memberikan pemahaman yang utuh terkait pemrosesan Data Pribadi sebelum Subjek Data Pribadi memberikan persetujuannya.
Ayat (1) Cukup jelas. Ayat (2) Huruf a Yang dimaksud dengan "Informasi pihak ketiga" antara lain identitas, tujuan penerimaan, dan jenis Data Pribadi. Huruf b Cukup jelas. Huruf c Cukup jelas. Ayat (3) Cukup jelas.
Ayat (1) Cukup jelas. Ayat (2) Yang dimaksud dengan "dalam rangka akuntabilitas pemrosesan Data Pribadi" antara lain untuk kepentingan pemenuhan kewajiban Pengendali Data Pribadi dan hak Subjek Data Pribadi atau dalam rangka pengawasan dari Lembaga.
Pengendali Data Pribadi harus memastikan pemenuhan hak Subjek Data Pribadi untuk menarik persetujuan sewaktu-waktu melalui mekanisme yang disediakan oleh Pengendali Data Pribadi.
Ayat (1) Cukup jelas. Ayat (2) Cukup jelas. Ayat (3) Cukup jelas. Ayat (4) Cukup jelas. Ayat (5) Cukup jelas. Ayat (6) Pada dasarnya, Anak memiliki hak-hak Subjek Data Pribadi yang diatur dalam Peraturan Pemerintah ini. Akan tetapi, pemenuhan terhadap hak tersebut harus didasarkan pada kemampuan Anak untuk memahami konsekuensi atau risiko dalam mengajukan permohonan untuk memenuhi hak tersebut. Oleh karena itu, Pengendali Data Pribadi perlu memahami kapasitas Anak dalam memahami konsekuensi atau risiko yang dimaksud. Dengan demikian, Pengendali Data Pribadi menyesuaikan usia Anak dengan produk dan layanan yang disediakan Pengendali Data Pribadi bagi Anak sesuai dengan peraturan perundang-undangan, sebagai bentuk pelaksanaan penilaian dampak Pelindungan Data Pribadi. Ayat (7) Dalam Peraturan Pemerintah ini, diatur bahwa pemrosesan Data Pribadi Anak wajib mendapatkan persetujuan dari orang tua Anak dan/atau wali Anak. Oleh karena itu, pemenuhan hak Anak terkait pemrosesan Data Pribadi Anak tetap memerlukan persetujuan dari orang tua Anak dan/atau wali Anak. Sebagai contoh, pemenuhan hak Anak terkait perubahan Data Pribadi berupa melengkapi, memperbarui, dan/atau memperbaiki kesalahan dan/atau ketidakakuratan Data Pribadi. Ayat (8) Cukup jelas.
Ayat (1) Dalam mengambil langkah untuk mengidentifikasi Penyandang Disabilitas, Pengendali Data Pribadi perlu memahami jenis Penyandang Disabilitas yang mengakses atau mungkin mengakses produk atau layanan yang diselenggarakannya dan memahami keterbatasan Penyandang Disabilitas dalam pengajuan permohonan hak Subjek Data Pribadi. Misalnya, Penyandang Disabilitas mental memiliki keterbatasan di dalam memahami risiko atau dampak hukum terkait persetujuan yang akan diberikannya atau perjanjian yang akan disepakatinya. Oleh karena itu, dalam hal Pengendali Data Pribadi memerlukan persetujuan dari Penyandang Disabilitas mental, maka Pengendali Data Pribadi tidak dapat meminta persetujuan tersebut langsung kepada Penyandang Disabilitas mental, tetapi wajib mendapat persetujuan dari wali Penyandang Disabilitas mental. Ayat (2) Cukup jelas. Ayat (3) Yang dimaksud dengan "prasarana" antara lain penyediaan fasilitas berupa bahasa isyarat, braille, dan komunikasi augmentatif. Ayat (4) Cukup jelas. Ayat (5) Cukup jelas. Ayat (6) Cukup jelas.
Pengendali Data Pribadi tidak dapat memuat atau mencantumkan klausul perjanjian yang mengalihkan tanggung jawab kepada Subjek Data Pribadi sesuai dengan ketentuan peraturan perundang-undangan.
Yang dimaksud dengan "ketentuan peraturan perundang-undangan" antara lain Undang-Undang mengenai perlindungan konsumen dan Undang-Undang mengenai pengembangan dan penguatan sektor keuangan.
Pengendali Data Pribadi dapat menggunakan dasar pemrosesan Data Pribadi berupa pemenuhan pelindungan kepentingan vital Subjek Data Pribadi dalam hal:
Huruf a Cukup jelas. Huruf b Kesulitan mendapatkan persetujuan antara lain meliputi keadaan di mana Subjek Data Pribadi tidak dalam keadaan sadar dan/atau terluka parah sehingga tidak mampu memberikan persetujuan terhadap pemrosesan Data Pribadi, wali dan/atau orang tua tidak mendampingi Subjek Data Pribadi untuk dapat memberikan persetujuan dalam hal Subjek Data Pribadi adalah Anak.
Ketentuan lebih lanjut mengenai pemenuhan pelindungan kepentingan vital Subjek Data Pribadi sebagai dasar pemrosesan Data Pribadi diatur dengan Peraturan Lembaga.
Ayat (1) Ruang lingkup pelaksanaan tugas dalam rangka kepentingan umum, pelayanan publik, atau pelaksanaan kewenangan ditentukan oleh peraturan perundang-undangan. Misalnya, penyediaan pelayanan publik yang mudah diakses oleh Penyandang Disabilitas sebagaimana dimaksud Undang-Undang mengenai Penyandang Disabilitas. Oleh karena itu, dasar pemrosesan Data Pribadi berdasarkan kepentingan umum, pelayanan publik, atau pelaksanaan kewenangan dilaksanakan sesuai maksud dan tujuan dari peraturan perundang-undangan yang dimaksud. Ayat (2) Cukup jelas.
Ketentuan lebih lanjut mengenai penggunaan pelaksanaan tugas dalam rangka kepentingan umum, pelayanan publik, atau pelaksanaan kewenangan sebagai dasar pemrosesan Data Pribadi diatur dalam Peraturan Lembaga.
Pengendali Data Pribadi dapat menggunakan dasar pemrosesan Data Pribadi berupa pemenuhan kepentingan yang sah lainnya dalam hal:
Pemenuhan kepentingan yang sah lainnya antara lain dalam rangka pemantauan keamanan, kesehatan, keselamatan, dan pencegahan kejahatan berdasarkan ketentuan peraturan perundang-undangan.
Hasil analisis dan penilaian sebagaimana dimaksud dalam Pasal 53 didokumentasikan oleh Pengendali Data Pribadi.
Ketentuan lebih lanjut mengenai penggunaan pemenuhan kepentingan yang sah lainnya sebagai dasar pemrosesan Data Pribadi diatur dalam Peraturan Lembaga.
PP Pasal 30 to 57 give each lawful basis its own paragraph, moving from a list in the statute to a set of conditions of use: explicit consent at Pasal 32 to 39, contract at 40 to 44, legal obligation at 45, vital interests at 46 to 48, public task at 49 to 52 and legitimate interests at 53 to 57.
The consequential change is at PP Pasal 55, which permits public bodies to rely on legitimate interests for purposes outside their public task, where the draft barred them outright. The second subparagraph of Article 6(1) GDPR bars the basis only for processing by public authorities in the performance of their tasks, so the enacted text lands close to the GDPR where the draft had been stricter.
ported from the GDPRGDPR Articles 5 and 6
What the GDPR provides. GDPR Article 6(1) makes processing lawful only where one of six bases applies: consent, necessity for a contract or for pre-contractual steps, a legal obligation, vital interests, a task in the public interest or official authority, and legitimate interests. The second subparagraph of GDPR Article 6(1) bars public authorities from relying on legitimate interests in the performance of their tasks.
GDPR Article 6(3) requires the legal obligation and public task bases to rest on Union or Member State law. GDPR Article 6(4) adds a compatibility test where data collected for one purpose are used for another, except where the further use rests on consent or on a Union or Member State measure.
UU Pasal 20 ayat (2) huruf a to f is the six limb list of GDPR Article 6(1)(a) to (f) in the same order, and the transposition shows in the detail.
Huruf b carries both contract performance and pre-contractual steps taken at the data subject's request, huruf c and huruf e carry the peraturan perundang-undangan anchor that answers GDPR Article 6(3), and huruf f writes the balancing factors into the statute where GDPR Article 6(1)(f) states the balance as an override clause.
Huruf d protects the vital interests of the Subjek Data Pribadi only, while GDPR Article 6(1)(d) also covers another natural person, which in the EU is what makes the basis usable in an emergency involving a third party. PP Pasal 46 supplies that case by regulation and goes further, to threats to property, but only where the subject's consent is hard to obtain.
Huruf a sets valid explicit consent as the general standard, where the GDPR asks only for an unambiguous indication under GDPR Article 4(11) and reserves explicit consent to GDPR Article 9(2)(a), GDPR Article 22(2)(c) and GDPR Article 49(1)(a), so Indonesia applies at the front door a test the GDPR keeps for sensitive data, profiling and transfers.
Nothing corresponds to the second subparagraph of GDPR Article 6(1), so the restraint on public bodies had to be built in the PP rather than read off the statute.
That is a difference of instrument more than of outcome, because the EU bar reaches only processing in the performance of their tasks, so a public body acting outside its tasks may still rely on GDPR Article 6(1)(f) subject to the balance that C-13/164 and C-621/225 govern, which is close to where PP Pasal 55 lands.
Commentary on each ayat, a pilot on this article and on Pasal 16, Pasal 46 and Pasal 56. Every citation in it was checked against the source it cites.
Ayat (1) requires every controller to have a basis for processing, and UU Pasal 57 ayat (1) sanctions it. PP Pasal 30 repeats the duty and fixes its timing: the basis must be in place before processing begins (PP Pasal 30 ayat (2)), chosen by the intent, purpose and need of the processing (PP Pasal 30 ayat (4)). PP Pasal 184 ayat (1) sanctions PP Pasal 30 ayat (1).
The EDPB reads Article 6 GDPR the same way. The basis must be established before the processing and for a specific purpose, and a controller cannot move to another basis afterwards, for instance to legitimate interests when its consent proves invalid (Guidelines 05/20206, paras 121 and 123). PP Pasal 30 ayat (2) closes the same door: a basis found after the event cannot meet a duty fixed before it.
PP Pasal 31 adds, in the same general part, a duty to ensure that processing is not discriminatory. Its elucidation confines discrimination to distinctions by race and ethnicity under the law on eliminating discrimination, so on the text a distinction by religion or sex falls outside the duty.
Ayat (2) lists six bases joined by dan/atau, and PP Pasal 30 ayat (3) repeats them. The CJEU reads the list in Article 6(1) GDPR as exhaustive and restrictive, and the bases other than consent narrowly, because they make processing lawful without the subject's agreement (C-252/217, paras 90 and 93).
UU Pasal 21 writes the controller's seven-item duty to inform for consent under huruf a, beside the subject's general right to information in UU Pasal 5. PP Pasal 62 ayat (2) extends the seven items to every basis in PP Pasal 30 ayat (3). The elucidation to its ayat (1) huruf a counts the basis itself among them, as Article 13(1)(c) GDPR does, and PP Pasal 184 ayat (1) sanctions PP Pasal 62 ayat (1).
Huruf a admits consent only if valid and explicit and given for specific purposes the controller has disclosed. PP Pasal 32 ayat (2) requires it to be given freely, knowingly, specifically and unambiguously (bebas, sadar, spesifik, dan tidak ambigu), the four qualities of Article 4(11) GDPR with sadar for informed. Its elucidation names bundling as ambiguity: consent folded into terms and conditions, so that reading them counts as agreeing. PP Pasal 35 ayat (3) bans deceptive or misleading requests.
PP Pasal 35 ayat (1) bars withholding or degrading goods or services when consent is refused, unless the service needs the processing, the test of Article 7(4) GDPR. The CJEU, assessing consent given to a dominant social network, said users must be able to refuse processing the contract does not need without giving up the service. That means offering them an equivalent alternative without that processing, if necessary for an appropriate fee (C-252/217, paras 148 to 150).
A consent that fails PP Pasal 32 ayat (2) is not persetujuan yang sah, so processing that relied on it has no basis. The sanction runs through UU Pasal 57 ayat (1) and, in PP Pasal 184 ayat (1), through PP Pasal 30 ayat (1). That list also carries PP Pasal 33 ayat (1) and PP Pasal 36 ayat (1), the duties to inform before consent and to prove it, but not PP Pasal 32 or PP Pasal 35.
Huruf b covers performing a contract to which the subject is party and meeting the subject's request before entering one. PP Pasal 41 ayat (1) requires a valid contract, a need for the processing to perform it, protective steps, a risk assessment and capacity to honour the subject's rights. PP Pasal 43 ayat (1) lists nine items the contract must contain, and a contract without them cannot serve as the basis (PP Pasal 43 ayat (2)).
The documentary conditions add to what the GDPR asks, and they cannot replace necessity. The CJEU treats the mention of processing in a contract as in itself irrelevant and asks whether the processing is objectively indispensable to a purpose integral to the contract (C-252/217, paras 98 and 99). In the PP that question belongs to the need test in PP Pasal 41 ayat (1) huruf b, and PP Pasal 40 ayat (4) bars processing beyond the contract.
For the second limb, PP Pasal 42 ayat (1) requires a written or recorded request and parties who will bind themselves in a contract. That reads more narrowly than the EDPB, which accepts pre-contract processing while it is still unclear whether a contract will follow, such as answering an enquiry about a service (Guidelines 2/20198, para 46).
Huruf c covers processing to meet the controller's own legal obligation under the laws and regulations. PP Pasal 45 ayat (2) says the obligation includes a court order or judgment and an order in a decision of a state administrative official issued under the law. An individual administrative decision can therefore create the obligation, not only a statute or a regulation.
PP Pasal 45 says nothing of what such a decision must state. Where a disclosure follows an authority's request rather than the statute itself, the CJEU requires the request to state its specific purposes. The addressee can then check that the transmission is lawful, and a court can review it (C-175/209, para 71).
The PP knows the device. PP Pasal 155 ayat (2) makes a request from an investigator, prosecutor or judge in a data protection offence state the data sought and their relevance, the period of processing and the basis of authority. An administrative order under PP Pasal 45 ayat (2) huruf b carries no such requirement, so on the PP's text an order stating no purpose still creates the obligation.
Huruf d covers the subject's vital interests, which the elucidation ties to survival. PP Pasal 46 allows the basis where the life, body or property of the subject or another party is threatened and consent is hard to get, as with an unconscious subject or an unaccompanied child (elucidation to PP Pasal 46 huruf b). PP Pasal 47 requires the subject to be told of the threat and of what follows once the purpose ends.
The regulation reaches further than the statute's gloss. Huruf d names the subject alone, while PP Pasal 46 huruf a covers threats to another party and to property and assets. Recital 46 GDPR describes a vital interest as one essential for the life of the subject or of another natural person, so on that reading Article 6(1)(d) GDPR does not reach property.
PP Pasal 46 huruf b also makes the basis depend on difficulty in obtaining consent. Article 6(1)(d) GDPR sets no such condition, and Article 9(2)(c) GDPR sets a stricter one for special categories, requiring the subject to be physically or legally incapable of consenting. A controller relying on the basis for a threat to assets stands on the regulation alone, since the elucidation to huruf d speaks only of survival.
Huruf e covers tasks in the public interest, public services and the exercise of the controller's authority under law. PP Pasal 49 ayat (2) confines it to carrying out a law that orders the controller to take an action. The elucidation to PP Pasal 49 ayat (1) ties the processing to the intent and purpose of that law, and PP Pasal 50 requires a policy document setting out the scope of the task and the purpose of processing.
Article 6(3) GDPR asks less of the law. The basis must be laid down in Union or Member State law, but for a public task the purpose may rest on the processing being necessary for the task. A public body whose statute sets a task in general terms must find a provision that orders the action, and PP Pasal 55 ayat (2) keeps legitimate interests out of its tasks.
PP Pasal 51 requires the subject to be told when processing begins. PP Pasal 51 ayat (3) lets the controller wait until the purpose is met where telling would disturb the public interest or public services, and PP Pasal 51 ayat (4) allows a public announcement where direct notice is impossible. The controller makes both judgments, so a subject may learn of public-task processing only after it has done its work.
Huruf f admits other legitimate interests, weighed by purpose, need and the balance between the controller's interests and the subject's rights. PP Pasal 53 requires an analysis of need, purpose and balance showing a legitimate interest. It also requires an assessment that the processing has no legal effect on the subject and does not harm them, with mitigation in place for any effect, and PP Pasal 54 requires both to be documented.
The analysis tracks the three cumulative conditions the CJEU reads into Article 6(1)(f) GDPR: a legitimate interest, necessity, and no overriding interest of the subject (C-252/217, para 106). The harm assessment has no separate counterpart. The elucidation's examples, security monitoring, health, safety and crime prevention, are tied to the laws and regulations, while the CJEU asks only that the interest be lawful, not that a law provide for it (C-621/225, paras 39 and 40).
The subject is told the basis and the purpose before processing, under PP Pasal 62 ayat (1), PP Pasal 62 ayat (2) and PP Pasal 62 ayat (4). The controller explains its use of the basis only on request, under PP Pasal 56, while Article 13(1)(d) GDPR requires the legitimate interests pursued to be stated when the data are collected (C-621/22, para 41).
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 2,634 national decisions since 25 May 2018, from 29 countries, as citing Article 5; most come from Italy (404), Spain (228) and Lithuania (225). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.
The DPO tags 1,188 national decisions since 25 May 2018, from 28 countries, as citing Article 6(1), 6(3) and 6(4); most come from Belgium (133), Italy (131) and Hungary (117). 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 5. Read it on GDPRhub
Cited in its commentary on Article 6(1), 6(3) and 6(4). Read it on GDPRhub
The Lembaga. No decision of the Lembaga exists, because it has not been established (CNBC Indonesia, 16 September 2026).