Signal Privacy vs Zero Data Protocol
Signal demonstrates that privacy can go beyond encrypting message content: an architecture can also minimize what the service provider itself needs to know.
Least Data adds: does the provider need to know the data at all?
Signal already implements extensive privacy by architecture.
Signal messages and calls are end-to-end encrypted by default. Signal states that it cannot decrypt or otherwise access their content, while message history normally remains on users' own devices.
Signal also uses privacy-preserving designs for supporting information such as profiles, groups, contact discovery and message delivery.
Zero Data Protocol does not position itself as a replacement for this architecture. It asks a broader question: how far can minimum provider knowledge extend across identity, collection, retention and secondary use?
Data can exist without the service provider needing to understand it.
Operational Knowledge
A functioning messaging service still needs certain technical information to register accounts, establish calls, route messages, prevent abuse and deliver communications.
Provider Knowledge Can Be Reduced
Signal's architecture is designed so that substantial categories of personal information do not need to be accessible to the service provider.
Signal begins with protection of communication content.
Signal states that messages and calls are always end-to-end encrypted. The service cannot decrypt or otherwise access their content.
Message history is normally stored on users' devices. When a destination device is temporarily offline, the Signal service queues an end-to-end encrypted message for delivery.
Messages
Communication content remains accessible to the intended endpoints, not to Signal as the intermediary.
Calls
Signal calls use end-to-end encryption so the service does not have access to the spoken communication content.
Local History
The normal message history architecture places the user's history on their own devices rather than making a plaintext server archive central to the service.
The more interesting question begins outside the message itself.
Encrypting message content is one privacy layer. Signal has also developed systems designed to reduce its own knowledge of supporting information surrounding communication.
| Category | Signal architectural direction | ZDP question |
|---|---|---|
| Message content | End-to-end encrypted | Can content remain inaccessible to the service while still being delivered? |
| Profiles | Profile information is end-to-end encrypted | Does the service provider need plaintext access to profile information? |
| Groups | Signal uses private-group technology designed to hide group information from the service | Does the provider need to know the user's social structure? |
| Contacts | Privacy-preserving contact discovery | Can discovery work without building a plaintext social graph? |
| Sender information | Sealed Sender is designed to reduce information exposed during delivery | Which routing information truly needs to be visible to the intermediary? |
| Identity | Phone number still required for registration; usernames reduce disclosure to other users | Can persistent identity dependency be reduced further? |
A social service does not automatically need a plaintext social graph.
Messaging applications need a way for users to discover which people they can communicate with.
Signal has developed privacy-preserving contact-discovery technology intended to let a user discover Signal contacts without giving the service a conventional plaintext record of the user's relationships.
Can a useful social function operate without collecting the complete underlying social graph in an intelligible form?
Even the envelope around a message can reveal information.
Traditional message delivery needs enough information to determine where a message should go and often who is sending it.
Signal's Sealed Sender technology was designed to reduce the information exposed to the service during message delivery by protecting additional sender information around the already encrypted message.
The phone number is now Signal's most visible remaining identity dependency.
A phone number is still required to register a Signal account. Signal explains that this supports contact discovery and helps limit spam.
However, Signal's phone-number privacy controls and optional usernames allow users to initiate new conversations without necessarily giving the other person their phone number.
Platform Identity
Signal still knows the phone number registered to the account because registration currently depends on it.
Human-to-Human Disclosure
Usernames and privacy controls can reduce whether that phone number needs to be disclosed to or discoverable by another person.
Can discovery, authentication and anti-abuse protections continue to evolve while reducing dependency on persistent personal identifiers?
Usernames separate “being reachable” from “sharing my phone number.”
Signal usernames are optional and exist primarily as a way to initiate contact. They are not public social-media handles and Signal does not provide a searchable public directory of usernames.
Users can also control whether others can find them using their phone number. This creates a useful distinction between identity required by the platform and identity required by another human.
Identity does not always need to disappear to become less intrusive.
Human Freedom Choice asks whether persistent identity must be exposed, discoverable or reused when the requested function does not require it.
Signal already demonstrates one version of this idea: a phone number can remain part of account registration while users gain choices about whether that number is visible or usable for discovery.
The next architectural frontier is not necessarily “no identity”. It is minimum necessary identity.
Data minimization changes what can later be produced.
On March 6, 2026, Signal published information about a U.S. grand jury subpoena concerning account information associated with 37 phone numbers.
Numbers Requested
The request sought account creation and last-connection information.
No Responsive Information
Signal stated that for 24 accounts it did not possess responsive information for the period covered by the request.
Responsive Information
Responsive information was provided for six accounts. Seven additional requested accounts did not exist.
Protecting data limits unauthorized access. Not possessing certain data can also limit what can later be disclosed.
Minimal provider knowledge is not the same as zero technical data.
Signal's own privacy policy documents additional technical information stored on its servers, including randomly generated authentication tokens, keys, push tokens and other material necessary to establish calls and transmit messages.
Signal states that it limits this additional technical information to the minimum required to operate the service.
For every remaining technical category, is this the minimum information required to perform the legitimate function?
Signal also demonstrates purpose-bound server retention.
Signal temporarily queues end-to-end encrypted messages when a destination device is offline. Once the receiving device confirms delivery, the message can be removed from the server mailbox.
Signal's technical documentation also describes automatic deletion of queued messages and encrypted attachments after defined limits when devices remain offline.
Once the delivery function is complete, what remaining server-side data still has a legitimate reason to persist?
Signal Secure Backups add an important nuance to Zero Retention.
Signal now provides optional Secure Backups. The archive is end-to-end encrypted and protected by a cryptographically generated 64-character recovery key that Signal says is never shared with its service.
Without that key, Signal states that it cannot read, decrypt or restore the contents of the backup archive.
Retention May Be Desired
A user may legitimately want to preserve message history against device loss or replacement.
Provider Knowledge Need Not Follow
Persistence can be designed so that storage exists without giving the provider the ability to understand its contents.
Data Exists ≠ Provider Must Know It
Signal helps reveal a useful architectural distinction.
Must the data exist?
If the function can work without collecting a category of personal data, avoid collecting it.
Must the provider know it?
If data must exist, examine whether encryption or privacy-preserving computation can prevent the intermediary from understanding it.
Must it remain?
Once the legitimate function ends, determine whether the information should disappear rather than become permanent history.
Signal provides a strong bridge toward Least Data.
Do not acquire what the function does not require.
Signal's private-contact and metadata-resistance work demonstrates that some useful functions can operate without giving the provider a conventional plaintext representation of the underlying personal information.
Do not retain what has completed its purpose.
Delivery queues and temporary encrypted storage can be tied to the operational function rather than indefinite history.
Do not create unnecessary secondary use.
Signal states that it does not sell, rent or monetize personal data or content, illustrating a service model that is not dependent on personal-data advertising.
The bridge from Signal to Zero Data Protocol
1 — Provider Knowledge
How much personal information does a messaging provider actually need to know in order to deliver a secure and reliable communication service?
2 — Persistent Identity
Can discovery, authentication and abuse prevention continue to evolve while reducing dependency on persistent personal identifiers?
From Signal to Least Data
WhatsApp, Telegram and Signal teach three different privacy lessons.
Protect the message.
E2EE protects personal communication content. ZDP then examines the surrounding identity, operational data and retention.
WhatsApp Privacy vs ZDP →Telegram
Question the persistence.
Cloud Chats and Secret Chats demonstrate different compromises between synchronization, persistence and E2EE.
Telegram Privacy vs ZDP →Signal
Minimize provider knowledge.
Privacy-preserving architecture asks how little the intermediary needs to know while still delivering the service.
Signal Privacy vs Zero Data Protocol
Are Signal messages and calls end-to-end encrypted?
Yes. Signal states that messages and calls are always end-to-end encrypted and cannot be accessed by Signal as communication content.
Does Signal store my message history on its servers?
Signal states that message history is stored on users' devices. End-to-end encrypted messages can be temporarily queued on Signal servers when a receiving device is offline.
Does Signal know who I communicate with?
Signal has developed privacy-preserving technologies including Sealed Sender, private groups and private contact discovery specifically to reduce the communication and social-graph information accessible to the service. This should not be interpreted as a claim that no network-level technical information can ever exist.
Does Signal require a phone number?
Yes. A phone number is currently required to register a Signal account. Signal also provides phone-number privacy settings and optional usernames so people can initiate communication without necessarily sharing their number.
Are Signal usernames public handles?
No. Signal usernames are optional tools for initiating contact. Signal does not provide a searchable public username directory.
Can Signal read Secure Backups?
Signal states that Secure Backups are end-to-end encrypted and protected by a 64-character recovery key that is not shared with Signal. Without that key, Signal cannot read, decrypt or restore the archive.
Is Signal a Zero Data platform?
No such claim is made. Signal demonstrates architectural approaches that strongly reduce provider knowledge and unnecessary data exposure, but this independent analysis does not describe Signal as implementing Zero Data Protocol.
Does Signal use or endorse Zero Data Protocol?
No. This page does not claim affiliation, endorsement, partnership or adoption of Zero Data Protocol by Signal.
What does Zero Data Protocol add to Signal's privacy model?
ZDP generalizes the architectural question across the data lifecycle: what personal data needs to exist, what the provider needs to know, how long information should remain, and what secondary use can be avoided.
Continue from minimal provider knowledge to Least Data.
Primary Signal documentation
This independent architectural analysis is based primarily on official Signal documentation reviewed in August 2026. Features and technical implementations may evolve.
Questions about Signal Privacy, Least Data or Zero Data Protocol?
Explore how end-to-end encryption, metadata resistance, identity, minimum provider knowledge and Human Freedom Choice fit into a Least Data architecture.
Contact Zero Data Protocol