Business

72 Hours to Report a Data Breach in Indonesia: What Must Be Ready by 16 January 2027

November 13, 2026 · 6 min read · Etzal Group Team

From 16 January 2027, Indonesia's Government Regulation 33 of 2026 (PP 33/2026) requires companies to notify data subjects and the supervisory agency in writing no later than 3 x 24 hours after a personal data protection failure becomes known. The regulation, which implements the Personal Data Protection Law, also sets out what the notice must say and what incident documentation must be kept.

For Indonesia breach notification, seventy-two hours sounds generous until you count what has to fit inside: confirming the event, sizing the affected data, drafting the letter, getting leadership approval and sending it. Companies without a procedure usually spend the first day working out who has the authority to decide.

A note on sources: the article numbers below come from law-firm and consultancy summaries, not from the official text. We read the detail of Articles 116 to 119 in one summary only.

What the regulation asks for

According to Veritask's summary (3 September 2026):

  • Article 114. Written notice to data subjects and the agency (the Lembaga) within 3 x 24 hours, or 72 hours, from the time the failure is known with reasonable certainty. The notice covers the data disclosed, when and how it was disclosed, the steps taken, and the contact of the data protection officer (PPDP) or a contact person.
  • Article 115. Public notification is required when the failure disrupts public services or seriously affects the public interest.
  • Articles 116 to 119. Incident documentation records the affected data, a description, the impact, recovery and the notification timeline, and is submitted to the agency. A processor must report a failure to the controller at the first opportunity.

RSM Indonesia (18 September 2026) maps it slightly differently: Article 117 covers internal policy, role allocation, escalation and post-incident review, while Article 118 covers the processor's duty to report to the controller. The two summaries agree on substance but not exactly on numbering, so check the official text.

When the clock starts

This is the question that matters most. DFDL's summary (page updated 28 September 2026) says the clock runs from when the controller has established the failure in a manner that is "certain, proper and reasonable" (in Indonesian, "pasti, patut dan wajar"). Veritask uses the phrase "known with reasonable certainty".

So there is a gap between the first alert and the start of the clock. That gap is not room to stall. If a company is deliberately slow to investigate so that the clock has not started, its own timestamps will show it. The safer stance is to set an internal deadline for verification and record the reason for every decision.

Where reports go while the agency does not exist

Katadata reported on 5 November 2026 that until the supervisory agency is formed, the Ministry of Communication and Digital Affairs (Komdigi) continues to carry out the personal data protection function. The sources we read do not describe a reporting address or form for the interim period. Do not guess. Check Komdigi's latest official announcement before 16 January 2027, and check again when an incident occurs, because the agency's status can change.

A one-page incident procedure

This section is our practical advice. Nobody reads a long procedure in a crisis, so aim for one page that answers six things.

1. Who decides that the clock has started. Name one person and one deputy, with phone numbers. The decision cannot depend on a meeting. This is usually the data protection lead or the head of IT, with a duty to inform directors within hours.

2. A verification deadline. Set, for example, 24 hours from the first report to answer three questions: is personal data involved, whose data, and was there in fact access, disclosure or loss. If the answers are not in, the decision escalates to directors.

3. Who drafts and who approves the letter. Prepare a template now, not during the incident. The template follows the content listed in Veritask's summary: what data was disclosed, when and how, what has been done, and whom to contact.

4. How to reach data subjects. Email, message, letter or an in-app notice. Decide the channel per group: customers, employees, suppliers. Check whether your contact data is complete enough to do it.

5. Evidence to keep. Preserve from the first minute:

  • relevant system and access logs, copied to a location where they cannot be altered
  • a decision timeline with times and names
  • the list of data and number of data subjects affected, with the counting method
  • copies of notices and proof of sending
  • recovery steps and the post-incident review

6. What to ask of vendors. Because a processor must report to the controller at the first opportunity, make sure the contract states a clear deadline in hours, an emergency contact that works around the clock, the minimum content of the report and a duty to hand over logs. A vendor that reports on day three makes your own deadline impossible.

The trade-offs you will face

  • Fast or complete. A notice sent at hour 60 is rarely complete. It is better to send an accurate notice that says more information will follow than to wait for full certainty and miss the limit.
  • Cautious or open. Overly defensive language makes customers assume the worst. Overly detailed language can help an attacker. Name the types of data and the steps recipients should take, without publishing the technical detail of the weakness.
  • Own team or forensic help. Internal staff know the systems, but they are also busy restoring service. Agree now when outside help is called and who can approve the cost.

Test it before January

Run a one-hour tabletop exercise with a simple scenario, such as a lost sales laptop or a hijacked email account. Measure three things: how long until the decision maker knows, how long until a list of affected data exists, and whether the letter template can be filled in without guessing. A first exercise almost always shows that what is missing is the data list and the contacts, not the technology.

If your systems do not yet produce logs good enough to answer "whose data was affected", our enterprise software team can help assess and fix that.

This article is not legal advice. Confirm your company's obligations with legal counsel and the official text of PP 33/2026.

Sources

Frequently asked questions

When does the 72-hour clock start in Indonesia?

According to Veritask's summary, when the failure is known with reasonable certainty. DFDL describes it as the point at which the controller has established the failure in a certain, proper and reasonable manner.

Who must be notified?

The affected data subjects and the supervisory agency. Because the agency has not yet been established, check the latest official announcement from the communications ministry for the reporting channel.

What must a vendor that processes our data do?

According to summaries by Veritask and RSM Indonesia, a processor must report a data protection failure to the controller at the first opportunity.

Author

Etzal Group Team

Etzal Group Team, helping businesses grow with technology. Contact us.

Related service

Free consultation

Not sure where to start? We will map the right system for your business, free.