UU PDP is Indonesia’s Personal Data Protection Law, Law No. 27 of 2022. It has applied in full since the two-year adjustment period ended on 17 October 2024, and the government has now issued its implementing regulation, Government Regulation No. 33 of 2026 (PP 33/2026), signed and promulgated on 16 July 2026. PP 33/2026 takes effect six months after promulgation, so from mid-January 2027. This guide explains who must comply, what the law and the regulation require, who enforces them today, and what a company should do before the regulation starts.
What Is UU PDP in Indonesia?
UU PDP sets rules for collecting, using, storing, transferring and deleting personal data. It was signed on 17 October 2022. Article 74 gave controllers, processors and related parties up to two years from promulgation to adjust, so the adjustment period ended on 17 October 2024.
The law separates two types of personal data (Article 4). Specific personal data covers health data and information, biometric data, genetic data, criminal records, children’s data, personal financial data and other data set by law. General personal data covers full name, gender, nationality, religion, marital status and data that can identify a person when combined.
Explore Our Services Regulatory Compliance in Indonesia
What PP 33/2026 Changes
PP 33/2026 is the implementing regulation for ten articles of UU PDP that each called for a government regulation. It runs to 225 articles, was promulgated in State Gazette 2026 No. 88, and takes effect six months after the promulgation date of 16 July 2026 (Article 225). It adds the following to what the law already said:
- Detailed procedures for data subject rights, records of processing, impact assessments, security measures, breach handling, cross-border transfers, supervision, administrative sanctions and dispute resolution.
- Specific response times for data subject requests, mostly 3 x 24 hours.
- Many details left to the supervisory agency. The regulation refers dozens of matters to a future “Peraturan Lembaga” (agency regulation), including the list of countries with equivalent protection, standard contractual clauses and the exact DPO rules.
- Days mean working days. The regulation defines “Hari” as a working day (Article 1(19)), while the 3 x 24 hour periods are counted in hours.
Until the agency issues its regulations, controllers and processors may continue processing as long as they do not breach PP 33/2026 (Article 223). Other existing personal data rules remain valid insofar as they do not conflict (Article 224).
Who Must Comply
UU PDP applies to every person, public body and international organisation that performs legal acts governed by the law, inside Indonesia, and also outside Indonesia where those acts have legal consequences in Indonesia or for Indonesian citizens who are data subjects abroad (Article 2(1)). It does not apply to processing by an individual for purely personal or household activities (Article 2(2)).
A foreign company is therefore covered when it processes data of people in Indonesia or when its processing has legal consequences in Indonesia. A company with an Indonesian entity, employees, customers or vendors in Indonesia should assume it is covered. The law uses “controller” for the party that decides the purpose and manner of processing, and “processor” for the party that processes data on the controller’s behalf. Digital businesses registered as electronic system operators carry these duties on top of their PSE registration obligations, and personal data handed over in a merger or acquisition is covered too (see M&A in Indonesia).
Lawful Basis for Processing
A controller must have a lawful basis for each processing activity (UU PDP, Article 20). The six bases are:
- explicit valid consent for one or more specific purposes;
- performance of a contract with the data subject, or steps taken at the data subject’s request before a contract;
- compliance with a legal obligation of the controller;
- protection of the data subject’s vital interests;
- performance of a task in the public interest, public service or the controller’s legal authority; and
- other legitimate interests, balanced against the data subject’s rights.
When consent is the basis, the controller must give the legality, purpose, type of data, retention period, processing period and rights information listed in Article 21. For employee data, contract and legal obligation are usually safer bases than consent, because employees may argue that consent given in an employment relationship was not free. That is XPND’s practical view, not a rule in the regulation. The same applies to CVs and HR files collected during hiring in Indonesia.
Data Subject Rights and Response Times
UU PDP gives data subjects the following rights (Articles 5 to 13):
- information about the identity of the requester, the legal basis, the purpose and accountability;
- completing, updating and correcting their data;
- access to and a copy of their data;
- ending processing, deletion and destruction;
- withdrawing consent;
- objecting to decisions based solely on automated processing, including profiling, with legal or significant effects;
- delaying or restricting processing;
- suing and receiving compensation; and
- obtaining their data in a common format and sending it to another controller (portability).
PP 33/2026 turns these into deadlines. The main ones are:
- correcting or updating data within 3 x 24 hours of receiving the request (Article 71(1));
- confirming a copy request and stating the time needed within 3 x 24 hours of a verified request (Article 78(2));
- stopping processing within 3 x 24 hours after consent is withdrawn (Article 92(2));
- delaying or restricting processing within 3 x 24 hours of the request (Article 99(1)); and
- when data is obtained indirectly, giving the information in Article 62(1) within 30 working days of obtaining it (Article 64).
Set up a documented process for receiving, verifying and answering these requests. The right to be informed, to access data, to withdraw consent and to restrict processing can be limited for defence and national security, law enforcement and certain public interests (UU PDP, Article 15).
Records of Processing and Impact Assessments
PP 33/2026 requires a controller to keep records of all its processing activities (Article 74). At minimum the record covers the controller and processor contact details, the DPO contact, the source and destination of data, the lawful basis, purpose, types of data, categories of data subjects, who else can access the data, how rights are met, the data flow map, the retention period, security measures and details of transfers.
A controller must also carry out a data protection impact assessment, before processing, when processing carries high risk (UU PDP, Article 34; PP 33/2026, Articles 120 and 121). The regulation lists these high-risk cases:
- automated decisions with legal or significant effects;
- processing specific personal data;
- large-scale processing;
- systematic evaluation, scoring or monitoring of data subjects;
- matching or combining datasets;
- new technology; and
- processing that limits the exercise of data subject rights.
The assessment must be documented and reviewed when risk changes, and the controller must note the DPO’s advice where there is one (Article 121).
Payroll and HR records are a typical example, because they hold salary, tax and family data; see our guide to payroll outsourcing in Indonesia if a vendor processes them for you.
Where a business installs cameras or other visual-data devices in public areas and records, PP 33/2026 also requires a clear notice that the device is operating, with a contact point.
Data Breach Notification
If personal data protection fails, the controller must notify the data subject and the supervisory agency in writing within 3 x 24 hours (UU PDP, Article 46(1); PP 33/2026, Article 114(1)). The period starts when the failure is known with certainty, reasonably and properly (Article 114(2)). The notice must state:
- what personal data was disclosed;
- when and how it was disclosed;
- what the controller is doing to handle and recover; and
- under PP 33/2026, the contact details of the DPO or a designated contact.
The controller must also inform the public when the failure disrupts public services or has a serious effect on the public interest (Article 115). It must document the incident and give the documentation to the agency (Article 116), keep internal breach policies and procedures (Article 117), and require processors to report a breach to the controller at the first opportunity (Article 118).
Many companies still use a 14-day period for breach notices. That is not what UU PDP or PP 33/2026 says.
Data Protection Officer (PPDP)
A controller and a processor must appoint a personal data protection officer (PPDP) when:
- the processing is for public service;
- the core activities require regular and systematic monitoring of personal data on a large scale; and/or
- the core activities consist of large-scale processing of specific personal data or data related to criminal acts.
Article 53(1) of UU PDP originally joined these conditions with “and”. Constitutional Court Decision No. 151/PUU-XXII/2024, delivered on 30 July 2025, changed the word at the end of the second condition to “and/or”, and PP 33/2026 Article 142(1) now uses “and/or”. In practice, meeting any one condition can trigger the duty to appoint a PPDP. Whether a business meets the “large scale” threshold depends on guidance the agency has not yet published.
The PPDP is chosen for professional competence, knowledge of law and data protection practice, and can be internal or external (Article 143 and 144). The appointment must take account of the organisation’s structure, size and needs. PP 33/2026 Article 146 requires management to involve the PPDP in processing activities, give it access to top management, keep it independent and free of conflicts of interest, and give it enough resources. A company with no PPDP obligation can still appoint one voluntarily, and doing so is a sensible way to organise compliance.
Transferring Personal Data Outside Indonesia
A controller may transfer personal data abroad if it follows these steps in order (UU PDP, Article 56; PP 33/2026, Article 165):
- Equivalent or higher protection. The receiving country must have equivalent or higher protection than UU PDP. The agency assesses this and must publish a list of such countries and international organisations (Article 168(2)). We have not seen that list.
- Adequate and binding safeguards. If step 1 is not met, the controller must ensure adequate and binding protection, such as legally binding instruments, standard contractual clauses set by the agency, binding corporate rules within a corporate group, or other instruments the agency recognises (Article 169). Binding corporate rules need the agency’s approval before transfer (Article 171(3)).
- Data subject consent. If neither applies, the controller needs the data subject’s consent. PP 33/2026 narrows this route. Consent-based transfers are allowed only when the transfer is not repeated, involves a limited number of data subjects, is needed for a compelling legitimate purpose, the controller has assessed the risk and applied safeguards, and the controller has informed the agency and the data subject (Article 173(2)).
Before any transfer, the controller must map the transfer, assess the legal instrument, assess the transfer’s risk, and tell the data subject the purpose, the safeguards and the risks (Articles 161 to 164). A routine group-wide or cloud transfer therefore does not fit the consent route, and that includes sending employee data to a parent company for shadow payroll. Prepare standard contractual clauses or binding corporate rules and wait for the agency’s list and templates.
Enforcement and Penalties
Administrative sanctions
A breach of many of the law’s provisions can lead to a written warning, temporary suspension of processing, deletion or destruction of personal data, and/or an administrative fine (UU PDP, Article 57(2); PP 33/2026, Article 184). The maximum fine is 2% of the annual revenue or receipts attributable to the violation (UU PDP, Article 57(3); PP 33/2026, Article 185(1)). The regulation lists factors for setting the fine, including the harm caused, the duration, the type and number of data subjects affected, the controller’s openness and cooperation, its scale and its ability to pay. In some circumstances the fine can be set as low as zero (Article 185(3)). A fine becomes state non-tax revenue.
The sanctions are imposed by the supervisory agency (UU PDP, Article 57(4)). As of the latest reports we found, in mid-September 2026, that agency had not been formed and its establishing presidential regulation had not been issued. Until then, and for a wider view of your obligations, see our regulatory compliance service; the Ministry of Communication and Digital Affairs continues to oversee electronic system operators under Government Regulation No. 71 of 2019, and the administrative sanctions in PP 33/2026 cannot be applied by the agency. This needs verification before you rely on it, because the position can change quickly.
Criminal and civil liability
The criminal provisions of UU PDP apply now and do not depend on the agency. Unlawfully obtaining or collecting personal data that is not yours to benefit yourself or others carries up to 5 years in prison and/or a fine of up to IDR 5 billion; unlawfully disclosing it, up to 4 years and/or IDR 4 billion (Article 67); and creating or falsifying personal data, up to 6 years and/or IDR 6 billion (Article 68). When a corporation commits the offence, punishment can fall on its management, controllers, the person giving the order, beneficial owners and/or the corporation, and the fine for a corporation can be up to ten times the maximum fine (Article 70).
Data subjects also have the right to sue and claim compensation for violations (Article 12(1)). PP 33/2026 sets the procedures for compensation claims and dispute resolution, including mediation facilitated by the agency.
What to Do Before PP 33/2026 Takes Effect
You have until mid-January 2027. A practical plan:
- Map your data. List every processing activity, the data types, who has access and where data goes, as the records requirement asks.
- Document the lawful basis for each activity, and review any that rely on consent.
- Set up a rights-request process that can meet 3 x 24 hour deadlines and verify requesters.
- Prepare a breach response plan that can notify the data subject and the agency within 3 x 24 hours, and a decision on who tells the public if needed.
- Decide on a PPDP. Check whether any of the three conditions applies and whether the role is held internally or by an external provider.
- Review vendors and cross-border flows. Update processor contracts, map transfers, and plan for standard contractual clauses or binding corporate rules.
- Run impact assessments for high-risk processing, and document them.
- Watch the agency. Its regulations will fix many details, so check for its establishment and for the first agency rules.
How XPND Supports PDP Compliance
XPND helps foreign-owned and local companies map personal data, document lawful bases, draft rights-request and breach procedures, review vendor and transfer arrangements, and prepare for the agency’s rules. To start with a gap assessment, contact XPND.