Data breach notification to the NPC: Advisory 2026-02
In May the NPC clarified how breach notices go through its DBNMS. Some requests cannot be combined, and filing one does not stop the five-day full report.
Published · 4 min read

On 11 May 2026 the National Privacy Commission issued Advisory No. 2026-02, on how organisations submit personal data breach notifications through its online Data Breach Notification Management System, the DBNMS. It deals with the requests an organisation can file: to be exempted from notifying the people affected, to postpone notifying them, to use other means of reaching them, or to get more time to submit the required documents. Its message is short. Some of those requests cannot be made together, and filing any of them pauses nothing: only a written answer from the NPC can move a deadline.
The deadlines come from NPC Circular 16-03, the breach rules issued in December 2016. The NPC must be told within 72 hours of the organisation, or whoever processes data for it, knowing or reasonably believing that a breach has happened. Where 100 or more people are affected, or disclosing sensitive information would harm them, there may be no delay: the notice goes in on what is known, and the full report follows within five days. The people affected are to be told within 72 hours too. Since April 2022 notifications to the NPC have gone through the DBNMS, not by email, post, courier or in person. The advisory adds one step: while a request is pending, the full breach report goes by email to admindbnms@privacy.gov.ph, with the subject line FBR_NameofPIC_NameofDPO, within five days of discovery.
The requests that cannot go together
The logic is plain once it is stated, as the law firm Quisumbing Torres does in its summary of the advisory. A request for exemption says no notice to the people affected is owed. A request to postpone, or to use alternative means such as a public communication, accepts that notice is owed and asks about when or how. Filing both for one breach contradicts itself, and the advisory warns that conflicting requests may be denied, one or all of them. Postponement and alternative means can be asked for together, and a breach counts as one incident when it involves the same people, the same data and the same kind of breach.
Then the part that does the most damage when it is missed. A request waiting in the DBNMS stops nothing. The full breach report is still due within five days of discovery, whatever is pending. And the NPC's silence is not an answer: only a resolution issued in writing counts, and its inaction is not to be read as approval, implied consent or an automatic grant. Breaking these rules can bring administrative fines under the NPC's fining guidelines, Circular 2022-01.
The rules are in use. On 10 November the NPC said ten government agencies, among them the BIR, the SEC and the DICT, had filed breach notifications, each reviewed by its Compliance and Monitoring Division. A case that was not on that list is the subject of my piece on the DMW-linked backups.
A notice is a workflow with a deadline
A breach notice fails where any workflow fails, at the handovers. Someone notices something odd, someone decides whether it is a breach, someone works out whose data it touched, someone files and someone signs. If those people are not named before the day, the 72 hours are spent finding them.
Most offices hold personal data on people who never chose their systems: staff, members, applicants. When I work on a system that holds it, a data processing agreement is in place before I touch anything, and the circular expects that kind of contract. Section 16 asks an organisation to use contractual or other reasonable means to make sure whoever processes its data reports a breach to it. The useful clause says how fast, in hours, because the 72 hours can start when the processor knows.
Five things to settle before you need them
- Name the people: who assesses an incident, who files in the DBNMS, who emails the full report while a request is pending, and who signs. The circular asks you to identify the person responsible for notification, and the same system takes your annual security incident report, so let one person file both.
- Decide in advance which request, if any, you would make for each kind of breach, and never pair an exemption with a postponement or alternative means for the same incident.
- Treat the five-day full report as fixed unless the NPC grants more time in writing. A pending request does not move it.
- Treat silence as a no. Only a written resolution from the NPC counts.
- Write into every supplier contract how quickly, in hours, the supplier must tell you of a breach.
If your breach plan has never been tried against a real clock, the fit check is one place to start.
Sources
- National Privacy Commission, NPC Circular 16-03: Personal Data Breach Management, 15 December 2016
- Quisumbing Torres, Data Breach Notification Procedure Further Clarified, 4 June 2026
- DivinaLaw Legal Watch, NPC Advisory No. 2026-02
- Newsbytes.PH, NPC launches online system for data breach notification reporting, 22 April 2022
- Newsbytes.PH, NPC confirms data breach reports from 10 gov't agencies, 10 November 2026
Enrique Lacambra III builds internal business systems from Cainta, Rizal.
Tell me what is broken and I will tell you if it is worth building. A 20-minute call, no charge, and I will say so if you do not need me.
