Powered by
The UU PDP wiki
Salinan v5.8 · 28 Sep 2026
BAB VPEMROSESAN DATA PRIBADI

Pasal 18 UU PDP

Joint controllers

1Legal text

Pasal 18

(1)
Pemrosesan Data Pribadi dapat dilakukan oleh 2 (dua) atau lebih Pengendali Data Pribadi.
(2)
Dalam hal Pemrosesan Data Pribadi dilakukan oleh 2 (dua) atau lebih Pengendali Data Pribadi harus memenuhi syarat minimal:
  1. a.
    terdapat perjanjian antara para Pengendali Data Pribadi yang memuat peran, tanggung jawab, dan hubungan antar-Pengendali Data Pribadi;
  2. b.
    terdapat tujuan yang saling berkaitan dan cara pemrosesan Data Pribadi yang ditentukan secara bersama; dan
  3. c.
    terdapat narahubung yang ditunjuk secara bersama-sama.

Official copy: salinan p. 10

2Implementing regulation

Implemented by PP 33/2026 Pasal 11, 12 and 16.

PP Pasal 11Pemrosesan Data Pribadi dapat dilakukan oleh Pengendali Data…
(1)
Pemrosesan Data Pribadi dapat dilakukan oleh Pengendali Data Pribadi Bersama.
(2)
Dalam hal Pemrosesan Data Pribadi dilakukan oleh Pengendali Data Pribadi Bersama, harus memenuhi syarat minimal:
  1. a.
    terdapat perjanjian antara para Pengendali Data Pribadi yang memuat peran, tanggung jawab, dan hubungan antar-Pengendali Data Pribadi;
  2. b.
    terdapat tujuan yang saling berkaitan dan cara pemrosesan Data Pribadi yang ditentukan bersama; dan
  3. c.
    terdapat narahubung yang ditunjuk bersama-sama.
(3)
Perjanjian sebagaimana dimaksud pada ayat (2) huruf a paling sedikit memuat:
  1. a.
    dasar pemrosesan Data Pribadi masing-masing Pengendali Data Pribadi;
  2. b.
    keterkaitan antartujuan pemrosesan Data Pribadi yang dikendalikan oleh masing-masing Pengendali Data Pribadi;
  3. c.
    keterangan mengenai kesepakatan cara pemrosesan Data Pribadi;
  4. d.
    jenis Data Pribadi yang diproses;
  5. e.
    pembagian peran dan tanggung jawab pemenuhan kewajiban hukum masing-masing Pengendali Data Pribadi sesuai dengan ketentuan peraturan perundang-undangan; dan
  6. f.
    narahubung yang ditunjuk bersama.
(4)
Pengendali Data Pribadi Bersama secara bersama-sama bertanggung jawab memastikan pemrosesan Data Pribadi dilakukan sesuai dengan perjanjian dan ketentuan peraturan perundang-undangan.

Read it in the regulationsalinan p. 10

PP Pasal 12Pengendali Data Pribadi Bersama sebagaimana dimaksud dalam…

Pengendali Data Pribadi Bersama sebagaimana dimaksud dalam Pasal 11 bertanggung jawab hukum secara tanggung renteng atas pemrosesan Data Pribadi sesuai dengan ketentuan peraturan perundang-undangan.

Read it in the regulationsalinan p. 11

PP Pasal 16Pengendali Data Pribadi Bersama dapat menunjuk Prosesor Data…
(1)
Pengendali Data Pribadi Bersama dapat menunjuk Prosesor Data Pribadi.
(2)
Ketentuan mengenai penunjukan Prosesor Data Pribadi oleh Pengendali Data Pribadi sebagaimana dimaksud dalam Pasal 13 dan Pasal 14 berlaku secara mutatis mutandis terhadap penunjukan Prosesor Data Pribadi oleh Pengendali Data Pribadi Bersama.

Read it in the regulationsalinan p. 13

3Commentary

3.1How the regulation implements it

Joint controllers are given joint and several legal responsibility at PP Pasal 12 and a shared appointment power at Pasal 16. Liability is therefore allocated by operation of law rather than by the arrangement between the parties, which limits how far an internal allocation can be relied upon.

3.2Where the GDPR stands

ported from the GDPRGDPR Articles 4 and 26

What the GDPR provides. GDPR Article 26(1) makes two or more controllers joint controllers where they jointly determine the purposes and means of processing, and requires them to fix their respective compliance responsibilities in a transparent arrangement, in particular for data subject rights and the information duties at GDPR Article 13 and Article 14. That arrangement may designate a contact point for data subjects.

GDPR Article 26(2) requires the essence of the arrangement to be made available to the data subject. GDPR Article 26(3) lets the data subject exercise rights against each controller whatever the arrangement says between them.

The three limbs of UU Pasal 18 ayat (2) carry the components of GDPR Article 26(1) in reversed order: huruf a is the arrangement on roles and responsibilities, huruf b is the joint element, and huruf c is the contact point sentence. The match at huruf b is not exact.

Huruf b pairs tujuan yang saling berkaitan with cara pemrosesan Data Pribadi yang ditentukan secara bersama, so joint determination attaches to the means limb while the purposes limb asks only that the purposes be interrelated. GDPR Article 26(1) requires joint determination of both.

The reversal matters, because GDPR Article 26(1) opens with joint determination as the fact that creates the status and treats the arrangement as the duty that follows, where UU Pasal 18 ayat (2) puts the agreement first among the syarat minimal, and PP Pasal 11 ayat (3) then prescribes what that agreement must contain.

Two smaller things change as well: the contact point is permissive in GDPR Article 26(1) and mandatory in huruf c, and GDPR Article 26(2), the duty to make the essence of the arrangement available to the subject, has no counterpart in the statute, although PP Pasal 63 supplies one by requiring joint controllers to tell the subject which controllers are involved, how their purposes interrelate, how processing is carried out and who the joint contact point is.

GDPR Article 26(3) has no counterpart at either level, so nothing tells a subject that the parties' allocation cannot be raised against a claim brought against one of them. UU Pasal 18 ayat (1) then says processing dapat dilakukan by two or more controllers, which reads as a status the parties elect and constitute by agreement.

In EU law it is a factual status found on conduct: C-210/163, C-25/174 and C-40/175 applied it under Directive 95/46 Article 2(d) to parties who had no arrangement and resisted the label, and C-683/216 ruled under GDPR Article 4(7) and Article 26(1) that classification as joint controllers requires neither an arrangement on purposes and means nor an arrangement on the terms of joint control.

So a missing agreement is a breach of GDPR Article 26(1) by parties who are already joint controllers, never a reason they are not.

4Decisions and guidance

Court of Justice of the EU

  • C-210/16Unabhängiges Landeszentrum für Datenschutz Schleswig-Holstein v Wirtschaftsakademie Schleswig-Holstein GmbH5 June 2018
  • C-25/17Proceedings brought by Tietosuojavaltuutettu10 July 2018
  • C-40/17Fashion ID GmbH & Co.KG v Verbraucherzentrale NRW eV29 July 2019
  • C-683/21Nacionalinis visuomenės sveikatos centras prie Sveikatos apsaugos ministerijos v Valstybinė duomenų apsaugos inspekcija5 December 2023

National supervisory authorities

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.

Article 4 GDPRDefinitions5 of 417 decisions

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.

  • 10234589Italy, Garante per la protezione dei dati personali26 February 2026 · fine EUR 15,000
  • 113/2024Belgium, GegevensbeschermingsautoriteitMediahuis N.V.6 September 2024Annulled by the Market Court on 19 March 2025 (judgment 2024/AR/1690).
  • NAIH-4375-2/2024Hungary, NAIH2024
  • 2023-431-0010Denmark, Datatilsynet14 February 2024
  • DecisionRomania, ANSPDCP2023 · fine EUR 1,000
Article 26 GDPRJoint controllers4 of 23 decisions

The DPO tags 23 national decisions since 25 May 2018, from 11 countries, as citing Article 26; most come from France (5), Denmark (4) and Slovenia (3). Listed here are the most recent, one per country, each opened at the authority and found to cite the article.

  • 10223383Italy, Garante per la protezione dei dati personali25 September 2025 · fine EUR 8,000
  • 64/2024Belgium, Gegevensbeschermingsautoriteit26 April 2024
  • 2021-7329-0052Denmark, Datatilsynet20 April 2023
  • DKN.5112.11.2021Poland, UODO6 November 2025

Cited on GDPRhub

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.

Article 4 GDPRDefinitions4 judgments

Cited in its commentary on Article 4(7). Read it on GDPRhub

Article 26 GDPRJoint controllers4 judgments

Cited in its commentary on Article 26(1), 26(2) and 26(3). Read it on GDPRhub

The Lembaga. No decision of the Lembaga exists, because it has not been established (CNBC Indonesia, 16 September 2026).

5Cross-references

Referred to by

  • No other article of the Law refers to this one.

6Sources

  1. 1UU 27/2022, salinan, p. 10.
  2. 2PP 33/2026, salinan: Pasal 11 and 12 at pp. 10 to 11; Pasal 16 at p. 13.
  3. 3Case C-210/16 Unabhängiges Landeszentrum für Datenschutz Schleswig-Holstein v Wirtschaftsakademie Schleswig-Holstein GmbH, 5 June 2018, ECLI:EU:C:2018:388. EUR-Lex.↑
  4. 4Case C-25/17 Proceedings brought by Tietosuojavaltuutettu, 10 July 2018, ECLI:EU:C:2018:551. EUR-Lex.↑
  5. 5Case C-40/17 Fashion ID GmbH & Co.KG v Verbraucherzentrale NRW eV, 29 July 2019, ECLI:EU:C:2019:629. EUR-Lex.↑
  6. 6Case C-683/21 Nacionalinis visuomenės sveikatos centras prie Sveikatos apsaugos ministerijos v Valstybinė duomenų apsaugos inspekcija, 5 December 2023, ECLI:EU:C:2023:949. EUR-Lex.↑
  7. 7EDPB, Guidelines 07/2020 on the concepts of controller and processor in the GDPR. EDPB.
  8. 8GDPRhub (noyb), commentary on Article 4 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.
  9. 9GDPRhub (noyb), commentary on Article 26 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.