SentraMind

Understanding

Breach clocks are not one clock

Singapore, Malaysia, Indonesia, Vietnam, and Thailand publish different notification deadlines. A single “72 hours” label hides the six-hour case.

Relative length of the in-force windows. Three days is drawn as 72 hours so the 6-hour duty stays visible.
  • Malaysia NCII initial 6 h
  • Singapore PDPA notice 3 days
  • Malaysia PDPA notice 72 h
  • Indonesia Art. 46 3×24 h
  • Vietnam to A05 72 h
  • Thailand PDPA 72 h

One regional label hides the duty that applies

Singapore, Malaysia, Indonesia, Vietnam, and Thailand each publish notification deadlines, and the deadlines are attached to different statutes and different populations. A slide that prints a single “72 hours” for the region has chosen the number that appears most often and dropped the rest. We checked the figures below on 12 August 2026 against the regulators’ and gazettes’ published texts, using archive copies and law-firm confirmation where an official site could not be reached directly, and reconfirmed every clock on 27 August 2026. Counsel decides what they require of a particular organisation.

The product implication is narrow: an incident export needs timestamps and harm-assessment fields that can be lined up with these clocks. The six-hour Malaysian infrastructure clock is the case that drives the design, because it is the shortest fixed interval among the duties in force.

Singapore gives an assessment window, then three calendar days

Part 6A of Singapore’s Personal Data Protection Act 2012 (PDPA) sets a clock with two stages. By the benchmark of the Personal Data Protection Commission (PDPC), the organisation has about thirty days to assess the breach. Once the breach is notifiable, notice to the PDPC is due within three calendar days.

A breach is notifiable at five hundred or more people, or where significant harm is likely. The three days run from notifiability, not from the first moment someone suspects that something went wrong. A template that starts a 72-hour timer for Singapore on day one is applying another country’s shape to this statute.

Malaysia publishes two clocks

Under Malaysia’s Personal Data Protection Act, as amended by Act A1727 and in force for this duty from 1 June 2025, the organisation has 72 hours to notify the Personal Data Protection Commissioner. Affected people are notified within seven days after that notice, where the trigger is significant harm or more than one thousand people. That pair is one duty, with two recipients and two intervals.

The Cyber Security Act 2024 (Act 854) sets a different duty for national critical information infrastructure, owed to the National Cyber Security Agency (NACSA): immediate electronic notice, an initial report within six hours, and a supplemental report within fourteen days. Government and banking are among the act’s eleven sectors. An export that can represent only a 72-hour personal-data notice cannot represent the six-hour report, which is why that report is the design-driving case.

Indonesia writes three times twenty-four hours

Article 46 of Indonesia’s personal-data law, UU PDP (Law 27/2022), requires written notice to the people affected and to the authority within three times twenty-four hours. We keep that interval in the statute’s own form. An export should be able to name article 46 and to show both recipients.

As of late August 2026, the implementing regulation is still unsigned and the personal-data authority, Badan PDP, does not yet exist. Administrative fines are dormant, while criminal provisions are live. Orientation can state the written interval. It cannot tell a reader that an administrative fine is currently being imposed, and it cannot skip the interval because the institution is unfinished.

Vietnam and Thailand are not the same 72 hours

Vietnam’s Personal Data Protection Law 91/2025/QH15 and Decree 356/2025/ND-CP set notice to A05, under the Ministry of Public Security, at 72 hours. Where the breach involves location or biometric data, the people affected must also be told within 72 hours. The authority and the extra recipient are part of the clock.

Thailand’s Personal Data Protection Act B.E. 2562 and the committee’s B.E. 2565 notification set 72 hours to the Personal Data Protection Committee, with notice to people when the risk is high. The first fine, in August 2024, included THB 3 million for missing that 72-hour notice, which is why the interval should be read as operative. A 24-hour clock for critical information infrastructure appears only in a draft amendment to the Cybersecurity Act. A page that prints the 24-hour figure as a current Thai duty is ahead of the law.

The export names the clock, and the calculator does not file

A product field that stores one “notify by” instant, with no jurisdiction and no population, will be wrong in at least one of these markets. The export has to be able to say which clock it is computing, who the notice is for, and which timestamps the harm assessment used. Those fields are the product claim. They do not file the notice.

The browser demonstration computes intervals from these deadlines so a reader can see the arithmetic. It is a calculator. Filing remains the organisation’s obligation, taken with counsel, against the text counsel tells them to use. Two items were unsettled when we last checked and should be rechecked before anyone relies on them: Indonesia’s pending authority and the Thai draft.

How to read this

Notice windows in force when we last checked on 27 August 2026. Draft clocks are not drawn.
Notice windows in force when we last checked on 27 August 2026. Draft clocks are not drawn.
MarketIn-force notice windowNot the same as
Singapore PDPA About 30 days to assess, then 3 days to notify Malaysia’s 6-hour infrastructure report
Malaysia 6 hours for NCII, 72 hours for personal data One field called “72 hours”
Indonesia, Vietnam, Thailand PDPA 72 hours, different authorities Thailand’s draft 24-hour clock

Orientation only. This briefing is not legal advice. A watch-list item is not a statement that the cited instrument is in force.