Compliance recordsData protection

What is a record of processing activities? A business guide to RoPA in Vietnam

Written by: LexData ConsultingLegal review: Ho Thi Ha Nhi
Definition in brief

A record of processing activities (RoPA) is an internal governance document that comprehensively inventories every activity of collecting, storing, using, sharing, transferring and destroying personal data within an organisation. Law 91/2025/QH15 does not set out a separate obligation called a 'RoPA', but the practical accountability obligations — the impact assessment dossier under Article 21, the responsibilities of the parties under Article 37, proving consent and producing documents during inspections and audits — make maintaining a data inventory a de facto mandatory foundation.

Official legal texts

Key takeaways for businesses

  • The RoPA is the backbone of an internal data governance programme; it is the input for preparing the DPIA dossier submitted to the A05 Department (Ministry of Public Security) (the impact assessment dossier under Article 21 of Law 91/2025 — a mandatory legal obligation) and for accounting to the specialised authority during inspections and audits.
  • Vietnamese law does not separately name an obligation to 'keep a RoPA'; however, both the controller and the processor are accountable for their processing activities under Article 37 of Law 91, so building and updating a data inventory is a near-mandatory governance practice.
  • Keep the record ready to produce whenever the specialised personal data protection authority (the A05 Department, Ministry of Public Security) carries out an unannounced inspection or audit.

What is a record of processing activities? RoPA in Vietnam under compliance governance standards

A record of processing activities (RoPA) is the data inventory document that lets a business keep comprehensive control over all of its internal information flows. One of the biggest challenges businesses face when implementing personal data protection compliance, and the first problem a RoPA in Vietnam should solve, is 'data blindness': management and the legal team do not know how many personal data flows exist in the business, which department collects the data, which server stores it, which partners it is shared with and who has access. Without an accurate inventory and data map, every effort to draft policies or invest in technical security solutions becomes meaningless.

To solve this problem, international governance practice (Article 30 GDPR) and compliance practice in Vietnam have popularised a core tool called the record of processing activities (RoPA). Note: the Personal Data Protection Law No. 91/2025/QH15 does not separately name an obligation called a 'RoPA'; however, a data inventory is the foundation that allows a business to fulfil the accountability obligations that are genuinely mandatory — the impact assessment dossier under Article 21 and the accountability of the controller and processor under Article 37. The RoPA is therefore regarded as a near-mandatory governance practice for both personal data controllers and personal data processors.

1. The strategic role of the RoPA in compliance governance

The RoPA is often likened to the 'data genome map' of the whole organisation. Far from being a passive spreadsheet, the RoPA plays a decisive role in 3 governance respects:

  • The foundation of the DPIA dossier (Article 21): Preparing the DPIA dossier submitted to the A05 Department (Ministry of Public Security) is a mandatory obligation; the impact assessment report in the dossier (Form No. 10, Point a, Clause 2, Article 19 of Decree 356/2025/ND-CP) must describe in detail the processing activities, the types of data and the protective measures. If the business does not yet have a complete data inventory, it cannot prepare the DPIA dossier accurately.
  • Evidence of the accountability principle: When a data leak occurs or when the A05 Department carries out an unannounced inspection, an up-to-date data inventory is a key document proving that the organisation understands its data flows and actively controls their risks.
  • The basis for exercising data subject rights (Article 4): When customers or employees ask to access or delete their personal data, the RoPA helps the IT team and the DPO pinpoint exactly which databases hold the data so it can be deleted within the statutory time limit.

2. Controller RoPA vs processor RoPA

Depending on the legal role under Article 2 of Law 91/2025/QH15, the content of the RoPA is designed from 2 angles:

  • Controller RoPA: A comprehensive record of the processing activities whose purposes and means the organisation itself decides (e.g. recruitment, customer care, customer loyalty programmes, office security cameras).
  • Processor RoPA: A record of the processing activities the organisation carries out on behalf of its clients under a data processing agreement (DPA) (e.g. an HRM SaaS provider recording each corporate client's HR data flows, or an outsourced customer care call centre).

3. Eight fields a RoPA in Vietnam should contain

With reference to Article 30 GDPR and the content that must be described in the impact assessment dossier under Article 21 of Law 91/2025/QH15, each processing workflow in the RoPA should record the following 8 groups of information:

  1. Name and contact details: The business name, legal representative, responsible department and the data protection officer (DPO).
  2. Specific purpose of processing: The specific reason the organisation needs to process the data (e.g. payroll and social insurance contributions, e-commerce order delivery).
  3. Categories of data subjects: Clearly identify whose data is collected (employees, individual customers, job applicants, partners).
  4. List of personal data fields: List each data field in detail, clearly separating basic personal data from sensitive personal data under Articles 3 and 4 of Decree 356/2025/ND-CP.
  5. Recipients and third parties: The internal departments that access the data and the external subcontractors (courier companies, cloud services, payment banks).
  6. Cross-border data flows: Determine whether the data is transferred outside Vietnam; if so, record the receiving country and the corresponding transfer dossier under Article 20.
  7. Expected retention period: How long each category of information is kept and the criteria for setting the period (under accounting law, labour law or by agreement).
  8. General description of security measures: The technical and organisational measures applied to protect the data (data encryption, multi-factor authentication, least-privilege access, backups).

Reference structure of a record of processing activities (RoPA) template for businesses

RoPA field What to record HR department example Sales department example
Processing workflow name Name of the specific business activity Timekeeping & employee payroll Processing retail orders on the website
Purpose of processing The specific objective Paying salaries, withholding tax and social insurance Delivering goods and collecting cash on delivery (COD) from buyers
Categories of data subjects Whose information is collected Permanent and probationary employees Individual customers shopping online
Type of personal data Details of the data fields Full name, citizen identity card (CCCD) number, bank account number, FaceID for timekeeping (sensitive) Full name, recipient phone number, delivery address
Applicable legal basis Corresponding legal provision Article 25 of Law 91 & employment contract (Point d, Clause 1, Article 19) Contract for the sale of goods (Point d, Clause 1, Article 19)
Third-party recipients External partners accessing the data Payroll bank, HRM software provider Delivery carriers (GHTK, Viettel Post)
Storage location Server infrastructure holding the data On-premise servers at the office & cloud in Vietnam Cloud servers located in Vietnam
Retention & destruction How long data is kept before deletion The statutory period for each type of record (accounting, labour, social insurance) 12 months from successful delivery
Security measures Technical safeguards and policies AES-256 encryption, role-based access control TLS 1.3 encryption in transit, 2FA authentication

4. A 5-step guide to building and running a RoPA in Vietnam for your business

To build a complete RoPA from scratch, a business should follow a standard 5-step process:

Step 1: Set up an internal data privacy taskforce

Appoint a data protection point person (the DPO or the legal team) to lead, working with representatives of the key departments: IT, HR, Marketing, Sales, Accounting and Customer Care.

Step 2: Design and issue a data discovery survey

Send a questionnaire to each department head to gather information: What information does the department collect? From which sources? Is the data stored in personal Excel files or in centralised software? Who is it shared with?

Step 3: Interview business users and draw a data flow map

The taskforce interviews operational staff directly to bring 'data blind spots' (shadow IT) to light, and draws a visual map of the data's journey from the entry point, through internal processing, to the storage points and the points where it is shared externally.

Step 4: Consolidate the information into a master RoPA

Standardise the collected information into a centralised governance register (a highly secured file or specialised data privacy management software). Check that the information in the RoPA is consistent with the DPAs signed and the privacy policy published on the website.

Step 5: Set up a periodic review & audit cycle

The RoPA is a living document; it cannot be prepared once and then left in a drawer. The business should set a review cycle of at least once every 06 months, or update it immediately whenever the business launches a new product, deploys new IT software, changes cloud service provider or undergoes a merger.

Decree 330/2026/ND-CP currently has no separate penalty provision for 'failing to keep a RoPA'. However, lacking a data inventory prevents a business from fulfilling its statutory obligations, and it will be penalised through the violations that directly result:

  • Failing to prepare, submit or update the impact assessment dossier (DPIA) because accurate input data is missing: Article 55 — a fine of VND 20–30 million for organisations; deliberately falsifying figures or providing misleading information in the dossier: VND 50–100 million.
  • Being unable to prove the data subject's consent, or processing without valid consent: Article 43 — a fine of VND 30–50 million (Points a and g, Clause 1).
  • Delaying or failing to respond to requests to access, correct or delete data because the data cannot be located: the group of provisions on exercising data subject rights (Articles 44–46), with a range of around VND 10–50 million depending on the violation.
  • Being caught unprepared in an unannounced inspection or audit: being unable to present an overall picture of data flows increases the risk of being found in breach of the data protection principles (Article 39, range of VND 20–60 million).

For the full penalty framework, see the handbook entry Penalties for personal data protection violations; for the process of preparing the impact assessment dossier, see the handbook entry The DPIA dossier.

Expert perspective from lawyer Ho Thi Ha Nhi

"LexData's practical advisory experience shows that when the authorities carry out an unannounced inspection, they will not read the lengthy privacy policies on the website; they will immediately ask to see the impact assessment dossier and the related data inventory documents. If the business can produce a detailed data inventory that is updated regularly and accurately reflects its internal software ecosystem, it has demonstrated transparency and a commitment to legal compliance, thereby significantly reducing the risk of being found in breach and heavily penalised."

A record of processing activities is only useful if it is kept up to date with real-world changes. Businesses that need a point person for periodic monitoring can consider an outsourced DPO service to help maintain compliance records, with the review schedule and scope of work set out in the agreement.

Frequently asked questions

Do small and medium-sized enterprises (SMEs) or startups have to keep a RoPA?

Law 91/2025/QH15 does not separately name an obligation to 'keep a RoPA' and does not require a record in any fixed template. However, a business acting as a controller or controller-processor (even if it only holds its employees' HR data) must prepare a DPIA dossier under Article 21 (a processor prepares one as agreed with the controller — Clause 3, Article 21) and meet its responsibilities under Article 37, so maintaining a data inventory proportionate to its size is the practical way to meet these obligations. Note: small businesses and startups may choose not to comply with Article 21, Article 22 and Clause 2, Article 33 for 05 years from 01/01/2026, and household businesses and micro-enterprises are not required to comply with them (Clauses 2 and 3, Article 38 of Law 91/2025; Article 41 of Decree 356/2025/ND-CP), except in three cases; medium-sized businesses do not qualify for this relief.

Must the RoPA be filed with the Ministry of Public Security (the A05 Department) every year?

No. The law does not require businesses to periodically file a standalone RoPA with the A05 Department. Nor does the law say where the RoPA must be kept; the obligation to maintain records at the business's head office applies to the DPIA dossier (Point a, Clause 1, Article 55 of Decree 330/2026/ND-CP). Good practice is to keep the RoPA with the DPIA dossier, ready to produce when an inspection is requested, since it is the data source for completing the DPIA dossier under Article 21.

Can a business manage its RoPA in an Excel file, or must it buy specialised software?

The law does not prescribe a mandatory form for the RoPA, so a business may keep it on paper or in electronic form (including Excel files or Google Sheets with secured access permissions). For small and medium-sized businesses with simple data flows, a properly governed Excel file is entirely valid. For large groups with hundreds of complex IT systems, specialised software will help automate updates and avoid errors.

Does the RoPA need updating when the business changes its cloud software provider or delivery partner?

Yes. Any change concerning external partners receiving data (processors), the location of storage servers or the purpose of processing should be recorded in the RoPA as soon as the change takes effect, so that the compliance records remain accurate at all times. If the change alters the content of the DPIA dossier already submitted (e.g. a processor is added or replaced), the business must also update the DPIA dossier under Article 22 of Law 91/2025 and Article 20 of Decree 356/2025/ND-CP.

Legal review

Ho Thi Ha Nhi

Founding Lawyer, LexData Consulting · Ho Chi Minh City Bar Association

The Vietnamese original of this entry has been reviewed for legal accuracy against the Personal Data Protection Law No. 91/2025/QH15 and current implementing legislation. This English edition is an unofficial translation for reference; the official legal texts are in Vietnamese.

Meet the LexData team

Go further with LexData

Related service

DPIA Dossier Preparation & Corporate RoPA Development Services

Work with our lawyers on the filings and documents, end to end.

Learn about the service

Get started

Ready to talk to LexData?

Book a free 30-minute consultation. We'll outline your priority risks and next steps for your size and sector — no obligation.

  • Reply within 1 business day
  • Confidential discussion

Or contact us directly

CONTACT

Request a consultation

Tell us what you need and the LexData team will get back to you shortly.

0/1,000

The information you provide is processed only to receive and respond to this request, in line with LexData’s Personal Data Protection Policy.