DPO Radio

If your organization relies on identity data, electronic identification or authentication in Vietnam, your obligations start with the Identity Law 26/2023/QH15. It covers citizen identity, the identity card and the identity database, and it is the legal basis for electronic identification. It took effect on 1 July 2024 and is in force today.
Two instruments sit beneath it, and they do different jobs:
Decree 320/2026/NĐ-CP, issued on 13 August 2026 and effective 28 September 2026, amends and supplements Decree 69; the two decrees are read together. It:
The Draft Law on Electronic Identification and Authentication is not part of this stack. It is a consultation draft, not enacted law, and ComplianceOne tracks it separately as readiness work.
Each layer needs different handling. Decree 69 obligations need execution and evidence today. Project 06 integrations need mapping as dependencies, not as obligations. Draft provisions need watching without being treated as binding. ComplianceOne keeps the layers connected and keeps each one at its own legal weight.
Law 26/2023/QH15 on Identity: passed 27 November 2023, effective 1 July 2024. Covers identity information, the identity card and the identity database.
Decree 69/2024/NĐ-CP on Electronic Identification and Authentication: issued 25 June 2024, effective 1 July 2024. It replaced Decree 59/2022/NĐ-CP.
Decree 320/2026/NĐ-CP: issued 13 August 2026, effective 28 September 2026, amends and supplements Decree 69 rather than replacing it.
Project 06 (Đề án 06), approved by Decision 06/QĐ-TTg of 6 January 2022, covering 2022–2025 with a vision to 2030.
Organizations that rely on identity information, electronic identification, authentication or verified state data.
Identity lifecycle; authentication evidence; controlled reuse of verified state data; population-database and VNeID dependencies.
Attribute inventories, lifecycle records, authentication logs, approvals and dependency maps.
Seven verified Decree 69 forms: TK01, TK03 and XT01 to XT05. Neither the Identity Law nor Project 06 prescribes a verified official form.
Before 31 December 2026 for national digital platforms and for covered non-banking accounts created before the amendment took effect on 28 September 2026, so the last day is 30 December 2026. Before 30 June 2027 for covered banking-sector accounts created before that date, so the last day is 29 June 2027. Both are set by Article 20(3) of Decree 320/2026/NĐ-CP.
Decision 1830/QĐ-TTg of 22 September 2026: a State plan to pilot connecting VNeID with Singapore's Singpass and Laos's LAeID. It directs ministries and creates no duty for, and no access by, a private organisation.
QCVN 16:2026/BCA (voice) and QCVN 17:2026/BCA (iris), issued by Circulars 169/2026/TT-BCA and 170/2026/TT-BCA on 1 October 2026 and effective 15 April 2027. They set technical requirements for biometric data and capture equipment serving the Identity Database.
The law, Decree 69, and Decree 320 are in force, the Decision 1830 pilot plan is a reference, and the draft law is tracked separately. Each sits on its own layer.
Decree 69 is where the day-to-day identity obligations sit. It governs electronic identity accounts and the authentication levels that apply to them. It is the only instrument in this stack with verified official forms:
Decree 320 amends and supplements Decree 69 from 28 September 2026. Most of its twenty articles rewrite numbered articles of Decree 69, so each obligation is cited to both decrees. It:
It prescribes no new form. TK01, TK03 and XT01 to XT05 still apply; what changed is the procedure behind them.
Project 06 is Vietnam's national programme for applying population data and electronic identification to public and private services. The Prime Minister approved it by Decision 06/QĐ-TTg, signed on 6 January 2022.
Its full English title is the Scheme on developing the application of population data, identification and electronic authentication in service of national digital transformation for the 2022–2025 period, with a vision to 2030. The Vietnamese title is Đề án phát triển ứng dụng dữ liệu về dân cư, định danh và xác thực điện tử phục vụ chuyển đổi số quốc gia giai đoạn 2022 - 2025, tầm nhìn đến năm 2030.
For compliance teams, Project 06 is the integration layer: the programme under which services connect to the population database and to VNeID. ComplianceOne tracks one obligation against it. You map the population-database, VNeID and public-service integrations your organization depends on, with the evidence behind each.
Project 06 prescribes no verified official forms and imposes no direct filing or sanctions obligations. ComplianceOne treats it as reference material within the Identity Law stack, and records you create for it are labelled as internal working documents.
Source: Decision 06/QĐ-TTg, 6 January 2022, Prime Minister of Vietnam.
Decision 1830/QĐ-TTg, in force since 22 September 2026, issues the Government's plan to connect VNeID with Singapore's Singpass and Laos's LAeID. It includes a pilot at Nội Bài and Tân Sơn Nhất airports from 15 November to 15 December 2026. It binds the Ministries of Public Security, Foreign Affairs, and Science and Technology.
It is not an implementing instrument of the Identity Law and does not cite it, Decree 69 or Decree 320. It places no duty on a private organisation and gives none access to any of the three systems. ComplianceOne keeps it as a reference with ministry milestones, apart from the duties above. An optional register lets an organisation that expects to rely on cross-border identity model a flow and hold it out of production until its evidence is recorded.
The Ministry of Public Security issued the national technical regulations on voice biometrics (QCVN 16:2026/BCA) and iris biometrics (QCVN 17:2026/BCA) on 1 October 2026. Both take effect on 15 April 2027, with no transitional provision. Their subject matter is biometric data and capture equipment serving the Identity Database. They set how samples are captured and stored and what capture devices must meet. QCVN 16 also sets how voice data is exchanged, protected, logged, corrected, deleted and handed over. QCVN 17 sets encryption and key management for iris data. A capture device needs a security check by the competent authority, which the regulations do not name. Under QCVN 16, a producer or supplier of voice capture software that falls within the regulation's subjects carries out conformity assessment and declares and registers its conformity under the law in force.
They do not make any processing lawful: that rests on the law that governs the processing, the Personal Data Protection Law and, for the Identity Database, the Identity Law itself. Whether an activity of yours is reached is your organisation's determination. ComplianceOne holds the requirements, the two commencement dates and, once the overlay is added directly, registers for capture components, voice-data transfers, readiness reviews and supervision and inspection records. Each component carries its deletion records and links to the processing records for the same data.
The draft law is not part of the active stack. It neither amends nor replaces Law 26/2023/QH15 or Decree 69. ComplianceOne tracks it as separate readiness work, so draft provisions never mix with current obligations or evidence.

For each attribute your organization processes, record where it came from, the lawful basis for using it and which verified state data it links to. Reuse of verified state data carries its legal basis, source and traceability on the record.
The register has no field for a personal identification number, a date of birth or a tax reference, and it stores no hash of one either. These values come from small, structured ranges, so a hash can be reversed by trying candidates until one matches.
Instead, each record shows that a verification happened:
Once Decree 69 is added to your workspace, ComplianceOne offers its 19 regulated attribute types (eight of them restricted), its ten verification methods and its four ranked authentication levels. When the decree changes, the update reaches your workspace without a product change.
The seven official forms, the electronic identity account lifecycle and authentication evidence sit in one workspace. Account creation, activation, change, suspension and termination keep their evidence attached. Authentication records keep the method, result, time and relying service, so you can answer an audit question from the record.
Record your population-database, VNeID and public-service integrations with the evidence behind each. This is documentation and evidence, not a production connection to VNeID.
Decree 320 sits beneath Decree 69 as an active amendment. Each obligation names both the amending article and the Decree 69 article it changes. The two linkage deadlines are tracked separately against the accounts they cover. The two appendix lists of integrable document types are available as reference lists, not as forms to fill in.
Where identity evidence also serves personal data protection, data governance or cybersecurity work, you can link the same records to those obligations. Each record keeps its original framework and audit history.
Maintains identity attribute inventories, source systems, and population-database or VNeID dependency records.
Explore Data MappingHolds the seven official Decree 69 forms and keeps internal lifecycle records clearly separate.
Explore Compliance FormsConnects authentication events and account lifecycle changes to accountable owners and approvals.
Explore Access & AccountabilityKeeps contributor, review, approval and evidence history across the identity stack.
Explore Audit TrailAssigns ownership and recurring review across the active instruments and the separate draft-readiness track.
Explore Program Governance


The Identity Law, Decree 69 and Project 06 stay on separate layers, so every record carries the legal weight of the layer it belongs to.

Population-database and VNeID dependencies are mapped with evidence, not connected live, so ownership and integration risk stay visible without overstating what ComplianceOne touches.

Regulated identity attributes are recorded without their values, so the register that answers an inspector never becomes a second copy of your identity data.
See how ComplianceOne helps structure evidence, ownership, and review for this framework.

Yes. Law 26/2023/QH15 and Decree 69/2024/NĐ-CP both took effect on 1 July 2024 and are in force. Decree 320/2026/NĐ-CP amended Decree 69 from 28 September 2026.
Project 06 (Đề án 06) is Vietnam's national programme for applying population data, electronic identification and electronic authentication to national digital transformation. It covers 2022–2025, with a vision to 2030. The Prime Minister approved it by Decision 06/QĐ-TTg on 6 January 2022. It is the programme under which organizations integrate with the population database and VNeID. ComplianceOne treats it as reference material and tracks it through integration-dependency mapping.
No. It prescribes no verified official forms and imposes no direct filing or sanctions obligations. ComplianceOne sets it alongside the parent law and manages its one piece of work, dependency mapping, like any other obligation.
No. It amends and supplements Decree 69 from 28 September 2026. Decree 69 remains the operative decree, and most of the amendment rewrites articles that stay in it, so obligations are cited to both.
No. It is a separate draft that ComplianceOne tracks separately, and it is not current law. It is also a different instrument from Decree 320/2026, which is an active government decree, not a law.
No. Decision 1830/QĐ-TTg is a State plan for ministries to pilot connecting VNeID with Singpass and LAeID. It grants no private organisation access to any of the three systems and places no duty on one. ComplianceOne keeps it as a reference, apart from Decree 69 and Decree 320.
No. ComplianceOne records your VNeID dependencies: which integrations exist, who owns them and what evidence supports each. It does not run a production connection to VNeID, issue electronic identity accounts or authenticate anyone. It records the evidence that a verification happened, never the attribute value or a hash of it.
Yes. The seven verified Decree 69 forms keep their official identifiers: TK01, TK03 and XT01 to XT05. Internal lifecycle records, including Project 06 integration records, are labelled as working documents prepared in ComplianceOne.

Test scoped workflows, evidence, and review with your compliance team.

Review applicability, evidence sources, and operating-model requirements.