The article helps companies identify the role of partners such as couriers, auditors and parent companies, so that they sign the right kind of contract.
About this article
Besides the controller and the processor, Vietnamese law recognises three further roles: the controller and processor, the third party and the data subject. Each role carries its own set of obligations. If it misidentifies a partner's role, an enterprise often signs the wrong type of contract and overlooks the basis for transferring data.
The content is for general information and does not replace legal advice on a specific case.
1. Vietnamese law distinguishes five roles in a processing activity
Five types of participant can be involved in a single personal data processing activity. The table below summarises how to tell them apart:
| Role | Test | Example |
|---|---|---|
| Data subject | The person whom the personal data reflects | Customers, employees, job applicants, dependants |
| Controller | Decides the purposes and means, without processing the data itself | An enterprise that outsources all storage and customer care |
| Processor | Processes at another party's request, under a contract | Payroll service company, software provider, outsourced call centre |
| Controller and processor | Decides the purposes and means and also processes the data directly | An enterprise that recruits and keeps records on its own systems |
| Third party | An organisation or individual outside the four roles above that takes part in processing in accordance with the law | An independent audit firm, a state authority receiving data under the law |
This article focuses on the three roles not yet discussed on their own: the controller and processor, the third party and the data subject.
2. The controller and processor must perform the duties of both roles
When an enterprise collects, stores and uses customer and employee data itself on its own systems, it both decides the purposes and processes the data directly. For those activities, the enterprise is a controller and processor. The law requires this party to perform in full both the controller's duties and the processor's duties.
This leads to three specific requirements for the enterprise:
- The enterprise must itself apply the full protection measures at the operational level, including access control, encryption, backup and logging, and not only adopt policies.
- The enterprise must answer data subject requests within the shorter time limits. Where no processor or third party is involved, the enterprise does not benefit from the extended time limits that apply when it must coordinate with those parties.
- The impact assessment dossier must describe both roles, covering the purposes the enterprise decides and the technical measures it operates itself.
An enterprise may be a controller and processor for the activities it carries out itself, but only a controller for the activities it has outsourced. The role must be recorded for each data flow.
3. A third party receives data under the law, not under the enterprise's instructions
The law defines the third party by exclusion. A third party is an organisation or individual that takes part in processing personal data in accordance with the law, but is not the data subject, the controller, the processor, or the controller and processor. There is no further guidance on this concept. From the definition, we suggest that an enterprise identify a third party with three questions:
- Does the recipient process the data on the enterprise's instructions and for the enterprise's purposes? If so, it is a processor.
- Does the recipient decide the purposes and means for its own business? If so, it is a separate controller, which this series calls an independent controller.
- Does the recipient take part in the processing because of a duty or power created by law, independently of the enterprise? If so, it is usually a third party.
Where a partner is a third party, the enterprise should note three points:
- An enterprise may transfer data to a third party only on a proper basis. For ordinary transfers, the parties must sign a transfer agreement. The agreement sets out the purpose, the types of data, the processing period, the legal basis, the protection duties and the duty to cooperate if a violation occurs.
- The enterprise's impact assessment dossier must include the third party's details.
- When a data subject asks to stop processing, correct or delete data, the enterprise may need a third party to act as well. In that case, the enterprise's time limit is extended. Even so, the enterprise remains the party that must carry out the data subject's request.
4. Four cases show how to allocate roles between an enterprise and data recipients
4.1. A delivery company may be a processor or an independent controller
An online shop sends the buyer's name, phone number and address to a delivery company. If the delivery company uses the data only to deliver the order under its service contract with the shop, and reports back to the shop, it is a processor. The delivery contract should include data processing clauses.
The delivery company's role changes if it also saves the recipient's phone number in its own customer system to promote its services, or decides the retention period under its own procedures. For those activities, the delivery company is an independent controller. The shop should state in the contract what data the delivery company may use for its own purposes. The shop should also inform buyers of this sharing.
Postal businesses also have their own duties under postal law, including the duty not to disclose unlawfully information about a person's use of postal services.
Conclusion: the delivery company's role depends on whether it sets its own purposes. The contract must reflect the actual role.
4.2. An independent audit firm is usually a third party
When auditing financial statements, an audit firm has access to payroll, employment contracts and customer receivables. Under the law on independent audit, the audit firm examines the financial statements and gives its own independent opinion in accordance with auditing standards. The audit firm therefore does not follow the enterprise's instructions on how to audit. Nor does it use the data for its own business outside the audit engagement.
Conclusion: in our assessment, an independent audit firm fits the role of a third party. The engagement contract should cover confidentiality, the scope of data provided, the retention of audit files and the duty to report incidents. By contrast, an accounting service company that keeps the books for the enterprise at its request is a processor.
4.3. A foreign parent company may hold several roles at once
A foreign invested company in Vietnam sends employee data to its parent company. The parent's role depends on what the data is used for:
- If the parent only operates a shared HR system and stores the data on behalf of the Vietnamese company, the parent is a processor.
- If the parent uses the data to decide regional promotions, set group pay policy or prepare consolidated reports, it sets its own purposes and is a controller for those activities.
In both cases, the data leaves Vietnam. The Vietnamese company must consider its duty to prepare a cross-border transfer impact assessment dossier and the available exemptions. A group relationship does not replace a processing agreement or a transfer agreement.
Conclusion: a parent company is neither automatically a controller nor automatically a processor. The enterprise needs to separate each of the parent's purposes to determine its role.
4.4. Tax and social insurance authorities receive data under the law, not under a contract
An enterprise files personal income tax finalisation and social insurance records. These records contain employees' identity details, income and dependants. The tax and social insurance authorities receive and process the data to perform state management duties. The enterprise does not decide how they use it.
The law allows processing without consent where the processing serves the activities of state authorities in accordance with the law. The law also allows transfer of data at the request of a competent state authority. The enterprise therefore does not need employees' consent. Nor does it need a data processing contract with the tax authority.
Conclusion: in our assessment, these authorities are neither controllers nor processors in the enterprise's processing activities. Even so, the enterprise must still do three things:
- Check whether a request has a legal basis.
- Provide only the data within its scope.
- Keep the written request together with a record of what was provided.
If someone calls claiming to be a tax officer and asks for the employee list through a messaging app, that is not a valid request.
5. Data subjects have rights, but also obligations
The data subject is the person whom the personal data reflects. One record may contain data on several data subjects. A dependant declaration filed by an employee contains data on the employee's spouse, children or parents. Each of them is a data subject.
In addition to the rights described in the overview article, the law places the following obligations on data subjects:
- To protect their own personal data.
- To respect and protect the personal data of others.
- To provide complete and accurate data about themselves as required by law, under a contract or when they have consented to processing.
- Not to obstruct the controller or processor in performing their legal rights and obligations.
Data subjects must exercise their rights to protect their own lawful rights and interests. An employee may ask for deletion of data that the enterprise must keep under tax, accounting or social insurance rules. In that case, the enterprise may refuse to delete the part it must keep. The enterprise must reply on time and give reasons for the refusal.
6. The Fashion ID judgment shows that the GDPR goes further with joint controllership
In Fashion ID (C-40/17, judgment of 29 July 2019), the Court of Justice of the European Union examined an online shop that embedded Facebook's "Like" button. The button caused visitors' browsers to send data to Facebook automatically, even if the visitor did not click it and had no Facebook account. The Court held that, for the collection and transmission of the data, the website operator can be considered a controller jointly with Facebook, because the two determine the purposes and means of that stage together. The Court reasoned that the operator embedded the button to increase the publicity of its goods on the social network, and both parties benefited economically.
The operator's responsibility is limited to the collection and transmission stage. The operator is not responsible for Facebook's processing after it receives the data. For the stage it controls, the operator must inform visitors. Where the processing relies on consent, the operator must obtain that consent from visitors itself.
The Court decided the case under the EU data protection directive that preceded the GDPR. Joint controllership was later set out as a rule of its own in the GDPR. Under that rule, joint controllers must agree how responsibilities are allocated, and data subjects may exercise their rights against each of them.
Vietnamese law has no joint controller mechanism. Applying the test of actual decision making, the website operator is still the controller for collecting and transmitting data through a plugin it embeds. The platform is the controller for its own processing. Behavioural tracking data on cyberspace is sensitive data. An enterprise that collects data by tracking websites or apps for behavioural advertising must have the data subject's consent.
| Issue | Vietnam | GDPR |
|---|---|---|
| Third party | A party outside the four other roles that takes part in processing in accordance with the law | A party other than the data subject, controller, processor and persons directly authorised by them |
| Party that both controls and processes | A separate role, liable for the duties of both | Not treated separately |
| Joint controllership | No joint controller mechanism; each party that sets its own purpose is a separate controller | Joint controllers must agree how responsibilities are allocated, and data subjects may exercise their rights against each of them |
| Third party plugins on a website | The operator is responsible for the collection it sets up; consent is needed to collect behavioural data for advertising | The operator determines collection and transmission together with the platform, and is responsible for that stage |
Fashion ID points to a rule that also applies in Vietnam: an enterprise is responsible for what its website or app sends out, even when the code that sends the data is supplied by someone else.
7. What to avoid when allocating the remaining roles
- Treating every data recipient as a processor. An audit firm, a state authority or a partner that sets its own purposes is not a processor. A standard data processing agreement therefore does not fit these parties.
- Sending data to the parent company without an agreement. Ownership is not a basis for transferring data.
- Providing data to someone claiming to be a state authority without checking the written request and its authority.
- Embedding third party plugins or tracking code on the website without consent and without knowing what data is sent.
8. What enterprises should do
- Classify every data recipient as a processor, an independent controller or a third party, and record it in the processing inventory.
- Use the right document for each role: a data processing agreement with processors, a transfer agreement with independent controllers, confidentiality clauses with third parties such as audit firms.
- Set up a procedure for state authority data requests, covering verification of authority, internal approval and record keeping.
- Separate the parent company's purposes and review cross-border transfer obligations.
- Audit third party code and plugins on websites and apps, and activate them only after the user has consented.
- Guide employees on how to provide data on family members. The enterprise should collect only what is necessary.
Read on in the Personal data protection series
- Previous article: Personal data processor: acting under contract, with duties of its own
- Next article: One FDI company, five data flows, five roles
- Related: Personal data controller: who decides and who is liable
- Related: Cross-border transfer of personal data, cloud and group sharing
- All 12 articles in the series: Personal data protection: the new legal framework and the obligations of enterprises


