Skip to main content

Personal Data Protection

Legal Support for Personal Data Breaches and Incidents in Vietnam

Justix advises Vietnam-based companies and foreign-invested businesses when personal data is exposed, accessed without authority, used outside its permitted purpose or affected by a security incident. We assess legal roles and notification duties, draft incident records and regulatory communications, coordinate with technical teams and vendors, and recommend legally grounded remediation. Digital forensics and technical recovery are separately provided.

Who this service is for

  • Vietnamese companies that discover possible exposure or unauthorized disclosure of customer, employee or user information.
  • Ecommerce, SaaS, technology, finance and healthcare businesses processing sensitive, location or biometric information.
  • Foreign-invested companies that must coordinate a Vietnam incident response with regional headquarters and legal teams.
  • Cloud, payroll, marketing or software service providers that detect a potential personal-data violation in systems they operate.
  • In-house legal, compliance, HR, IT and risk-management teams responding to individual complaints or authority inquiries.

Common problems we solve

  • The team cannot determine whether a breach has occurred

    A missing device, suspicious login or exposed file is reported, but there is insufficient verified information on affected data, legal roles and whether notification obligations have been triggered.

  • Headquarters applies a blanket 72-hour deadline

    The group policy treats every alert alike without distinguishing Article 23(1), the additional reporting cases in Article 23(3), processor-to-controller notification and special rules for location or biometric data.

  • Incident evidence is not properly preserved

    Relevant access records may be overwritten, staff messages lost or initial decisions undocumented; the legal team cannot reconstruct the sequence reliably.

  • Vendors give incomplete or delayed information

    A cloud, CRM or outsourcing provider reports a possible incident but has not confirmed the affected processing, log availability, containment measures or contractual responsibilities.

  • The proposed customer notice is not yet accurate

    Communications teams want to announce an affected-customer count before validation, while other stakeholders propose waiting indefinitely for a final forensic report.

  • Location or biometric records may be affected

    A transport, attendance or identity-verification system may have exposed regulated categories that trigger distinct customer-notification and record-retention requirements.

  • Technical remediation is complete but legal work remains open

    Accounts are secured, yet the incident record, regulatory analysis, customer requests, vendor responsibility and changes to relevant policies remain unresolved.

What Justix does for you

  • 01

    Conduct legal intake and fact mapping: Document detection time, involved systems, categories, recipients, existing evidence and outstanding questions, working from IT-provided information rather than purporting to conduct a forensic examination.

  • 02

    Assess roles, deadlines and reporting triggers: Distinguish controller, combined controller-processor, processor and third-party duties; assess Article 23 and specific obligations under Article 29 of Decree 356.

  • 03

    Prepare incident and notification documents: Assist with incident minutes, Article 28 notification content, Form No. 08 where applicable, individual notices and other written explanations under the agreed mandate.

  • 04

    Coordinate with technical responders and providers: Identify evidence to preserve and legal questions requiring log analysis; review contractual duties to supply information, support containment and cooperate with the customer.

  • 05

    Advise on external communications and remediation: Review proposed notices and responses to affected individuals, suppliers and authorities; recommend corrective legal and contractual actions with designated client decision-makers.

  • 06

    Close out the legal response: Organize the incident chronology, communications, evidence register, unresolved obligations and post-incident changes to policies, processes or agreements.

What you receive

  • Preliminary legal assessment identifying statutory roles, reporting questions and facts requiring confirmation.
  • Incident timeline, evidence-preservation request list and responsibility matrix across Vietnam management, legal, IT and vendors.
  • Draft incident minutes, Form No. 08 notification where applicable and supporting regulatory explanations within scope.
  • Draft communication for affected individuals, counterparties or authorities where a legal basis for notification exists.
  • Vendor information-request and cooperation documents, plus a legally prioritized corrective action register.
  • Legal close-out memorandum identifying outstanding duties, record retention and prevention measures.

Team in charge

  • LL.M.

    Nguyễn Phúc Mạnh

    Head of Corporate Legal Affairs & Contracts

    Corporate legal affairs, contracts and employment law

    10 years of experience

  • Jurist

    Trần Thanh Nhàn

    Head of Corporate Legal Department – Licensing and Administrative Procedures

    Intellectual Property & Corporate

    9 years of experience

  • Kỹ sư công nghệ

    Trần Văn Tùng

    Cố vấn kỹ thuật về bảo vệ dữ liệu cá nhân

    Công nghệ thông tin & bảo vệ Dữ liệu cá nhân

    10 years of experience

How it works

  1. 1

    Step 1. Capture the initial situation

    Confirm what was discovered, when, in which system, what categories may be affected, and the internal decision-making and technical-response owners.

  2. 2

    Step 2. Determine notification obligations

    Apply the correct statutory role and triggering conditions, identify any relevant deadlines, proposed recipients and missing verified facts.

  3. 3

    Step 3. Prepare legal documents

    Draft incident records, communications and any applicable Form No. 08, using confirmed technical findings and clearly identified uncertainties.

  4. 4

    Step 4. Coordinate and update the response

    Review vendor answers, individual inquiries and authority requests; update legal recommendations if facts or impact change.

  5. 5

    Step 5. Document close-out and next actions

    Deliver the correspondence and decision record, remaining legal tasks, evidence-retention considerations and improvement recommendations.

What you need to prepare

  • An initial incident account: detection time, reporters, affected systems, observed conduct and containment steps already taken.
  • Known data types and populations affected, with sources for estimated numbers and a distinction between confirmed and unconfirmed figures.
  • Preserved technical reports, logs and vendor alerts that can be safely shared; passwords or unnecessary raw personal data should not be sent.
  • Relevant service agreements, DPAs, response SLAs and privacy policies, including contact details for suppliers.
  • Existing incident-response plans, internal records, notices already sent and any customer or regulator correspondence.
  • Authorized management contact plus Vietnam legal, IT, communications and vendor-management representatives.

Timeline

Legal assessment and document milestones are agreed after initial fact gathering, considering statutory deadlines, incident complexity and available client personnel.

The service does not imply a 24/7 incident-response retainer or a fixed response-time promise. Statutory 72-hour duties apply only where the legal conditions are met.

Fees

Quoted per incident based on urgency, entities, systems, affected data, vendors, legal documents and authority interactions. No verified published flat fee is available. Forensic investigation, system recovery, penetration testing, litigation and continuing advisory support require separately agreed work.

How our fees work

Justix advises Vietnam-based companies and foreign-invested businesses when personal data is exposed, accessed without authority, used outside its permitted purpose or affected by a security incident. We assess legal roles and notification duties, draft incident records and regulatory communications, coordinate with technical teams and vendors, and recommend legally grounded remediation. Digital forensics and technical recovery are separately provided.

What to do when personal data may have been compromised

An incident may involve an unauthorized file disclosure, account compromise, suspicious access to a customer system or an unlawful use of employee records. Record the detection time, affected processes and immediate containment measures. The technical team should preserve evidence and assess systems while legal counsel determines notification and role-specific obligations.

Justix organizes the legal fact-gathering and supports the company in identifying responsible individuals, legal deadlines and documents. The analysis should begin promptly rather than waiting for a full forensic close-out.

Distinguishing security alerts from personal data violations

A security warning does not by itself prove personal data has been disclosed. Conversely, using contact records for an unauthorized purpose can raise personal-data compliance concerns without any system intrusion.

The company needs evidence concerning the nature of information, individuals involved, recipients, purpose, rights and potential harm. Those findings inform Article 23 of Vietnam’s Law No. 91/2025/QH15 and any applicable sector requirements.

Authority notification and the 72-hour rule

Article 23(1) provides for notice to the competent personal-data authority within 72 hours of discovery where the specified controller, combined controller-processor or third party discovers a violation capable of the harms described in the Law. A processor that discovers a violation must promptly notify its controller or combined controller-processor.

Article 23(3) also lists circumstances for notifying the authority, including prohibited or non-agreed processing and failures to uphold individual rights. The applicable duties depend on statutory role, facts and relevant triggering conditions, not a blanket rule for every incident.

What a Form No. 08 notification should cover

Article 28 of Decree No. 356/2025/ND-CP identifies the incident description, timing, location, affected categories and volume of data, privacy contacts, potential consequences and mitigation actions. It directs relevant parties to use Form No. 08 and the applicable statutory submission channel.

Justix can prepare an incident record, review supporting materials and draft the required notice. Unverified details should be identified as such; figures should not be presented as final without an evidentiary basis.

Special obligations for location and biometric data

Article 29 of Decree No. 356/2025/ND-CP requires controllers and combined controller-processors, where an incident involves location or biometric personal data, to notify affected individuals within 72 hours of discovery and make the specified authority report. It also requires incident records to be retained for at least five years after remediation.

The individual notice includes the type of data, potential risks, protective actions and contact details. These special provisions should not be generalized to all ordinary personal data incidents.

Vendors, forensic responders and customer communications

A cloud, payroll or CRM provider may hold critical access records and be responsible for containment in its environment. Contracts and DPAs can establish evidence, contact and cooperation requirements; legal counsel should verify those provisions and coordinate requests.

Justix assists with contractual and regulatory communications. Qualified IT and forensic specialists remain responsible for collecting technical evidence, investigating systems, closing vulnerabilities and restoring services.

Deliverables, fees and work after the incident

Depending on scope, the company may receive a preliminary legal opinion, incident chronology, draft reports, communications, vendor requests and a remediation register. The work should close with a clear list of outstanding commitments and changes to policies or contracts.

Fees and delivery milestones depend on incident facts, affected entities, technical and vendor involvement, volume of legal documents and authority interactions. No 24/7 legal-response coverage or fixed fee is assumed. Forensics, system recovery, disputes and recurring support require separate agreements.

Legal basis: Article 23 of Law No. 91/2025/QH15; Articles 28–29 and Form No. 08 of Decree No. 356/2025/ND-CP. Confirm current filing procedures at the time of submission.

Frequently asked questions

Must every suspected personal data breach be notified within 72 hours?

No single deadline should be applied without identifying the relevant parties and triggers. Article 23(1) establishes a 72-hour authority notice for the specified roles and potential harms; Article 23(3) contains further notification cases.

What should a software processor do when it detects an incident?

Under Article 23(1), a processor must promptly notify its controller or combined controller-processor. Any other regulatory duty should be evaluated under the applicable provisions and its actual role.

Which reporting template applies in Vietnam?

Article 28 of Decree 356/2025/ND-CP prescribes the notification content and Form No. 08. The filing route and current administrative procedures must be confirmed when the report is made.

What if the number of affected people is still unknown?

Record what is verified and separate well-founded estimates from open questions. A missing final technical report is not a justification for ignoring a notification assessment or inventing affected-person counts.

Must every affected customer receive a notice?

The answer depends on the facts and applicable law. Article 29 of Decree 356 provides a specific 72-hour notice to affected individuals where the incident involves location or biometric data; other requirements must be assessed separately.

How long must incident records be retained?

Article 29 specifies at least five years from completion of remediation for the relevant location or biometric data incidents. That particular period should not be presented as a universal retention term for every security event.

Will Justix investigate our servers and restore data?

The standard engagement is legal: obligations, documents, regulatory coordination and analysis of evidence supplied by qualified responders. Forensics, malware removal and system recovery are technical services.

Is the company released from liability if the vendor caused the incident?

Not automatically. Legal roles, allocation of processing decisions, the DPA, breach cooperation and statutory duties must be reviewed independently of where the event originated.

Is representation before authorities or disputes included?

Only to the extent stated in the engagement and appropriate authorization. Litigation, compensation negotiation, specialized investigations and ongoing retainers are separately scoped.

See other personal data protection services

Other services in this area