Vietnam has rules for identifying core and important data. Applying them consistently to existing databases, cloud services and automated decisions is harder. With new sanctions taking effect on 11 November, classification now carries a direct cost to service continuity.

The decision before the penalty

A software company serving Vietnam from Singapore needs to know what kind of data is moving before it can decide whether a flow requires regulatory approval. Classification can determine whether it needs an assessment, whether a transfer can proceed and which processing activity may have to stop after a violation.

Decree 363 introduces data sector sanctions from 11 November 2026. Decree 330 already provides sanctions for personal data violations in AI systems. A draft circulated through the Can Tho police website proposes a 2 hour reporting window for core data incidents, while the Data Security Law project undergoes legislative scrutiny.

Operators need a defensible classification to determine which requirements apply. Yet lawmakers are still examining how classification and appraisal should work across public and private organisations, and how to define overseas processing through international platforms.

That uncertainty has a commercial consequence. A company can budget for a fine. Budgeting for a disputed classification that interrupts a service its customers depend on is much harder.

The classification rules already contain thresholds

Decision 20/2025/QD-TTg, effective since 1 July 2025, lists 26 core data entries and 18 important data entries. The important list incorporates the core list, so these are overlapping categories.

Many entries concern unpublished state information. The relevant unpublished citizen and organisation data entries can also matter to commercial operators:

Basic data on Vietnamese citizens: important data at least 100,000 citizens; core data at least 1,000,000 citizens.

Sensitive data on Vietnamese citizens: important data at least 10,000 citizens; core data at least 100,000 citizens.

Bank account, payment history or debt obligation data on Vietnamese enterprises and organisations: important data at least 10,000 enterprises or organisations; core data at least 100,000 enterprises or organisations.

A provider holding sensitive citizen data should examine the relevant entry well before reaching 100,000 people. Private ownership does not automatically put a customer database outside the framework.

Classification starts with the records themselves. A dashboard's user count cannot show whether they contain basic citizen data, sensitive data, corporate payment information or several categories at once.

A hypothetical SaaS provider may treat customer profiles, support tickets and identity documents as separate features. A review must examine their contents, links and overseas processing. It needs a reproducible method for counting people or organisations, handling duplicates and tracing supplier copies. The company should be able to explain its method to an authority and reproduce the result when the database changes.

Growth can change the result. A customer, acquisition or integration can alter a dataset's composition and scale without changing its cloud region. Classification must follow those changes.

Responsibility exists but certainty takes more work

Decision 20 assigns implementation and guidance to the Ministry of Public Security, with defence responsibilities allocated to the Ministry of National Defence. Ministries and provincial authorities must guide classification within their sectors and jurisdictions.

Businesses still need to identify the applicable guidance and who can resolve a contested interpretation. A fintech combining identity checks, corporate payments and an AI fraud model must map each activity to the relevant provisions. It also needs to know whether a transfer assessment settles classification or leaves a separate question unresolved.

At the National Assembly Standing Committee's 23 September review of the Data Security Law project, scrutiny called for consistent assessment and appraisal based on datasets' nature, regardless of public or private ownership.

It also sought compatibility between proposed data risk tiers, the Data Law's classifications and the Cybersecurity Law's information system levels. Companies need to know how decisions under these schemes affect each other.

Enforcement is becoming more specific while lawmakers are still examining how its underlying classifications should be applied consistently.

The November deadline applies to existing operations

Decree 363 takes effect on 11 November 2026. Its maximum organisational fine is VND200 million. Article 19 allows suspension of affected overseas transfer or processing activities for 3 to 12 months for specified violations.

The consequences depend on the conduct. Overseas hosting is not automatically unlawful, and a missing document does not automatically attract the maximum penalty or suspension.

Conduct completed before 11 November is handled under the rules applicable when it occurred. Conduct that began earlier and continues when the decree takes effect falls under the new sanctions provisions. An old Singapore hosting contract therefore needs review if it involves covered data and processing. The date on which a cloud contract was signed cannot settle the status of the activity continuing under that contract.

Decree 165/2025/ND-CP requires an assessment and a satisfactory written assessment result before covered core data transfers. Important data generally needs no prior approval, but operators must prepare an impact assessment and submit it to the relevant ministry 15 days before processing. Exceptions have their own conditions.

For quantifying covered overseas transfers, the decree counts accumulated data transferred or processed since 1 July 2025. Today's production snapshot may miss that history. Deleting live records should not be assumed to erase it.

The business must be able to explain the category assigned to a continuing flow and why its chosen procedure is appropriate. That requires historical evidence about overseas processing, beyond the cloud contract and a count of current users.

AI brings a separate route to suspension

Decree 330's AI provisions concern personal data protection, including annual compliance assessments, risk controls and automated decision safeguards. They have been effective since 19 August 2026.

Article 67 provides a 3 to 6 month suspension of the relevant AI system or platform for specified violations in paragraph 3. These include automated decisions affecting public security and order or the lawful rights and interests of organisations or individuals, where the system lacks oversight or does not allow a request for human reassessment.

The provision can apply without a core dataset. Its trigger is the regulated personal data processing and AI system conduct.

A fintech using an overseas fraud service must examine what reaches the supplier, whether the transfer involves core or important data, and whether the AI processing and human review comply. These require separate legal analyses but share evidence about data contents, purposes, supplier access and system behaviour.

Teams should connect that evidence. Transfer assessments must describe deployed processing; AI reviews must account for what the model receives; customer explanations must match the product's decision process. Otherwise, completed compliance documents can leave the activity poorly understood.

A 2 hour clock requires classification in advance

The draft attachment proposes assessment and reporting within 2 hours of discovering a core data incident, initial notification within 24 hours for other data incidents, and a full report within 72 hours.

These remain proposals. The attachment is marked draft, has no enacted law number and proposes commencement on 1 December 2027. Its reporting windows must be considered separately from Decree 363's November deadline.

If reporting speed depends on the data category, responders need that classification before an incident. After a hypothetical supplier account compromise, engineers must establish access, preserve logs and contain the account. Starting a debate about core data status then could consume much of the proposed 2 hour window.

A classification register should link legal assessments to systems, datasets, responsible staff and reporting contacts. Product or supplier changes should trigger review.

Contracts must also support timely incident information. Suppliers need to understand which facts customers must report. A promise to investigate promptly leaves timing and decision authority unresolved.

A newly posted draft may be an older version

The Can Tho attachment has 58 articles. Official reporting of the 23 September Standing Committee review describes a bill with 25 articles.

A later website posting therefore cannot establish that the attachment is a newer legislative text. The relationship between those versions needs verification before its deadlines, article numbers or proposed effective date can be attributed to the bill under consideration.

The reporting proposal and legislative project belong to the same evolving policy discussion. Counting them as separate binding layers would exaggerate today's obligations.

Businesses should distinguish enacted laws, implementing decrees, consultation drafts and legislative submissions. Records should identify a text's origin, preparation date and whether later versions changed relevant provisions.

The September scrutiny offers a clearer signal of the questions lawmakers are considering. It also sought clearer treatment of overseas processing through international platforms. It raised the cost of parallel physical backups in Vietnam and suggested considering domestic control of encryption keys as an alternative.

Those questions affect architecture and spending. They need resolution through the legislative process before a circulating draft becomes a final migration instruction.

Uncertainty can impose costs before an inspection

Unclear classification can prompt a buyer to demand local hosting, a vendor to apply the strictest interpretation across customers, or a smaller provider to delay a product rather than fund infrastructure changes whose scope remains unsettled.

These are possible responses, not established market outcomes. They explain how uncertainty can impose procurement and engineering costs before an inspection. Usable classification guidance gives businesses a basis for evaluating those demands before committing to expensive changes.

Moving a primary database to Vietnam may leave backups, support tools, analytics and AI services processing information abroad. A local server address gives a partial account of the system. Conversely, ordinary commercial software cannot be assumed outside the framework without examining the relevant entries and thresholds.

A documented view of data and its uses lets a company identify restrictions, seek specific clarification and isolate affected activities. Procurement teams can then discuss concrete requirements instead of asking whether an entire platform is "Vietnam compliant".

The test is whether an operator can reach a defensible answer

Implementation guidance should make classification easier to apply, verify and revisit. Sector examples could explain existing thresholds in payments, identity verification, software and shared clouds. A route to written interpretation would help resolve cases crossing sectors or jurisdictions.

Guidance should distinguish who resolves classification questions from who assesses a transfer, and explain each decision's effect. Where several bodies are involved, operators need a consistent answer they can rely on during later scrutiny.

After 11 November, published enforcement decisions could show authorities' approach through dataset classifications, specific violations and the scope of suspended activities.

Operators should first review continuing overseas processing against existing rules. They need to document what they hold, why they assigned each category and which assessment or approval supports the activity. AI personal data controls and verified versions of the Data Security Law need separate tracking.

Vietnam has built a legal foundation for classification and transfer control. The implementation challenge is producing consistent answers inside commercial systems before sanctions interrupt them.

By 11 November, a SaaS provider or fintech needs an answer it can document: this is the data we process, this is its legal category, and this is the procedure that permits this flow to continue.