Privacy and encryption

Messages and attachments

Message and attachment content is encrypted on the client using libsodium. Conversation keys are delivered to authorized devices in encrypted envelopes. The server stores ciphertext without receiving ordinary user keys in plaintext.

This does not hide all metadata. The service processes accounts, memberships, identifiers, event times and other operational information.

Protect your device keys

Google sign-in verifies the account but does not replace encryption keys. Do not delete application data or secure key storage to fix a playback error. Older messages and attachments may need an earlier key version or an exchange with another authorized device.

Decryption cannot be guaranteed without the correct available key. Changing a password or reinstalling the app does not, by itself, recover lost keys.

Calls, bots and AI

Calls use WebRTC/LiveKit with transport encryption. We do not claim end-to-end content encryption for calls. Local recordings live on the device; encrypted meeting notes have separate protection.

An integration sends bot text to the API over HTTPS, so that outgoing text is known to the gateway. The server encrypts the new bot message with a fresh one-off key for recipient devices. The bot does not receive the conversation key or read human messages. External AI data is processed by the selected provider.

Account, billing and support

The service owner can view account records, workspaces, order status and technical AI usage accounting. This does not reveal encrypted conversation content. Support and registration/confirmed-payment notifications may be delivered to a private Telegram group. Business notifications contain a display name and internal identifier; payment notifications also contain the order reference and amount, never conversation content, keys or AI prompts.