Powered by
The UU PDP wiki
Salinan v5.8 · 28 Sep 2026
BAB VIKEWAJIBAN PENGENDALI DATA PRIBADI DAN PROSESOR DATA PRIBADI DALAM PEMROSESAN DATA PRIBADI

Pasal 27 UU PDP

Limited and specific processing

sanctioned by Pasal 57 ayat (1)

1Legal text

Pasal 27

Pengendali Data Pribadi wajib melakukan pemrosesan Data Pribadi secara terbatas dan spesifik, sah secara hukum, dan transparan.

Official copy: salinan p. 13

2Official elucidation

Yang dimaksud dengan "secara terbatas dan spesifik" adalah pengumpulan Data Pribadi harus terbatas sesuai dengan tujuan pemrosesannya serta tujuan pemrosesan Data Pribadi harus secara eksplisit, sah, dan telah ditentukan pada saat pengumpulan Data Pribadi.

Yang dimaksud dengan "sah secara hukum" adalah pemrosesan Data Pribadi dilakukan sesuai dengan ketentuan peraturan perundang-undangan.

Yang dimaksud dengan "transparan" adalah pemrosesan Data Pribadi dilakukan dengan memastikan bahwa Subjek Data Pribadi telah mengetahui Data Pribadi yang diproses dan bagaimana Data Pribadi tersebut diproses, serta setiap Informasi dan komunikasi yang berkaitan dengan pemrosesan Data Pribadi tersebut mudah diakses dan dipahami, dengan menggunakan bahasa yang jelas.

3Implementing regulation

Implemented by PP 33/2026 Pasal 58 to 60.

PP Pasal 58Pengendali Data Pribadi wajib melakukan pemrosesan Data Pribadi…sanction list
repeats UU Pasal 27

Pengendali Data Pribadi wajib melakukan pemrosesan Data Pribadi secara terbatas dan spesifik, sah secara hukum, dan transparan.

its elucidation

Yang dimaksud dengan "sah secara hukum" adalah pemrosesan Data Pribadi dilakukan sesuai dengan ketentuan peraturan perundang-undangan.

Read it in the regulationsalinan p. 30

PP Pasal 59Terbatas dan spesifik sebagaimana dimaksud dalam Pasal 58…
(1)
Terbatas dan spesifik sebagaimana dimaksud dalam Pasal 58 dilakukan dengan meminimalisasi Data Pribadi yang diproses.
(2)
Meminimalisasi Data Pribadi yang diproses sebagaimana dimaksud pada ayat (1) dilakukan dengan mempertimbangkan:
  1. a.
    hubungan antara Data Pribadi yang diproses dan tujuan pemrosesan Data Pribadi;
  2. b.
    kecukupan Data Pribadi yang diproses untuk mencapai tujuan pemrosesan Data Pribadi; dan
  3. c.
    Data Pribadi yang diproses tidak melebihi dari yang dibutuhkan untuk mencapai tujuan pemrosesan Data Pribadi.

Read it in the regulationsalinan p. 31

PP Pasal 60Transparan sebagaimana dimaksud dalam Pasal 58 dilakukan…
(1)
Transparan sebagaimana dimaksud dalam Pasal 58 dilakukan dengan:
  1. a.
    memastikan Subjek Data Pribadi mengetahui Data Pribadi yang diproses;
  2. b.
    memastikan Subjek Data Pribadi mengetahui cara pemrosesan Data Pribadi; dan
  3. c.
    menyampaikan Informasi dan komunikasi terkait pemrosesan Data Pribadi yang mudah diakses, dipahami, dan menggunakan bahasa yang jelas.
(2)
Pemrosesan Data Pribadi secara transparan sebagaimana dimaksud pada ayat (1) harus dilaksanakan secara jujur dan iktikad baik.
its elucidation

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.

Read it in the regulationsalinan p. 31

4Commentary

4.1How the regulation implements it

Limited and specific processing is given effect through data minimisation at PP Pasal 59 and transparency duties at Pasal 60, with the parent duty sanction-backed at Pasal 58. Minimisation is stated as an operative test rather than a principle, which is what makes it auditable.

4.2Where the GDPR stands

ported from the GDPRGDPR Article 5

What the GDPR provides. GDPR Article 5(1) sets the processing principles. Point (a) requires processing to be lawful, fair and transparent in relation to the data subject, point (b) requires collection for specified, explicit and legitimate purposes, and point (c) limits the data to what is adequate, relevant and necessary for those purposes. Article 5(2) then makes the controller responsible for compliance and able to demonstrate it, which is the accountability principle.

The four adjectives in Pasal 27 line up one for one with the GDPR terms. Terbatas answers to Article 5(1)(c), spesifik to the specified purposes in Article 5(1)(b), and sah secara hukum and transparan to the lawfulness and transparency limbs of Article 5(1)(a).

What is absent from the article is the remaining limb of Article 5(1)(a), fairness, though it is not absent from the regime: PP Pasal 60 ayat (2) requires transparent processing to be carried out secara jujur dan iktikad baik, and PP Pasal 35 ayat (3) forbids asking for consent by deceptive or misleading means, which is the direct answer to the interfaces the deceptive design guidelines describe.

The difference is rank rather than presence. In the EU fairness is a principle in Article 5(1)(a) that reaches every basis and every stage; in Indonesia it arrives as a qualifier on transparency and on consent gathering. Article 5(2) accountability has no home in Pasal 27 either, and the nearest Indonesian equivalent is not the recording duty at Pasal 31 but UU Pasal 16 ayat (2) huruf h, which requires processing to be bertanggung jawab dan dapat dibuktikan secara jelas.

Minimisation is where the EU line has moved most: C-446/214 held that Article 5(1)(c) precludes data being aggregated, analysed and processed for targeted advertising without restriction as to time and without distinction as to type of data, and C-439/195 shows the same principles limiting a public register even where a statute authorises the disclosure.

PP Pasal 59 makes that argument operative in Indonesia, since it defines terbatas dan spesifik as minimisation and sets three tests, relationship to the purpose, sufficiency for the purpose, and no excess beyond what the purpose needs.

5Decisions and guidance

Court of Justice of the EU

  • C-446/21Maximilian Schrems v Meta Platforms Ireland Limited4 October 2024
  • C-439/19Proceedings brought by B22 June 2021

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 5 GDPRPrinciples relating to processing of personal data5 of 2,056 decisions

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.

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 5 GDPRPrinciples relating to processing of personal data7 judgments · 2 EDPB documents

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).

6Cross-references

Referred to by

7Sources

  1. 1UU 27/2022, salinan, p. 13.
  2. 2Penjelasan UU 27/2022, salinan, p. 44.
  3. 3PP 33/2026, salinan: Pasal 58 to 60 at pp. 30 to 31.
  4. 4Case C-446/21 Maximilian Schrems v Meta Platforms Ireland Limited, 4 October 2024, ECLI:EU:C:2024:834. EUR-Lex.↑
  5. 5Case C-439/19 Proceedings brought by B, 22 June 2021, ECLI:EU:C:2021:504. EUR-Lex.↑
  6. 6EDPB, Article 29 Working Party - Guidelines on transparency under Regulation 2016/679. EDPB.
  7. 7EDPB, Guidelines 4/2019 on Article 25 Data Protection by Design and by Default. EDPB.
  8. 8EDPB, Guidelines 03/2022 on deceptive design patterns in social media platform interfaces: how to recognise and avoid them. EDPB.
  9. 9GDPRhub (noyb), commentary on Article 5 GDPR, CC BY-NC-SA 4.0, as captured on 26 September 2026. GDPRhub.