Transfer outside Indonesia
Pasal 56
Official copy: salinan p. 24
Implemented by PP 33/2026 Pasal 160 to 174.
Ayat (5) delegates the detail on cross-border transfer to a government regulation, now PP 33/2026. PP Pasal 168, 172 and 174 pass it down again to a Peraturan Lembaga.
Dalam melaksanakan transfer Data Pribadi sebagaimana dimaksud dalam Pasal 160, Pengendali Data Pribadi dan/atau Prosesor Data Pribadi harus:
Huruf a Cukup jelas. Huruf b Cukup jelas. Huruf c Cukup jelas. Huruf d Penilaian efektivitas instrumen hukum termasuk penilaian mengenai potensi akses oleh otoritas publik di negara ketiga atau Organisasi Internasional yang menjadi wilayah tujuan transfer Data Pribadi melalui atau tanpa sepengetahuan pihak penerima transfer Data Pribadi. Huruf e Cukup jelas. Huruf f Cukup jelas. Huruf g Mengevaluasi ulang secara berkala dalam kurun waktu yang memadai misalnya apakah selama kurun waktu tersebut pernah dilakukan pelanggaran oleh penerima transfer Data Pribadi atau instrumen pelengkap tidak lagi efektif.
Pengendali Data Pribadi harus melakukan penilaian atas kebutuhan transfer Data Pribadi dan dampak transfer Data Pribadi terhadap hak Subjek Data Pribadi melalui penilaian atas risiko transfer Data Pribadi.
Dalam hal pertukaran Data Pribadi antar penegak hukum dilaksanakan ke luar wilayah hukum Negara Republik Indonesia, pertukaran Data Pribadi dilaksanakan sesuai dengan ketentuan transfer Data Pribadi dalam Peraturan Pemerintah ini.
Penilaian tingkat Pelindungan Data Pribadi yang setara atau lebih tinggi sebagaimana dimaksud dalam Pasal 165 ayat (1) dilakukan oleh Lembaga.
Ayat (1) Huruf a Memiliki peraturan perundang-undangan di bidang Pelindungan Data Pribadi termasuk melakukan pertimbangan terhadap aspek pertahanan, keamanan nasional, dan penerapan hukum pidana di negara penerima transfer Data Pribadi. Huruf b Cukup jelas. Huruf c Cukup jelas. Ayat (2) Cukup jelas. Ayat (3) Cukup jelas. Ayat (4) Cukup jelas.
Ayat (1) Huruf a Instrumen yang mengikat secara hukum dan dapat dipaksakan termasuk pengaturan administratif antara otoritas yang antara lain berisi pengaturan mengenai pemenuhan prinsip Pelindungan Data Pribadi, hak Subjek Data Pribadi, dan kewajiban Pengendali Data Pribadi sesuai dengan ketentuan Undang-Undang mengenai Pelindungan Data Pribadi. Huruf b Cukup jelas. Huruf c Peraturan korporasi yang mengikat merupakan kebijakan Pelindungan Data Pribadi yang dipatuhi oleh Pengendali Data Pribadi dan/atau Prosesor Data Pribadi yang didirikan di wilayah hukum Negara Republik Indonesia untuk transfer atau serangkaian transfer Data Pribadi ke satu atau lebih Pengendali Data Pribadi dan/atau Prosesor Data Pribadi ke luar wilayah hukum Negara Republik Indonesia dalam satu kelompok perusahaan yang terlibat dalam kegiatan ekonomi bersama. Huruf d Cukup jelas. Ayat (2) Cukup jelas. Ayat (3) Cukup jelas.
Ketentuan lebih lanjut mengenai pelaksanaan Pelindungan Data Pribadi yang memadai dan bersifat mengikat diatur dalam Peraturan Lembaga.
Ayat (1) Yang dimaksud dengan "melaksanakan kewajiban sesuai dengan ketentuan peraturan perundang-undangan" termasuk menginformasikan kepada Subjek Data Pribadi mengenai kemungkinan risiko transfer Data Pribadi mengingat tidak adanya Pelindungan Data Pribadi yang memadai dan bersifat mengikat, dan tidak adanya tingkat Pelindungan Data Pribadi yang setara atau lebih tinggi. Ayat (2) Cukup jelas.
Ketentuan lebih lanjut mengenai pelaksanaan persetujuan untuk transfer Data Pribadi ke luar wilayah hukum Negara Republik Indonesia diatur dalam Peraturan Lembaga.
PP Pasal 160 to 174 operationalise the statute's three-layer cascade, and the enacted text centralises its first limb in a way the draft did not.
The controller must ensure an equal or higher level of protection under Pasal 165(1), but the assessment of that level is expressly performed by the Lembaga under Pasal 167, against three criteria at Pasal 168(1): that the receiving country has data protection legislation, a supervisory authority, and international commitments or obligations arising from an international agreement or binding instrument.
Pasal 168(2) then requires the Lembaga to establish a list of countries and international organisations meeting that standard, where the draft at Pasal 184(2) provided only that it may do so. Where the receiving country is not on the list the cascade moves to adequate and binding protection at Pasal 169 to 172, then to explicit consent at Pasal 173, with legal-instrument and transfer-risk assessments required beforehand at Pasal 162 and 163.
The Constitutional Court has now tested the statutory limb. In Case No. 137/PUU-XXIII/20253, pronounced on 19 January 2026, it rejected a challenge to Pasal 56 in full and held at paragraph [3.15] that all four ayat conflict neither with popular sovereignty under Article 1 ayat (2) of the 1945 Constitution nor with the requirement of parliamentary approval for an international agreement under Article 11.
The three-layer mechanism therefore stands, and two questions are left open: the criteria the Lembaga will apply in practice, and whether a bilateral data arrangement would itself qualify as an adequacy decision.
diverges from the GDPRGDPR Articles 44, 45, 46, 48 and 49
What the GDPR provides. Chapter V builds a three-step cascade. Article 45 lets a transfer proceed with no further authorisation where the Commission has decided that a third country ensures an adequate level of protection, assessed against the rule of law, enforceable rights, an effective and independent supervisory authority and international commitments, subject to periodic review and a list published in the Official Journal.
Absent adequacy, Article 46 requires appropriate safeguards giving enforceable rights and effective remedies, through standard contractual clauses, binding corporate rules under Article 47, approved codes or certification. Failing both, Article 49 permits a transfer only under narrow derogations, the first of which is explicit consent given after the data subject has been informed of the possible risks of the transfer arising from the absence of an adequacy decision and appropriate safeguards.
Article 44 holds the chapter together by requiring that the level of protection is not undermined, onward transfers included, and Article 48 addresses orders from third country authorities.
The three rungs sit in Chapter V's order, ayat (2) against Article 45, ayat (3) against Article 46 and ayat (4) against Article 49(1)(a), but only the first two rungs do the same work. Article 45 says adequate, and it took Schrems I to read that as essentially equivalent to the level guaranteed inside the EU, where ayat (2) writes setara atau lebih tinggi into the statute and arrives at the same standard without the litigation.
Who applies that standard is the first divergence, and the PP moves Indonesia closer to the EU than the statute is: Article 45 makes adequacy a central Commission act with a published list a controller may rely on, UU Pasal 56 ayat (2) puts the judgment on the controller, and PP Pasal 167 and Pasal 168(2) hand it back to the Lembaga with a country list and three criteria that read like a compressed Article 45(2).
The third rung is the larger divergence in the statute, because Article 49 consent is a derogation, construed restrictively, tied to information about the specific risks and unfit for repetitive or large-scale flows, while UU Pasal 56 ayat (4) makes consent the ordinary fallback whenever the first two limbs fail.
PP Pasal 173 ayat (2) closes most of that route: a transfer on consent must be non-repetitive, concern a limited number of subjects and be notified to the Lembaga, the conditions GDPR Article 49(1) sets for its compelling legitimate interests derogation, so a regular flow cannot use consent to pass an unfavourable country list.
Chapter V also carries an onward-transfer rule at Article 44 and a rule at Article 48 on foreign authority orders, and UU Pasal 56 has neither, so a chain that leaves the first recipient runs out of statutory text at the border.
The regulation adds little: PP Pasal 160 ayat (4) says only that an onward transfer stays subject to the laws and regulations, and PP Pasal 162 ayat (2) huruf i has the controller weigh the chance of one.
Commentary on each ayat, a pilot on this article and on Pasal 16, Pasal 20 and Pasal 46. Every citation in it was checked against the source it cites.
Ayat (1) permits a controller to transfer data to a controller or processor outside Indonesia in accordance with this Law. PP Pasal 160 ayat (3) defines the transfer by three criteria: a controller acting under the law makes the data available to a receiving controller or processor, and the recipient is outside Indonesia. They track the three criteria of EDPB Guidelines 05/20214 (section 2, p. 7), except on who may be the exporter.
PP Pasal 160 ayat (3) huruf a and huruf b name only a controller, where the EDPB's exporter may also be a processor, and in its reasoning the Constitutional Court3 read UU Pasal 56 ayat (1) as a transfer only a controller may make ([3.14.1], p. 212). Read literally, a processor in Indonesia that passes data to a sub-processor abroad makes no transfer, although PP Pasal 161 addresses controllers and processors alike.
PP Pasal 160 ayat (2) puts sender and recipient under a duty to protect the data under Indonesian law, and PP Pasal 184 ayat (1) sanctions it. PP Pasal 161 sets seven steps for every transfer, from mapping to periodic review, which track the six steps of EDPB Recommendations 01/20205; the elucidation to its huruf d adds possible access by foreign authorities. The EDPB stops those steps at an adequacy decision, while PP Pasal 161 reaches listed destinations too.
In its reasoning at [3.14.1] the Constitutional Court placed transfer inside the whole Law, answering a plea for a consent requirement with the consent basis in UU Pasal 20 ayat (2) huruf a. The EDPB states the European rule as a two-step test: a basis for the processing first, the transfer rules second (Guidelines 2/20186, p. 3).
Ayat (2) makes the controller ensure that the recipient's country protects data at a level equal to or higher than this Law. In its reasoning at [3.14.1] the Constitutional Court3 called the equivalence assessment a technical and administrative act of the executive and read ayat (2) with UU Pasal 59 and UU Pasal 60 (pp. 215 and 216).
The Court said the final, authoritative and binding power to set the list of equivalent countries lies with the state through the Lembaga, and that controllers will act on the Lembaga's guidance and list (pp. 216 and 217). The passage supports its conclusion that no parliamentary approval is needed, and the holding at [3.15] does not repeat it.
PP Pasal 168 ayat (1) asks whether the country has data protection law, a supervisory authority and international commitments, and its elucidation adds defence, national security and criminal law. Article 45(2) GDPR also asks for effective and enforceable rights with administrative and judicial redress, and for an authority that is independent and works in practice. PP Pasal 168 ayat (1) huruf b asks only that an authority exist.
Measured against Article 45(2) GDPR, a country could make the Indonesian list with a supervisory body under government control and no redress for Indonesian data subjects, because the three criteria do not exclude it. The controller's own duty in ayat (2), sanctioned by UU Pasal 57 ayat (1), then rests on a list that asks less than the European one.
Ayat (3) requires adequate and binding protection where ayat (2) is not met. PP Pasal 169 ayat (1) lists its forms: a legally binding and enforceable instrument for agencies or authorities, standard contractual clauses, binding corporate rules, and other instruments the Lembaga recognises. The Lembaga sets the clauses and approves corporate rules (PP Pasal 170 ayat (1), PP Pasal 171 ayat (3)), and the controller accounts to it in a written or recorded document (PP Pasal 169 ayat (2)).
The elucidation to PP Pasal 169 ayat (1) huruf a counts administrative arrangements between authorities as binding and enforceable instruments. Article 46 GDPR keeps the two apart: an arrangement that is not legally binding needs the supervisory authority's authorisation and must carry enforceable and effective rights (Article 46(3)(b) GDPR; Guidelines 2/20207, para 71). The PP folds them together with no authorisation step, and asks for provisions on the subject's rights without asking that the subject can enforce them.
The Constitutional Court3 read ayat (3) as the state's answer where the recipient's country falls short, with the controller as the state's extended hand ([3.14.2], p. 218). It reasoned that a proposed effective-remedy requirement was already accommodated by ayat (2) (p. 219), a provision that is by definition unmet whenever ayat (3) applies.
Article 46(1) GDPR allows a transfer on safeguards only where enforceable rights and effective legal remedies are available (C-311/188, para 103). The minimum content of the Lembaga's clauses in PP Pasal 170 ayat (2) names neither, so the remedy question the Court answered through ayat (2) stays open on the rung where it arises.
Ayat (4) requires the subject's consent when ayat (2) and ayat (3) both fail. PP Pasal 173 ayat (2) allows such a transfer only if it is not repetitive, involves a limited number of subjects and is needed for a purpose that does not set aside the subject's interests or rights and freedoms. The risk must be assessed and suitable measures applied, and the Lembaga and the subject told of the transfer and the compelling legitimate interest it serves.
They are the conditions of the second subparagraph of Article 49(1) GDPR, the compelling-legitimate-interests derogation that the EDPB calls a last resort for residual cases (Guidelines 2/20186, section 2.8, p. 14). The consent derogation in Article 49(1)(a) GDPR carries no such limits on its face. By attaching them to consent, the PP keeps ayat (4) from carrying a regular or large-scale flow.
At [3.14.3] the Constitutional Court3 declined to read into ayat (4) a duty to tell the subject of the transfer's risks first, reasoning that the addition would not change the provision's function. The regulation supplies it anyway.
PP Pasal 164 ayat (2) huruf d requires information on transfer risks before a transfer, save one made for the subject's vital interests, which PP Pasal 164 ayat (3) lets the controller explain afterwards. The elucidation to PP Pasal 173 ayat (1) requires the risk information of Article 49(1)(a) GDPR for consent-based transfers.
Ayat (5) delegates transfer to a government regulation, and PP 33/2026 answers with PP Pasal 160 to PP Pasal 174. Every rung ends at the Lembaga: an assessment and a list for the first, clauses, approval or a written or recorded account for the second, and a notice for the third (PP Pasal 173 ayat (2) huruf e). PP Pasal 165 ayat (4) also lets the Lembaga assess compliance with all three.
Until the President establishes the Lembaga under UU Pasal 58 ayat (3), no rung can be fully complied with as the PP writes it, and the PP names no one to act in its place. The regulation takes effect on 16 January 2027, six months after its promulgation on 16 July 2026 (PP Pasal 225).
At paragraph [3.15] the Court held that Pasal 56 ayat (1) to (4) do not conflict with popular sovereignty under Article 1(2) of the 1945 Constitution, with the requirement of parliamentary approval for an international agreement under Article 11(1) and (2), or with Article 28G(1).
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 30 national decisions since 25 May 2018, from 11 countries, as citing Article 44; most come from Finland (6), Denmark (4) and Belgium (4). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.
The DPO tags 42 national decisions since 25 May 2018, from 13 countries, as citing Article 46; most come from Belgium (14), Finland (8) and Greece (3). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.
The DPO tags 2 national decisions since 25 May 2018, from 2 countries, as citing Article 48; most come from Denmark (1) and Spain (1). 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 44. Read it on GDPRhub
Cited in its whole commentary on Article 46. Read it on GDPRhub
The Lembaga. No decision of the Lembaga exists, because it has not been established (CNBC Indonesia, 16 September 2026).