DPO Radio

AesirX ComplianceOne | QCVN 16 and QCVN 17 Vietnam Voice and Iris Biometrics

Overview Image

Circular 169 and 170: Scope and Current Status

The Ministry of Public Security issued Circular 169/2026/TT-BCA and Circular 170/2026/TT-BCA on 1 October 2026. Each issues a national technical regulation: QCVN 16:2026/BCA on voice biometrics and QCVN 17:2026/BCA on iris biometrics. Both take effect on 15 April 2027. They are issued, not yet in force.

What they cover:

  • The subject matter. Voice or iris biometric data, and the equipment that captures it, serving the national Identity Database (Cơ sở dữ liệu căn cước) (section 1.1 of each regulation).
  • Who they name. Police units, and agencies, organisations and individuals involved in collecting, managing or using the biometric. Also those who buy, import, trade, test, certify or make capture equipment to serve the Identity Database (section 1.2).
  • What they set. How samples are captured and stored and what capture equipment 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.

An open reading. In section 1.2 the words "to serve the Identity Database" close the list of equipment activities (and likewise in section 5.1). The text does not settle whether they also limit collecting, managing and using the biometric. The confidentiality duty in section 4.4 carries no such words. Whether an activity of yours is reached is your organisation's determination, made with its counsel.

No transition. There is no transitional provision and no staged commencement. Both Circulars take effect on the same day.

What they leave to other law. They set technical requirements. They supply no legal basis, consent rule, impact assessment or transfer rule; they require the data to be handled as the law provides (section 3.1). Those questions are answered under the law that governs the processing: the Personal Data Protection Law 91/2025/QH15 and its decrees and, for data in the Identity Database, the Identity Law. Neither QCVN sets a retention period of its own. Neither Circular prescribes a form or states a sanction.

Overview Image

How QCVN 16 and QCVN 17 Relate to the Identity Law

The Identity Law (Law 26/2023/QH15, amended by Law 118/2025/QH15) is the law under which the Identity Database is built, and both Circulars cite it among their legal bases. They also cite the Law on Standards and Technical Regulations, the Personal Data Protection Law and the Cybersecurity Law 116/2025/QH15.

The Circulars amend no instrument. Once added to your workspace, the two records sit under the Identity Law and are cross-referenced to the Personal Data Protection Law, Decree 356/2025/NĐ-CP, the Data Law and the Cybersecurity Law. Read them with the Identity Law for the database they serve, and with the Personal Data Protection Law and the Identity Law for whether the processing may happen at all.

Technical Provisions and Compliance Obligations

ProvisionWhat It RequiresWhat You Need
Article 3(2); sections 1.1, 1.2, 4.5, 5.1Voice data and capture equipment serving the Identity Database; related organisations and individuals implement the CircularYour own determination of whether each activity serves the Identity Database, with its basis
Sections 2.1.1–2.1.2, 2.1.4Natural voice captured directly, not replayed; a person able to read reads the passages in the regulation's appendix, a person unable to read speaks freely on a suggested topic; stored as mono, uncompressed WAV (PCM) at 16,000 Hz or more and 16 bit or more; every sample carries two separate metadata layers; exchanged between systems in a digitally signed XML packageEvidence that capture, storage and exchange follow the format
Section 2.1.3A sample that fails any signal-quality criterion in Table 2 (Bảng 2) is rejected or destroyed, and signal quality is measured automaticallyEvidence of the quality check in the capture software
Section 2.1.6Capture software has the mandatory functions and publicly declares, in its technical documentation, its analysis algorithm's name and version and the parameters that affect results, records the algorithm's known limitations in metadata and ensures results can be independently reproducedThe software's algorithm declaration
Section 2.2Microphones meet Table 3 and sound cards meet Table 4A datasheet or test report for each component
Section 2.3The acoustic environment meets Table 5 for a first enrolment into the Identity Database, and in every other case is measured before each session and recorded in the session metadataThe environment measurements
Sections 3.1, 4.4Voice data is sensitive biometric information, kept confidential, used for its purpose and scope, and never shared or transferred unlawfullyThe processing record and its legal basis, kept under the Personal Data Protection Law
Section 3.2A capture device is security-checked by the competent authority (the text names neither the authority nor a procedure or timing), and carries technical documentation and instructions when put into use; whoever manages or operates it keeps it working and maintains its technical conditions (section 3.2.3)The security-check reference, the documentation held and the device-upkeep evidence
Section 3.3Capture software is checked for conformity with section 2.1.6 before official use, using a standard test data set a competent authority issues (the text names neither); a producer or supplier that falls within the regulation's subjects carries out conformity assessment, declares conformity (công bố hợp quy) and registers the declaration under the law in force before the software is put into use. Section 1.2 names makers of capture equipment, not of software, so whether a software producer is within the subjects is part of the open readingThe declaration's reference and its registration
Section 3.4Data retention follows the law in forceThe instrument you rely on for each period
Sections 3.5.1–3.5.3Encryption at the capture device, two-way authenticated encryption between device and server, and a hardware key-management device at the central databaseEvidence of the encryption in place
Sections 3.5.4–3.5.8Role-separated access, an immutable audit log, correction records that never alter the original, deletion only on a ground section 3.5.6.3.1 names, of the originals, corrections and every copy at once, by at least the Purge level, a provenance record for every sample and a chain-of-custody record for every transferA record of each deletion and a chain-of-custody record for each transfer
Sections 4.1–4.3, 5.1The Department of Security Industry and the focal unit disseminate, guide, monitor, inspect and urge the regulation's application; the focal unit manages and secures the capture, processing, storage, sharing and use system; provincial and city police organise implementation locally, subject to inspection and supervision by the Ministry and the competent functional units; the bodies concerned disseminate it within their own managementA record of each act carried out or received, with the references of what came back

ProvisionWhat It RequiresWhat You Need
Article 3(2); sections 1.1, 1.2, 4.5, 5.1Iris data and capture equipment serving the Identity Database; related organisations and individuals implement the CircularYour own determination of whether each activity serves the Identity Database, with its basis
Sections 2.1, 2.4The mandatory capture conditionsEvidence of how capture is set up
Sections 2.2, 2.7A capture device meets every row of Table 1: infrared light of 700–900 nm, 18 pixels/mm or more, iris images of at least 640 x 480 pixels, AES-256 or stronger encryption and the other rowsA datasheet or test report for each device
Section 2.3Iris images stored in one of the four Table 2 formats, uncompressed or compressed under ISO/IEC 15948 (PNG) or ISO/IEC 15444 (JPEG2000), lossless or lossy as Table 2 setsEvidence of the storage format
Section 2.5Stored image sizes for each matching use, on chip and in the systemEvidence of the sizes used
Section 3.1Iris data is sensitive biometric information, processed lawfully, for its purpose, kept confidential and access-controlledThe processing record and its legal basis, kept under the Personal Data Protection Law
Section 3.1.3Iris data encrypted and stored as the Identity Law provides; a key-lifecycle mechanism; key management consistent with the information-security standards in the Cybersecurity Law and ISO/IEC 27001:2022 (latest version applies, section 1.4)Key-lifecycle evidence
Section 3.2A capture device is security-checked by the competent authority (the text names neither the authority nor a procedure or timing), and carries technical documentation and instructions when put into use; whoever manages or operates it keeps it working and maintains its technical conditions (section 3.2.3)The security-check reference, the documentation held and the device-upkeep evidence
Sections 4.1–4.3, 5.1The same dissemination, guidance, monitoring, inspection and local-implementation roles as the voice regulation, for irisA record of each act carried out or received, with the references of what came back

QCVN 17 has no conformity-assessment section and prescribes no conformity procedure, although section 1.2 lists conformity certification among the activities it covers. The text does not say whether a conformity duty attaches to iris capture devices under the Law on Standards and Technical Regulations. Two-way authenticated encryption in transmission is a QCVN 16 requirement only.

QCVN 16 and QCVN 17 state no false-acceptance, false-rejection or recognition rate. They state no minimum sample duration and no number of languages or dialects either.

ObligationTimelineReference
Circular 169 and QCVN 16 take effect15 April 2027Article 2 of Circular 169
Circular 170 and QCVN 17 take effect15 April 2027Article 2 of Circular 170
Earlier deadline or grace periodNone statedArticle 2 of each
Retention of voice data and provenance recordsThe period the law in force setsSections 3.4 and 3.5.7 of the voice regulation
Retention of the voice audit logThe period of the competent authoritySection 3.5.4 of the voice regulation

Neither Circular prescribes a form. Eight internal templates come with the two Circulars in ComplianceOne, labelled as your own working records. Each is the record behind one of the biometric capture registers, and is filled there rather than as a generic form.

Form / AnnexOfficial IDPurposeRequired For
Voice biometric capture component — QCVN 16 recordNone (internal template)One record per voice capture component: capture software, microphone, sound card, capture station, exchange interface or storage systemBringing a voice component into use
Iris biometric capture device — QCVN 17 recordNone (internal template)One record per iris capture device, capture or processing software, or storage or encryption systemBringing an iris device into use
Voice biometric data transfer — chain-of-custody recordNone (internal template)The sending and receiving sides of each voice-data transfer, the method and the integrity resultEach transfer of voice data
Voice and iris readiness reviews (practice)None (internal template)A person's dated review against one regulation, in their own words, with a state per requirement and a second person's confirmationA readiness review, a recommended practice
Voice biometric data deletion recordNone (internal template)Each deletion of voice data: who carried it out, its ground, what was deleted and the method, then a second person's confirmationEach deletion of voice data
Voice and iris guidance, monitoring and inspection recordsNone (internal template)Each act of dissemination, guidance, monitoring, inspection, urging or local implementation carried out or received, and its follow-upEach act under sections 4.1–4.3 and 5.1
Overview Image

How ComplianceOne Supports Circular 169 and 170 Compliance

Once the two Circulars are added to your workspace from the Sector Overlays catalog, directly or for reference, they show as upcoming until 15 April 2027, under the Identity Law. The two Circulars are available in the Enterprise Unlimited package, through the Sector Overlays module, whether installed directly or for reference.

What you can use today:

  • The requirements. The regulations' duties are carried section by section, each requirement citing its section. Duties are marked mandatory. The two recommended practices for each regulation are not, and each says it is a recommended practice.
  • Biometric Capture Components. A register of every voice and iris capture component your organisation uses, operates or supplies. Each component holds its maker, supplier, model and version, and a person's scope determination with its basis and your organisation's role: within scope, not within scope or not determined. A determination can record more than one of your organisation's roles, such as a police unit that also operates the device. It is added, never overwritten, so the history stays. A component with none reads Not determined, and one determined not within scope lists nothing as missing.
  • Security check and, for voice software, conformity. The component holds the security-check reference, date and versions covered, as your team enters them from the result it holds. Voice capture software also holds the reference of its conformity check, which the text does not say who carries out, and the assessment, declaration of conformity and registration references of a producer or supplier within the regulation's subjects. A registration is accepted only after its declaration.
  • Evidence by area. One area for each evidence section the regulation's template declares for the component's type. Voice areas include storage format, signal quality, encryption and keys, and deletion by Purge; iris areas include the device, image format and key lifecycle; both include device upkeep for capture devices. Each area holds a statement and the documents bound to the component.
  • What is missing. Each component lists what is still missing, as a list and never as a score. Marking a component in use records who did it and what was missing at that moment.
  • Deletion records. Each deletion of a voice component's data is recorded on the component with who carried it out and when, its ground, what was deleted and the method, and confirmed once by a second person. The second person is a practice of your organisation, not a duty of the text. It reads awaiting confirmation, confirmed or not confirmed, as the confirmer recorded.
  • Biometric Chain-of-Custody Records. The sending side and the receiving side of each voice-data transfer, recorded by two different people within your organisation, a practice the register holds rather than a duty of the text. When the other side is another organisation, you record your half and its references, and nothing is read from its records. A transfer whose receiving side recorded a checksum mismatch reads Not accepted, an incomplete transfer lists what is missing, and neither counts as completed. A transfer recorded wrongly is not overwritten. Another person withdraws it with a reason, and the corrected transfer is recorded as a new one that names the transfer it replaces. That is your correction practice, not a duty of the text.
  • Biometric Readiness Reviews. A person's dated review against each regulation, in their own words, with the reviewer's state for each requirement and a snapshot of what was missing on each component in scope when it was saved. A second person can confirm it once. No readiness flag, score, count or percentage is added.
  • Biometric Supervision and Inspection Records. Each act of dissemination, guidance, monitoring, inspection, urging or local implementation your organisation carried out, and each inspection or supervision it received. Each holds the follow-up the act asks for and the references of what units sent in reply. Nothing on it says an act was complied with.
  • An inspection evidence pack. Choose one regulation, one component or the components linked to one system, and a period. The components, determinations, checks, evidence index, links, deletion and custody records, readiness reviews and supervision records export as PDF, DOCX or XLSX, with the regulations' boundary statement.
  • Two procedures, one per regulation, for bringing a component into use, and the commencement of each Circular.
  • Scope guidance on who each regulation reaches and what it leaves open, and two risk areas with no fine amount, because the Circulars state none.

The registers work once the overlay is added to your workspace directly; added for reference, it gives the content and the registers say why they are not in use.

Kept beside your personal data records. Each component links to the processing activities, impact assessments, transfer assessments, vendors and systems your organisation already holds for the same data. The link shows on both sides: each of those records lists its linked capture components, and says when a component changed after it was linked, so its owner can review it. The link changes nothing on the linked record, and the owner's review clears the prompt. The legal basis, consent and transfer questions are answered in Data Mapping and Assessments.

What it does not do. ComplianceOne records the evidence your team enters. ComplianceOne does not test, certify or security-check a device or software, file or register a declaration of conformity, or connect to the Identity Database. It does not decide whether a regulation reaches your activity, and a QCVN record never makes biometric processing lawful. It deletes no biometric data and does not confirm that a deletion happened. It does not disseminate, guide, monitor, inspect or supervise anything, and it reads no other organisation's records.

Related Modules

Data MappingData Mapping

Holds the processing activities a capture component links to, and lists the linked components

Explore Data Mapping

DPIA AssessmentsDPIA Assessments

Holds the impact and transfer assessments for the same biometric data, each listing the linked capture components

Explore DPIA Assessments

Audit TrailAudit Trail

Keeps every change to those records

Explore Audit Trail

Compliance Checklist

Organizations preparing for QCVN 16 and QCVN 17 should confirm:

You have a record of every voice and iris capture component your organisation uses, makes, imports or supplies.

For each one, a person has recorded whether it serves the Identity Database and why, or marked it not determined.

Each capture device used for the Identity Database has its security-check reference and documentation recorded.

Each voice capture software version has its conformity check recorded and, where its producer or supplier falls within the regulation's subjects, its declaration of conformity and registration reference — or a recorded reason why none is held.

Every voice-data transfer has a complete chain-of-custody record, with the other organisation's reference where it is on the other side.

Every deletion of voice data is recorded with its ground, scope and method, and confirmed by a second person.

Each inspection, guidance or monitoring act your unit carried out or received is recorded with its follow-up.

Each component is linked to the processing activity and impact assessment that cover the same data.

A readiness review is dated before 15 April 2027.

Background Image

See ComplianceOne in Action

See how ComplianceOne keeps each capture component's scope decision and evidence on record.

Demo Image
Ronni K. Gothard Christiansen

Ronni K. Gothard Christiansen - Technical Privacy Engineer & CEO

Technical Compliance Expert, 32+ Years Open Source Advocate, X-BoD Open Source Matters Inc.

Or contact via

ronni@aesirx.io+84 909 500 760

Frequently Asked Questions

The text does not settle that. Its subject matter is voice data and capture equipment serving the national Identity Database. Whether its subjects go further, to every organisation that collects, manages or uses voice biometrics, is an open reading. Your team records its own determination, with its basis.

The text does not say. It uses "serve the Identity Database" without defining it, so whether verifying a person against the database serves it is an open reading. Your team records its own determination for each flow, with its basis. QCVN 16 and QCVN 17 concern voice and iris only. Separately, whether they reach collecting or using these biometrics outside the Identity Database at all is the open reading above.

Your organisation, with its counsel. ComplianceOne records the determination and its basis, and never makes one.

No. QCVN 17 states no false-acceptance, false-rejection or recognition rate. It mentions 1:1 and 1:N matching only for stored image sizes. Section 2.5.2 gives 2–6 kB on a chip, suited to 1:1 matching, and section 2.5.3 gives 20–50 kB in the system, suited to all matching. Table 3, the only place 1:N appears, is a bar chart that prints no figure for any bar. None of this is an accuracy figure.

No. QCVN 16 states no minimum sample duration and no number of languages. Its only dialect provision is a metadata field naming the dialect region: North, Central or South.

The text gives none: there is no transitional provision, and both Circulars take effect on 15 April 2027. It does not say how its before-use requirements apply to a component already in use on that day; your organisation determines that with its counsel.

No. Meeting the QCVN does not establish a lawful basis, consent, a completed impact assessment or a lawful transfer abroad. Those are questions under the law that governs the processing (the Personal Data Protection Law 91/2025/QH15 and its decrees and, for the Identity Database, the Identity Law), answered in your processing records.

No. Both regulations require capture devices to be security-checked by the competent authority, which neither text names, and neither states a procedure or timing. Under QCVN 16, capture software is checked for conformity before official use with a standard test data set a competent authority issues. A producer or supplier of that software that falls within the regulation's subjects carries out conformity assessment, declares conformity and registers the declaration under the law in force before the software is put into use. Whether a software producer falls within those subjects is part of the open reading, because section 1.2 names makers of capture equipment, not of software. ComplianceOne records the references your team enters; it checks nothing and files nothing.

No. A deletion record holds what the person who carried out the deletion entered and what a second person recorded from their own check. A supervision record holds an act your organisation carried out or received. ComplianceOne deletes no biometric data and carries out none of those acts.

No. ComplianceOne has no connection to the Identity Database or to any other State system. It records evidence about your components and your transfers.

QCVN 16 and QCVN 17 state no retention period. QCVN 16 leaves data retention to the law in force (section 3.4), keeps provenance records for the period the law sets (section 3.5.7) and audit logs for the period the competent authority sets (section 3.5.4). QCVN 17 has no retention provision; section 3.1.3 requires iris data to be encrypted and stored in accordance with the Identity Law, without saying whether that reference governs how long it is kept. Record which instrument you rely on for each period.

The Circulars state no sanction of their own.

Next Steps

Icon Image

Start a Compliance Pilot

Record one capture component from scope decision to security check, evidence and processing-record link, and export it as an inspection evidence pack.

Icon Image

Discuss Your Compliance Needs

Review which of your voice and iris components serve the Identity Database, and who holds the evidence.