The article helps companies work out whether they are the controller, through four practical cases.
About this article
The personal data controller is the organisation or individual that decides the purposes and means of processing personal data. It bears primary responsibility to the data subject, including for damage that arises while another party processes the data on its behalf.
The content is for general information and does not replace legal advice on a specific case.
1. The controller decides why and how personal data is processed
Every activity that affects personal data, from collection, storage and analysis to sharing or deletion, is processing of personal data. For each processing activity, an enterprise needs to identify which party decides the purposes and means of processing. The party that decides these two matters is the personal data controller.
Purposes and means are understood as follows:
- Purpose: what the data is processed for, such as signing an employment contract, delivering goods, credit scoring or sending advertising.
- Means: how the data is processed, including which data is collected and from whom, how long it is kept, who may access it and with whom it is shared.
A controller does not have to handle the data itself. An enterprise that engages another company to store or analyse data, or to send messages on its behalf, remains the controller if the enterprise itself decides the purposes and means of processing. Conversely, a party does not become the controller merely because the data sits on its servers.
The controller is an organisation or individual, not a department or an employee. When the human resources department decides to collect applicants' files, the controller is the enterprise. The personal data protection staff appointed by the enterprise carry out data protection work on its behalf. Legal responsibility stays with the enterprise.
2. The role follows the facts, not the label in the contract
The law identifies the controller by which party actually decides the purposes and means of processing. A contract may call a party the "processor", but if that party decides on its own to use the data for its own purposes, it is the controller for that activity.
An enterprise can test each processing activity with four questions:
- Who decides to collect the data, and for what purpose?
- Who decides which data is collected and how long it is kept?
- Who decides with whom the data is shared?
- Whose activity does the result of the processing serve?
The party named in the answers to most of these questions is the controller. A party that decides only technical matters, such as the software, the servers or the encryption method, and does so within a framework set by another party, usually remains a processor.
The same enterprise may be the controller for one data flow and the processor for another. The role must therefore be identified for each processing activity, not once for the whole enterprise. When it prepares the personal data processing impact assessment dossier on the official form, the enterprise must also declare its role for each group of data subjects and to describe the processing flow for each role.
3. Four cases show how the controller is identified
3.1. A bank is the controller of customer data, even when it outsources its call centre
A bank collects identification, account and transaction information to open accounts and provide its services. The bank decides which data is collected, how long it is kept and with whom it is shared, so the bank is the controller. Customer information of credit institutions is sensitive personal data, so the bank must apply a higher level of protection.
When the bank engages a company to run its customer service call centre under scripts and procedures set by the bank, the call centre company is a processor. The bank remains the controller and remains responsible to its customers.
3.2. An employer is the controller of its employees' data
An enterprise collects applicants' files, employment contracts, attendance data, payroll and information on dependants to manage its workforce. The enterprise is the controller of this data.
If the enterprise engages a payroll service company, that company processes the data at the enterprise's request and is a processor. When the enterprise files social insurance records or finalises personal income tax, the state authority receives the data under the law, not as the enterprise's processor. The role of these authorities is discussed in the article on third parties.
3.3. A clinic is the controller, and its booking software provider is a processor
A clinic uses online software from a technology company for patients to book appointments and for storing medical records. The clinic decides which information is collected and uses it for treatment. The clinic is the controller and the software provider is a processor.
The software provider's role changes if the provider uses patient data on its own to advertise its own services. For that advertising, the provider decides the purpose itself. It therefore becomes a controller and must meet every controller obligation on its own account, including the obligation to have a lawful basis for processing.
At the same time, the provider breaches its duty as a processor: to process data only in accordance with its contract with the clinic. Health data is sensitive personal data, so this breach has more serious consequences for patients.
3.4. One order may have two controllers for two purposes
A shop selling on an e-commerce platform receives the buyer's name, telephone number and address to deliver the goods. The platform decides how buyer account data is collected and kept to operate the platform. For that purpose, the platform is the controller. If the shop keeps the telephone number to send its own promotional messages, the shop has decided on a new purpose and is the controller for that activity.
The new purpose needs its own legal basis. A buyer who gives a telephone number to receive goods has not agreed to receive advertising.
4. Most enterprises are both controller and processor
Vietnamese law provides for a separate role called the personal data controller and processor. This is a party that decides the purposes and means of processing and also processes the data itself. For example, an enterprise that recruits its own staff, keeps records on its own systems and runs its own customer service is a controller and processor.
A controller and processor must meet all responsibilities of both the controller and the processor. When it prepares its compliance documents, an enterprise should not record itself only as a controller. If it does, it will miss the processor's responsibilities, such as applying full protection measures at the stage where it processes the data directly.
5. The controller is liable to the data subject for damage
The law gives the controller the following main responsibilities:
- Decide the purposes and means of processing and set them out clearly in documents or agreements with the data subject.
- Define the rights and obligations of each party in agreements and contracts on data processing.
- Apply suitable management and technical measures to protect the data, and review them when needed.
- Select a suitable processor.
- Give effect to the rights of data subjects, with clear procedures and forms.
- Keep records of the data subject's consent. In a dispute, the controller bears the burden of proving that consent.
- Notify the specialised personal data protection authority within 72 hours of detecting a violation. This duty applies where the violation may harm national security, public order and safety, or may infringe the life, health, honour, dignity or property of the data subject. Where the incident involves location data, biometric data, or sensitive data in finance and banking, the controller must also notify the affected data subjects within 72 hours.
- Prevent unlawful collection of data from its systems, equipment and services.
- Cooperate with the Ministry of Public Security and competent state authorities.
Liability to the data subject for damage rests with the controller. The law makes the controller liable to the data subject for damage caused by the processing, while the processor is liable to the controller. When data leaks at a service provider, the customer may therefore claim compensation from the enterprise that is the controller. The enterprise will find it easier to recover that compensation from the provider if the contract sets out a clear indemnity.
The exemption for small enterprises is narrow. Household businesses and micro enterprises do not have to prepare and update personal data processing impact assessment dossiers or appoint a personal data protection department or staff. Small enterprises and startups may choose whether to apply these obligations for 05 years from 1 January 2026.
The exemption does not apply to a party that provides personal data processing services, directly processes sensitive personal data, or has processed the data of 100,000 or more data subjects. The 100,000 data subjects are counted cumulatively over all data the enterprise has processed. From the time the enterprise reaches the threshold, it is no longer exempt. Apart from the exempted obligations, a small enterprise is still a controller and must still meet the responsibilities above.
6. Vietnamese law is close to the GDPR but differs on three points
Under the European Union's General Data Protection Regulation (GDPR), the controller is the party that determines the purposes and means of processing. This is the same approach as Vietnamese law. In its guidelines on the concepts of controller and processor, the European Data Protection Board (EDPB) also identifies the role by actual influence. Under those guidelines, a processor may decide non-essential means, that is, technical details such as the choice of software, hardware or specific security measures. Enterprises may refer to these guidelines when allocating roles in difficult cases.
| Issue | Vietnam | GDPR |
|---|---|---|
| Definition of controller | The party that decides the purposes and means of processing | Similar |
| Party that both controls and processes | A separate role that must meet the responsibilities of both | Not a separate role; a controller that processes data itself remains a controller |
| Several parties controlling together | No specific rules | Joint controllers, who must agree on how responsibilities are shared |
| Liability for damage | The controller is liable to the data subject; the processor is liable to the controller | The data subject may also claim against the processor when it breaches its own obligations or acts against instructions |
Vietnamese law has no joint controller mechanism for cases where several enterprises decide the purpose of processing together, for example two companies running a joint promotion. In such cases, the parties should sign an agreement that states which party collects the data, which party answers data subject requests and which party gives notice of an incident.
7. What to avoid when identifying the controller
- Claiming to be a processor to reduce obligations. An enterprise that decides the purpose of processing itself is a controller, whatever the contract says.
- Assuming the foreign parent company is automatically the controller. If the Vietnamese company recruits, signs contracts and manages employee data itself, it is the controller, even when it uses a group system.
- Identifying the role once for the whole enterprise. The role must be identified for each processing activity.
- Signing with providers without an indemnity clause. The controller is liable to the data subject, so the contract should allow the enterprise to recover loss caused by the provider.
8. What enterprises should do
- Draw up a register of processing activities and record the enterprise's role in each.
- Apply the four role questions to data flows that involve providers, partners or group companies.
- State the purposes and means of processing in notices, documents or agreements with data subjects.
- Review contracts with processors for the scope of processing, protection measures, incident notice, indemnity, and deletion or return of data at the end of the contract.
- Set up a procedure for data subject requests and a procedure for notifying violations within 72 hours.
- Check the exemption conditions before deciding not to prepare an impact assessment dossier or not to appoint personal data protection staff.
Read on in the Personal data protection series
- Next article: Personal data processor: acting under contract, with duties of its own
- Related: Controller and processor, third party and data subject
- Related: One FDI company, five data flows, five roles
- All 12 articles in the series: Personal data protection: the new legal framework and the obligations of enterprises


