Companies used to the GDPR cannot rely on legitimate interests in Vietnam, because Vietnamese law has no equivalent general basis. The article helps them check which activities can truly proceed without consent.
About this article
Consent is the main basis for processing personal data in Vietnam, and the cases where consent is not needed are listed specifically. Vietnamese law has no general basis equivalent to the GDPR's "legitimate interests". The closest basis is the protection of rights or legitimate interests against an infringing act. An enterprise relying on this basis must prove that it meets all of its conditions.
The content is for general information and does not replace legal advice on a specific case.
1. Five groups of cases allow processing without consent
As a general rule, an enterprise must have the data subject's consent before it collects personal data, unless the law provides otherwise. The law lists five groups of cases where consent is not needed:
| Group | Content | Business example |
|---|---|---|
| Protection in urgent cases or against an infringing act | Protecting the life, health, honour, dignity, rights or lawful interests of the data subject or another person in an urgent case; protecting one's own rights or legitimate interests, those of another person, the State or an organisation, as necessary, against an infringing act | Giving an injured employee's details to a hospital; using camera footage to report a theft |
| Emergencies, security, crime prevention | Dealing with a state of emergency or a threat to national security; preventing riots, terrorism, crime and violations of law | Cooperating with the authorities in a specific case |
| Activities of state authorities | Serving the activities of state authorities and state management in accordance with the law | Filing tax, social insurance and labour reports |
| Performing an agreement with the data subject | Performing an agreement between the data subject and the organisation or individual concerned, in accordance with the law | Using an address to deliver goods; using a bank account number to pay salary |
| Other cases provided by law | Cases provided for in other laws | Keeping accounting records containing personal data for the period set by accounting law, at least 10 years for vouchers used to record the books; recording in public places where the law allows it |
The last group applies only to cases specifically provided for in another legal instrument. An enterprise cannot add new cases itself. If an activity falls outside every group in the table, the enterprise needs the data subject's consent.
2. The "rights or legitimate interests" basis applies only where there is an infringing act
The first group has two limbs. The first covers urgent cases where a person's life, health or honour must be protected. The second allows an enterprise to process data where necessary to protect its own rights or legitimate interests, or those of another person or the State, against an infringing act. This is the basis enterprises cite most often, and the one most often misapplied.
An enterprise can test its position with four questions:
- Is there a specific right or legitimate interest to protect? For example, a right to recover a debt that is due, ownership of property or a trade secret.
- Has an infringing act occurred, or is one occurring? In our view, a general future risk is usually not enough, because this basis only covers protection "against an infringing act".
- Is the processing necessary to protect that right? The enterprise processes only data related to the infringing act, and only for as long as necessary.
- Can the enterprise keep a record proving the three points above? The party relying on this basis bears the burden of proof, whether it is the controller, the processor, the controller and processor or a third party.
If any of the four answers is "no", the enterprise should not rely on this basis.
3. Four cases show the limits of the no-consent bases
3.1. Using a contract to recover a debt protects a right against an infringing act
An equipment rental company has an individual customer who is three months overdue. The company uses the contract, contact details and payment history to send a demand letter and file a lawsuit. The customer's non-payment infringes the company's property rights. The company uses only data related to that debt.
Conclusion: the company may rely on the basis of protecting its legitimate rights against an infringing act. It may also rely on the performance of the agreement. It may not, however, post the debt on social media or send it to the customer's relatives or colleagues, because that goes beyond what is necessary.
3.2. Giving camera footage to the police after a theft
A shop discovers missing goods. The shop extracts footage showing the suspected thief and sends it to the police. In this case, a specific infringement of property has occurred. Providing the footage is necessary for the competent authority to deal with the case.
Conclusion: the shop has a basis to process the data without the consent of the person filmed. It should make a record of the extraction, stating the time, the content and the recipient. If the shop posts the footage on its social media page as a "warning", the post may infringe the honour and dignity of the person shown. This basis does not cover such a post.
3.3. Reviewing a work mailbox when an employee is suspected of leaking customer data
A company finds its customer list in a competitor's hands. There are signs that the list was sent from an employee's work email account. The company reviews the sending log of that account for the relevant period.
Conclusion: a specific infringing act has occurred, so the company may rely on the basis of protecting its legitimate rights. The company may review only the account, the period and the type of information concerned.
Employees must be told in advance about monitoring of work systems, usually through the internal labour rules or an IT use policy. The internal labour rules are a suitable channel, because the enterprise must communicate them to employees and post their main points at the workplace. The company should keep a record of the signs of breach, the scope of the review and who carried it out.
3.4. Fraud scoring of every customer usually falls outside this basis
An e-commerce app wants to analyse the usage behaviour of all users to detect potentially fraudulent accounts early. In this case, no user has committed a specific infringing act. The activity is general prevention. In addition, data tracking users' behaviour and use of services in cyberspace is sensitive personal data.
Conclusion: in our assessment, the basis of protection against an infringing act is difficult to apply to general prevention of this kind. The enterprise should rely on one of two other bases:
- Clearly obtained consent.
- A specific duty imposed by sectoral law. For example, anti money laundering law requires financial institutions to identify customers, including where a transaction is suspected of involving money laundering.
Once a specific fraudulent transaction has been detected, processing data related to that transaction may fall within the protection basis.
4. No consent does not mean no controls
When processing data without consent, an enterprise must set up a supervision mechanism with four elements:
- Processing procedures and rules, with allocated responsibilities.
- Appropriate protection measures and regular risk assessment.
- Periodic review and assessment of compliance.
- A mechanism to receive and handle feedback and complaints.
Other obligations still apply in full: respecting the data subject's right to be informed, keeping data accurate, retaining it only for an appropriate period and keeping it secure. The main difference concerns the data subject's rights. For activities that fall within the no-consent cases, a data subject cannot ask to withdraw consent or restrict processing. Nor does the enterprise have to follow the procedure for stopping processing when the data subject objects to the processing.
5. The GDPR has a general "legitimate interests" basis; Vietnam does not
The European Union's General Data Protection Regulation (GDPR) sets out six lawful bases of equal standing. Consent is only one of them. The legitimate interests basis allows processing that is necessary for the legitimate interests of the controller or a third party, unless the data subject's interests or fundamental rights override them.
The controller must carry out a three-step assessment: whether the interest is legitimate, whether the processing is necessary, and whether that interest outweighs the impact on the data subject. This basis does not require any infringing act. The GDPR recitals give examples of legitimate interests: fraud prevention, direct marketing, intra-group transfers for internal administration and network security.
| Activity | GDPR | Vietnam |
|---|---|---|
| General fraud prevention | May rely on legitimate interests | Needs consent or a sectoral rule, unless a specific infringing act has occurred |
| Direct marketing to existing customers | May rely on legitimate interests, with a right to object | Needs the customer's consent |
| Sharing data within a group for internal administration | May rely on legitimate interests | Needs a specific basis, usually consent or performance of the employment contract, and a transfer agreement |
| Network and system security | May rely on legitimate interests | To be assessed activity by activity; once there is a specific incident or attack, the protection basis may apply |
| Debt recovery, litigation | May rely on legitimate interests | May rely on protection of rights against an infringing act |
| Burden of proof | The controller must show it has balanced the interests | The party relying on the basis must prove it |
In the rows on group sharing and network security, the Vietnam column reflects our assessment, as there is no guidance yet. Enterprises in groups headquartered in Europe often already have legitimate interests assessments for many activities. These assessments do not automatically become a lawful basis in Vietnam. The enterprise must reassign each activity to one of the five Vietnamese groups, or move it to consent.
6. What to avoid when processing data without consent
- Copying "legitimate interests" from the group policy into the Vietnamese data protection policy.
- Treating "performance of the contract" as a basis for everything involving the customer, including marketing, behavioural analysis or sharing with partners. This basis covers only what is needed to perform the agreement.
- Citing the protection basis without a record proving the infringing act and the necessity.
- Skipping the supervision mechanism on the assumption that activities without consent need no procedures.
7. What enterprises should do
- Record a lawful basis for each activity in the processing inventory, using the five Vietnamese groups or consent.
- Prepare an assessment on a template each time the enterprise relies on the protection basis, covering the right to be protected, the infringing act, the data to be processed, why it is necessary and who approved it.
- Review group policies and replace "legitimate interests" with bases that fit Vietnamese law.
- Adopt an IT use policy so that employees know about monitoring measures in advance.
- Set up the supervision mechanism for no-consent activities: procedures, risk assessment, periodic review and a feedback channel.
Read on in the Personal data protection series
- Previous article: One FDI company, five data flows, five roles
- Next article: Valid consent on websites, apps, calls and paper
- Related: Controller and processor, third party and data subject
- Related: Employee personal data: from recruitment to termination
- All 12 articles in the series: Personal data protection: the new legal framework and the obligations of enterprises


