How Lem handles your data — plain English, no legalese.
When you use Lem you explicitly connect your own Telegram and/or WhatsApp account and choose specific groups or chats for Lem to monitor. Only messages from those selected sources pass through our pipeline.
For each monitored message we process:
To read your groups from your own account (which is the core of Lem's no-bot privilege), we store your Telegram session string or WhatsApp pairing data. These credentials are encrypted at rest with AES-256-GCM before being written to the database.
You can disconnect any account at any time from Settings → Sources. Disconnecting immediately revokes the session and deletes it from our storage.
We use OpenAI's GPT-4o-mini model to extract structured fields from your messages according to the schema you define. Each message text is sent to OpenAI's API via an encrypted connection. OpenAI's data retention and API policy apply to that transit (openai.com/privacy).
We do not use any third-party analytics in the cabinet that receive your message content.
All data in transit is encrypted with TLS 1.2+. Database backups are encrypted and retained for 7 days.
You can at any time:
Lem is in public beta. While we apply production-grade security practices, by using Lem during beta you accept:
The cabinet (app.lem.in.ua) uses localStorage (not cookies) to persist your login JWT, selected language, and onboarding flag. The landing (lem.in.ua) uses no cookies or analytics.
Questions, data exports, or deletion requests: @ivvi_1 on Telegram.