SecureChat encrypts message content on your device before transmission. The current delivery service cannot decrypt message content, but it necessarily processes limited connection and routing metadata to deliver messages.
Message content: End-to-end encrypted. The service receives only the encrypted payload.
Service metadata: The central signaling relay processes network address, connection timing, sender and recipient sx_ identifiers, delivery state and activation/entitlement requests. Operational logs may contain these routing identifiers and timestamps.
Local data: Contacts, keys and message history are stored on the device in encrypted storage. Optional diagnostics must be described in the app before collection.
All messages are encrypted end-to-end on your device using XChaCha20-Poly1305. The current central relay forwards an opaque encrypted payload only when the recipient is online; this handler does not provide an offline message queue. Routing metadata is separate from encrypted content.
IFR holder discounts are not active in the current sales flow. Any future browser verification will be disclosed separately and will not run inside the Android app.
Kaspa identity anchoring is a roadmap feature and is not performed by the current release.
github.com/NeaBouli/securechat/issues
Chameleon and other StealthX products have separate data flows and policies. This policy describes SecureChat only.
© 2026 Vendetta Labs — Greece · Source-Available