Private messaging
One-to-one text messaging with end-to-end encryption, delivery status, offline queues and asynchronous delivery across unstable networks.
Messaging without the social graph.
Tanelo is a planned privacy-first messenger built around end-to-end encrypted communication, pseudonymous identity, resilient delivery — designed to reduce dependence on advertising, tracking and centralized content access.
Pseudonymous identity
No phone number required
No phone number required
Client-side history
No central chat archive
No central chat archive
Alextanelo://alex-74
Encrypted
Message Alex…
A messenger built around privacy boundaries, not data collection.
Tanelo combines familiar messaging features with an architecture designed to minimize metadata, avoid centralized conversation storage and keep message content inaccessible to the service infrastructure.
Encrypted audio
Planned one-to-one audio calls with end-to-end encrypted media and adaptive quality, without relying on central media servers.
Groups & channels
Private groups by invitation, public channels without exposing subscriber lists, and one-way broadcast channels.
Pseudonymous access
Identity without phone numbers, with contacts added through invitations or links rather than uploaded address books.
Client-side history
Conversation history is intended to live on the client side, with configurable deletion and message lifetime controls.
Privacy-first
Tanelo is built with privacy at its core, without advertising or unnecessary behavioral tracking.
Centralized service control. Decentralized transport.
The core idea is a hybrid model: the service layer remains manageable, while user communications are designed to travel over a resilient transport layer that does not expose message content or social relationships to a central service.
Client applications
Web • iOS • Android • CLI
Encrypted identity & messaging layer
Pseudonymous access • end-to-end encryption • local history
Resilient transport layer
Adaptive routing • reduced fixed entry points • censorship resistance goals
Service management
Account access • devices • service evolution
“The infrastructure should support Tanelo — not become a place where private communication can be read, profiled or centrally archived.”
01Metadata minimization. Separate identity, transport and billing concerns to reduce correlation.
02Explicit trust boundaries. Treat client devices and execution environments as potentially untrusted.
03Resilience. Design transport behavior to adapt to degraded or restricted network conditions.
04Sustainability. Use architectural and economic controls against abuse rather than centralized content surveillance.
Privacy should be a system property.
Tanelo’s planned design treats privacy as an architectural constraint rather than a setting users have to discover later.
No central message archive
The service is not planned to keep a central store of message or call history.
No address-book graph
Contact discovery is planned around invitations and links rather than uploading a user’s entire address book.
No ads or tracking
The planned commercial model is focused on privacy and without advertising.
Web
iOS
Android
CLI