Zalo Privacy vs Zero Data Protocol
Zalo is more than a messaging application in Vietnam. It connects private communication, Official Accounts, Mini Apps, businesses and public-service channels. Zero Data Protocol adds a different architectural question: when one account connects many relationships, how much personal data needs to follow the user between them?
Verified where required.
Identified where necessary.
Unlinked where unnecessary.
Zalo protects communication in important ways. ZDP asks what should exist beyond the communication.
What Zalo already addresses
Zalo has published a technical end-to-end encryption protocol for supported conversations. Its documentation describes 1-to-1 and group-chat encryption, device-held keys, multi-device session management and encrypted file sharing. [2]
Zalo Mini Apps also use explicit permission mechanisms for sensitive functions such as phone-number or location access, and Zalo recommends requesting permissions in the context where they are actually needed. [5]
What Zero Data Protocol adds
Encryption answers: who can read protected content?
Zero Data Protocol asks an additional question: which identity, relationship data, history, permissions and secondary-use data need to exist at all?
The two questions are complementary rather than interchangeable.
A messaging account that has become part of everyday digital infrastructure
The architectural interest of Zalo comes from the number of different relationships that can coexist around the same persistent account.
Communication
Private conversations, groups, media, files and calls.
Businesses
Official Accounts, customer communication, notifications and CRM-style relationships.
Mini Apps
Function-specific services operating inside the wider Zalo environment.
Public Services
Government and public-service organizations also use Zalo Official Accounts and Mini Apps as communication and service channels. [4]
The ZDP question is not “Should Zalo know nothing?”
It is: “What must this specific function or relationship know—and what does not need to cross into the next one?”
Official Accounts and Mini Apps extend Zalo beyond private messaging
Zalo reported that by September 2025 approximately 17,000 verified Official Accounts belonging to government agencies existed on the platform, together with approximately 220 Mini Apps across provinces and municipalities. Zalo describes use cases including administrative procedures, public communication, education, healthcare and citizen feedback. [4]
This does not make Zalo a national identity system. It demonstrates something more relevant to this analysis: a communication account can become a gateway into many distinct digital relationships.
Content protection and data existence are different layers
End-to-end encryption
Zalo's published technical whitepaper describes end-to-end encryption for supported 1-to-1 and group conversations. It states that encryption keys are stored on user devices rather than Zalo servers and describes technologies including Curve25519, X3DH, Double Ratchet and Sesame-style multi-device session management. [2]
The document also describes encrypted handling for message types including text, voice messages, images, video and files. [2]
Important scope limitation
A published encryption protocol should not automatically be interpreted as proof that every Zalo function, call type, backup, Mini App or business interaction is universally end-to-end encrypted in the same way.
ZDP therefore analyses each function separately rather than treating the platform as one homogeneous privacy architecture.
Encryption protects content.
Retention determines how long data continues to exist.
Backup creates a second architectural question
Zalo's current help documentation states that text-message backups are stored on Zalo servers. It also states that messages from end-to-end encrypted conversations are included in backup by default, while users can disable backup for those conversations. [3]
The same documentation explains that photos can be backed up through the user's Google Drive, while voice messages, files and videos are not included in the standard Zalo backup described on that page. [3]
| Layer | Documented Function | ZDP Question |
|---|---|---|
| Live Conversation | Supported conversations can use Zalo's published E2EE architecture. | What operational data still needs to exist around protected content? |
| Text Backup | Text messages may be backed up to Zalo servers. | How long is recovery genuinely required? |
| E2EE Chat Backup | Included by default in backup according to Zalo Help; user can disable it. | Could retention be reduced for users who prioritize ephemerality? |
| Photo Backup | Can use the user's Google Drive. | Which party needs which copy, and for how long? |
This analysis does not infer whether Zalo can decrypt any particular backup unless the cited documentation explicitly establishes that fact.
Zalo begins from a persistent phone-linked account
Zalo's account-registration guidance requires a phone number to create and activate an account, and its account documentation states that each account is linked to one phone number at a time. [6]
This identity model also exists inside a specific Vietnamese regulatory environment. Government Decree 147/2024/NĐ-CP, effective from 25 December 2024, introduced authentication requirements for active social-network accounts, normally through a Vietnamese mobile number, with personal identification used in specified situations. [7]
Zero Data Protocol does not propose removing identity where identity is legally or functionally necessary.
It asks whether that verified identity must automatically propagate into every subsequent interaction.
Identity can be necessary without becoming universal
Verified where required
Security, regulation or a specific service may legitimately require a verified account.
Identified where necessary
A payment, delivery, medical appointment or administrative procedure may require specific personal information.
Unlinked where unnecessary
Another Mini App, merchant, information service or content experience may not require access to the same identity or historical context.
Human Freedom Choice means preserving meaningful user choice whenever persistent identity or personal-data dependency is not functionally necessary.
Zalo Mini Apps already demonstrate an important design principle
Zalo's developer documentation divides Mini App permissions into categories including device permissions and user-information permissions. Access to data such as the user's phone number requires user approval, and location access is also permission-controlled. [5]
Zalo explicitly recommends requesting permissions in context and, when a Mini App first opens, requesting only permissions genuinely required for its core functions. [5]
This is an important point of convergence. ZDP does not claim to invent function-specific permission boundaries. It asks whether the same logic can be extended further: from minimum permissions toward minimum underlying data existence, retention and secondary use.
An Official Account can know more than a chat needs
Zalo's Official Account documentation allows businesses to manage customer information such as name, phone number, address, date of birth and gender when the customer agrees to share it. It also provides segmentation, custom fields and tools for recognizing existing customers. [8]
These capabilities can be useful for legitimate customer relationships. ZDP therefore does not ask for a single universal “zero data” configuration.
What must this particular relationship know?
A restaurant, retailer, hospital, public authority and delivery service do not necessarily require the same identity attributes, historical context or retention period.
Communication, service delivery and advertising are different purposes
Zalo's privacy information lists service provision, personalized content, promotions and advertising, research and development, security and fraud prevention among purposes for account information. It also describes circumstances in which information may be shared within the VNG ecosystem or with third parties, including consent-based scenarios. [9]
Communication
Data required to deliver a conversation.
Transaction
Data required to complete a specific service or commercial action.
Public Service
Data required for a legitimate administrative or public-service function.
Advertising
Data used to personalize, segment or promote content and offers.
Can information remain bound to the relationship and purpose that created it?
Three architectural questions after security and consent
Do not request what the function does not need.
A service should not automatically inherit every available identity field, contact attribute or device permission simply because the wider platform possesses it.
Do not preserve data after its legitimate purpose has ended where avoidable.
Backup, recovery and operational continuity can be legitimate. ZDP asks how much persistence is genuinely necessary for each function.
Do not automatically transform one relationship into another purpose.
Data supplied for communication, a transaction or a public service should remain purpose-bound wherever architecture and law allow.
One Zalo account. Three completely different relationships.
Imagine one user who uses Zalo to:
- message a family member;
- follow a local government Official Account;
- open a restaurant Mini App.
The first relationship may require communication identifiers. The second may sometimes require verified information for a specific administrative action. The third may only need a booking time and a way to confirm the reservation.
The existence of one verified Zalo account does not, from a Least Data perspective, automatically mean all three relationships need the same personal-data profile.
ZDP objective: preserve the usefulness of the ecosystem while reducing unnecessary cross-context identity and data dependency.
Why Zalo deserves its own ZDP locomotive
| Platform | Primary ZDP Territory | Core Architectural Question |
|---|---|---|
| Protect the Message | What still needs to exist around an encrypted message? | |
| Telegram | Question Persistence | What actually needs to persist? |
| Messenger | Recoverable Encrypted History | How much encrypted history needs to remain recoverable? |
| LINE | Digital-Life Ecosystem | What data does each function genuinely need? |
| Zalo | Messaging Identity → Local Service Gateway | What must each relationship know? |
The Zalo → ZDP corridor
Protect what must exist.
Remove what does not need to exist.
Least Data is not only a security question
Reducing unnecessary identity dependency also preserves the user's ability to move between different digital relationships without automatically carrying the same persistent profile everywhere.
This is the human layer we call Human Freedom Choice.
Frequently asked questions
Is Zalo end-to-end encrypted?
Zalo has published a technical E2EE protocol covering supported 1-to-1 and group conversations and multiple message types. The existence of that protocol should not be generalized into a claim that every Zalo function, call, backup, Mini App or business interaction uses identical E2EE protection.
Does Zero Data Protocol claim that Zalo uses ZDP?
No. Zero Data Protocol is an independent architectural framework. This page does not imply partnership, endorsement, certification or adoption by Zalo or VNG.
Why is the phone number important in the Zalo analysis?
Zalo account creation uses a phone number, while Vietnam also operates a regulatory framework requiring authentication of active social-network accounts. ZDP therefore does not treat identity as something that can simply be removed. It asks where identity is necessary and where it does not need to propagate further.
What is the difference between encryption and Zero Retention?
Encryption is primarily about protecting information from unauthorized reading. Retention is about how long information continues to exist. Data can be strongly encrypted and still remain stored for a long period.
Why are Zalo Mini Apps relevant to ZDP?
Zalo Mini Apps use function-specific permission mechanisms. This provides a useful architectural starting point for asking whether each Mini App also needs the same identity, history, retention and secondary-use context as the wider account.
What makes Zalo different from the LINE ZDP page?
LINE is analysed primarily as a broad digital-life ecosystem. Zalo's distinctive ZDP territory is the transition from a phone-linked messaging identity into business, Mini App and public-service relationships inside the Vietnamese digital environment.
Zero Collection
Ask whether the data needs to be collected in the first place.
Explore Zero Collection →Zero Exploitation
Ask whether data remains bound to the purpose that created it.
Explore Zero Exploitation →Sources used for this independent analysis
Visit VNG source ↗
Visit Zalo technical source ↗
Visit Zalo Help ↗
Visit Zalo source ↗
Visit Zalo Mini App documentation ↗
Visit Zalo Help ↗
Visit Government source ↗
Visit Zalo OA documentation ↗
Visit Zalo Privacy Information ↗
Sources and volatile platform information were reviewed for this page in August 2026. Platform features, policies, technical deployments and regulation can change.
Independent analysis — no affiliation implied
Zero Data Protocol is an independent architectural framework. Zalo, VNG and all related names, products and trademarks belong to their respective owners.
This page is educational and analytical. It does not state or imply that Zalo or VNG has adopted, implemented, approved, certified or endorsed Zero Data Protocol.
Zero Data Protocol is not a law, certification, encryption technology, messaging platform or replacement for applicable privacy and data-protection regulation.
The next privacy question is not only “How is the data protected?”
It is also: How much personal data needs to exist at all?