When a data incident occurs, an enterprise has very little time to notify. The article helps it prepare an incident procedure in advance, so that it notifies the right people on time.

About this article

When an enterprise discovers a violation that may harm data subjects, it has 72 hours to notify the specialised personal data protection authority. For location data, biometric data and sensitive financial data, it must also notify the affected individuals within the same period. Cybersecurity law adds duties to respond to incidents, keep system logs and store data in Vietnam.

The content is for general information and does not replace legal advice on a specific case.

1. The 72 hours run from discovery of the violation

The controller, the controller and processor, and third parties must notify the specialised personal data protection authority no later than 72 hours after discovering a violation. This duty applies where the violation may harm national defence, national security, public order and safety, or may infringe the life, health, honour, dignity or property of data subjects.

Three points matter when determining the duty:

  • The clock starts at discovery, not when the investigation into the cause is complete. The enterprise should not wait for full information before notifying.
  • The threshold is "may cause harm". Many leaks of customer data, such as phone numbers with purchase history, can lead to fraud. These incidents therefore usually must be notified.
  • A processor does not notify the authority directly but must promptly notify the controller. The controller should set in the contract a specific deadline for the processor to notify it, such as 24 hours. The controller then has enough time to notify the authority.

The controller must also do four things: make a written record confirming the violation; stop the violation; remedy its consequences; cooperate with the authority while the matter is handled.

2. Notice to the authority uses the prescribed form and has four groups of content

The enterprise sends the notice in the prescribed form, directly or through the National Personal Data Protection Portal. The notice contains:

  • A description of the violation: time, place, conduct, organisations and individuals involved, types of data and volume of data.
  • Contact details of the data protection unit or personnel, or of the data protection service provider.
  • The possible consequences and damage.
  • The measures taken to address and mitigate the harm.

The notice must be truthful. If the enterprise deliberately conceals or misstates the nature or scale of the incident or the number of people affected, the enterprise is sanctioned for a separate violation.

3. Three groups of incidents must also be notified to affected individuals

3.1. Incidents involving location data or biometric data

The controller must notify the affected data subjects within 72 hours from discovery. The notice must contain at least:

  • When and how the violation was discovered.
  • The type of data affected: location, biometric or both.
  • The severity and the risks to the data subject's rights and interests.
  • The measures taken, under way and planned to remedy the incident.
  • Guidance for data subjects on protecting themselves.
  • Contact details of the data protection personnel and the incident handling unit.

If the enterprise cannot notify everyone affected for technical or emergency reasons, it must publish a notice on its official website or app. It then sends individual notices as soon as possible. The enterprise must keep the incident file for at least 5 years from the date the incident is fully remedied.

3.2. Leak or loss of sensitive data in finance, banking and credit information

The organisation that collected the data directly must notify both the authority and the data subjects no later than 72 hours after discovering that sensitive data has been leaked or lost. The notice must contain at least the content listed in section 3.1. This group includes banks, finance companies, payment intermediaries, e-wallets, securities companies, insurers and credit information organisations.

3.3. Processing of biometric data that causes damage to the data subject

Apart from incidents, where the processing of biometric data causes damage, the organisation collecting and processing the data must notify the person harmed.

4. Cybersecurity law adds overlapping duties

A data leak is often also a cybersecurity incident. Under the Law on Cybersecurity 116/2025/QH15, effective from 1 July 2026, and its implementing rules effective from 19 August 2026, enterprises also have the following duties:

  • Incident response and remediation. The owner of an information system must have an incident response plan suited to the system's security level. For information systems important to national security, when an incident exceeds the owner's capacity to handle, the owner must do three things: immediately notify the specialised cybersecurity force; preserve the scene and evidence; report on the remediation.
  • System logs. Enterprises providing services on telecommunications networks, the internet and value-added services in cyberspace must keep system logs, including accounts, login and logout times, IP addresses, source ports and logs of information processed. The logs must be retrievable for at least 12 months.
  • Data storage in Vietnam. Domestic enterprises providing these services must store in Vietnam the personal information of users in Vietnam, data created by those users and data on users' relationships. Foreign enterprises must store data and open a branch or representative office in Vietnam only when the Minister of Public Security so decides. Such a decision may be issued only after the enterprise has failed to comply with 3 written requests within up to 6 months. After the decision, the foreign enterprise has 12 months to comply and must store the data for at least 24 months.

The duty to keep system logs helps the enterprise meet its duty to notify. System logs are the main source for establishing the time, scope and volume of the data leaked, which are mandatory contents of the 72 hour notice. If it does not keep logs, an enterprise breaches cybersecurity law and will also struggle to notify correctly and completely. An organisation that fails to keep logs for the required period may be fined VND 60 million to 100 million.

5. Four cases and the conclusions

5.1. A cloud storage bucket left open to the public

A retail chain discovers that a cloud storage bucket has been publicly accessible for three weeks. The bucket holds an export of 80,000 customers' data. This is a hypothetical case. The data includes names, phone numbers and purchase history. This data may be used for fraud.

The enterprise must do four things: lock the bucket; use the access logs to identify who downloaded the file; make a written record; notify the authority within 72 hours from discovery. For this type of data, the enterprise does not have to notify customers. Even so, it should notify them so that customers stay alert.

5.2. Unauthorised access to a facial recognition attendance system

A vulnerability in a factory's facial recognition attendance software is exploited. The incident exposes face images and biometric templates of 1,200 employees. This is a hypothetical case. The enterprise must notify the authority and each employee within 72 hours. The notice must contain the minimum content. The enterprise must also keep the incident file for at least 5 years.

5.3. An e-wallet exposes transaction histories

An e-wallet discovers a bug that lets users see other users' transaction histories. This is a leak of sensitive financial data. The e-wallet must notify both the authority and the affected users within 72 hours. If it notifies late, the e-wallet may be fined VND 50 million to 70 million.

5.4. An outsourced payroll provider falls for a phishing email

An employee of a payroll service company clicks a fake link, exposing login credentials to clients' payroll data. This is a hypothetical case. The payroll company is a processor, so it must promptly notify each client. Each client, as controller, makes its own assessment and notifies the authority within 72 hours of discovering the violation.

The law does not set a separate starting point for a controller that learns of a violation from its processor. In our assessment, each client should count the 72 hours from the moment it receives the payroll company's notice, and should not wait until its own checks are complete.

6. Fines relating to incident notification

ConductFine for an organisation
A processor not promptly notifying the controller; no written record; deliberately concealing or misstating incident informationVND 10 million to 20 million
Notifying the authority later than 72 hoursVND 40 million to 60 million
Not notifying the authority and affected individuals within 72 hours for incidents involving location or biometric data; not keeping the file for 5 yearsVND 50 million to 70 million
Finance and banking: no notice or notice later than 72 hours; incomplete noticeVND 50 million to 70 million
Not stopping the violation, not remedying its consequences, not cooperating with the authorityVND 60 million to 80 million

Besides these fines for notification, the enterprise may be fined for other violations linked to the incident, such as failing to apply security measures or to encrypt data in the cloud. The enterprise may also have to compensate those harmed.

7. Europe also uses 72 hours but allows a risk assessment

IssueVietnamGDPR
Notice to the authorityWithin 72 hours where the violation may cause harmWithin 72 hours where feasible, unless the breach is unlikely to result in a risk to individuals; reasons must be given for any delay
Notice to data subjectsMandatory for location, biometric and sensitive financial data; within 72 hoursMandatory where the risk is high, for any type of data; without undue delay
RecordsAt least 5 years for incidents involving location or biometric dataAll breaches documented, with no specific period
ProcessorPromptly notifies the controllerNotifies the controller without undue delay

Enterprises with GDPR procedures usually already work to 72 hours. They need to make two adjustments:

  • In Vietnam, whether affected individuals must be notified depends on the type of data, not on the level of risk.
  • The deadline for notifying affected individuals is a fixed 72 hours.

8. What to avoid when handling a data breach

  • Waiting until the investigation ends before notifying, missing the 72 hour deadline.
  • Having no prepared notice template, so time is lost gathering information when an incident occurs.
  • Signing contracts with processors that set no incident notice deadline.
  • Not keeping enough system logs, so the scope of the leak cannot be established.
  • Treating incidents as purely an IT matter, without involving the data protection personnel and the legal team.

9. What enterprises should do

  • Issue an incident response procedure stating who decides, the 72 hour deadline and a contact list.
  • Prepare notice templates for the authority and for affected individuals, especially for biometric and financial data.
  • Add incident notice terms to contracts with processors, with a deadline shorter than 72 hours.
  • Check the log configuration so that logs can be retrieved for at least 12 months.
  • Determine whether data must be stored in Vietnam if the enterprise provides online services.
  • Run an incident drill at least once a year and keep a record of it.

Read on in the Personal data protection series