| Email requirement | TelegramUnknown: not established for the version and configuration in question. | SignalUnknown: not established for the version and configuration in question. |
|---|
| Username / discovery | TelegramUnknown: not established for the version and configuration in question. | SignalOptional; no public username directory. [1] [2] |
|---|
| Number visible to contact | TelegramUnknown: not established for the version and configuration in question. | SignalCan be hidden: number visibility AND discovery set to Nobody; a number already known to the contact is not forgotten. [1] [2] |
|---|
| Global user ID | TelegramUnknown: not established for the version and configuration in question. | SignalService account remains linked to the phone number. [1] [2] |
|---|
| Forward secrecy | TelegramUnknown: not established for the version and configuration in question. | SignalDocumented protocol property; depends on clients and linked devices. [1] [2] |
|---|
| Post-compromise security | TelegramUnknown: not established for the version and configuration in question. | SignalCryptographic recovery after temporary compromise; not while spyware remains in control. [1] [2] |
|---|
| Key verification | TelegramUnknown: not established for the version and configuration in question. | SignalOut-of-band Safety Number; AKV does not certify identity and requires the other account’s number. [1] [2] |
|---|
| Relay / TURN | TelegramUnknown: not established for the version and configuration in question. | SignalEnable Always Relay Calls when peer IP exposure matters; the relay sees the IP. [1] [2] |
|---|
| What the provider learns | TelegramProvider can process cloud messages and metadata. [1] [2] | SignalRegistration number and limited account data; not normal E2EE content by design. [1] [2] |
|---|
| What the contact learns | TelegramThe contact receives messages and the profile you share, and can keep a copy. [1] [2] | SignalThe contact receives messages and the profile you share, and can keep a copy. [1] [2] |
|---|
| What the network / ISP learns | TelegramThe network sees destinations, timing and volume; Tor or a relay changes the observer. [1] [2] | SignalThe network sees destinations, timing and volume; Tor or a relay changes the observer. [1] [2] |
|---|
| Push notifications | TelegramUnknown: not established for the version and configuration in question. | SignalExact APNs payload not captured; manage local notification previews. [1] [2] |
|---|
| Apple / Google exposure | TelegramStore, installation and push can create metadata; exact profile linkage depends on the OS and was not tested here. [1] [2] | SignalStore, installation and push can create metadata; exact profile linkage depends on the OS and was not tested here. [1] [2] |
|---|
| Groups | TelegramCloud groups are not E2EE. [1] [2] | SignalUnknown: not established for the version and configuration in question. |
|---|
| Calls | TelegramDocumented calls; their network path must be distinguished from messaging. [1] [2] | SignalDocumented calls; their network path must be distinguished from messaging. [1] [2] |
|---|
| Backups | TelegramUnknown: not established for the version and configuration in question. | SignalUnknown: not established for the version and configuration in question. |
|---|
| Source code and binaries | TelegramRepositories and component-specific scopes recorded in Phase 2; no current binary rebuilt bit-for-bit here. [1] [2] | SignalRepositories and component-specific scopes recorded in Phase 2; no current binary rebuilt bit-for-bit here. [1] [2] |
|---|
| Audits | TelegramUnknown: not established for the version and configuration in question. | SignalProtocols and AKV examined under distinct scopes; not the whole infrastructure or every binary. [1] [2] [3] |
|---|
| Public law-enforcement evidence | TelegramCivil production under seal in India; fields and scope partly contradictory. [1] | SignalPublished 2026 provider response: creation and last-connection dates for six accounts; not messages. [1] [2] [3] |
|---|
| iOS | TelegramYes, client listed in the study. [1] [2] | SignalYes, client listed in the study. [1] [2] |
|---|
| Android | TelegramYes, client listed in the study. [1] | SignalYes, client listed in the study. [1] |
|---|
| Windows | TelegramYes, client listed in the study. [1] [2] | SignalYes, client listed in the study. [1] [2] |
|---|
| macOS | TelegramYes, client listed in the study. [1] [2] | SignalYes, client listed in the study. [1] [2] |
|---|
| Linux | TelegramYes, client listed in the study. [1] [2] | SignalYes, client listed in the study. [1] [2] |
|---|
| Avoid if… | TelegramYou want to hide cloud text from the provider. [1] | SignalYou refuse to give a number to the service. [1] [2] [3] [4] |
|---|
| Recommended configuration | TelegramControl devices, identities, notifications and files; verify client, version and calling path. [1] [2] | SignalVisibility and discovery: Nobody; fresh username, neutral profile, verified Safety Number, relayed calls when needed. [1] [2] [3] [4] |
|---|
| Remaining unknowns | TelegramCurrent network behaviour, distributed binaries and forensic evidence remain incomplete; check version, OS and configuration. [1] [2] | SignalCurrent network behaviour, distributed binaries and forensic evidence remain incomplete; check version, OS and configuration. [1] [2] |
|---|
| Ease of use | TelegramUnknown: not established for the version and configuration in question. | SignalVery practical for iPhone + PC; the primary phone remains necessary. [1] [2] [3] [4] |
|---|
| Network anonymity | TelegramNo general resistance to a global passive observer is demonstrated. [1] [2] | SignalNo general resistance to a global passive observer is demonstrated. [1] [2] |
|---|