You are using an outdated browser and your browsing experience will not be optimal. Please update to the latest version of Microsoft Edge, Google Chrome or Mozilla Firefox. Install Microsoft Edge

March 2, 2017

Vietnam: Domain and Company Name Regulations Tested

Managing Intellectual Property

On January 12, 2017, the Ho Chi Minh City Court rendered a ruling in favor of a major Silicon Valley high-tech company, ending a lengthy dispute between the company and a Vietnamese entity over the latter’s unauthorized use and registration of a company name and a domain name which incorporated the U.S. company’s registered trademark. To the delight of the U.S. company, the court resolved the dispute in an expedient 55 days. The brand owner’s course of action provided a useful test of new regulations on domain name and company name disputes.

Domain Names

Until recent changes were made in the law, domain name disputes have been difficult to resolve efficiently in Vietnam due to a lack of cohesion between the IP administrative enforcement bodies and the domain name registry. Enforcement bodies such as the Ministry of Science and Technology (MOST) regularly ordered domain names to be withdrawn in their final rulings on IP infringements, but the domain name registry would refuse to enforce the decision. In August 2015, the Ministry of Information and Communication (the parent authority of the registry) introduced Circular No. 24/2015/TT-BTTTT (Circular 24) with guidance on domain name violations. However, the gap between the IP authorities and the registry persisted until the issuance of Joint Circular No. 14/2016/TTLT-BTTTT-BKHCN in June 2016, which codified a mechanism to cancel disputed domain names based on IP authorities’ rulings.

At the end of 2016, this new mechanism had yet to be tested in practice. Despite the uncertainties involved, after several failed attempts to reach an amicable settlement, the U.S. company decided to petition the MOST Inspectorate for an administrative action to combat this blatant cyber-squatting, and at the same time sued the infringer before the Ho Chi Minh City Court, to take advantage of benefits that an administrative action could not bring forth.

In the course of a domain name dispute settlement, it is critical to freeze the disputed domain name, or run the risk that the infringer might transfer it to another entity, forcing the brand owner to restart the proceedings with the new registrant as the infringer. However, under current regulations, there is no regime to do so. Circular 24 removed the automatic regime of freezing domain names upon the commencement of court action. Previously, the domain name registry was authorized to freeze domain names, albeit only upon a court-granted preliminary injunction; however, this proved to be almost infeasible.

Fortunately, the U.S. company convinced MOST to call on the domain name registry to freeze the domain names. After multiple discussions, the registry agreed to freeze the domain names not only at MOST’s request but also due to the commencement of a civil suit. The registry’s move could mark a good precedent for further cases, especially in civil actions. The registry may agree to freeze disputed domain names upon the filing of a civil suit, without waiting for preliminary injunctions.

While this administrative action was in progress, the court ruled on the dispute. As such, the brand owner did not fully test the new regulation on administrative action, but saw that the new regulations could indeed help to effectively facilitate enforcement.

Company Names

IP-infringing company names are another headache for brand owners, as there has not been an effective mechanism in place to enforce administrative bodies’ final rulings on IP infringement. Per Decree 99/2013/ND-CP, if a brand owner wins an administrative action, the IP authority’s final ruling can order the removal of an infringing word mark from a company’s name, or require the infringer to abandon any identical/similar business lines. Failure to comply with this order can lead to a revocation of the infringer’s business license. However, the Law on Enterprises does not recognize such revocation based on a ruling from an IP administrative body. To deal with this gap in the law, MOST and the Ministry of Planning and Investment introduced Joint Circular 05/2016/TTLT-BKHCN-BKHDT, shifting the legal basis for the license cancellation from the IP body’s ruling on infringement to a new basis concerning the failure of the infringer to provide a requested justification for infringement. Per the Law on Enterprises, such failure to deliver a justification for certain violations can result in a cancellation of the business license. Under the new regulation, the business registry will request the infringer to justify its IP violation. If the infringer ignores the request, the registry will withdraw its business license. If the infringer submits a justification, it is uncertain whether the registry would still revoke the license. This regulation is somewhat convoluted, but now provides hope to rights-holder plaintiffs.

In this case, the U.S. company believed that the infringer would lodge an explanation if requested, which would put it at risk of losing the battle for the company name. Thus, the company focused on a civil suit instead of administrative action. Following a civil action, the business registry would be required to enforce the court’s judgment on the name change as well as the business license revocation. In fact, given the conclusive evidence submitted to the court, the defendant had to admit to infringement in its company name and agreed to settle the dispute.

The brand owner’s harmonious combination of administrative action and civil action allowed it to reap the advantages of both systems and mitigate the associated risks. These legal proceedings provide useful experience for the company and other IP owners in dealing with future infringement, and the swift civil suit could encourage other owners to rely on the courts more in the coming time.

RELATED INSIGHTS​ 

August 10, 2026
On July 31, 2026, Thailand’s Big Data Institute (BDI) launched a public consultation on the principles of a proposed new data-sharing law, with comments accepted until August 31, 2026. If enacted, the law would establish Thailand’s first comprehensive framework for government and private-sector data sharing, creating a systematic, secure, and transparent regime to support analytics, policymaking, research, and innovation. Central Data-Sharing Platform The draft law establishes a central system for data sharing, managed by the BDI. Government agencies would be required to connect to the BDI’s Data Integration and Intelligence Platform (also referred to as D2), in accordance with the BDI’s rules and procedures. Five Dimensions of Data Sharing The draft law covers five key types of data sharing between government (G), businesses (B), and consumers (C): G2B: Private organizations may request government data specifically for research and development purposes. The BDI will assess the applicant’s data governance, security, and privacy capabilities whether such measures meet prescribed standards before forwarding the request to the relevant government agency within 90 days. Any dispute may be escalated to a newly established Data-Sharing Promotion Committee for final determination. G2G: Government agencies may request data from other agencies through the central system. The data-holding agency must respond within 90 days, taking legality, necessity, proportionality, public interest, and personal data protection into account. Disputes may be referred to the Data-Sharing Promotion Committee for adjudication. B2G: In emergency situations involving public safety, economic security, or disaster response, the Minister of Digital Economy and Society may require private entities to provide data through the central data-sharing system. Government agencies must specify the data requested, demonstrate its necessity and expected benefits, and request only data reasonably available to the data holder. Requests for personal data must be limited to the minimum amount necessary. B2C: Royal decrees may
August 10, 2026
Thailand’s Office of the Personal Data Protection Committee (PDPC) recently released draft guidance on records of processing activities (ROPA) for personal data controllers and processors under the Personal Data Protection Act B.E. 2562 (2019) (PDPA). The draft guidance, which was presented to the public on July 7, 2026, addresses both controller records of collection, use, and disclosure of personal data and processor records of processing activities carried out on behalf of controllers. If implemented, the guidance will significantly expand organizational expectations for ROPA preparation, maintenance, and use across all sectors. Key Takeaways The draft guidance contains several important implications for organizations subject to the PDPA: ROPA reframed as a core accountability tool. The guidance elevates ROPA from an administrative record to a central accountability mechanism, connecting controller duties with recordkeeping obligations. ROPA as a source for privacy notices and governance documents. ROPA should serve as the primary source for privacy notices and align with consent management, retention schedules, DPIAs, incident response plans, and vendor contracts. Expanded scope across all activities. ROPA must cover all processing activities across the organization—including security, finance, HR, and external contractors—with correct controller or processor classification for each. Ongoing maintenance and auditability. ROPA must be updated for any change to systems, purposes, or processors, reviewed at least annually, and maintained with version control and a designated owner. Enhanced vendor, processor, and cross-border transfer requirements. Organizations must document all processors, external recipients, and cross-border transfers, specifying purposes, access scope, and destination countries. Linkage with risk assessment, DPIAs, and LIAs. ROPA should assign risk levels to each activity and identify when data protection impact assessments (DPIAs) or legitimate interests assessments (LIAs) are required, functioning as a risk-management tool. ROPA and data breach readiness. Incomplete ROPA can delay breach response and notification. Organizations should map data flows, vendors,
August 4, 2026
Thailand’s Personal Data Protection Act B.E. 2562 (2019) (PDPA) could soon see some important changes, as a draft bill to amend the PDPA has been introduced in the House of Representatives. The draft amendment is currently in the public consultation phase, with comments accepted from July 16 to August 15, 2026. If enacted in its current form, the amendment would make three key changes: expanding the government exemption to cover anticorruption operations, introducing a statutory definition of “government agency,” and restructuring the lawful bases for personal data processing to align with international standards. Background The PDPA has encountered several enforcement challenges since its implementation, including three core problems identified by the bill’s sponsors: (1) the current exemptions for government agencies do not cover anticorruption and misconduct-prevention operations; (2) the PDPA lacks a clear statutory definition of “government agency,” causing legal uncertainty as to which entities are covered; and (3) the existing framework for lawful bases of data processing does not align with international standards—particularly the multiple-lawful-bases system in the EU’s General Data Protection Regulation (GDPR)—making compliance inflexible for both government and private sector entities. Expanded Government Exemption The current PDPA exempts government agencies performing duties related to national security (including fiscal security), public safety, anti-money laundering, forensic science, and cybersecurity. The proposed amendment adds “prevention and suppression of corruption and misconduct” to this list of exempted functions. This would allow anticorruption bodies—most notably the National Anti-Corruption Commission (NACC), which is identified as a directly affected party—to collect, use, and disclose personal data without being subject to PDPA requirements when carrying out their duties. New Statutory Definition of “Government Agency” Notably, while the current PDPA use the term “government agency” in several provisions, the term is not comprehensively defined, creating potential uncertainty as to its scope. The draft bill therefore
August 3, 2026
On July 23, 2026, the Bank of Thailand (BOT) released for public comment its draft Notification on Digital Channel Security, which would significantly expand the scope and stringency of Thailand’s existing mobile banking security framework. If finalized in its current form, the draft notification would extend mandatory security requirements to credit card providers and credit providers, cover internet banking in addition to mobile applications, phase out SMS one-time passwords (OTPs) for transaction authentication, and introduce biometric verification requirements for high-value transactions. The public comment period is open through August 24, 2026. Background The BOT’s existing Mobile Banking Security Notification, issued in 2024, sets minimum security standards for financial institutions, specialized financial institutions (SFIs), and e-money providers, significantly reducing “money-draining app” fraud. However, fraudsters have since shifted to nonbank providers and internet banking channels, prompting the BOT to propose broader security requirements. Expanded Scope of Regulated Entities and Channels The existing Mobile Banking Security Notification covers only financial institutions, SFIs, and e-money providers offering mobile banking services. The draft expands coverage in two key areas: entities and channels. On the entity side, it adds credit card providers and credit providers that offer fund transfers to third parties at other financial service providers or that provide cash withdrawal services to individual retail customers. On the channel side, it broadens coverage to include internet banking in addition to mobile banking. Strengthened Customer Authentication The draft introduces enhanced authentication requirements in three areas: Service enrollment and device changes. Providers must implement rigorous identity verification, notify customers of enrollment results through out-of-band communication channels, and adopt risk-mitigation measures such as cooling-off periods and temporary transaction limits. Transaction-level authentication. Providers must use two-factor authentication for fund transfers, cardless ATM withdrawals, and transaction limit increases. Secure authentication factors. Key requirements include the following: “What-you-know” factors must