DPO Radio

Decree 363/2026/NĐ-CP, Quy định xử phạt vi phạm hành chính trong lĩnh vực dữ liệu, was issued by the Government on 19 September 2026 and published on the Government portal on 23 September 2026. It is effective 11 November 2026 (Article 34). It was signed for the Government by Deputy Prime Minister Hồ Quốc Dũng and is proposed and implemented by the Ministry of Public Security. It runs to 36 articles in four chapters, with no annex and no official form.
It is binding enacted law, not guidance and not a draft. The text is final, with an effective date of 11 November 2026.
The decree sanctions administrative violations in the data field under Data Law 60/2024/QH15. It reaches Vietnamese agencies, organisations and individuals, foreign parties in Vietnam, and foreign agencies, organisations and individuals directly participating in or connected with data activities in Vietnam (Article 2(1)).
What it changes commercially: provenance, quality, owner and subject authorisation, purpose limitation and a protection assessment made before collection become enforceable evidence. A record of processing activities or a privacy notice alone does not show that a collection procedure was in force, that a protection assessment preceded collection, that authenticity was checked, or that the notified scope was kept.

The Data Law is the parent statute. The duties Decree 363 sanctions are set out in other instruments:
Decree 363 adds the consequence layer: which failures are sanctionable, at what level, with which supplementary penalties and corrective measures.
Two related but distinct enforcement tracks. Article 1(2) says Decree 363 does not govern violations within the scope of the decree on administrative sanctions in the fields of cybersecurity and personal data protection. The exclusion names that decree by its title, not its number; the decree carrying that title is Decree 330/2026/NĐ-CP.
Decree 363 is not a personal-data fine regime. The two are never merged, and they are never added together for one act. Where one act touches a dataset that is both personal and core or important, the text does not draw the line; which track applies is a determination a person makes with counsel.
| Provision | What It Establishes | Operational Implication |
|---|---|---|
| Article 1(2) | Conduct within the cybersecurity and personal-data sanctions decree's scope is excluded | Record which track each exposure sits on, and who decided it |
| Article 2(1) | Reaches foreign agencies, organisations and individuals directly participating in or connected with data activities in Vietnam | Foreign cloud, platform and data-service providers assess their own exposure; expulsion is available for foreign nationals |
| Article 4(2) | Supplementary penalties: deprivation of a certificate for a term, confiscation of tools, software and data, suspension of data activities, suspension of a database, exchange or sandbox, suspension of Fund participation, expulsion | Track suspension and deprivation exposure beside the fine, not after it |
| Article 4(3) | Eighteen corrective measures, from restoring data and notifying affected parties to deletion, correction, surrender of unlawful gains and repayment to the Fund | Corrective measures need completion evidence, not only payment |
| Article 5(4) | Before deleting data, the authority records its name, type, size, format, location, identifier and hash | Keep deletion records that carry the same identification |
| Article 6 | Every stated amount is the individual level and an organisation is fined twice, except five provisions stated at the organisation level; individual maximum 100 million VND | Never quote a figure without the party it applies to |
| Articles 7–26 | Twenty offence articles, from prohibited acts and collection through cross-border transfer, exchanges, intermediaries, the Fund and controlled testing | Map each offence to the obligation it sanctions and the evidence that answers it |
| Article 22(1)(b) | Processing of important and core data is logged, and the log kept at least six months | Retain and produce the processing log |
| Article 34, Article 35(1) | Effective 11 November 2026; conduct that began earlier and continues on that date is handled under this decree | An unremedied gap on 11 November is continuing conduct |
Every amount in the offence articles is stated at the individual level, and an organisation is fined twice that amount. Five provisions are the exception. They are stated at the organisation level:
The individual maximum is 100 million VND. Article 6 states no organisation maximum as a figure; 200 million VND follows from the doubling rule and matches the top authority ceilings. There is no revenue-percentage fine and no gain-multiple fine. Unlawful gains are recovered as a corrective measure.
| Conduct | Individual | Organisation | Reference |
|---|---|---|---|
| Collecting or creating data without the consent of the data subject or owner, or without authenticity and quality checks | 20–40 million VND | 40–80 million VND | Article 8(1)(a), c |
| No collection procedure, or no protection assessment before collecting | — | 20–40 million VND, stated at the organisation level | Article 8(1)(b) |
| Collecting beyond the notified scope or purpose; fabricated or source-inconsistent data; core or important data; sensitive leakage | 40–60 million VND | 80–120 million VND | Article 8(2) |
| Falsifying data in Party, State or Fatherland Front databases; deliberately supplying inaccurate data or refusing a lawful data request | 40–60 million VND | 80–120 million VND | Article 7(1) |
| Unlawfully obstructing data processing or governance; attacking, appropriating or damaging databases short of a crime | 60–80 million VND | 120–160 million VND | Article 7(2) |
The heavier consequence is often not the fine. Data-exchange operation can be suspended for 12–18 months (Article 23). The data-exchange certificate and the intermediary, analysis and aggregation certificate can be withdrawn from use for 6–12 months (Article 23, Article 24). Database operation can be suspended for 6–9 months where core or important data is collected unlawfully (Article 8). Tools, software and data can be confiscated, and unlawfully collected data must be deleted.
| Obligation | Timeline | Reference |
|---|---|---|
| Decree takes effect | 11 November 2026 | Article 34 |
| Conduct that began before and continues on 11 November 2026 | Handled under this decree from that date | Article 35(1) |
| Limitation period for sanctioning | One year — the authority's window, not a duty the organisation performs | Article 3(1) |
| Keep the processing log for important and core data | At least 6 months | Article 22(1)(b) |
| Suspension of data-exchange operation | 12–18 months | Article 23 |
| Deprivation of the data-exchange or intermediary, analysis and aggregation certificate | 6–12 months | Article 23, Article 24 |
| Suspension of database operation for unlawful collection of core or important data | 6–9 months | Article 8 |
The 24-hour and ten-year data-exchange clocks that Article 23 sanctions are stated by Decree 314/2026 and are carried there, so each duty is raised once.
Decree 363 prescribes no form and has no annex. Violation records are made on the forms of the general administrative-violations framework. Everything ComplianceOne supplies for this instrument is an internal preparation template and is labelled as one — never an official form.
The 24-hour and ten-year data-exchange clocks that Article 23 sanctions are stated by Decree 314/2026 and are carried there, so each duty is raised once.
Decree 363 prescribes no form and has no annex. Violation records are made on the forms of the general administrative-violations framework. Everything ComplianceOne supplies for this instrument is an internal preparation template and is labelled as one — never an official form.

Ready to add to your workspace. Decree 363 is available as an enforcement decree under the Data Law, effective 11 November 2026, taken from the official signed text. It has twenty-four fine areas covering all twenty offence articles. Each one names:
Figures computed for your party. Penalty Readiness computes exposure from installed fine schedules and applies the individual-versus-organisation rule. Once the decree is installed and your exposure inputs are recorded, its areas are computed there, with the effective date of 11 November 2026. A figure is a stated range for the party that applies, never a prediction of what an authority will impose.
Cases run to closure. Enforcement Cases records an inspection notice or violation record under the decree, links the fine areas, and records the decision and each corrective measure executed with its evidence.
Evidence where it already lives. The data registry, core and important classification, breach notifications, the deletion proof chain, data-service provider records and the audit trail each hold part of what an inspection under this decree asks for. For the rest, Decree 363 comes with six internal preparation templates:
The templates are available in the Form Catalog from 11 November 2026, the decree's effective date.
On the public roadmap. Planned next:
The internal templates above provide a place to record that evidence while the planned functionality is developed.
ComplianceOne does not determine that a violation occurred, predict an authority's decision or fine, route between Decree 363 and Decree 330 on its own, or add the two decrees together. It is not legal advice.
Tracks each fine area with its stated range, attribution rule and suspension exposure
Explore Risk AssessmentAssigns owners and remediation work to address gaps under Decree 363
Explore Program GovernanceHolds the data registry that shows collection method, purpose and legal basis for each dataset
Explore Data MappingRecords core and important classification, the escalation in Articles 8, 10, 13 and 14
Explore Data ClassificationKeeps the proof chain for deletion and destruction as a corrective measure
Explore Deletion OrchestrationRecords breach notifications to data subjects when a corrective measure requires them
Explore Incident ResponseHolds the six internal preparation templates, clearly labelled as internal documents
Explore Compliance FormsOrganizations subject to Decree 363 should confirm:
See how ComplianceOne computes a data-field fine for the party that applies, shows the suspension exposure beside it, and holds the collection and provenance evidence an inspection asks for.

Decree 363 was issued on 19 September 2026 and took effect on 11 November 2026 under Article 34. It is final, enacted law, not a draft, and conduct that began before that date and continued on it is handled under this decree.
No. It expressly excludes violations within the scope of the cybersecurity and personal-data sanctions decree, which is Decree 330/2026/NĐ-CP. Decree 363 covers the broader data field: non-personal, mixed, core and important data, state databases, data products and services, exchanges and intermediaries.
Not without the attribution rule. Stated amounts are individual levels and an organisation is fined twice, except in five provisions stated at the organisation level. Every range is a range, multiple violations can each be sanctioned, and suspension or certificate deprivation can outweigh the fine.
Yes. Article 2(1) reaches foreign agencies, organisations and individuals directly participating in or connected with data activities in Vietnam, and expulsion is available for foreign nationals.
No. It records a person's determination of which track applies, with the reasoning. It never routes an exposure on its own and never adds the two decrees together.
No. It has no annex and no official form. Violation records use the general administrative-violations forms; ComplianceOne's templates for this decree are internal preparation records.

Test your collection procedures, prior protection assessments, provenance records and exposure by fine area against the requirements of Decree 363/2026.

Review which of your data activities fall under Decree 363, which sit on the Decree 330 track, and the associated suspension risks.