Does Your Company Need a Data Protection Officer in Indonesia? The PP 33/2026 Triggers
November 13, 2026 · 5 min read · Etzal Group Team
Indonesia's Government Regulation 33 of 2026 (PP 33/2026), effective 16 January 2027, spells out when data controllers and processors must appoint a data protection officer, known locally as PPDP (pejabat or petugas pelindungan data pribadi), and what the role requires. For a mid-sized company this is an organisational and budget decision that lands exactly while 2027 plans are being drafted.
The question is rarely answered correctly at the first attempt. Some companies assume they are too small, although their core activity monitors thousands of people every day. Others appoint someone on paper only, with no time and no authority.
A note on sources: the article numbers below come from law-firm and consultancy summaries, not from the official text. The range is cited differently too: Veritask writes Articles 142 to 147, DFDL writes Articles 140 to 147.
What the regulation asks for
According to Veritask's summary (3 September 2026), a PPDP must be appointed in three situations:
- Processing personal data for public services.
- A core activity that requires regular and systematic monitoring on a large scale.
- Large-scale processing of specific data (the law's term for more sensitive categories) or data related to criminal offences.
Veritask also notes that the PPDP must have independent access to top leadership and adequate resources.
DFDL's summary (page updated 28 September 2026) adds two important points. First, the appointment triggers are "and/or" in line with Constitutional Court Decision 151/2024, so all three need not be met at once. Second, there is no numeric threshold for "large scale". DFDL also says the officer must be independent, with direct access to senior management and adequate resources.
RSM Indonesia (18 September 2026) maps the articles: appointment triggers in Article 142, appointment criteria of professionalism, knowledge and competence in Article 143, then duties, position, independence, resources and conflicts of interest in Articles 144 to 146.
Testing the three triggers
The questions below are our working tool for the DPO requirement Indonesia now sets, not official criteria. Answer them honestly and keep the answers.
Trigger 1: public services
- Do you process data on behalf of a government body or run a service assigned by the state?
- Are you a vendor or processor for a public service provider?
Note that the duty targets controllers and processors. A private company running systems for a public service should check this with legal counsel.
Trigger 2: regular and systematic monitoring on a large scale
- Does your core business depend on routinely observing people's behaviour? Examples worth checking: location tracking of driven fleets, loyalty programmes that record shopping patterns, apps with behavioural user profiles, CCTV analytics.
- Is the monitoring part of the product, not just support?
The key phrase is "core activity". Employee attendance at a factory is support. A platform that sells insight from user behaviour makes it core.
Trigger 3: specific or crime-related data, large scale
- Do you process specific data as a routine part of the business?
- Is the volume large relative to your size and service area?
Clinics, laboratories, employee health benefit providers, lenders and background check providers should test this trigger first.
On "large scale"
Because there is no numeric threshold, do not wait for an official number. Write a one-page memo: number of data subjects, data types, geographic reach, retention period and your conclusion with reasons. If in doubt, treat the trigger as met. A memo explaining why you appointed an officer never hurts. A memo that fails to explain why you did not can.
Three appointment models and their trade-offs
| Model | Strength | Weakness |
|---|---|---|
| Full-time internal | Knows the processes, always present | Fixed cost, hard to hire |
| Internal, combined with another role | Cheap, quick to appoint | Risk of conflict of interest and lack of time |
| External service | Expertise available at once | Needs legal confirmation, less familiar with daily operations |
A combined role is the most common choice in mid-sized companies and the one most often done badly. RSM's summary lists conflicts of interest among the matters regulated. Our advice follows from that: avoid giving the role to someone who decides the purpose and method of processing, such as the head of IT, marketing or HR. They would be reviewing their own decisions. Legal, compliance, risk or internal audit functions usually fit better.
An external service appeals to companies with no compliance function. The sources we read do not say whether the PPDP may come from outside the company. Do not assume it is allowed. Ask legal counsel before signing a service contract.
Resources you need to provide
The requirements of access to leadership and adequate resources, mentioned by all three summaries, are easy to write and easy to breach. In concrete terms, we suggest:
- a direct reporting line to directors, written into the appointment letter
- a clear time allocation if the role is combined, for example two days a week
- a budget for training and legal support
- access to the processing inventory, vendor contracts and incident logs
- a seat in approval meetings for projects that touch personal data
- assurance that performance is not appraised by the unit being overseen
The professionalism, knowledge and competence criteria cited by RSM mean the appointment should come with evidence: relevant work history, training or certification.
If your conclusion is "not required"
Still name one person responsible for data protection, even without the PPDP title. Other duties in PP 33/2026, such as the processing record, processor contracts and incident notification, still need someone to hold them. Revisit the conclusion whenever the business changes: a new product, an acquisition, or a public sector client.
What to do this week
- Answer the three-trigger questions with the heads of operations, IT and legal.
- Write the one-page "large scale" memo.
- Choose an appointment model and cost it for the 2027 budget.
- Draft the appointment letter with the reporting line and time allocation.
If the new officer needs systems that can show which data is kept where, our enterprise software team can help prepare them.
This article is not legal advice. Confirm the appointment duty for your company with legal counsel and the official text of PP 33/2026.
Sources
- Veritask, 3 September 2026: technical rules for personal data protection under PP 33/2026
- DFDL, page updated 28 September 2026: Indonesia personal data protection law, GR 33/2026
- RSM Indonesia, 18 September 2026: summary of PP 33/2026
Frequently asked questions
When must a company in Indonesia appoint a DPO?
According to Veritask's summary, when it processes data for public services, when its core activity requires regular and systematic monitoring on a large scale, or when it processes specific data or crime-related data on a large scale.
What number counts as large scale?
According to DFDL's summary, PP 33/2026 has no numeric threshold for large scale, so companies need to make their own assessment and record the reasoning.
Can the DPO be an external provider?
The sources we read do not say. Treat it as an option to confirm with legal counsel, not as a settled rule.
Related service
Free consultation
Not sure where to start? We will map the right system for your business, free.
