Authors
On 16 July 2026, the Government issued Government Regulation No. 33 of 2026 on the Implementing Regulation of Law No. 27 of 2022 on Personal Data Protection ("GR 33/2026"). Nearly four years after the enactment of Law No. 27 of 2022 on Personal Data Protection, as amended[1] ("PDP Law"), GR 33/2026 translates many of the PDP Law's general obligations into concrete requirements.
GR 33/2026 will enter into force 6 (six) months after its promulgation, namely on 16 January 2027.[2] While many technical matters are delegated to further regulations of the personal data protection agency ("PDP Agency"), the core obligations are already clear. In this edition of our ARMA Update, we summarise the key points of GR 33/2026 for businesses.
A. Stricter Conditions for Each Legal Basis
GR 33/2026 sets out specific conditions for each of the 6 (six) legal bases for processing under the PDP Law and requires that a legal basis be in place before any processing begins.[3] The most notable changes are as follows:
Consent: Consent must be given explicitly, freely, knowingly, specifically, and unambiguously. A personal data controller ("Controller") may not reduce the quality of its goods or services because a data subject refuses consent, unless the service genuinely requires the data, and may not obtain consent through deceptive or misleading means. Controllers must also provide a mechanism for giving and withdrawing consent and keep evidence that consent was given. Where the data subject is a child, the Controller must take steps to identify the child, obtain consent from the parent and/or guardian, and verify such consent, taking into account available technology.[4]
Performance of a contract: GR 33/2026 expressly provides that a contract cannot replace consent as a legal basis. Performance of contractual obligations may serve as a legal basis for processing personal data where a valid agreement exists between the Controller and the data subject, the processing is necessary for the performance of such agreement, appropriate personal data protection measures are fulfilled, and the Controller has considered the potential risks to the data subject, as well as its ability to uphold data subject rights and comply with its obligations under the applicable laws and regulations.[5] Further, such a contract must contain at least 9 (nine) elements, including the processing purposes, their relation to the purpose of the contract, and the consequences if the data is not processed. Failing this, the Controller cannot rely on this legal basis.[6]
Legal obligations: GR 33/2026 clarifies that legal obligations include: (i) court orders and/or judgments; and (ii) decisions or orders issued by state administrative officials in accordance with applicable laws and regulations.[7]
Vital interests: GR 33/2026 further clarifies the requirements for relying on vital interests as a legal basis for processing personal data, namely: (i) the existence of a threat to the life, physical safety, and/or property or assets of the data subject or another person; and (ii) difficulties in obtaining consent from the relevant data subject.[8]
Performance of duties in the public interest, provision of public services, or exercise of official authority: This legal basis is mainly relevant to public bodies, but is available to any Controller, provided that the processing carries out an action that applicable laws and regulations specifically require of the Controller. A Controller relying on this legal basis must also maintain an adequate policy document setting out the scope of the duty and the purposes of the processing.[9]
Legitimate interests: The Controller must first conduct and document an assessment balancing its interests against the rights of the data subject, and data subjects are entitled to request an explanation of its reliance on legitimate interests.[10]
In practice, we expect the contractual necessity requirements to have the broadest impact, particularly on employment contracts and platform terms.
B. New Documentation and Accountability Requirements
GR 33/2026 requires Controllers to prepare and maintain, among others, the following:
a record of processing activities ("ROPA") containing at least 13 (thirteen) elements, namely: (i) the name and contact details of the Controller, any joint Controller, and/or the Processor; (ii) the DPO's contact details; (iii) the sources from which the personal data is collected and the destinations to which it is sent; (iv) the legal basis for processing; (v) the processing purposes; (vi) the types of personal data; (vii) the categories of data subjects; (viii) parties other than the Controller that may access the personal data; (ix) the fulfilment of data subject rights; (x) data flow mapping; (xi) retention periods; (xii) the technical and organisational security measures; and (xiii) details of personal data transfers. The ROPA must be updated whenever any of these elements changes, made available for audit and supervisory purposes, and provided to the PDP Agency upon request. Where a Processor is engaged, the Controller must ensure that the Processor keeps its own ROPA (covering at least the Processor's name and contact details, the scope of processing, transfer details, and a general description of its security measures), although this does not relieve the Controller of its own recording obligation;[11]
a retention policy setting out, among others, retention periods, deletion methods, and the responsible persons;[12]
an internal data breach prevention and handling policy;[13] and
a privacy notice for every legal basis, which must remain accessible throughout the processing and may not contain exoneration clauses.[14]
Controllers must also conduct internal and external personal data protection audits,[15] and where personal data is obtained other than from the data subject, notify the data subject within 30 (thirty) working days of collection.[16]
C. Controllers, Processors, and Data Protection Officers
GR 33/2026 prescribes minimum contents for agreements between joint Controllers and between Controllers and personal data processors ("Processors"). Joint Controllers are jointly and severally liable for the processing, while Processors must obtain the Controller's prior written approval before engaging a sub-processor.[17] Consistent with the principles stipulated under the PDP Law, Processors are also directly accountable for their processing, as they must document their processing activities, respond to information requests from the PDP Agency, demonstrate compliance, and conduct audits.[18]
As for data protection officers ("DPO"), GR 33/2026 clarifies that a DPO may consist of an individual or a team, internal or external, and must be able to act independently with access to top management. GR 33/2026 also reiterates that a DPO must be appointed where the processing is carried out for public services, the Controller's core activities require regular and systematic large-scale monitoring of data subjects, or its core activities involve large-scale processing of specific personal data and/or personal data relating to criminal offences.[19]
D. Data Subject Rights
Data subjects exercise their rights through a recorded request accompanied by proof of identity, which the Controller must verify proportionately. GR 33/2026 further introduces, among others, a detailed procedure for the deletion and destruction of personal data, including an official record (berita acara), and a right to object to decisions based solely on automated processing, including profiling, that produce legal effects on or significantly affect the data subject, in which case the Controller must offer human involvement. The right to data portability is limited to processing carried out by automated means on the basis of consent or the performance of a contract.[20] In line with our previous ARMA Update on compensation claims, data subjects must first submit compensation claims to the Controller, which must have a policy for handling such claims, before filing a lawsuit.[21]
E. Data Breach Notification and DPIA
The 3 x 24 (three times twenty-four) hour deadline to notify data subjects and the PDP Agency of a data breach runs from the moment the breach becomes known with certainty, properly, and reasonably (secara pasti, patut, dan wajar). Controllers must also submit breach documentation to the PDP Agency, while Processors must report breaches to the Controller at the earliest opportunity. Where a breach disrupts public services and/or seriously affects the public interest, the Controller must also notify the public.[22]
A data protection impact assessment ("DPIA") must be completed before high-risk processing (including automated decision-making with legal or similarly significant effects, processing of specific personal data, large-scale processing, systematic evaluation, scoring, or monitoring of data subjects, matching or combining of datasets, use of new technology, and processing that restricts the exercise of data subject rights) begins and reviewed whenever the risk changes. Notably, the elucidation of GR 33/2026 confirms that the use of "new technology" includes artificial intelligence, machine learning, and the internet of things.[23]
F. Cross-Border Data Transfers
Before any transfer of personal data abroad, Controllers must carry out a transfer assessment (commonly referred to as a transfer impact assessment). Controllers and/or Processors must, among others, record and map the transfer life cycle, limit the transferred data to what is necessary, identify the legal instrument relied on and assess its effectiveness before the transfer, adopt supplementary contractual, technical, and/or organisational measures where needed, and periodically re-evaluate the transfer.[24] The assessment must consider, among others, the storage location and access to the data, its format (e.g., plain text, pseudonymised, or encrypted), the possibility of onward transfers, and the impact on data subject rights.[25] Controllers must also assess the necessity of the transfer and its risks to data subjects,[26] and inform data subjects of the purpose, safeguards, and risks of the transfer beforehand.[27] Unlike the adequacy list and standard contractual clauses, these assessment obligations do not depend on further regulations from the PDP Agency. Further, GR 33/2026 provides that:
- the PDP Agency will issue a list of countries and international organisations deemed to have an equivalent or higher level of personal data protection;[28]
- standard contractual clauses will be issued by the PDP Agency, while binding corporate rules may only be used within a corporate group and require the PDP Agency's prior approval;[29] and
- consent may only be relied on as a last resort, namely where the destination does not provide an equivalent or higher level of protection and no adequate and binding safeguards are in place. Consent-based transfers are also limited to non-repetitive transfers involving a limited number of data subjects and require the Controller to inform the PDP Agency.[30]
Accordingly, consent can no longer serve as a general fallback for corporate groups that routinely transfer data to overseas affiliates or service providers.
In light of the above, certain mechanisms, such as the adequacy list, standard contractual clauses, and approval of binding corporate rules, will only become operational once the PDP Agency is established and issues its implementing regulations. Pending these regulations, Controllers and Processors must continue to process personal data in a manner that does not conflict with GR 33/2026.[31]
G. Mergers, Acquisitions, and Dissolutions
Before transferring personal data in a merger, demerger, acquisition, consolidation, or dissolution, the Controller must assess its outstanding obligations and update its DPIA. Importantly, the old and new Controllers are treated as joint Controllers until the transaction is completed, and must enter into a data protection agreement, which may form part of the transaction documents. The new Controller may only process the data for its own purposes after the data subjects' objection period has ended.[32]
H. Enforcement and Sanctions
The administrative sanctions under the PDP Law remain, including administrative fines of up to 2% (two percent) of annual revenue or annual receipts. GR 33/2026 clarifies that sanctions may be imposed without a prior written warning and cumulatively, and that fines are calculated based on 10 (ten) variables, including the duration of the violation, the number of affected data subjects, and the Controller's cooperation.[33] Sanction decisions will be published on the PDP Agency's official media.[34] An objection may be filed within 14 (fourteen) working days, which does not suspend the sanction, and is deemed granted if the PDP Agency does not decide within 14 (fourteen) working days.[35]
I. Practical Next Steps
With less than 3 (three) months remaining until GR 33/2026 enters into force, businesses may consider:
- reviewing agreements and templates that rely on contractual necessity, particularly employment contracts and customer terms;
- preparing or updating their record of processing activities, retention policy, data breach policy, legitimate interest assessments, and DPIAs;
- updating data processing agreements with service providers, particularly on sub-processor approval and audit rights;
- testing data breach response procedures, including the 3 x 24 hour notification and the assessment of whether public notification is required;
- identifying any processing of children's data and putting in place mechanisms to identify children and to obtain and verify parental or guardian consent;
- mapping cross-border data flows and preparing transfer assessments and notices; and
- assessing whether a DPO must be appointed and how the function will be structured.
In conclusion, GR 33/2026 moves Indonesia's personal data protection regime from general principles to detailed, enforceable obligations. While certain mechanisms under GR 33/2026 will depend on further regulations to be issued by the PDP Agency, which has yet to be formally established, most of its obligations will apply directly once GR 33/2026 enters into force. Businesses that begin aligning their practices with these requirements at an early stage will therefore be better positioned to ensure compliance by 16 January 2027.
- Law No. 27 of 2022 has been amended by Law No. 1 of 2026. ↩
- Article 225 of GR 33/2026. ↩
- Article 30 of GR 33/2026. ↩
- Articles 32 to 38 of GR 33/2026. ↩
- Article 41 (1) of GR 33/2026. ↩
- Articles 40 (5) and 43 of GR 33/2026. ↩
- Article 45 of GR 33/2026. ↩
- Article 46 of GR 33/2026. ↩
- Articles 49 (2) and 50 of GR 33/2026. ↩
- Articles 53, 54, and 56 of GR 33/2026. ↩
- Article 74 of GR 33/2026. ↩
- Article 75 of GR 33/2026. ↩
- Article 117 of GR 33/2026. ↩
- Articles 62 and 65 of GR 33/2026. ↩
- Article 138 (2) of GR 33/2026. ↩
- Article 64 of GR 33/2026. ↩
- Articles 11, 12, 14, and 15 of GR 33/2026. ↩
- Article 141 of GR 33/2026. ↩
- Articles 142, 144, and 146 of GR 33/2026. ↩
- Articles 20 to 25, 86, 87, 94, and 111 (3) of GR 33/2026. ↩
- Articles 106 to 108 of GR 33/2026. ↩
- Articles 114, 115, 116, and 118 of GR 33/2026. ↩
- Articles 120 (2) and 121, and Elucidation of Article 120 (2) of GR 33/2026. ↩
- Article 161 of GR 33/2026. ↩
- Article 162 (2) of GR 33/2026. ↩
- Article 163 of GR 33/2026. ↩
- Article 164 of GR 33/2026. ↩
- Article 168 (2) of GR 33/2026. ↩
- Articles 170 and 171 of GR 33/2026. ↩
- Articles 165 and 173 (2) of GR 33/2026. ↩
- Article 223 of GR 33/2026. ↩
- Articles 131, 134, and 135 of GR 33/2026. ↩
- Articles 184 (7), 184 (8), and 185 of GR 33/2026. ↩
- Article 195 (2) of GR 33/2026. ↩
- Article 197 of GR 33/2026. ↩
Disclaimer:
This client update is the property of ARMA Law and intended for providing general information and should not be treated as legal advice, nor shall it be relied upon by any party for any circumstance. ARMA Law has no intention to provide a specific legal advice with regard to this client update.
Related Updates
Latest Updates