Invite, then decide
Invitations arrive privately with the context needed to accept or decline. Declining does not announce a reason to the group.
Private by construction
Message one person, bring a group together, or open a channel for just the people who need it. Kintrel encrypts the conversation on participant devices before the relay carries it.
Groups with real boundaries
Kintrel groups grow by invitation. Inside them, a channel is a restricted subgroup with its own member list and encryption—not a label on a conversation everyone can read.
A channel is not listed to parent-group members outside its roster.
Invitations arrive privately with the context needed to accept or decline. Declining does not announce a reason to the group.
Sender-key encryption protects group messages, and membership removal triggers key rotation so removed members do not receive future content.
Keep the main conversation close, switch into focused channels, and address the right person without exposing mention targets to the relay.
Group and channel support follows the client release and platform capabilities shown on the downloads page.
What the relay knows
Kintrel’s store-and-forward service routes an opaque envelope to the right device. The keys that open it stay with the participants.
Relay can process
Relay never receives
Strong foundations
A client-to-server implementation of a Signal-style design, built around the Thureos cryptographic core.
X3DH and PQXDH establish a session using public prekeys, including a post-quantum component.
The Double Ratchet protects one-to-one sessions, while sender-key chains protect groups. Encryption and decryption happen on client devices.
The relay stores and forwards opaque ciphertext until a recipient device acknowledges it.
Privacy after decryption
Encryption protects content while it travels. Kintrel also makes the moments after decryption explicit, when your screen or another app can become the boundary.
“Confirm before a file leaves Kintrel” is on by default. Opening, sharing, saving, or playing a decrypted file in another app asks first and explains what Kintrel can no longer control.
Turning warnings off does not weaken separate open/share restrictions for protected and disappearing messages.Desktop can cover Kintrel when its window becomes inactive. Mobile clients obscure app-switcher previews, and supported systems request screen-capture exclusion.
Sensitive messages relock on blur or background even when the optional desktop curtain is off.Require fresh device-owner authentication before revealing sensitive content, or set an absolute expiration that follows the message across supported devices.
These controls reduce exposure; they cannot stop another camera or a compromised recipient device.Native clients, shared design
Move between supported native phone and desktop clients without moving the cryptographic boundary to the server. Each linked device participates as its own secure endpoint.
Choose your platformHow Kintrel is made
Kintrel’s client experience is built with Kotlin®, Kotlin Multiplatform, and Compose Multiplatform.
Technology marks identify tools used by Kintrel; no affiliation or endorsement is implied.
Ready when you are