The article helps companies vet service providers before handing over data and draft a complete data processing contract.
About this article
The personal data processor is the organisation or individual that processes personal data at the request of the controller, under a contract. The processor does not set the purpose of processing, but it has its own duties under the law and is liable to the controller for damage it causes.
The content is for general information and does not replace legal advice on a specific case.
1. The processor acts for the controller and only under a contract
An organisation is a processor when three conditions are met together:
- It processes at another party's request, namely the controller or the controller and processor.
- It has a contract or agreement with that party on the processing.
- It does not set the purpose of processing. A processor may choose tools, software or technical methods. The controller decides the purpose of processing.
The contract is a legal requirement, not a formality. A processor may receive data only after a contract or agreement with the controller is in place, and may process the data only in accordance with that contract. If an enterprise sends a customer list to a provider before the contract is signed, the processing is in breach from the first step.
An enterprise's employees are not processors. When employees process data within their assigned work, they act as part of the enterprise. The enterprise remains the controller or the controller and processor.
2. Four typical processor cases
2.1. A payroll service company processes employee data for the enterprise
An enterprise sends attendance records, salaries, bank account numbers and dependants' information to a service company to calculate payroll, personal income tax and insurance. The service company follows the enterprise's procedure and returns the results to the enterprise. The service company is a processor.
2.2. An outsourced call centre calls customers under the enterprise's script
An insurer engages a call centre to remind customers to pay premiums, using a list and script provided by the insurer. The call centre is a processor. If the call centre uses the same list to promote the products of another business that also engages it, the call centre has set a new purpose itself. For that activity, the call centre becomes a controller. At the same time, it breaches its contract with the insurer.
2.3. Software and cloud providers store data for the enterprise
An enterprise uses customer management software or rents cloud servers to store data. The provider stores the data and runs the system, but does not decide what the data is used for. The provider is a processor. The law sets specific requirements for contracts with cloud service providers. These requirements are described in section 6 below.
2.4. A messaging agency sends text messages and emails for the enterprise
A retail chain engages an agency to send branded text messages and emails to loyalty customers. The retail chain decides who receives what and when. The agency is a processor. The retail chain, as controller, must still ensure it has a lawful basis to send advertising to each customer.
3. The processor has its own duties under the law
A processor does more than perform the contract. The law gives the processor the following duties:
- Receive data only after a contract or agreement on data processing with the controller is in place.
- Process data strictly in accordance with the contract or agreement.
- Apply full personal data protection measures.
- Be liable to the controller for damage caused by its processing.
- Prevent unlawful collection of data from its systems, equipment and services.
- Notify the controller promptly on detecting a violation of personal data protection rules.
- Cooperate with the Ministry of Public Security and competent state authorities.
The processor must help the controller give effect to data subject rights. When a data subject asks to stop processing, or to view, correct, obtain or delete data, the controller is responsible for responding and acting on the request. Where the data is held by a processor, the controller has up to 20 days to complete a request to stop processing, 15 days for a request to view, correct or obtain data, and 30 days for a request to delete data.
These are the controller's deadlines towards the data subject, not deadlines set for the processor itself. The controller should therefore set a shorter period for the processor in the contract, so that the controller has time to check the result and reply to the data subject.
4. A processor that sets its own purpose becomes a controller
Roles follow the facts. When a processor uses data for its own purposes, such as advertising its services, training models, developing products or selling to others, it becomes a controller for that activity. It must then meet every controller obligation on its own account. It must have a lawful basis for processing and is directly liable to the data subject.
The data subject may also hold the original controller liable for damage. The controller should therefore state expressly in the contract that the processor may not use the data for other purposes, including data that has been aggregated or analysed.
5. Some personal data processing services require a certificate
Apart from the processor role under each contract, the law separately regulates the business of providing personal data processing services. The services are:
- Providing and operating systems and automated software to process personal data on behalf of a controller.
- Scoring, ranking and assessing the creditworthiness of individuals.
- Collecting and processing personal data online from websites, applications, software and social networks.
- Collecting and processing data through health care, health monitoring and medical service applications.
- Collecting and processing data through education software with monitoring features, such as attendance, video recording, behaviour scoring and emotion recognition.
- Analysing and mining personal data to find trends, predict user behaviour or optimise services.
- Encrypting personal data in transit and in storage.
- Automated processing of personal data using big data, artificial intelligence, blockchain or metaverse technologies.
- Providing personal location data through application platforms.
An organisation providing these services must obtain a certificate of eligibility from the Ministry of Public Security, through the specialised personal data protection authority. The main conditions are:
- Being an organisation or enterprise established and operating under Vietnamese law.
- Having a head in charge of personal data processing who is a Vietnamese citizen residing in Vietnam.
- Having at least 03 staff who meet the standards for personal data protection staff.
- Having suitable infrastructure, equipment and technology.
- Having a satisfactory result for its personal data processing impact assessment dossier, and for its cross-border transfer impact assessment dossier where applicable.
Once certified, the organisation must assess its compliance once a year. When acting as a processor, it must ask the controller to obtain the data subject's consent before providing the service. When obtaining consent, the controller must ensure that the data subject knows the types of data processed, the purpose of processing and the service provider.
The first service in the list, providing and operating automated systems or software that process data on behalf of a controller, is broad. Enterprises that provide software or outsourced services involving customer data should check whether their services fall within the list. Enterprises that engage such services should also check the provider's certificate before signing.
6. A contract with a processor needs specific terms
The law requires a contract but does not list mandatory terms for every processing contract. Enterprises may use the terms the law requires for cloud computing contracts and for data transfer agreements as a reference. A contract with a processor should cover:
- Scope of processing: purpose, types of data, groups of data subjects and duration.
- Data flows and the role of each party, with the corresponding responsibilities.
- Security measures, technical and organisational, including access rights. Data in the cloud must be encrypted at rest and in transit.
- Subcontractors: conditions for their use and the duty to pass data protection requirements down to them.
- Support for data subject rights, within periods shorter than the controller's statutory deadlines.
- Incident notice on detection, early enough for the controller to notify the specialised authority within 72 hours.
- Immediate notice of any change that may affect personal data.
- Deletion or return of data at the end of the term or on termination.
- The controller's right to audit and the processor's indemnity.
- Cross-border transfer, if the processor stores or accesses data from abroad.
7. Vietnamese law is close to the GDPR but adds a licensing regime
Under the European Union's General Data Protection Regulation (GDPR), the processor is also the party that processes data on behalf of the controller. A processor that decides the purpose is also treated as a controller. The main differences are:
| Issue | Vietnam | GDPR |
|---|---|---|
| Terms of the processor contract | A contract is required; detailed terms are set only for some cases, such as cloud computing | The law lists mandatory terms for every processor contract |
| Subcontractors | No general rule; cloud providers must ask subcontractors to comply | Prior written authorisation of the controller is required |
| Licensing | Some processing services need a certificate of eligibility from the Ministry of Public Security | No licensing of processors |
| Liability for damage | The processor is liable to the controller | The data subject may claim against the processor when it breaches its own obligations or acts against instructions |
Enterprises with European group companies often already have a GDPR data processing agreement template. Enterprises may use it as a base, but should supplement it with Vietnamese requirements, such as checking the certificate, the deadlines for data subject rights and the 72 hour incident notice.
8. What to avoid when engaging a processor
- Handing over data before signing. A processor may receive data only after a contract or agreement is in place.
- Using a standard service contract without data terms. When an incident occurs, the enterprise has no basis to demand support or indemnity.
- Not controlling subcontractors. Data may pass through several layers of providers without the enterprise knowing.
- Not checking the certificate when the service falls within the list of personal data processing services.
9. What enterprises should do
For enterprises engaging a processor:
- List the providers with access to personal data, with the types of data and purposes.
- Sign data processing agreements for current contracts that have no data terms.
- Check the certificate of eligibility of providers whose services fall within the list.
- Set internal deadlines for the processor to support data subject requests and to report incidents.
For enterprises acting as processors:
- Check whether your services fall within the list of personal data processing services.
- Refuse to receive data before a contract or agreement on data processing is in place.
- Do not use client data for your own purposes, including analysis or product development, unless the contract allows it.
- Set up a procedure to notify the controller of violations as soon as they are detected.
Read on in the Personal data protection series
- Previous article: Personal data controller: who decides and who is liable
- Next article: Controller and processor, third party and data subject
- Related: Controller and processor, third party and data subject
- 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


