Fines up to 2% of Annual Revenue: How Indonesia's Data Protection Sanctions Are Calculated
November 13, 2026 · 5 min read · Etzal Group Team
Indonesia's Government Regulation 33 of 2026 (PP 33/2026), effective 16 January 2027, sets four types of administrative sanction for personal data protection violations, with a fine of up to 2% of annual revenue or receipts. According to Veritask's summary (3 September 2026), the regulation also contains factors that can bring the ceiling down to zero rupiah.
For finance leaders, those two figures, 2% and zero, mark the range of exposure. Where your company would land within it is decided mostly by what is done before an incident, not after.
Three limits need stating up front. The article numbers below come from law-firm and consultancy summaries, not from the official text. No fine has been imposed under this regulation, and its supervisory agency has not been established. The calculation procedure still awaits that agency's rules, so check the latest official announcement before using any figure in provisioning.
What the regulation provides
According to Veritask's summary, Articles 184 to 185 set out four sanctions:
- A written warning.
- Temporary suspension of personal data processing.
- Deletion or destruction of personal data.
- An administrative fine.
Sanctions can be imposed cumulatively. The fine is at most 2% of annual revenue or receipts. That ceiling can be lowered to as little as zero based on factors such as impact, duration, the number of data subjects affected, the scale of the business and cooperation during the examination.
SIP Law Firm (8 November 2026) notes that the four sanctions and the 2% ceiling originate in Article 57 of Law Number 27 of 2022, the Personal Data Protection Law. PP 33/2026 details how they are applied.
DFDL's summary (page updated 28 September 2026) adds detail that matters to finance:
- "Revenue" is defined in Article 185 as the gross inflow of economic benefits from ordinary business activities, excluding contributions from capital providers.
- Article 185 paragraph (2) contains ten calculation variables.
- Article 187 leaves the procedure to a regulation of the agency (the Lembaga).
- An objection is filed within 14 working days and does not automatically suspend enforcement. A claim before the State Administrative Court (PTUN) remains open.
Reading the exposure correctly
This section is our analysis, not the wording of the regulation.
The base is gross, not profit
The definition summarised by DFDL uses gross inflow. For thin-margin businesses such as distribution and trading, 2% of gross revenue can equal most of a year's net profit. Purely as arithmetic: on annual revenue of Rp100 billion, the ceiling is Rp2 billion. That is a ceiling, not an estimate of a fine.
The sources we read do not explain which financial year is used, or whether the base is a single entity or a group. Ask legal counsel, and watch for the agency regulation that will set the procedure.
The fine is not the most expensive sanction
A temporary suspension of processing can hurt more than a fine. If the order hits sales, payroll or customer service systems, the loss is counted per day. A deletion order can also erase an asset: a customer database built over years.
Because sanctions can be cumulative, the worst case is not "a 2% fine" but a fine plus suspension plus deletion. Put all three in the risk register.
An objection does not stop the clock
Per DFDL, an objection does not automatically suspend enforcement. From a cash perspective, treat a sanction as a liability that may fall due before the dispute is resolved. Fourteen working days is also short, so the defence file has to exist before it is needed.
Mitigating factors and their evidence
The factors summarised by Veritask can be mapped to evidence you should already hold. This table is our practical suggestion.
| Factor | What lowers exposure | Evidence to prepare |
|---|---|---|
| Impact | Leaked data is limited and encrypted | Encryption policy, data classification |
| Duration | Incident detected and stopped quickly | Monitoring logs, incident timeline |
| Number of data subjects | Data is not kept beyond need | Retention policy, proof of periodic deletion |
| Business scale | Outside your control | Financial statements |
| Cooperation | Documents handed over fast, consistent answers | Processing record, processor contracts, DPIAs, request log |
The pattern is visible: nearly all the evidence consists of documents that other parts of PP 33/2026 already require. A company that does the basic obligations is building its defence file at the same time.
Two factors deserve particular attention.
Retention. The number of data subjects affected by an incident depends on how much data you hold. Deleting inactive customer data and old job application archives is the cheapest way to cut exposure. The trade-off is that marketing and analytics lose some historical data, so this decision belongs at director level.
Cooperation. Being cooperative does not mean admitting everything. It means being able to answer quickly and consistently. That is only possible with one accountable person, one document store and a tidy decision record.
What finance leaders should do
- Put it in the risk register. Record three scenarios: fine, temporary suspension and data deletion, each with a risk owner.
- Work out your own ceiling. Take 2% of gross revenue for the last financial year as an internal reference figure, noting that the official procedure is not yet published.
- Check the cyber insurance policy. Ask your broker whether administrative fines, notification costs and business interruption are covered, and what the exclusions are.
- Fund the basics. The inventory, contracts, incident procedure and retention need a small budget relative to the exposure.
- Ask for regular reporting. One page per quarter from the data protection lead: document status, incidents and data subject requests.
Do not use cases from other countries to estimate Indonesia data protection fines. The legal basis differs and there is no enforcement practice yet.
If a retention policy is hard to run because core systems have no scheduled deletion feature, our enterprise software team can help add it.
This article is not legal or accounting advice. Confirm the exposure and any provisioning treatment with legal counsel, your auditor 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
- SIP Law Firm, 8 November 2026: corporate legal compliance checklist 2027
Frequently asked questions
What is the maximum fine for a personal data violation in Indonesia?
According to summaries by Veritask and SIP Law Firm, the administrative fine is at most 2% of annual revenue or receipts.
Can the fine be lower than that ceiling?
According to Veritask's summary, the ceiling can be reduced to as low as zero based on factors such as impact, duration, number of data subjects affected, business scale and cooperation during the examination.
Has any company been fined under PP 33/2026?
No. The regulation only takes effect on 16 January 2027, the supervisory agency has not been established, and the calculation procedure still awaits that agency's rules.
Related service
Free consultation
Not sure where to start? We will map the right system for your business, free.
