Skip to main content
Intelligent Security Governance — 340+ Frameworks Powered by Ayurak AI
Blog/Compliance Guides

Indonesia PDP Law (Law No. 27 of 2022): A Practical Compliance Guide

Indonesia's Personal Data Protection Law (UU PDP) sets GDPR-style duties for controllers and processors. Here is who it covers, what it requires and how to prepare.

Indonesia PDP Law (Law No. 27 of 2022): A Practical Compliance Guide

Indonesia's Personal Data Protection Law, known as UU PDP, is the country's first comprehensive, cross-sector data protection statute. It borrows heavily from the EU GDPR in structure, with data subject rights, defined controller and processor roles, breach notification and meaningful sanctions. This guide covers what the law says, who must comply, and how to build a workable program.

What it is

The Personal Data Protection Law is Law No. 27 of 2022 (Undang-Undang Pelindungan Data Pribadi). The Indonesian legislature passed it, and it was enacted in October 2022. It is binding national law, not a standard or voluntary scheme. Before it, personal data rules were scattered across sectoral laws and regulations, including electronic information and transactions rules and sector-specific rules for areas such as financial services and health.

The law came with a transition period of two years from enactment for controllers and processors to adapt. That period has ended, so the obligations should be treated as in force. Implementing regulations and the supervisory institution have been slow to materialise, and their status may have changed. Check the current state of secondary regulation and agency guidance before finalizing your program.

Who it applies to

The law applies to individuals, companies, public bodies and international organizations that process personal data. It has extraterritorial reach. It covers processing that takes place in Indonesia, and also processing outside Indonesia that has legal consequences in Indonesia or for Indonesian citizens as data subjects outside Indonesia. A foreign company offering services to people in Indonesia should assume it is in scope.

The law distinguishes:

  • Data controllers, who determine the purposes of processing and control it.
  • Data processors, who process data on a controller's behalf.
  • Data subjects, the individuals the data relates to.

It exempts purely personal or household processing. It also contains carve-outs for certain national defense, law enforcement and state administration purposes, which most commercial organizations will not rely on.

Key requirements and control areas

Lawful basis and consent

Processing needs a lawful basis. The law recognizes explicit consent, performance of a contract, a legal obligation, protection of vital interests, a public interest or public service task, and legitimate interests. Where consent is used, it must be explicit and documented, and requests need to be clear about purposes. Controllers must be able to show that consent was given.

General and specific personal data

The law separates general personal data (such as name, gender, nationality, religion and combined identifiers) from specific personal data. Specific data covers health data, biometric and genetic data, criminal records, children's data and personal financial data, among others. Specific data carries heavier obligations, including impact assessments.

Data subject rights

Individuals have rights to information about processing, to access and obtain a copy of their data, to correct inaccuracies, to have data deleted or ended in certain cases, to withdraw consent, to object to certain automated decision-making including profiling, and to seek redress. They also have a right related to data portability. You need an intake and response process with defined deadlines and identity verification.

Controller and processor obligations

  • Keep records of processing activities.
  • Maintain security measures proportionate to risk, including protection against unauthorized access and disclosure.
  • Carry out a data protection impact assessment where processing is high risk, for example large-scale processing of specific data, automated decision-making with significant effects, or systematic monitoring.
  • Bind processors by agreement and supervise them.
  • Delete or destroy data when the retention purpose ends or when requested, subject to legal retention duties.

Data Protection Officer

Controllers and processors must appoint a DPO (an official or officer for personal data protection) in defined situations. These broadly cover public service processing, core activities involving regular and systematic large-scale monitoring, and large-scale processing of specific or criminal data. Confirm the exact triggers against the text and any implementing rules.

Breach notification

When protection fails, the controller must notify affected data subjects and the supervisory institution in writing within 3x24 hours (72 hours) of becoming aware of the failure. The notice must describe what data was disclosed, when and how, and what remediation is under way. Public notification can be required in some cases.

Cross-border transfers

A controller may transfer personal data out of Indonesia if the receiving jurisdiction offers an equal or higher level of protection. If it does not, the controller must ensure adequate and binding safeguards. If neither can be shown, the transfer needs the data subject's consent. Plan for transfer mapping and contract terms with offshore vendors and cloud providers.

Assessment, audit and enforcement

There is no certification scheme under the law. Compliance is demonstrated through documentation and supervision, not an external attestation. The law provides for a supervisory institution appointed by the President, with powers to issue policy, supervise and impose administrative sanctions. How that body is established and operates has been evolving, so track current developments.

Sanctions fall into two groups:

  • Administrative sanctions include written warnings, temporary suspension of processing, deletion of personal data and administrative fines. The fine is capped as a percentage of annual revenue related to the violation (up to 2%).
  • Criminal sanctions apply to offenses such as unlawfully obtaining or disclosing personal data, falsifying personal data for gain, and unlawful use of data. They include imprisonment and fines, and corporations can be fined at a higher multiple, with additional penalties such as asset seizure or business suspension. Check the statute for specific amounts.

Data subjects can also seek compensation for violations.

A practical path to compliance

  1. Scope the law's reach. Decide whether you process data of people in Indonesia, as controller, processor or both, and note any sector regulators such as the financial services authority that add rules.
  2. Build a data inventory. Map systems, data categories, purposes, recipients, locations and retention. Flag specific personal data and children's data.
  3. Assign a lawful basis to each purpose. Redesign consent flows where you depend on consent, and keep evidence of when and how it was given.
  4. Run impact assessments for high-risk processing and record decisions and mitigations.
  5. Update notices and policies so privacy information is clear and available in Indonesian where your audience needs it.
  6. Stand up a data subject request process with intake, verification, routing and response tracking.
  7. Set up breach response with detection, triage, regulator and individual notification templates, and a clock that tracks the 72-hour deadline.
  8. Review vendors and transfers. Put processor agreements in place, assess recipient jurisdictions, and document safeguards for each cross-border flow.
  9. Decide on DPO appointment and define its authority, independence and reporting lines.
  10. Monitor and test. Train staff, test controls on a schedule and review the program when implementing regulations change.

How it maps to other frameworks

The overlaps below are partial. Meeting another framework does not mean you comply with UU PDP.

  • GDPR: The closest overlap. Roles, lawful bases, data subject rights, impact assessments, DPOs and breach notification are structurally similar. Details differ, including the lawful bases list, transfer mechanics and sanctions, so a GDPR program needs a gap review rather than reuse as is.
  • ISO/IEC 27001: Supports the security obligations through its risk-based information security management system and Annex A controls. It does not cover data subject rights or lawful basis.
  • ISO/IEC 27701: A privacy extension to ISO 27001 that addresses controller and processor responsibilities. It is a useful structure for a privacy management system.
  • SOC 2: The Security and Confidentiality criteria, and the Privacy criteria if in scope, overlap with safeguards, access control and incident handling. SOC 2 is an attestation, not a legal compliance mechanism.
  • NIST Privacy Framework and CSF: Helpful for organizing privacy and cybersecurity risk work, but with no legal equivalence.

FAQs

Does the UU PDP apply to a company based outside Indonesia?

It can. The law reaches processing outside Indonesia that has legal consequences in Indonesia or for Indonesian citizens as data subjects outside Indonesia. Companies serving users in Indonesia should assess their exposure.

Is data localization required?

The UU PDP does not impose a blanket localization rule. It sets conditions for cross-border transfers. Other sector or public-sector rules may impose localization requirements, so check those separately.

How fast must a breach be reported?

The law requires written notification to affected individuals and the supervisory institution within 3x24 hours of becoming aware of a failure of personal data protection. Build your incident process around that clock.

Is consent always required?

No. Consent is one of several lawful bases. Contract, legal obligation, vital interests, public interest and legitimate interests are also recognized. Choose and document the basis for each purpose.

Is there a certification for UU PDP compliance?

Not under the law. Organizations show compliance through records, assessments and responses to the supervisory body. Standards such as ISO 27001 or 27701 can support the work but do not replace legal compliance.

How Aristiun helps

Aristiun is the AI-powered compliance automation and threat modeling platform, powered by Ayurak AI. For Indonesia PDP work, it gives security and privacy teams a single evidence base that serves several regimes at once, so the same records support UU PDP alongside the other compliance frameworks you follow.

  • Map controls across 340+ frameworks, with each piece of evidence linked to the relevant controls across all applicable frameworks at once.
  • Collect evidence automatically from connected systems such as AWS, Azure, GCP and GitHub, instead of using manual screenshots or spreadsheets.
  • Monitor control effectiveness and get alerts when controls drift, so you can fix issues before auditors find them.
  • Generate threat models from code, IaC and architecture diagrams, and map vendor controls to your compliance requirements to support processor and transfer reviews.

Found this insightful?

Share it with your security team or save it for later.

Get Started

Ready to secure your organization?

See how Aristiun automates compliance and strengthens your security posture across 340+ frameworks.